Live data from Hacker News

What is RISC-V and why it matters to Canonical

ubuntu.com

91–100 of 129 posts

Re: What is RISC-V and why it matters to Canonical

#91

Earlier quoted context omitted.

I think 10 years is a more realistic estimate. Probably first in servers and Android phones.

They are everywhere already in microcontrollers like ESP32.

Yeah but op was talking about directly using a RISC-V computer. The embedded RISC-V CPUs are effectively black boxes.

Re: What is RISC-V and why it matters to Canonical

#92
post #9
post #3

Earlier quoted context omitted.

unironically, this. i've been hearing about arm computer for almost twenty years and only just recently general-purpose decently-priced arm laptops have been released (qualcomm laptops, the macbook neo). and arm desktop are still not a thing, in practice.

I have an ARM desktop from 1986 or 1987 https://chrisacorns.computinghistory.org.uk/Computers/A500.h...

technically true, practically irrelevant.

Re: What is RISC-V and why it matters to Canonical

#93
post #4
post #3

Earlier quoted context omitted.

unironically, this. i've been hearing about arm computer for almost twenty years and only just recently general-purpose decently-priced arm laptops have been released (qualcomm laptops, the macbook neo). and arm desktop are still not a thing, in practice.

Well, Apple M1/M2/etc. are, technically, ARMv8, and they're available as desktops.

they're not general-purpose in the sense that you can run any operating system nor they're decently priced.

Re: What is RISC-V and why it matters to Canonical

#94
post #31

Will RISC-V end up with the same (or even worse) platform fragmentation as ARM? Because of absence of any common platform standard we have phones that are only good for landfill once their support lifetime is up, drivers never getting upstreamed to Linux kernel (or upstreaming not even possible due to completely quixotic platforms and boot protocols each manufacturer creates). RISC-V allows even higher fragmentation…

PC/x86 was an extreme outlier, sadly, and it was because of Microsoft/Intel business model. The architecture details was historically mostly decided on by Wintel, yet the system integration was done by many vendors, whose best interest was to stay as compatible as possible. Its unlikely that another platform would be able to reach this state, the PC architecturing was subsidized from the M$ software monopoly that nobody would have wanted to suffer thru again.

Re: What is RISC-V and why it matters to Canonical

#95
post #47

I stopped listening to what Canonical says. They often get involved in things and disturb the ecosystem then abandon stuff or dig a "not invented here" hole. Unity, Bazaar, Mir, Upstart, Snap, etc. All of them had existing well established projects they attempted to uproot for no purpose other than Canonical wanted more control but they can't actually operate or maintain that control.

Snap is definitely not abandoned.

Snap is a terrible. It's the reason why I stopped using Debian based distros after decades for desktop usage.

Lying to users and turning apt install commands into shims for a barely functional replacement was disrespectful. Flatpak was and still is better, but even then if I say I want a system package you give me a system package. If you have infrastructural reasons why you cannot continue to provide that package then remove it, Debian based systems have many ways to provide such things.

Canonical did it because they wanted to boost Snap usage and if failed while sending a clear message they don't respect their user base.

Re: What is RISC-V and why it matters to Canonical

#96
post #47

I stopped listening to what Canonical says. They often get involved in things and disturb the ecosystem then abandon stuff or dig a "not invented here" hole. Unity, Bazaar, Mir, Upstart, Snap, etc. All of them had existing well established projects they attempted to uproot for no purpose other than Canonical wanted more control but they can't actually operate or maintain that control.

Snap is definitely not abandoned.

[deleted]

Re: What is RISC-V and why it matters to Canonical

#98
post #83

Earlier quoted context omitted.

Wayland was created in 2008. Mir was created in 2013. Bazaar and Git were created around the exact same time. Unity was abandoned after a failed attempt to circumvent Gnome 3. I was actually involved with the development of Compiz and they hired Sam to work on Unity, as he was one of the masterminds behind Compiz, but again they just didn't have the vision or execution to make it work.

Unity was great, after it was abandoned I tried yet again GNOME 3, me that in the past have collaborated with Gtkmm, ended up moving into XFCE, and nowadays I am fully on macOS/Windows anyway. If I ever go back to GNU/Linux full time, GNOME certainly won't be it.

Things improved a lot with Gnome over the years, but as a fellow Gnome 2 user the initial release of 3 and the following years were a real kick in the teeth.

Things have improved, but the overall Gnome Foundation attitude hasn't improved. They are still very stubborn and remove basic features. This seemed to start when they did their infamous "focus groups" where they claim users can't understand basic things.

I get the desire to provide a cohesive experience, but I think you can do that while also giving people control.

KDE is shaping up to be much better and it's likely because Valve is providing commercial support and exposing it to a larger audience.

Cosmic is the new kid backed by system76 and its pretty nice too and may rescue Gnome in some ways in due time.

Re: What is RISC-V and why it matters to Canonical

#99

I stopped listening to what Canonical says. They often get involved in things and disturb the ecosystem then abandon stuff or dig a "not invented here" hole. Unity, Bazaar, Mir, Upstart, Snap, etc. All of them had existing well established projects they attempted to uproot for no purpose other than Canonical wanted more control but they can't actually operate or maintain that control.

In a way it's really sad how many swings and misses Canonical has taken in its history.

I'm fine with a company getting things wrong from time to time. What I don't like is the attitude where they walk into the room and start moving the furniture around while smugly dismissing or ignoring talented and established people. Then after a bit of milling around they just give up and leave the room and everyone has to clean up the mess.

Re: What is RISC-V and why it matters to Canonical

#100

I stopped listening to what Canonical says. They often get involved in things and disturb the ecosystem then abandon stuff or dig a "not invented here" hole. Unity, Bazaar, Mir, Upstart, Snap, etc. All of them had existing well established projects they attempted to uproot for no purpose other than Canonical wanted more control but they can't actually operate or maintain that control.

I was honestly wishing Ubuntu would keep upstart alive. I preferred it as init system.

That is half the problem. They often introduce neat ideas, but then fail or refuse to integrate them with he rest of the FOSS ecosystem. Then anyone who subscribes to their experiment is left cleaning up the mess and trying to migrate the features or ideas they like to the remaining projects that should have been extended in the first place.
Post reply on HN