Show newer

@divVerent@social.tchncs.de I don't think that has anything to do with how humans think, it's a habit taken from older ecosystems like Java where that's the standard, huge do-it-all frameworks. Whereas in JS a dependency is zero-cost so if you write it in a separate file you can just as well publish it as a module

@goat@hellsite.site alright then, I will schedule a video call meeting for tomorrow, 7:30am okay for you?

@goat@hellsite.site I messaged you to ask for help with solving this issue do you have some time

@divVerent@social.tchncs.de yeah lol, anything but JS (and Rust?) has dependency hell all the time.
Python is finally moving to a dependency config "inspired by" npm and cargo though, with lockfiles and everything, just will take 10 years for people to migrate to it I guess

@divVerent@social.tchncs.de maybe the original JS was never intended for that, but Ecmascript has grown a lot since then. It's currently the language with the best module system so yeah, large codebases shouldn't exist, ideally you're just combining separate modules (either written by you as well or someone else). A combination of does-one-thing-and-does-it-well module is easier to audit, easier to refactor and easier to understand

@divVerent@social.tchncs.de lol so it's literally a band-aid on the messed up large code base, ok

CloudFlare 

@thufie selesti.com/news/checking-for- might be useful, even though they do this from a pro-cloudflare standpoint lmao

CloudFlare 

@thufie no i mean, it would be useful to check both?

smh I'd really like a nice camera gimbal, even though I don't (currently) record video at all lol

@divVerent@social.tchncs.de imo typed programming is more often than not used as a band-aid. If your code has clear variable and function names it should kinda be obvious what is expected to be passed where. I wouldn't be against a native type-system but it should be optional, and way more expressive than TS.
== sure, easy enough to have an eslint rule to warn you, null and undefined encode different meaning, "exists but is empty" vs "does not exist" basically, so it's good to have both

Even though it's literally always a gross misunderstanding of either the module system, or ~~performance~~ (spoilers; v8 is real fucking fast). Or just repeating it because others said it was bad so it must be bad, right?

Show thread

people continue to have trouble with the concept that oppressed groups making blanket statements about their oppressor group doesn't necessarily implicate any particular individual of that group

I should probably just get used to always calling it ECMAScript / ES because otherwise people just can't help their kneejerk javascript bad!!11!!

it's almost exactly 2 years ago that I got super into listening the DOOM ost, it got me through a *horrible* Java group project where I was basically the only person who knew programming, got them a good mark tho..

@dumpsterqueer@ondergrond.org smh i hate mondays

@dumpsterqueer@ondergrond.org harness that doom energy!

Show older
Pixietown

Small server part of the pixie.town infrastructure. Registration is closed.