Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

I Used Arch, BTW: macOS, Day 1

yberreby.com

Post reply on HN
Print view View original

101–110 of 110 posts

Re: I Used Arch, BTW: macOS, Day 1

#101

Post by LargoLasskhyfv »

mmcnl wrote: post #71
qudat wrote: post #40

Earlier quoted context omitted.

Why not just run an OS in a VM and full screen it?

Because it's very cumbersome. Managing with multiple audio devices and displays must be done in the host OS. Keyboard shortcuts might not work correctly. Gestures might not work correctly. Suspending and resuming is a pain, basically need to login twice. It's a lot of friction.

Do you even need to 'login' on a system which only you, personally is running in a VM?

I'd disable that as one of the first things. Just autologin with no password.

For the thing running in the VM, not the host.

Re: I Used Arch, BTW: macOS, Day 1

#102

Post by likeclockwork »

rollcat wrote: post #78
vouaobrasil wrote: post #52

Earlier quoted context omitted.

What about support for graphics? Does it work?

Yes, thanks to the heroic efforts of Alyssa Rosenzweig https://rosenzweig.io/ >, Asahi Lina https://www.youtube.com/c/AsahiLina >, and others. Unfortunately, a lot of this effort seems stalled by some of the Linux kernel developers' hostility towards Rust, which also prompted Hector Martin (marcan42) to leave the project. Now at the current rate, Apple is still moving backwards faster than the FOSS community is movin…

Is Rust the only programming language that is usable for this work?

Re: I Used Arch, BTW: macOS, Day 1

#103

Post by qn9n »

notpushkin wrote: post #57
Sytten wrote: post #21

My homebrew story is always something along the lines of: Me: Please install software A. Homebrew: In order to install it I will also install 20 libraries (some need to be built from source), update openssl, update Python and wreck all virtual environments. Also since its been a while I decided it must be time to upgrade your other unrelated packages. Enjoy!

I just use https://mise.jdx.dev/ for everything command-line nowadays, and keep brew for casks only.

I've been using this for a while now, much better versioning system. Great tooling support with multiple backends, fast and information rich CLI. Highly recommended over brew.

Re: I Used Arch, BTW: macOS, Day 1

#104

Post by sarlalian »

likeclockwork wrote: post #102
rollcat wrote: post #78

Earlier quoted context omitted.

Yes, thanks to the heroic efforts of Alyssa Rosenzweig https://rosenzweig.io/ >, Asahi Lina https://www.youtube.com/c/AsahiLina >, and others. Unfortunately, a lot of this effort seems stalled by some of the Linux kernel developers' hostility towards Rust, which also prompted Hector Martin (marcan42) to leave the project. Now at the current rate, Apple is still moving backwards faster than the FOSS community is movin…

Is Rust the only programming language that is usable for this work?

No, however it makes driver development easier and all the work to date is in rust, so changing languages would be exceedingly painful.

Re: I Used Arch, BTW: macOS, Day 1

#105

Post by sarlalian »

qudat wrote: post #40
jasoneckert wrote: post #11

For the same reasons, I prefer Linux - but also like Apple Silicon platform. As a result, I use Fedora Asahi Remix natively on the hardware. It's a few generations behind in support (M1- and M2-based systems right now), but I can't tell you how good it feels to be able to use Linux natively on Apple Silicon hardware. In my workflow, Fedora Asahi Remix runs at least twice as fast as macOS on the same hardware for any…

Why not just run an OS in a VM and full screen it?

That’s what Mitchell Hashimoto does.

Re: I Used Arch, BTW: macOS, Day 1

#106

Post by alexeiz »

For some time after the introduction of the M1 CPU Macbooks provided the best battery life experience. So it would make sense to use a Macbook if you wanted your laptop to work more than 4-5 hours unplugged. But now Intel Core Ultra series 2 and AMD Strix Point laptops are almost as good. Sure you won't get 20 hours of battery life, but you get about 10-15 hours and it's already good enough. Performance of Intel/AMD CPUs are also good enough: about M2 performance-wise. Sure they are a couple of generations behind Apple, but for most tasks it doesn't matter. Linux compatibility is also getting there. You can choose a Thinkpad if you want to be sure that Linux runs on it. But even many consumer-grade laptops are supported but Linux thanks to recent kernel updates. Essentially what I'm saying is that if you want a good laptop experience and you like Linux, you don't have to settle for Macbook anymore.

Re: I Used Arch, BTW: macOS, Day 1

#107

Post by rollcat »

likeclockwork wrote: post #102
rollcat wrote: post #78

Earlier quoted context omitted.

Yes, thanks to the heroic efforts of Alyssa Rosenzweig https://rosenzweig.io/ >, Asahi Lina https://www.youtube.com/c/AsahiLina >, and others. Unfortunately, a lot of this effort seems stalled by some of the Linux kernel developers' hostility towards Rust, which also prompted Hector Martin (marcan42) to leave the project. Now at the current rate, Apple is still moving backwards faster than the FOSS community is movin…

Is Rust the only programming language that is usable for this work?

So far nearly all of the kernel/driver code in the modern (~1990+?) history of osdev has been written in C/C++. However it appears that Rust can make you incredibly productive, at the very least in experimental/explorative development based solely on reverse engineering.

It's promising.

Re: I Used Arch, BTW: macOS, Day 1

#108

Post by timcobb »

crabique wrote: post #92
timcobb wrote: post #7

Earlier quoted context omitted.

Every time I need to update anything on brew, I end up updating thousands of packages and it goes on and on for a long time.

The trick for smooth experience is to treat it like `pacman -Syu`: brew update && brew upgrade && brew autoremove && brew cleanup && brew doctor Running this every few days and fixing everything that it explicitly complains about kept me issue-free for the last 10 years or so.

Interesting, thank you. That makes sense, but it is not convenient IMO.

Re: I Used Arch, BTW: macOS, Day 1

#109

Post by timcobb »

timcobb wrote: post #108
crabique wrote: post #92

Earlier quoted context omitted.

The trick for smooth experience is to treat it like `pacman -Syu`: brew update && brew upgrade && brew autoremove && brew cleanup && brew doctor Running this every few days and fixing everything that it explicitly complains about kept me issue-free for the last 10 years or so.

Interesting, thank you. That makes sense, but it is not convenient IMO.

I guess it could just be a cron job

Re: I Used Arch, BTW: macOS, Day 1

#110

Post by crabique »

timcobb wrote: post #109
timcobb wrote: post #108

Earlier quoted context omitted.

Interesting, thank you. That makes sense, but it is not convenient IMO.

I guess it could just be a cron job

I wouldn't recommend doing it from a cronjob, there are sometimes things that require sudo to update, breaking changes and important notes from Brew maintainers in the output. It's really important to inspect the output in order to see everything Brew doesn't consider normal.

Lately I'm running this like once every 2-3 weeks and it's still surprisingly nice to use. The problems only really manifest when you never run this "maintenance" snippet and only use the `brew install`, which will attempt to do the housekeeping stuff when you want/expect it the least.

Post reply on HN