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.

I don't think they did an exceptional job keeping teams separated. In fact, I think monorepos only end up artificially tying teams down with an arbitrary and completely unnecessary constraint.

Also, not all work is services.

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.

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.

I don’t think anyone believes that you are a list of well known apis.

shhh don't raise suspicions.

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.

Is it not generating HTML on the server to be served to the client?

No, it generates the code that creates the DOM, sets the application state based on the user's setting, and updates the webapp to resume working in a consistent state.

It basically sends a frozen instance of a full blown JavaScript application.

What you’re describing is, in my opinion, an overly complicated form of dynamically rendering HTML on the backend.

That's because you're oblivious to the problem domain,and thus you're falling back to the unrelated but similar sounding things you're familiar with to fill in the void of your understanding of the actual problem.

Anyway, that’s my opinion on the matter

My point is that your opinion is a misinformed one,and really doesn't hold up to scrutiny.

learn Haskell, write better code

The same has been said about C but people just keep writing awful code in Python.

I agree. The GIL and packaging woes are a good indication that it's range of applications isn't as extensive as other tech stacks.

But sudo-rs seems to have a bit of a different usecase since it is intended as a drop in replacement for sudo, hence it must be able to handle the sudoers file aso.

Other than being yet another "standard tool X clone written in Rust" project, does it actually provide any tangible value?

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.