‍fuchsiaaaaaaaaaaaaaaaaa @f0x@pixie.town

@divVerent@social.tchncs.de yeah I avoid em too, but I like to think my pages still look good :P

pretty sure i've only followed the kick-off lectures this whole quarter, none after that..
but have been quite active in all the group writing assignments, those are okay

@divVerent@social.tchncs.de from my experience it's only the huge frameworks that struggle to do updates correctly, exactly because they're so bulky. If you choose your modules right a npm update will just work

@divVerent@social.tchncs.de huh, React works perfectly taking components from all sorts of dependencies, nesting however you like. It's by far the most pleasant UI library I've worked with.
jQuery on the other hand...

@goat@hellsite.site i showed you my meeting please accept

@divVerent@social.tchncs.de yeah, that's what 'npm update' does as well

@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

@goat@hellsite.site Hi

@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 nullchecks like this lol https://github.com/f0x52/matrix-appservice-irc/blob/ba003bebd1d4271110e96f1179260a033674e149/src/bridge/MatrixHandler.ts#L887 TypeScript has only ever been a nuisance to me...

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

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

@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