LogFAQs > #924578135

LurkerFAQs, Active DB, DB1, DB2, DB3, DB4, Database 5 ( 01.01.2019-12.31.2019 ), DB6, DB7, DB8, DB9, DB10, DB11, DB12, Clear
Topic List
Page List: 1
TopicPython is a horrible language
Yellow
07/12/19 4:35:06 AM
#8:


Grendel posted...
Well that's your own fault for not using a linter.


class Person:
easily_misspelled_thing = 89

def __init__(self, name, years):
self.years= years
self.name = name

name = 'Joe'
number = 8

#Swapped, no error
guy = Person(number, name)

#Mistake, no error
guy.easily_mispeled_thing = 5


Grendel posted...
That's really up to you. You can use type hints and enforce them with mypy.

I definitely will use that, thank you. That fixes the type mixup hole, but not the misspelling and creating new fields on accident. Intellisense from 2018 helps that, but not entirely.

I also don't care for the use of a C# 'var' for every defined object.

Grendel posted...
There are some legitimate gripes with Python, but your list is garbage.

Oh yeah?

Let me just google the first list I find
http://net-informations.com/python/iq/disadvantages.htm

Speed, yeah, I said that
Deployability, yeah
Memory, yup, sort of goes along with being interpreted

Wasn't the whole point of interpreted languages to be easily shared? Seems like a bit of a Python flaw. I just don't understand the point of interpreted languages in general tbh. They all have their porting quirks regardless, whether you want to do it in the compiler or not.
---
... Copied to Clipboard!
Topic List
Page List: 1