Hexnut @ambihelical@qoto.org

@nuncio @AstraKernel Yeah I don't think it is _intentionally_ hard to understand, everything is there for a reason. It's goals of performance and memory safety are hard to achieve without the mechanisms it has. On the other hand, I think they could have made it a bit less noisy syntactically.

@AstraKernel I will look at this site when I am sober. Right now, after a day writing C++ and interviewing for a programmer in same, it is speaking to me. I am pretty sure it is just the alcohol having its way with me. But it is seems correct in so many ways....

@no0ob@infosec.exchange It's my understanding that firefox is at 10% because Mozilla let most of the rust team go. I'm guessing that's (a good part of) the reason why.

I'm also kind of perplexed by the idea that there's some sort of "artistic vision" in play. Clearly there's an ideology of memory safety, but I would never argue that is about art, and it's truly a good and practical thing.

As a C++ embedded programmer, I can say that most embedded codebases I've seen do not use exceptions at all, and I might add thankfully, as it makes the exceptional path explicit and easier to reason about. The code ends up being a lot of "if" conditional error handling early returns to avoid the exceptional cases. In development assertions are used to find problem areas during testing. Rust might make this kind of code easier to read to be honest, if the ? operator can be used in these cases.

I haven't tried any graph work with Rust yet, so you may be right about that.

@jbowen @Mara Same energy

@dpiponi Can I subscribe to your newsletter? I want free wine.

@carnage4life I usually miss slack more than email especially when a email turns into a conversation. It's just painful.

@BigEatie @akib emacs has crashed on me multiple times. I3wm never that I recall. Also emacs freezes up quite a bit more often which I usually solve by killing it.

@davidstalane@mastodon.social @squispix

You probably have an old package.

According to this: https://github.com/bbatsov/solarized-emacs/issues/438 it doesn't use dash anymore.

Try M-x package-refresh-contents first, possibly after removing elpa/* first. Also if there's a package-quickstart.el remove that too.

@deavid Not really there would be a benefit if all current devs were rust devs but i don’t think it would be worth it to train up current c++ devs. This was true for all projects I can remember. I wish it was different but I have to be realistic. If I was doing a green field project and had to hire everybody it could possibly work. Never been in that situation so far.

@deavid It looks like it does but I haven’t tried it.

@deavid I work in embedded, 95% of what I've seen, from Linux embedded to RTOS based is C++. The only place I have seen C is for a bare metal target.

To be honest, many of the developers I've seen barely write good C++, it's more like Cish C++. I don't have much confidence that most of the ones I've seen will be capable of transitioning to an embedded Rust target, so it might be difficult to transition with an existing team.

However if I was building a team from scratch for a new codebase, I'd look hard at Rust. There I could hire specifically for Rust or at least Rust enthusiastic C++ developers.

@volkris The appointment was probably just to deflect repub criticism; as only repubs suspect any intent. Now they have nothing to complain about until the investigation is complete, which will probably find no evidence of any wrongdoing, other than shoddy handling of the documents.

@carnage4life I work at a company with "unlimited vacation", and I've never felt this way, and I take time off that I need to stay healthy without guilt. I have a feeling that places where it's like as you describe are probably dysfunctional. On the other hand, if you are the one applying the pressure and not the company, it's a "me" problem, and you should probably look at fixing that.

@hnb It's always worth it to pore over the release notes to see what has improved. It's not that old though, came in with 28.1 iirc.

@SETIEric An overripe banana would be a better bet

@AstraKernel Hopefully the like's and retweets were just because it was funny