I doubt many modern head units exist that don't rely on the Linux kernel

Rad, what's it running on? Is there a blog post or something to read?

Android depends on the Linux kernel

Those patch notes.. I have no issue reading AI code, but man AI writing is so grating for some reason

Ah yea from the original: 2024 Kia EV6, stock head unit

Oof you're right completely forgot.

So OP compiled the Linux kernel to the chip architecture, which was the real feat, and that is admirable

I know it isn’t.

No, you don't. You're either an LLM prompted to be an asshole or Dunning Krugering all over this thread and that is why people are calling you out. Because what OP did is pretty cool and no one actually likes an asshole who also clearly has no idea what they're talking about

Seriously gagged a bit reading that

Getting Nura running on a car head unit isn't just "compiling the kernel for a different architecture" and if you knew half of what you claim to know, you'd know that. That is, in fact, the easiest part and not "the real feat" by any means.

I've been working in Linux for almost 15 years without anything of the sort. False dichotomy

It's a fair point, but I think Linux users still often slip under the radar and that will be harder the more professional solutions there are

Direct responsibility is a stretch, but I don't think huge. You're responsible for what the people you hire do, that's just the way it works

Sure they are, it expands what is considered "industry standard" and that has far reaching effects.

I don't know the story but you don't have zero responsibility just because you used a subcontractor...

Security is constantly used as a guise for removing consumer rights and as someone who has been in the security industry for about 9 years I'm so sick of it.

First and foremost, everyone please understand: the user should be allowed to opt into your concept of insecurity: you do not know their threat model and you do not know their risk tolerance.

Using exploits in low level drivers in the wild is approaching APT level, and even if there were a simple one to use it'd likely be useless without some sort or local access to the device (bar some horror show bug in a Bluetooth or WiFi firmware). The risk is incredibly low for the average person. I'd put it pretty close to 0.

Wire transfers aren't instant and for large sums (your inheritance) the banks will likely require more than just a request from your app. If the bank cares about that then they can also use the attestation APIs which would be more than sufficient, as much as I hate them.

This boogey man of the APT going after my technologically illiterate with nation state level exploits needs to die. Long ago we entered a new era of security where it just isn't worth it to waste exploits. Especially when you can just text people and ask for their money and that works plenty well.

Security is not a valid reason to soft brick consumer devices at some arbitrary end of life date.

For anyone who really needed to see the conclusion.

And the entire sequence

::: spoiler spoiler

:::

Async features in almost all popular languages are a single thread running an event loop (Go being an exception there I believe). Multi threading is still quite difficult to get right if the task isn't trivially parallelizable.

The coordinated strike had an immediate impact. Millions of people in Dubai and Abu Dhabi woke up on Monday unable to pay for a taxi, order a food delivery or check their bank balance on their mobile apps.

I honestly can't tell if this paragraph is supposed to be satirical.

This is the most unsatisfying GIF I've ever seen. I hate it.

JavaScript alone is not a simple beast. It needs to be optimized to deal with modern JavaScript web apps so it needs JIT, it also needs sandboxing, and all of the standard web APIs it has to implement. All of this also needs to be robust. Browsers ingest the majority of what people see on the Internet and they have to handle every single edge case gracefully. Robust software is actually incredibly difficult and good error handling often adds a lot more code complexity. Security in a browser is also not easy, you're parsing a bunch of different untrusted HTML, CSS, and JavaScript. You're also executing untrusted code.

Then there is the monster that is CSS and layout. I can't imagine being the people that have to write code dealing with that it'd drive me crazy.

Then there are all of the image formats, HTML5 canvases, videos, PDFs, etc. These all have to be parsed safely and displayed correctly as well.

There is also the entire HTTP spec that I didn't even think to bring up. Yikes is that a monster too, you have to support all versions. Then there is all of that networking state and TLS + PKI.

There is likely so much that I'm still leaving out, like how all of this will also be cross platform and sometimes even cross architecture.