While the other answers are funny, the real answer nowadays is either “murder” or “assassination”. There is not really a more specific word for it.

Might not be new but it’s not been posted here before :)

Not nearly as readable though

I don’t agree with the comment there. In my mind, the LTS release would not mean anything. It would just be a label on an arbitrary release every couple of years. I feel it could help the ecosystem align on which MSRV to choose, so that you don’t have one crate choosing 1.x, another chooses 1.(x+1) and another chooses 1.(x+5). It would be nice if we just sort of agreed that if you care about your crate being used by somewhat older compilers, use the LTS version and consider the implications if your MSRV go beyond that version.

Of course any crate author is free to completely ignore this and choose whatever MSRV they desire. But perhaps a significant amount of authors would put at least a little effort (but not much) in trying to avoid raising the MSRV above the LTS version, just as authors may try to avoid breaking changes and such. It’s just a nudge, nothing more.

An LTS release scheme, combined with encouraging libraries to maintain MSRV compatibility with LTS releases, could reduce this friction.

This actually sounds like a good idea. Currently crates are choosing their MSRV all over the place. If we just got a bit of alignment by calling every ~17th Rust release (roughly 2 years worth of releases) an “LTS” release, then crates could be encouraged to keep their MSRV compatible with that release.

But we also heard a consistent shape of gaps [in core]: many embedded and safety-critical projects want no_std-friendly building blocks (fixed-size collections, queues) and predictable math primitives, but do not want to rely on “just any” third-party crate at higher integrity levels.

I think some fixed-size collections and stuff like that would be super nice in core. Something with simple, predictable semantics, just like Vec has (i.e. no optimizations for certain usage patterns, like small string optimizations and that sort of stuff). With const generics working for integers, fixed size collections in core shouldn’t even be that hard (it’s certainly been done in many crates already).

I really don’t like that simply drawing a certain arrangement of lines and colors is now a crime

I’m sorry to break it to you, but this has been illegal for a long time and it doesn’t need to have anything to do with CSAM.

For instance, drawing certain copyrighted material in certain contexts can be illegal.

To go even further, numbers and maths can be illegal in the right circumstances. For instance, it may be illegal where you live to break the encryption of a certain file, depending on the file and encryption in question (e.g. DRM on copyrighted material). “Breaking the encryption of a file” essentially translates to “doing maths on a number” when you boil it down. That’s how you can end up with the concept of illegal numbers.

Is Dioxus easy to get started with?

I haven’t tried it myself but I’ve read the tutorials and it looks very React-inspired. It looks quite easy to pick up. It is still based on HTML and CSS but you can use one code base for all platforms.

Rust programs can definitely still consume a lot of memory. Not using a garbage collector certainly helps with memory usage, but it’s not going to change it from gigabytes to kilobytes. That requires completely rethinking how things are done.

That said I’m very much in favour of everyone learning Rust, as it’s a great language - but for other reasons than memory usage :)

Or just use rust for everything with Dioxus. At least, that’s what Dioxus is going for.

This is the way with modern software engineering, especially in the industry. It comes from the basic fact that:

1. Companies want to get code for free from the internet - someone else already wrote that code, let’s use it for free and have better profit margins!
2. Companies do not want to spend time and effort vetting that free code, as that would make it… well, not free. That would require manpower (perhaps unless you trust AI to do it these days…) and that’s money.

Basically they want to eat their cake and have it too. This applies to all modern package managers for modern languages that make it easy to distribute your own code and consume free online code.

I doubt the industry will ever mature to a point where this will stop, as the tradeoff of getting free code with no work is just too good for most companies, especially the smaller ones.

I would say no, ochre would have more of a red or orange-y tint.

Billboards and other physical ads and such suck but are thankfully already mostly illegal where I live.

Problem with other kinds of advertising is that it can’t be made illegal, not truly. People would still do it, it would just not be marked as such. I’m not sure how to fix this.

Have you tried the Rust book? I learned via that and it’s great.

I think that’s quite harsh. As I said, I know it’s not what OP asked and it was just a suggestion. I’m just adding it as an option. Perhaps someone else reading the thread will find it useful, if not OP (who I don’t think you should speak for).

OP mentioned they want native speed and were struggling with badly documented libraries. I feel like it was appropriate to at least mention Rust, considering those two things. Since when is widening a discussion slightly considered bad? You don’t have to reply to my comment either, if my comment does not seem interesting to you. Let alone downvote it. You can just leave it alone, it doesn’t hurt anyone.

Not that cool maybe but I once played a lot of Pathfinder (1st edition). I made a website with a detailed database of all the items in Pathfinder with very specific filters and also including a random item generator. You can try it out here:

https://sortekanin.com/collection/items/

I know it’s not really what you’re asking, but have you considered learning Rust? In many ways, Rust is more similar to C than C++ and is just as capable. There are quite a few very well documented (as is common in the Rust ecosystem) Rust libraries for GUIs, including efficient native ones or immediate mode ones and such. Just a suggestion.

but it doesn’t stop them from existing on the fediverse.

Well of course, nobody has absolute power over the fediverse like that. Anyone can start an instance and create millions of bot accounts if that’s what they wanted. But “the fediverse” is only what it looks like from the point of view of your instance. If stuff is blocked or defederated, it may as well not exist.

The point isn’t to eliminate all bad behavior on the fediverse (that’s not possible, by design of the system, and that’s good). The point is to allow users to seek towards those instances that keep bad behavior out.

You only need to stop it on your own instance. You can’t do anything else anyway. Users will go to the instances that aren’t flooded with bots.

Warcraft 3 custom maps still drag me back sometimes.

There’s nothing that can be done to stop it

That’s not true at all. You can definitely do something:

• Make a sign up process that filters out most low effort bots (e.g. applications, invite trees)
• Get more moderators to catch the bots earlier. In a similar vein, encourage users to report bots.
• Defederate from instances that don’t have similar measures, i.e. that don’t take bot prevention seriously.