Arm acquisition

[Arwen]

...

Concerning RISC-V, what's the problem with an Open Source alternative?

It's vaporware. annoyingly and unsolicitedly pushed in every topic. oh, it's like Jehovah's Witnesses.
Would be a totally different story, if it really existed somewhere else, other than stupid near-almost-technology gnu/propaganda blogs. but so far, it doesn't. MIPS does exist, whose ripoff your RISCV is. it's open. and even schmopen. somehow, I don't see enthusiasm about it. why? gnu/influencers didn't tell you about it? it's just all so vanity talks. laughably irrelevant and absolutely out of reality. okay, you wanna chat about "big things", hapenning in the industry, that's normal, but why should it necessarily end up with moaning, generating tons of snivel about "endangering the Sacred Cow of Open Source"? come on, it's beyong cr4p!

...
when something "immature and overpriced" (and non-existent, worth to add) is being so aggressively advertized, it's a scam.

You do realize that Pine64 is in the process of releasing a product with a RISC-V processor?
It's due in the next few months.

True, it's using an embedded SoC, and not a very powerful one. (But, this won't be the first Pine64 product with a low power, low performance embedded SoC, see PineTime. To be clear, PineTime is NOT RISC-V.)

Here is the link;

Wiki - Pinecil

Some of the people stating they are considering RISC-V, (Western Digital), are ones that can then avoid processor royalty costs. Plus, benefit from tayloring the instruction set for their application. Like a hard drive controller SoC that has a sector checksum accelerator built in.

I personally want to see open source hardware like Ethernet controller chips. With TCP/SCTP/UDP off-load engines, perhaps using RISC-V.

But yes, RISC-V CPUs / SoCs that are equiv to a Raspberry Pi are currently vapor ware.