Cloudflare - louded as one of the top developers in certain circles, should have known better than to release it so early without full vetting.

Nobody follows proper development cycles anymore either way. Knowing if a service of yours goes down it can cause that much trouble should inform you to be a more stringent and have hard policy as to production rollouts.

It's why I don't and won't work for them, that and their sales tactics; netflix as well. It's the reason I get annoyed when people complain about alternatives and still fail to realize that it's very difficult to replace things without some funding.

@Gnostic

Rust is what happened to cloud flare. ;D
post here

@igorzwx  No problem. You shined the light there .. I'll check out your apps and let you know.

This alsa point is one I've hammered for a long time. Alsa is actually capable, it's just different api and configuration isn't always obvious. Though comparing to pulseaudio and pipewire saying configuration isn't obvious doesn't matter at all there because it's no where near obvious there either.

Pretty much. Same difference. It's not memory safe, but it sure is modern. 🤣

In general it's become vitriolic. Mostly because of social media and fanatic users who support only a single distro or single thing and attack everything else. I don't see it getting any better either.

Same as always, NIH here. We don't control that, so here's our replacement that we do control. That's all it ever is

Users feel entitled or demand it. When faced with choices people won't chose to their benefit if it costs them anything. They'll wait until it's too late and then, well, it's too late. 

I would rather spend the time to take what's useful OFF of gtk2 than to keep gtk2 running at all. That's where I am at this point.

@greenjeans

Saw that too.. Just was being nice.

@unixuser

There is no panacea to the issue. It does not make software more or less safe. Either way. Just hope people start paying attention and not jump ship to replace system components with it.

Not when the language itself still leaks memory and it's known, and hasn't been fixed, yet.

XFCE, IceWM, Trinity, is all I can think of... I'll let you know when I finally roll up the one I forked into a package for devuan. Might be a little bit on that one..

I'm not sure about the state of Trinity on devuan, nor IceWM but I'm sure Ice would be the closest to working outside of XFCE. There's also openbox but it's more suited to those that want to create a fully custom environment than most are confortable with.

Honestly, that depends on who in their cult of personality you speak to. It "stops" the range of attacks we've known for a while. Buffer overflows, double frees, etc.. problem is, it still leaks memory itself. Though that doesn't seem to bother them or raise red flags to most of them. I'm sure some do see it as a problem, but the crazy forward charge through it doesn't make sense.

It's memory strict and the protocol for using memory is the borrow checker.. which again, just use unique_ptr in C++. Only one owner can own it, solves the same issue..

Bounds checking, etc is something that's been done in the past compilers, add infinitum.. It's not new, just some compilers don't concentrate on it. This to me, is seriously a case of, if you've read the compiler docs or in linux --help, at least. You can glean what you'll need to turn on / turn off..

The claim is that you can bet there are nearly no issues when it works. Don't mind the fact that it's still running on a compromised machine substrate and any binary in memory is susceptible to random attacks.. the borrow checker and their efforts aren't going to and can't protect them from that.

then there was that whole debacle with their trademark.
https://www.theregister.com/2023/04/17/ … rk_policy/

If you want to learn a new language and you don't mind strange syntax, check out Zig. It's honestly a better option than rust.