3 ms·
I'm still astonished that large companies run large systems on Python. I don't doubt that they're making the right decision, but it's a testament to how powerfu
by wutbrodo 7y ago
I'm still astonished that large companies run large systems on Python. I don't doubt that they're making the right decision, but it's a testament to how powerful inertia in large engineering systems is,given how incredibly horrible Python is for writing maintainable, sustainable multi-developer code. The most unfortunate part is that every engineer on a Python system has to be much more talented and disciplined to keep a workable system than they have to for statically typed languages (esp memory-safe ones), and yet one of the main attractions of choosing Python is chosen is that any rando can be nominally productive in it, which is helpful for talent-starved small companies.
- soulnothing 7y agoThe early portion of my career was python. Coming from OCaml/Haskell. I couldn't really deal with J2EE. But I've seen a frustrating trend recently. Where companies on languages like C#/Java. With a massive code base are moving to Python. I often get recruiter calls to lead a new python team, transitioning away from (Java/C#/etc). The sole reason, is it takes to long to develop a feature in the legacy language. Which is resultant of outdated software and practices. I generally try and steer them towards CI/CD and newer lighter frame works. But someone way up heard python was the hot new thing. Now all critical back-end services must be in python. To add to this I pushed for type hinting. But type hinting will "slow down developers". Part of the problem to me, at least. Is the person dictating development frameworks, languages, etc. Isn't really a coder, and heard about thing X at some conference. I like python, but it's an infrastructure quick scripting language. Additionally a lot of the good python devs I know shifted over to tensor flow and machine learning.