Content pfp
Content
@
https://opensea.io/collection/dev-21
0 reply
0 recast
2 reactions
Monteluna pfp
Monteluna
@monteluna
I still can't find a reason to ever use Python server-side. I worked for multiple startups that did this and stood on the idea that OO design was the only religion that mattered. Today in the year 2025 of our lord Satoshi, when you get type safety with Typescript and plenty of other strongly typed languages, what's the point of using Python for anything beyond scripting and data?
3 replies
0 recast
5 reactions
Monteluna pfp
Monteluna
@monteluna
If you typecheck data from your database, the only real errors you can have are library. Typescript serverside eliminates a lot of boilerplate because it will fail typecheck if your code doesn't work. If you're using a database that's JSON and your shape is messed up, that's not a language problem. You have operational issues. In any case, why would anyone choose to split backend and frontend in 2025? Just use typescript unless you want to waste time.
1 reply
0 recast
1 reaction
Leeward Bound pfp
Leeward Bound
@leewardbound
i use backend python and i slightly prefer it to modern typescript (which has gotten much better but still kinda sucked for backend dev 2-3y ago) imho it's more pleasant to read and write and it feels like a much cleaner codebase, every time modern tools like uv + ruff fix many toolchain issues. typing is supported pretty well in many packages, and it's always optionally there, i use it lots. npm ecosystem still has its issues as well, and this is just a feeling, but generally i trust any python package to "just work" even if the maintainer doesn't touch it in 5-10y, as opposed to 5-10mo from npm i really like django framework, for the ORM (which many people hate? idgi) and built in auth and admin pages - it's nuts to me that nothing in JS comes close right now im also currently a fan of a newish framework called mountaineer, which does python-backed SSR of tsx pages via rust bindings, like a fastapi nextjs replacement, it solves frontend/backend typing consistency and is fun to use (unlike nextjs)
2 replies
0 recast
0 reaction
Leeward Bound pfp
Leeward Bound
@leewardbound
just came here to add that i spent the last hour debugging a production bug in TS because my Numeric column with my Numeric typeorm that returns a Numeric zod schema was returning a string value typescript types are weakly enforced suggestions ๐Ÿ˜
1 reply
0 recast
0 reaction
Monteluna pfp
Monteluna
@monteluna
Oh come on run time data deserialization is *always* weird business. The type is checked so you did eliminate a host of possible programmer errors. You'd still get those errors in python occasionally especially if you're using a relatively newish ORM. ๐Ÿ˜…
1 reply
0 recast
1 reaction
Leeward Bound pfp
Leeward Bound
@leewardbound
sure and agree python wouldn't handle this any better! but your original statement was "If you typecheck data from your database, the only real errors you can have are library." which was maybe a bit cavalier ๐Ÿ˜‰
2 replies
0 recast
0 reaction
Monteluna pfp
Monteluna
@monteluna
How's that not a library bug? It should throw and you expected it to throw!
1 reply
0 recast
1 reaction
Leeward Bound pfp
Leeward Bound
@leewardbound
i expected a Numeric and my typing assured me it is a Numeric, but the language itself doesn't actually enforce typing at all. whether this is a typeorm bug or a higher level psql driver bug isn't quite clear to me. my point is just that the whole "end-to-end typechecked" line of thinking often fails to account for the fact that this is lint-time type checking!
1 reply
0 recast
0 reaction
Monteluna pfp
Monteluna
@monteluna
Idk I would agree to disagree here. I'd have to ask why you're doing this serialization server side, whether there's a better option, or what's really going on. I personally see typescript as good for things like maintenance, refactoring, design, etc. because that's the stuff that causes businesses to fail or be stagnant. If you're senior you know you're going to get hit with some weird bugs, and that's ultimately why you're paid, because a junior wouldn't even be able to debug it. This happens in all languages, libraries, etc. There is no programming language that's perfect of course, so I'm not sure I would agree this is the be all end all for all typescript as a whole.
1 reply
0 recast
1 reaction