Debatable whether minified JS is "open source", in the same way that compiled machine code is technically still visible, just unfeasible to comprehend (despite, or perhaps in spite of decompilers).
Anyway, minified JS lacks comments and prompts to read from. The explanation I have accepted is just the sheer massive quantity of JS code and libraries coupled with all the documentation surrounding it.
Professional engineering is really about implementing processes and procedures that create reliable and dependable systems. Ultimately it's about responsibility and risk management. Being an engineer has nothing to do with understanding or implementing technology or technical details and specifications (unless you are in an extremely junior level engineering position). That work already has another title: that's called being a technologist (and there ain't nothing wrong with that title and that work).
Very, very, very few technologists (including self-taught programmers, computer scientists, and even some engineering grads) have, or even understand the skills needed to manage technical risk, simply because those skills are not part of any of those curriculums and the licensure required to be recognized to conduct those activities. It requires knowledge, training, and certification specifically, not just a university degree or x years on the job. Of course, it's not the sort of distinction that the general public understands by "engineering" since the public kind of just takes the act of technical risk management for granted.
Conversely, it's perhaps also why the number of engineers with hands-on skills is shockingly lower than we expect: using technology is not on the engineering curriculum.
But yeah, just because the general public confuses technical skills with engineering doesn't give you, lacking all three of : an accredited engineering degree, an engineering licence, and perhaps most importantly, malpractice insurance, licence to call yourself an engineer.
It's stupid shit like this why regulation is not the answer to big tech. But then we wouldn't need regulation if big tech didn't ruin all that was good about the Internet to begin with.
People are the problem. At large scale they turn everything to shit. Both in the private sector and in the public sector. Both meddling, making decisions on your behalf. In all cases taking your power away. It was better when we were just small communities, suffering and learning from the consequences of our own actions.
For me personally, this comment rings true, but the reality is that if you do feel this way (like I), then you were never the audience for this add. Believe it or not, still plenty of people out there with buy-a-car-as-a-present kind of money.
Think lottery winner, successfully YouTuber buying their parents a car as a thank you, plain old old money types ...
What's your beef with PHEVs? Most people use EV driving on them almost exclusively or at least a majority of the time. So your 83% number is way too high. And battery isn't practical for 100% of situations (there are no silver bullets). PHEVs are still a huge win. HEVs can go in the garbage though.
Damn, these are savage.
To be fair, robots kinda wear out over time too, arguably at a faster rate. At least living tissue can self repair.
Considering that this thing won't fit under any overpasses, the furthest you are going camping is your backyard.
Am I throwing away all my mice, keyboards, DAC, digital pens, and other peripherals just so I can have a connector with more bandwidth than I'll ever need? Nah.
Am I buying them or adapters all over again just so I can be compatible with a new universal standard that I don't need? Double nah.
KVM switches, or breakout hubs that these devices plug into, then a single USB c device goes to the computer is the most logical avenue for a migration. But this will take a long time. Most people don't even have that kind of luxury.
What does "stale code" even mean in this context?
Does that mean it falls behind stable? Just merge stable into your branch; problem solved.
Or is this just some coded language for "people aren't adopting my ideas fast enough". Stop bitching and get good.
Typing characters is maybe 1% of the job. The other 99% is understanding how the change affects everything else. Changing a single line of code in a function called by 1000 other functions each themselves called in 10 other functions can still potentially be more work and a bigger change than changing 9000 lines of code in a function called once.