• 1 Post
  • 9 Comments
Joined 2 years ago
cake
Cake day: June 10th, 2023

help-circle
  • You need to get over the bloat of virtual environments. It’s the same as node_modules and it’s completely necessary if you want more than a single python project to live on your machine.

    I personally use poetry as my dependency manager and build tool. It’s not perfect but it’s a lot better than pipenv or just rawdogging pip like a maniac. uv is the new hotness, but I haven’t tried it so can’t vouch. People seem to like it though.

    JavaScript is also an interpreted language with tons of build tools. The reason to have one for python is mainly about packaging and code distribution, so same as JavaScript. If you want to distribute a program you probably don’t want to just point people to a GitHub repo, and if you want to publish a package on pypi it needs to be bundled correctly.

    For ecosystem there isn’t much I can do for you, it completely depends on what you’ll be working on. Baseline you want pydantic for parsing objects, assuming some APIs will be involved. You want black for code formatting, flake8 for linting, pytest for testing. If you’re gonna write your own APIs you can’t go wrong with fastapi, which works great with pydantic. For nice console stuff there’s click for building cli apps and rich and textual for console output and live console apps respectively.

    People are actively trying to replace flake8 and black with feature compatible stuff written in rust but again I haven’t tried those so can’t vouch.

    Coming from react you’re gonna need to pretty quickly switch gears to thinking more object oriented. You’re gonna be annoyed at how you can’t just quickly declare a deeply nested interface, that’s just how it is. The biggest change other than object oriented thinking will probably be decorators. Typescript had them experimentally and only for classes, python has them for classes and functions natively. They’re a bit tricky to wrap your mind around when you want to write your own, but not too bad. A lot of Google hits will be outdated on this front. Google specifically “decorators ParamSpec” to see how to make them properly.

    Good luck in your new job, you’ll be grand!


  • I code both typescript and python professionally, and python is almost as much of a mess, just a different kind of mess. The package manager ecosystem is all over the place, nobody is agreeing on a build system, and the type system is still unable to represent fairly simple concepts when it comes to function typing. Also tons of libraries just ignore types altogether. I love it, but as a competitor to JavaScript in the messiness department it’s not a good horse.



  • That’s a good link, the author has a bachelor’s in philosophy, so that gives it some credibility, and he is providing a nuanced summary of some philosophers’ views on individual wealth. Schopenhauer is the only one to come close to what you’re saying, and he’s famously the most depressed/depressing guy to ever have walked the earth, not that that means he should be discredited of course. As a list this in no way backs up your point about wealth on a societal level. Just because you identify with an idea that does not make it true.

    Here’s an actual research paper with statistics touching on this subject. The authors argue that local wealth coupled with large inequality may cause many people to borrow above their means, causing unhappiness.




  • Gotta know, are you serious or joking here? Follow up question: are you a developer and have you ever worked on a medium+ sized project? The amount of dependencies you end up with is astounding, you can’t just “know” when all those APIs changed, that would be a full time job just to stay on top of. And that’s not even taking into consideration transitive dependencies. If a library doesn’t use semantic versioning, 99% of the time it’s correct to avoid it just to save yourself the headache.