8 ms·

It's sad to say, but I think I'm over Python. It's not fun or pretty anymore, with all of the versioning headaches, the nightmare pit of dependency management,

by Mizza 5y ago

It's sad to say, but I think I'm over Python. It's not fun or pretty anymore, with all of the versioning headaches, the nightmare pit of dependency management, different runtime versions shipping on different machines. It's like they keep adding all of these features I don't want so it seems more like a 'big boy' language, but without any benefits in runtime performance. What I really liked Python for was as a _productive_, high velocity language - when I just want to bang an idea or a prototype out. Now there are all these design considerations about what version to target, what language features to use.. blah. I just wanted 2.8+ with sane unicode, and that's it. Grumble grumble.

mynameisash 5y ago
I really loved learning Python maybe ~20 years ago. At the time, I had been super into Perl and was also learning a bit about PHP. Python was such a breath of fresh air. I use Python some in my day job, and it just can't get over how painful it is. Far too many production bugs that aren't caught by linting, far too slow processing for big data work. Despite my dislike, it certainly does excel at being a glue language, hence why all of our data scientists use it with numpy and various ML libraries.
1ark 5y ago
Switch to Nim and programming will be fun again.
- Mizza 5y ago
  I have been working in Elixir lately and enjoying it quite a lot! Keeping an eye on Nim as well..
  - 1ark 5y ago
    Elixir is pretty good too. Elixir, Phoenix and Ecto have the best docs I have ever seen.
lbhdc 5y ago
I've been feeling this lately. I have been working on large python code bases the last couple years, and its been a pretty awful from a maintenance perspective. For my next position I want to avoid it.
melling 5y ago
I’m just starting to like Python. Worked with it off and on for years but Perl was my goto scripting language. I prefer static typing and thought Python was too slow, which it sort of is. Also thought a decade a foot dragging to get everyone to 3.x was too much. Glad that’s over and i don’t have to worry about legacy code. Now, Python, with Pandas, NumPy, Matplotlib, etc, provide the best “get shit done” language. Throw in Jupyter Lab and i find myself extremely productive. might try type hints next.
deleted 5y ago
[deleted]
deleted 5y ago
[deleted]
carapace 5y ago
I'm with you. I used to be a huge Python fan boy and I used it professionally for many years. With the 2->3 transition and all the new baloney it seems to me that it's being "improved" to death. For backend web stuff Erlang/Elixer makes way more sense, for scientific stuff Julia makes more sense, for rapid application development (RAD) Nim makes more sense, and with Go and Rust and Zig and D and so on there are just better options out there for most tasks.
goodoldneon 5y ago
It's still really easy to bang out prototypes; you don't need to use all the bells and whistles. But since Python is also at the heart of huge companies, it needs to be able to work well for large, mature codebases, too. These PEPs exist because the community is clamoring for them. This blog post highlights some improvements that directly address friction I've faced

by Mizza 5y ago

mynameisash 5y ago

I really loved learning Python maybe ~20 years ago. At the time, I had been super into Perl and was also learning a bit about PHP. Python was such a breath of fresh air. I use Python some in my day job, and it just can't get over how painful it is. Far too many production bugs that aren't caught by linting, far too slow processing for big data work. Despite my dislike, it certainly does excel at being a glue language, hence why all of our data scientists use it with numpy and various ML libraries.

1ark 5y ago

Switch to Nim and programming will be fun again.

Mizza 5y ago
I have been working in Elixir lately and enjoying it quite a lot! Keeping an eye on Nim as well..
- 1ark 5y ago
  Elixir is pretty good too. Elixir, Phoenix and Ecto have the best docs I have ever seen.

lbhdc 5y ago

I've been feeling this lately. I have been working on large python code bases the last couple years, and its been a pretty awful from a maintenance perspective. For my next position I want to avoid it.

melling 5y ago

I’m just starting to like Python. Worked with it off and on for years but Perl was my goto scripting language. I prefer static typing and thought Python was too slow, which it sort of is. Also thought a decade a foot dragging to get everyone to 3.x was too much. Glad that’s over and i don’t have to worry about legacy code. Now, Python, with Pandas, NumPy, Matplotlib, etc, provide the best “get shit done” language. Throw in Jupyter Lab and i find myself extremely productive. might try type hints next.

deleted 5y ago

[deleted]

deleted 5y ago

[deleted]

carapace 5y ago

I'm with you. I used to be a huge Python fan boy and I used it professionally for many years. With the 2->3 transition and all the new baloney it seems to me that it's being "improved" to death. For backend web stuff Erlang/Elixer makes way more sense, for scientific stuff Julia makes more sense, for rapid application development (RAD) Nim makes more sense, and with Go and Rust and Zig and D and so on there are just better options out there for most tasks.

goodoldneon 5y ago

It's still really easy to bang out prototypes; you don't need to use all the bells and whistles. But since Python is also at the heart of huge companies, it needs to be able to work well for large, mature codebases, too. These PEPs exist because the community is clamoring for them. This blog post highlights some improvements that directly address friction I've faced