leucineleprec0n's comments

Instruction set baselines should ideally be well-regulated open standards. They should also be good, and not moronic academic projects running of 32B opcode space because of religious dedication to silly extensions and the uniformity of an ISA for saving pennies on microcontrollers to high performance CPUs.

RISC-V in principle is a great idea. Hopefully we’ll get something that’s at the caliber of a well-oiled machine backed by real experience and practical high performance use like Arm V8 and V9 someday that’s a bit more open, but as of right now RISC-V not only isn’t that on a technical level but is fighting some serious fragmentation.

https://www.theregister.com/2024/05/29/riscv_messsaging_stru...

And here’s David Chisnall on ISAs, which do matter:

https://queue.acm.org/detail.cfm?id=3639445

Surprisingly this page looks like it’s been updated more recently. They also added RISC-V support for Starnix recently.

This is naïve though. Regulation — especially such as this — has to be enforced and there is obviously room to over and under interpret the text of the law on a whim, or varying fines. OAI knows this and looking at the EU lately, what they’re doing is wise.

Yes. The whole “non-maneuverable” line is kind of a blurry one with modern algorithms/comms and the altitude adjustments possible

Yeah it’s not new, people have known.

I don’t think it was 50K in practice, published maybe but it was widely known it reach higher.

Absolutely. This is the primary reason those “UFO’s” AKA balloons and drones are concerning: Signals intelligence (and/or radar jamming in the same vein which the DOD reported has occurred off the coast of Virginia).

It’s alarming many leaped to suggest LEO satellites obviate the need for balloons/drones/spy planes because it really isn’t true; there are some things for which a proper resolution and capture is simply only possibly with proximity, at least more than a satellite has. In fact that’s why we still use U-2 spy planes (upgraded) and did for the balloon.

Given the number of unidentified drone/balloon incursions reported by the Pentagon in the last few years near ships and air force bases I do wonder what’s been exposed about our radars and or datalinks. It also doesn’t necessarily matter that the data is encrypted (a weird refrain I saw) because the operating frequencies and behavior of the emitters on our aircraft, ships is in and of itself valuable information.

Can you expand on this? Any links?

"But I actually think, 10 years from now, everyone in the world is going to be trying to figure out how [best] to use Fuchsia. I think there’s gonna be some serious competitive advantages that using Fuchsia is going to give companies, and they’re going to need to figure out how they’re going to adopt it. That’s where I think [Fuchsia] will be in about 10 years."

- Chris McKillop.

Google are also making Fuchsia compatible with the ADB tool for developers at the moment. (https://9to5google.com/2022/08/26/fuchsia-adb-proposal/) (https://fuchsia-review.googlesource.com/c/fuchsia/+/715977/)

And just finished their Fuchsia rollout for Nest Hub Max, with the rollout for the entry-level Nest Hubs completed last year. (https://9to5google.com/2022/08/24/nest-hub-max-fuchsia-rollo...).

I love the freedom Android provides what with the utter clusterfuck that is the Linux kernel’s driver interface and GPL. Yay freedom.

An MIT license is fine. Great, even, because Fuchsia is in fact still an open source OS.

Hardware OEM’s don’t owe the public transparent firmware blobs.

Right. This is what I think Fuchsia and Zircon probably are headed for long term but people really felt the compulsive contrarian need to stake out the experiment/retention project angle since so many saw the obvious but were hyperbolic about the timescale.

This is not true and it’s odd people still take this bait voluntarily. At best this line used to be cheap PR to avoid GPL and Linux disciples going ballistic and to keep media off the project as much as possible.

They’ve shipped Fuchsia on a real product now - the Nest Hub - they have Chrome working on Fuchsia, and an Android syscall interface in the works.

They removed this line from the site, possibly since it read as provocative, but for a few recent years they had updated Fuchsia.dev with “Fuchsia is not a science experiment”. Anyways, Google has a tendency to scrap projects as we all know but I don’t know if the recent trends point in that direction just yet, but it is possible - the project lead did leave recently and reportedly Meta were going to use Fuchsia for an AR/VR platform and switched to Android, likewise Google.

Google won’t be producing Ad Campaigns against GPL, no. Yet the licensing model of the Linux Kernel & the kernel developer policy towards drivers & driver interfaces effectively renders Android hostage. This complicates Android’s architecture greatly which is why they’ve spent exorbitant sums of time trying to ameliorate the damage.

Anyways, if you’re going to build an alternative or fork another stack —- you might as well hit two birds with one stone. Fuchsia’s relatively distinct capability-based, quasi-microkernel (it is not in fact a microkernel on a strict read) architecture is a chance to cleave off technical debt and start anew on security, and it’s relative modularity dovetails into the whole driver, kernel interface issue.

Frankly if the drivers didn’t suck hot shit I think many of us would.

First party bloat is arguably worse.

Jesus Christ, thank you. People act as if bullshit like TV and FaceTime are perfectly innocuous binaries without 6478 daemons molesting your memory irrespective of deliberate use & permissions.

God willing.

Dude it’s like some ancient web UI despite existing in the native settings software, it’s utterly slow as fuck to load and only faintly responsive to touch. It is clearly a deliberate ploy by Cupertino. Or in practice, an update is “not on the agenda this cycle”

Of course.

I may have talked to you about this, but I feel the same, iOS 7 also absolutely marred the sustained & graphical performance of the OS via the over reliance on increasingly n-dimensional neon or parallax bullshit whereas skeuomorphic design needed a lift but was nominally perfect by way of consistency and hardware demands. I miss Forstall a lot. I even feel their hardware today is designed a bit more sloppily. Idk, people cheered the departure of Ive or Forstall.

Really other than Tim whom I don’t care for — Craig Federighi is cog incarnate. Software has only had one good fucking release on iOS since 7 — that being iOS 12. I can’t even imagine how pernicious the internal influence has been on a normative scale adjusted toward “Apple design and UX of Forstall”