4 ms·
Python has huge uptake outside of the ML domain. I can't see an AI winter affecting the many people using Numpy for non-ML purposes (i.e., scientists in academi
by cossatot 4y ago
Python has huge uptake outside of the ML domain. I can't see an AI winter affecting the many people using Numpy for non-ML purposes (i.e., scientists in academia, most of whom still deal with normal numerical and data analytical modeling, not ML) much less Django.
- TylerE 4y agoI'm...aware. I think a lot of us that aren't using NumPy or ML stuff are rather looking for a good excuse to get away from what the ecosystem has become. (Yeah, I'm still bitter about Py3...Python user since the 1.5.2 days)
- Karrot_Kream 4y agoPlenty of other options out there if you've fallen out of love with Python and don't need good numerical libraries. Give JS, Elixir, or Crystal a try if you want something more dynamic. Nim if you want something a bit off the beaten path. Go, Rust, Java, Kotlin, and Scala if you want something more static.
- TylerE 4y agoSadly it's what pays the bills atm.
- nl 4y agoBitterness isn't really a winning strategy. I thought the whole Python 3 thing was a huge problem. Lately I've been doing JS/Typescript dev and breaking changes like this happen continually and no one blinks.
- anony23 4y agoWhat is the python3 thing?
- nl 4y agoPython 3 had incompatible changes with Python 2. You had to update your code, and for some years it meant lots of projects stayed on Python 2.
- TylerE 4y agoThe problem was never your code, really, it was the dependencies. Wasn't that hard for quite a while to find situations where dependency A was Py3 compatible and B was not (and the incompatibility went both ways, especially in early 3.x releases, you could NOT have one codebase that worked with both). Sometimes A dropped Py2 support before B gained Py3. Pain pain pain. Then add the increasing level of insanity as the answer to "python packaging sucks" was repeatedly to add yet another layer.