However, we’re still implementing IPv6, so how long until we could actually use this?

We can already use custom verbs as we please: we only need to have clients and servers agree on a contract.

What we don't have is the benefit of high-level "batteries included" web frameworks doing the work for us.

Also, TIL that the IETF deprecated the X- prefix more than 10 years ago. Seems like that one didn’t pan out.

Can you elaborate on that? The X- prefix is supposedly only a recommendation, and intended to be used in non-standard, custom, ah-hoc request headers to avoid naming conflicts.

Taken from https://datatracker.ietf.org/doc/html/rfc6648

In short, although in theory the "X-" convention was a good way to avoid collisions (and attendant interoperability problems) between standardized parameters and unstandardized parameters, in practice the benefits have been outweighed by the costs associated with the leakage of unstandardized parameters into the standards space.

I still work on software that extendively uses X- headers.

Ah, the Microsoft tradition of always having the wrong priorities.

I wouldn't be too hard on Microsoft. The requirement to curate public package repositories only emerged somewhat recently, as demonstrated by the likes of npm, and putting in place a process to audit and pull out offending packages might not be straight-forward.

I think the main take on this is to learn the lesson that it is not safe to install random software you come across online. Is this lesson new, though?

that managers want to stay in control of everything, and they decide whether they do it or not.

That's fine, it's a call from the manager.

That doesn't make it Agile's fault though. In fact, one of the key principles of Agile is providing developers with the support they need. Blaming Agile for the manager single-handledly pushing for something in spite of any feedback does not have any basis.

So is it just Amazon getting hit for this? Or will they be going after the manufacturer as well?

Nowadays it's hard to tell the difference between Amazon and Ali Express. Even if it's a third-party dropship business selling through Amazon, it's still Amazon doing the listing, selling, and transaction processing.

Even if you argue that the same store can sell stuff elsewhere, Amazon is still the one selling those. At best, you'd need to argue that after hitting Amazon, other stores should follow.

As a former civil engineer who now works in software, “software engineer” irks me. “Engineer” means you’re supposed to be licensed and you have a responsibility for the public good above your responsibility to your employer.

This. I think some people don't understand that titles are not whimsical status symbols and hold actual legal and regulatory meaning. A random guy can hold an engineering degree and not be an engineer, while a random guy with no degree can actually be a engineer if he jumps through all the hoops.

In engineering fields, being a member of a professional engineering body is critical to work in the field, because the main value proposition of these credentials is to prevent incompetent people from working on critical tasks which can potentially have important consequences to society if they are done poorly. For example, people can die if an engineer signs off on a project for a residential building that collapses due to shoddy work. If that happens then the engineers who signed off on the project will be investigated and if they are held responsible not only can they be held criminally responsible for their work but their license will be pulled, which is society's response to ensure this problem won't happen again.

I wish there was a linter that stopped my colleagues from adding in a half-gigabyte of Apache Spark artifacts to go with a single line of code, which makes the product impossible to deploy to customers;

It sounds like this would be simple to catch during code reviews, or in the very least with a regression test running after the packaging stage.

or to implement another fucking O(n^2) algorithm that flies through the test suite and craps out in production;

It sounds like the job for a performance test.

or our placement students from trying to get ChatGPT shit through code review.

Aren't code reviews catching this?

I also fucking hate checkstyle, or any of its friends like Google’s spotless; sometimes you want to format your code so that the underlying thinking is more obvious, perhaps to highlight how some parts are different and make things that are not as you would expect stand out, but no.

I'm afraid that's not supposed to be handled at the code formatting level. That's supposed to be handled by extracting code to a method or a dedicated class, and cover with unit tests to illustrate how it's expected to work. If you're trying to handle that with non-standard code formatting then I'm afraid you're writing bad code.

So there is fundamentally no difference between cargo and any other contemporary dependency/package manager.

I would also mention support for third-party compiler cache systems. Install something like ccache, set a couple of flags in the CMake project, and your whole project can now reuse build artifacts with barely no CPU load.

So you want me to invest my time (...)

I don't want you to do anything, but I'm not the one wasting my time complaining over how others contribute to FLOSS projects. If you feel entitled to complain about other people's contributions, in the very least you need to put your money where your mouth is.

I am constantly losing track of which function is where and I’m never quite sure if I have code in the right place.

That's not a Rust concern but a software architecture concern. The software architecture pattern you follow determines how the project is structured taking into account what requirements it needs to comply to address common requirements, such as ensuring that things that change a lot will be easier to change and things that don't change won't get in the way.

I recommend you read up on topics such as layered architecture, hexagonal architecture/ports and adapters, clean architecture, etc.

That said, incels REALLY hate Naomi for whatever reason.

I think you're way out of line with the insults and broad accusations. I am bare new to the 3D printing community and I never heard of Naomi Wu before. The article only mentions she is an influencer, and this discussion makes little to no efforts to add context to why is a particular influencer relevant to 3D printing.

Calls to clarification are faced with comments like yours, accusing those of asking a simple question of being incels.

This behavior reflects poorly upon you in particular and the 3D printing community in general. Please pay attention to what you say and do.