Outside of my own specialty I can people in the software industry bogged down by managing excessive boilerplate. I think this happens most often in web dev and data science.

In my opinion this is an indication that the software tools for those ecosystems need improvement, but rather than putting in the design effort to improve the tools in the ecosystem, these Big Data companies see an opportunity to just throw LLMs at it and call it a commercial product.

Until people start applying the same logic everywhere for consistency, not just in file names.

I assume he thinks this will win over more Gen Z than it will lose him Boomers, and no one will ever hold him to this promise anyway.

I really admire that you're committed to recycling and waste reduction. Do you have any resources you'd recommend for me to learn more about what's going on in that space and what's being done to combat the acceleration of plastic and electronics waste?

I know it's "not your job" to educate me, but everything I can find on the topic suggests that we don't have a viable path to manage the accelerating growth of waste, and we don't have very effective systems for recycling, so even recyclable waste is mostly just being dumped in landfills because it's more "economical" to just keep churning out products from new materials. I'd be very happy for all of that to be wrong, so any credible source you can point me at to debunk that narrative would be very much appreciated.

Let me know which part was confusing to you

The part where you left out any viable path for any of the hypothetical solutions to be realized 🤷‍♂️ You of all people should know that a blueprint is worthless if there's no process available to build what it describes.

Damn here I am thinking that this is one of the most important parts of civilization.

I mean yeah, I do agree that sanitation and water works are the crowning achievement of human civilization to this very day. But I've gotta say it doesn't inspire confidence if the people running those systems think that concerns about sustainability are something to have a group chuckle about.

Just because the work you do is important doesn't mean it's beyond the scrutiny of ecological sustainability. All your good work won't amount to much in the long run if we can't find a path to reducing consumption and prolonging the viability of these systems. We don't have infinite resources, and our ability to recycle is nowhere near what it needs to be to keep up with economic demand.

Tell you what, why not be the change you want to see in the world and stop flushing your toilet, stop using tap water, stop recycling anything, and don't set your garbage out.

My partner and I are unironically taking the time to research subsistence farming and how to maintain very basic personal water collection and waste removal/reuse systems. We're also learning about perma-computing so that hopefully we can preserve some of the knowledge that humans have accumulated into the future.

We see it as a foregone conclusion that human civilization as we know it will entirely collapse, probably sooner than anyone cares to admit, so we're making contingency plans. People with your dismissive attitude are a big part of why we see it as a forgone conclusion. Because as far as we can tell you're in the 95%+ majority of people on this planet, which means hardly anyone is putting effort into solving these existential problems that we're facing. Problems which you have offered no viable solution to, despite your insistence otherwise.

I would personally love to see AOC as president. Unfortunately I don't constitute a majority of the electoral college, and right now that's the only backstop we have against the descent into a fascist dictatorship.

Considering most JIT compilers for JavaScript are written in C++, I can't conceive of a reason you couldn't implement one in Rust.

Is part of your requirement that unsafe doesn't get used anywhere in the dependency tree? If so you'd have to take away most of the Rust std library since many implementations in there have small strategic uses of unsafe under the hood.

In my entire software engineering career, which spans embedded systems to CAD applications, I've never encountered a case where GOTO is actually needed (but maybe some places where it can be used as a dirty shortcut to save you some lines of code).

As for arbitrary function pointers, if those function pointers are written in Rust then they'll come with all the safety assurances afforded to Rust code. I suppose if you're worried about the danger of running ussr-code with unsafe in it, you could probably have your JIT refuse to compile the unsafe keyword specifically.

I'm sure you're on the shop floor for every one of those conversations.

But anyway, enjoy being confidently incorrect: https://www.consumerreports.org/cars/car-safety/tesla-driver-monitoring-fails-to-keep-driver-focus-on-road-a3964813328/

I feel like this is rapidly approaching the "is water wet?" conundrum.

I think it's bizarre to make this big of a deal out of it. It's such a useless hill to die on, and not actually sound logic to assume that a minor use of vulgar language invalidates everything surrounding it.

The fact that you're still going on about this just makes you a curious sociological phenomenon rather than the paragon of virtue that you seem to think you are.

I could easily defeat 600,000 babies in a chess match.

That link doesn't prove whatever you think it's proving.

The open source ecosystem does not rely (exclusively) on project maintainers to ensure security. Security audits are also done by major enterprise-grade distribution providers like Red Hat Enterprise. There are other stakeholders in the community as well who have a vested interest in security, including users in military, government, finance, health care, and academic research, who will periodically audit open source code that they're using.

When those organizations do their audits, they will typically report issues they find through appropriate channels which may include maintainers, distributors, and the MITRE Corporation, depending on the nature of the issue. Then remedial actions will be taken that depend on the details of the situation.

In the worst case scenario if an issue exists in an open source project that has an unresponsive or unhelpful maintainer (which I assume is what you were suggesting by providing that link), then there are several possible courses of action:

• Distribution providers will roll back the package to an earlier compatible version that doesn't have the vulnerability if possible
• Someone will fork the project and patch the fix (if the license allows), and distribution providers will switch to the fork
• In the worst case scenario if neither of the above are possible, distribution providers will purge the vulnerable package from their distributions along with any packages that transitively depend on it (this is almost never necessary except as a short-term measure, and even then is extremely rare)

The point being, the ecosystem is NOT strictly relying on the cooperation of package maintainers to ensure security. It's certainly helpful and makes everything go much smoother for everyone if they do cooperate, but the vulnerability can still be identified and remedied even if they don't cooperate.

As for the original link, I think the correct takeaway from that is: If you have a vested or commercial interest in ensuring that the open source packages you use are secure from day zero, then you should really consider ways to support the open source projects you depend on, either through monetary contributions or through reviews and code contributions.

And if there's something you don't like about that arrangement, then please consider paying for licenses on closed-source software which will provide you with the very reassuring "security by sticking your head in the sand", because absolutely no one outside the corporation has any opportunity to audit the security of the software that you're using.