There are ways to structure it, but most importantly JS JIT usually discards type info instead of keeping it in the native dynamic code, because otherwise the performance wins are more marginal. That's the wrong thing to do. It's a dynamic language, it should act like it.
@hayley would be able to give more concrete and relevant examples.
@Alex@iska The current terms of use nonsense, if applied, is in fact non-Free and incompatible with the MPL & GPL if made necessary to run the program.
I think the role that the DMCA and similar bad laws have had in this matter should not be underestimated (https://pluralistic.net/tag/dmca/).
Requiring blackbox reverse-engineering to avoid legal trouble (such as technical felony acts) is *not* a reasonable hurdle and it's why it is so hard to reach feature parity with things that are readily available on Windows.
If those laws were abolished, a lot of things would suddenly become *much* easier to reverse-engineer, because one wouldn't have to shy away from simply decompiling proprietary software to liberate it.
It shows those people have not tried to even see how hard bootstrapping the knowledge they're assuming of others actually is, especially now that search engines have enshittified into uselessness and the hardware their comment pertains to no longer comes with useful manuals for their operation.
In a lot of cases, the knowledge also pertains to hacks for patching over design flaws & botched work that should've been done properly to start with (which would make said knowledge entirely obsolete as anything other than a curiosity).
It reeks of unacknowledged #privilege (and a heaping of normalization of deviance).
@Suiseiseki It's possible through reverse-proxy and VPN setups to ruin outwardly visible uptime of a service via DNS failure. The server itself may become unable to resolve the VPN it needs to maintain service uptime.
@novenary@wolf480pl@mikoto > after all artificial market segmentation for electronics is a scam to charge you more for hardware that barely costs more to produce, there is no reason to sell crippled CPUs and machines with less than the maximum supported amount of memory
Agreed.
> for repair, I don't really see anything wrong with leaving that up to specialists
Those specialists cost a fortune (often enough to make buying a new machine more palatable) when they're available at all (which they aren't here, I'd need to commute for a long time or ship the machine at considerable expense). It is also concerning that so much stateful hardware (but hard to reflash by users) remains on a machine, such that if the repair specialist is malicious, they can get up to shenanigans nearly undetectably.
> the sad reality is that capitalism will not do the right thing here anyway, and in most cases perfectly repairable machines end up in the landfill/junkyard regardless of user serviceability for a whole host of reasons, including user miseducation and obsolescence, or insurance writing off vehicles way too liberally
@novenary@wolf480pl@mikoto That would be okay if they also sold the microsoldering kit alongside the computer, since it's going to be necessary to upgrade it at all.
Because of course they designed that to be upgradable, right? They didn't just commit to generating e-waste unnecessarily, right?
Just as importantly as upgrades though, soldered-on RAM /cannot be replaced easily/ which is a major problem if any of it goes bad. Especially if it's not ECC memory.
@dalias You're saying that email shouldn't notify failed delivery at the transport level?
I'd certainly find it pretty helpful to get error emails back when I fail to get any answer from some representative or business for days or weeks. Are they just incompetent or ignoring me, or did they actually never receive it?
Hi, I'm Lispi, Lisp (Technomancer) Wizard (to eventually be).You might know me from @lispi314@mastodon.top I like Free Software, #Emacs and resilient computing a lot.I also like anime girls, animes with cute girls doing cute things and artwork with them too. Cute stories are good too.Some Pins:Software and Assumed Privilege, common problems: https://mastodon.top/@lispi314/111253066257920146Writing Privacy-preserving software & services 101: https://mastodon.top/@lispi314/110849018589421824#Kopimism #FreeSoftware #CommonLisp