this post was submitted on 13 Apr 2024
727 points (95.8% liked)
linuxmemes
21428 readers
736 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack members of the community for any reason.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
- These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudo
in Windows. - No porn. Even if you watch it on a Linux machine.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't fork-bomb your computer.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
In that post, his critiques were around the problems with the STL and everyone using Boost. The STL has improved significantly since then, and it would be a limited subset of c++ if it was ever allowed
There have been mailing list conversations earlier this year, citing that clang/gcc now allowing c++ in their own code might mean they’ve taken care of the issues that made it unusable for kernel code
https://lore.kernel.org/lkml/e5949a27-999d-4b6e-8c49-3dbed32a00bc@zytor.com/
I’m not saying it will happen, but it’s not being shot down as an absolute insanity anymore, and I wouldn’t have expected Rust to be allowed in the kernel, either
Oh interesting. I didn't realize boost was the main issue. Most people I've talked to were complaining about VTables introducing a bunch of indirection and people blindly using associative containers.
Vtable equivalents are used extensively in the kernel
You’ll find structs all over the place setting them up, e.g. every driver sets up a .probe function that the core will call, since it doesn’t know what driver it’s loading
Right the issue was more because they're so easy to throw in without thinking about it so people overuse them. That may just be older devs complaining about newbies though.