I guess I should have put a /s but I thought it was pretty obvious. The 68 in Algol 68 is 1968. COBOL is from 1959. Modula-2 is from 1977.
My point exactly was that all the hot new languages are built with LLVM while the “new” language options on GCC are languages from the 50’s, 60’s, and 70’s.
I am not even exaggerating. That is just what the projects look like right now.
GCC is adding cool new languages too!
They just recently added COBOL and Modula-2. Algol 68 is coming in GCC 16.
think it’s fair to say performance rust is hard to write
This situation proved exactly the opposite.
They wrote a utility to pass functional tests. It did. Then people said it was too slow. So, in just a few days or hours, they dramatically sped it up while still passing the tests.
Seems like it was pretty easy to write fast Rust code in this case.
The best thing about all the C smugness here is how quickly it backfired.
Out of dozens of utilities in uutils, two were slower than the GNU equivalents. In case the logic escapes some, that means that the others were already as fast or faster. Some are multiples faster. The overall uutils suite is faster then GNU Coreutils already and will only get better. There was nothing for C fans to be smug about to begin with.
Of the two that were slower, it seems to have only taken a few days to make them faster. The article only tells us about one which is now 50% faster than the GNU version.
But the promise of Rust is not that Rust is faster anyway. It is that it is easier and safer to refactor. The actual promise of Rust is that you can address issues like performance without as much fear that you will break everything.
After the reported slowness, both of the two uutils implementations were dramatically sped up in just a couple of days or even hours. They are tested against the GNU test suite and so we know these tests are still passing. That is the promise of Rust. This example proves the Rust claims real. The C smugness did not age well.
The C versions (GNU) can clearly be sped up as well. The question is who will do that and when. Because speeding up old C code is not nearly as easy or fun. My guess is that it is going to be more than a couple days before we see headlines bragging that GNU has caught up.
The GNU Coreutils are maintained by Red Hat if we look at who contributes the code and who maintains the dev servers. They are professionally maintained. It is not a rag tag bunch of amateurs. So if uutils is already faster, it does not bode well for the C implementation.
Once they get their Wayland compositor working, I would not be surprised if Steam runs on it.
We may not be disagreeing. I guess it depends what you mean by read.
Cool. I used to but mostly Chimera Linux these days.
That said, I probably have more instances of Debian running than anything else if you count VMs and containers.
The distro matters less than it used to now that we have Flatpak and Distrobox.
If you are hardcore, your distro puts /bin, /usr/bin, and /usr/sbin in all in the same directory.
Einstein reportedly said “Never memorize something you can look up in a book”. When asked the speed of sound he said , “I do not know but that number is commonly found in textbooks”.
I am not going to spend my life reading manuals. Reading my furnace manual years before a problem arises is unlikely to help me.
However, I completely agree that RTFM is a great thing to do with confronted with a gap in knowledge or problem to be solved. Not the whole manual probably, just the relevant parts.
I think it is much more important to store ideas in your head than information. That said, those ideas do not come from nothing.
I might not read the man pages of every command on a Linux system. At least, not all of them. But I should know high-level what commands are available and what they generally do. That allows me to think of them when they would be useful. But I probably have no idea what the proper syntax is for any of them when I go to use them.
And “the manual” is not always the best place to get ideas, even if it is the authoritative source for specific knowledge.
Time spent reading the manual is time not spent doing something else. Spend your time learning. Spend most of it learning what is possible. In my view, that is the best strategy.
I am not much of a bash guy so it took me a moment to understand what this was doing.
Too bad I have to read so many man pages before I get to bash or sh.
It does if tech changes fast.
First, many rich people are older people.
Regardless of age, rich people bought expensive TVs when even the best ones were smaller. They still work great and have not been replaced.
Also, a TV is not as important to rich people. If they want to watch the game, they get tickets. The old screen is good enough. And a smaller screen probably fits nicer into their decor. In a poor household, the TV is the centrepiece and even if it is ugly, it looks better than the rest of the room.
Finally, rich people may be busier. I do not want this comment to be misunderstood but the reality is that television is just not as central to their lives.
Mostly though, I just think older TVs are smaller.
Ya. The CEO has a person that has a phone and a laptop.
Every time the CEO walks by he thinks “that guy has upper management written all over him”.
Chimera Linux is developing something called Turnstile. It will provide the necessary service management stuff on Chimera Linux, which does not use systemd. GNOME is the “default” desktop on Chimera.
My understanding is that Chimera wants to do this on a way that will work with other non-systemd systems as well. So this may be your solution to running GNOME on Void.
It has nothing to do with Rust. Permissive licenses are more popular with new projects. Rust is more popular with new projects.
The stats show that people are more likely to be attacked by a shark on days when they had ice cream. Eating ice cream does not make you more likely to be attacked by a shark. They are just both things that happen at the beach.
Soft Landing Systems (SLS). So many disks!
This is all about RISC-V servers for now. Those are arriving soon (later this year). Both Vector extensions and virtualization are essential features. This is where Ubuntu is planting their flag.
RVA23 will be a great foundation for the desktop too but that is not going to happen until the end of 2026 or even 2027. Any then though, RISC-V boards may actually be powerful enough to compete. At that point, Ubuntu will be ready with a mature ecosystem.
It all makes sense but I feel it purposely leaves us desktop or SoC users behind.
Agreed. If something happened, Greg would certainly take-over at least temporarily. Then the LKML would fight over succession like they fight over everything else. It would take too long, it would be dysfunctional, at least one person would quit the project but they would settle on a perfectly workable solution in the end. And it would evolve from there.
There is a whole hierarchy of ownership in the kernel. It is not entirely explicit. It can be quite fluid. It is not as dire as the article states.
I love Haiku but this is a reasonable question
I have built single pass compilers that do everything in one shot without an AST. You are not going to get great error messages or optimization though.