Debian GNU/Linux running bare metal on the Apple M1 with a mainline kernel

Seek tech partnerships with others lacking such time constraints and optimize shared responsibilities with existing partners. YOLO Time waits for no man.

> achieving great things when you're young requires a combination of hard work, privilege, and supportive adults (parents/teachers/etc) and most people just didn't (or don't) have the same opportunities.

I think that it's easy to externalize emotions about success in young people by projecting the help of an adult as the driving factor for that young person's success. Although this may be true in some cases, there are a large number of young motivated people who are just self-starters, with or without the resources of a backing adult.

I say this because, more than privilege or adult support, I think success at a young age boils down to hard work (as you've mentioned), having passion, and being prepared for luck, i.e. taking advantage of opportunities.

I think parents and teachers play a large role in the development of a person: this is obvious. What I'm not a fan of is when people lessen the success of a young person by shifting the accomplishment to be a simple cause of the environment in which they were raised, rather than the efforts and attitudes of the person who put the work in to accomplish what they did. Support ≠ doing it for them.

To summarize: I agree with your larger point (to not beat yourself up when seeing a great accomplishment at a young age) but disagree that success at a young age hinges on privilege and parents over luck and perseverance.

1. It's a protected job in most countries 2. It's just boring for kids.

In addition with programming you can create and mod games which is how a lot of people start their first programming steps as a kid. Kids don't just start programming because they think hmm I want to program. No they want to do something and to do it they have program. There is 0 incentive for a kid to do notary work.

Unfortunately, “just” running code in kernel mode is incredibly hard on the iPad. There’s e.g. a hardware mitigation that turns a memory region to read-only and also only allows kernel code to run from this region. This mitigation is locked down and cannot be disabled once XNU is running on the iPad (http://siguza.github.io/KTRR/).

On top of that page tables are also protected by a “kernel within the kernel” (https://blog.svenpeter.dev/posts/m1_sprr_gxf)

Getting past all that is going to be very hard if not impossible.

Yes it's costly, restrictive, the hardware still has some flaws and you can't replace parts but most Apple users, myself included, are happily paying the price.

I have an M1 Macbook Pro for a few months now and it's blazingly fast, the battery lasts for 15-20 hours and I've only heard the fan for a few minutes so far while stressing it with heavy compilation. Under normal circumstances it's entirely silent. I wouldn't trade it for anything else at this point.