Live data from Hacker News

Asahi Linux Progress Linux 7.0

asahilinux.org

311–320 of 385 posts

Re: Asahi Linux Progress Linux 7.0

#311
post #100
post #96

Earlier quoted context omitted.

No, battery life isn't on par. The only way to get the battery life Framework advertised is on Windows' 'Ultra Efficiency' mode which cuts CPU performance by 25-50%, lowers brightness by 30% and deprioritizes everything in the background to such an extreme that responsiveness of those is measured in seconds. It is not comparable at all to M-series or Snapdragon laptops happily chugging along at full capability and ge…

They're talking about the new model announced, with a larger battery and ARM architecture. Not released yet, I don't think.

It's hard to imagine it'll come close to the complete MacBook package and it'll likely be similarly priced.

- Screen

- Speakers

- The unbelievable trackpad

- Battery life

- GPU performance (Linux gaming on this would be amazing)

Re: Asahi Linux Progress Linux 7.0

#312

I really hope this project continues to gain momentum. Apple Hardware + Linux is the least fscked OS running on the best hardware. MacOS continues to be a tire fire with endless bugs and churn between versions.

I've run all 3 major OSes before. MacOS by far has the least bugs and kinda just works. My variosu Linux adventures have always resulted in doing random patches for audio or screen incompatibility. My windows days were plagued with battery issues. I feel like most Linux ricers wishs for a MacOS-like experience, except with more customisation. (Which is entirely possible now with the ricing on Mac)

I agree that MacOS is more polished. However overall, Linux is a better complete package - especially for power users, gamers and engineers.

Linux GUIs are _fine enough_ though the jank is still present. The good news is they will get better with more users entering the chat.

The thing to note is that, we don't want to confuse "it's not as good right now" with "It's bad so I will never use it" because that signals a lack of interest.

There is a non-zero chance that Apple could be compelled to support it if enough people express interest (historically, they have with bootcamp).

Competition is good, even if the competition is bad right now. We must encourage it.

Re: Asahi Linux Progress Linux 7.0

#313
post #4

When I think about it, I don't understand why Apple wouldn't want to help this effort and just provide all the documentation. All the classic reasons ("competitive advantage", "secrets", etc) do not hold water in this day and age.

It feels very close to “right to repair”. The coffee grinder you bought came as a single package but it has burrs, gears, machine screws, a motor, etc. If one of those components fails, we should be able to replace it ourselves and as such they should be documented. The laptop has various pieces of hardware in it and corresponding drivers in macOS to make them tick. Did we buy the hardware and the drivers as an insep…

I think there is a strong case that "the right to repair" includes software. If that doesn't mean drivers must be open source, it should at least mean hardware is documented such that a driver can be written from it.

But the US still doesn't have the right to repair hardware, haha.

I hope the EU is listening. They won't get far with their sovereign software push if hardware cannot be used. Even on the Android side, you can't write an alternative to Android because all of the hardware has locked bootloaders and hidden drivers. Good luck reverse engineering the hardware/drivers on a Samsung Galaxy - let alone an iPhone or MacBook.

Re: Asahi Linux Progress Linux 7.0

#314
post #306
post #296

Earlier quoted context omitted.

DMIX was typically not an out of the box default, and had multiple shortcomings.

Even so, surely it would have been easier and better to just fix or replace dmix (in kernel, in the existing data path) than introduce a userspace daemon, break API compatibility, and so on. It’s been 20 years and pulseaudio is still flaky / high latency / incomprehensible. Professional flows that care use stuff like jack.

Doing audio mixing well is something that is, for a number of reasons, hard to do in kernel. And if you're still using pulseaudio, why? The rest of the world's moved to pipewire, which also provides a jack-compatible interface.

Re: Asahi Linux Progress Linux 7.0

#315

Earlier quoted context omitted.

In my personal experience macOS is fine but updates are often buggy or regress performance. Linux has just been the more polished option. Plus it just has a nicer desktop and apps.

I stay 1 major version behind with MacOS. If you do that you should have a pretty stable experience. You still get all the security patches but skip most bugs/regressions.

I stay 0 major versions behind with macOS and have a pretty stable experience.

Re: Asahi Linux Progress Linux 7.0

#316
post #199

Earlier quoted context omitted.

Little to no monetary benefit, hardware changes now need to be documented for Linux, loudest and most critical users but smallest volume.

> Little to no monetary benefit A 1-3% of the market out of the 5% that Linux already is, is little to no monetary benefit?

Apple has many easier ways to win 1-3% of 5%.

Re: Asahi Linux Progress Linux 7.0

#317

Earlier quoted context omitted.

This is the delulu Linux world thinking all over again. “Just get one with no dGPU, just this chipset, just this and this escoteric thing” and you’ll be fine.

This is how macOS works, too. "Just buy this M.2 adapter and this transcode card but not that GPU" and your hardware will be supported for two major releases.

The chip has a ton of rancid built into it what GPU are we buying to do what?

Re: Asahi Linux Progress Linux 7.0

#318
post #296
post #274

Earlier quoted context omitted.

ALSA had DMIX by default, all that before Pulseaudio. I remember Knoppix and a few more doing that.

DMIX was typically not an out of the box default, and had multiple shortcomings.

It was on tons user oriented distros.

Re: Asahi Linux Progress Linux 7.0

#319
post #306
post #296

Earlier quoted context omitted.

DMIX was typically not an out of the box default, and had multiple shortcomings.

Even so, surely it would have been easier and better to just fix or replace dmix (in kernel, in the existing data path) than introduce a userspace daemon, break API compatibility, and so on. It’s been 20 years and pulseaudio is still flaky / high latency / incomprehensible. Professional flows that care use stuff like jack.

TBH pipewire works much better than pulse, up to the point to replacing jack itself. But DMIX worked fine for non-professional user needs and with very low CPU usage. Yes, it was Jackd for the professional but Windows had ASIO drivers too.

Re: Asahi Linux Progress Linux 7.0

#320
post #318
post #296

Earlier quoted context omitted.

DMIX was typically not an out of the box default, and had multiple shortcomings.

It was on tons user oriented distros.

This is the era where I was the lead on Ubuntu laptop support, and I promise you that dmix was not a trivial option to make things work out of the box.
Post reply on HN