The velocity that RISC-V development is seeing is remarkable. The first commercial ARM processor (ARM1) started design in 1983 and was released in 1985. The first Linux-capable ARM processor was the ARM2, released in 1986. The first 64-bit variant was Armv8-A, released in 2011, with Armv9.6-A in 2024.

RISC-V was first released in 2014 and the stable privileged and unprivileged ISAs were released 2021 and 2019 (including the first stable rv64I), respectively. The first Linux-capable RISC-V processor released was the SiFive Freedom U540, which came out in 2018. The current rv64I variant of RISC-V is at 2.1, released in 2022.

I’m optimistic that RISC-V can and will compete, given its compressed development timeframe and mass adoption in MCUs and coprocessors. The big hurdles really are getting rid of the hardware implementation bugs (ex. failure to correctly implement IEEE754 floats in THead C906 and C910 CPUs), and getting software support and optimizations.

There are several HPC companies iterating towards commercial datacenter deployment, of special note being Tenstorrent, which both has an interesting, novel architecture and Jim Keller (know for AMD K8, AMD64, and Apple M-series) as CTO. They may be able to displace NVIDIA a bit in the DC AI/ML space, which could help to force GPU prices to get more reasonable, which would be nice.

Overall, yeah, rv64 has a good deal of catching up to do but, with the ISA not requiring special, exorbitant licensing, hardware development is moving much faster that expected and may be competitive with ARM in more spaces soon, if they don’t succeed in using governments as an anti-competitive bludgeon.

Well, no, you’re not going to be etching CPUs into silicon wafers in your basement

Actually: https://docs.hackerfab.org/hacker-fab-space

Sad. I was rooting for their weird-looking trucks, though they looked more and more like vapor-ware.

I thought that they tried too hard to align with Quake 3’s twitch-gaming.

Zork.

Giving away the only UT game that matters? Wow.

Ceasing to exist? Because that’s what it should do. Keep that commercial rot out of here.

…I don’t actually know what you mean, if you know what I mean.

They undergrounded fiber down the road from me but still no service in my city :(.

Probably for themselves only.

I maintained a CEPH cluster a few years back. I can verify that speeds under 10GbE will cause a lot of weird issues. Ideally, you’ll even want a dedicated 10GbE purely for CEPH to do its automatic maintenance stuff and not impact storage clients.

The PGs is a separate issue. Each PG is like a disk partition. There’s some funky math and guidelines to calculate the ideal number for each pool, based upon disks, OSDs, capacity, replicas, etc. Basically, more PGs means that there are more (but smaller) places for CEPH to store data. This means that balancing over a larger number of nodes and drives is easier. It also means that there’s more metadata to track. So, really, it’s a bit of a balancing act.

could be used for social welfare systems

For needy billionaires, maybe.

It’s also available on nearly every unix-like machine since the 70s. So, super useful to know how to use. I personally also like (neo)vim as an IDE and its optional regex functionality because that allows once to efficiently edit massive files with minimal effort.

As a long-time vim enjoyer, I like your gusto. Imagine if you could apply regexes to that carpenter’s axe.

(Also, what sort? Do you have one of those awesome Gransfors Bruks ones?)

And there’s also resilience against natural disasters. Having processor manufacturing limited to one place is just a bad idea.

The guitar binary has a dependency on the curser package which is a deprecated version of cursor with an accidental misspelling. Running the make with sudo replaced this at the system level. Best just to reinstall.

> sudo make guitar

Oh no. Do not build guitar as root.

You know, if I can use vim bindings and regex, I might try it out. I tend to try to keep my neovim plugins fairly lightweight when I config myself. Not being electron is a big plus.

Ctrl is already used my a large number of commands in POSIX shells. This is one of the places that I really like Apple’s solution (despite really not liking most of what they do). Super/GUI/Command + c/v is a great improvement in the terminal.

Fair enough. Those are things that I like to be able to use, however. Which makes nano/pico/micro a non-starter for me. Different strokes for different folks.