4 ms·
They didn't mention anything about typing as reason for switching. They said "It's a really frustrating ecosystem to work in, all the deps, toolchains, build pr
by quacker 9y ago
They didn't mention anything about typing as reason for switching. They said "It's a really frustrating ecosystem to work in, all the deps, toolchains, build process is extremely fragile." They switched to python for the ecosystem and tooling.
- always_good 9y agoI don't understand the distinction. JavaScript tooling is notoriously complicated on the front-end, not the back-end. And I doubt they're saying that they switched to Python on the front-end.
- quacker 9y ago> I don't understand the distinction. The distinction was that cdnsteve was motivated to switch to Python due to issues with the toolchain and build system, not that JavaScript was weakly-typed. > JavaScript tooling is notoriously complicated on the front-end, not the back-end. And I doubt they're saying that they switched to Python on the front-end. You have a good point, though you still have to pull in dependencies and deal with NPM when running JS on the server-side (especially if the server is doing non-trivial stuff). Idk, maybe an approach with server-side rendering using Python did away with much of the JS usage which made things nicer.
- TheDongIsYou 9y agoI still don't see the point, you'll probably need to pull dependencies whether you use is or any other language. And as for build tools, people like to complain way too much, maybe they prefer just using bash scripts instead..
- quacker 9y agoMaybe python's dependency management (pypi/pip) is nicer than NPM? (I think it is, at least)
- mmirate 9y ago> fragile ... was the keyword, or at least that was how I read it.