HNHacker News
TopNewBestAskShowJobs

leucineleprec0n

94 karma · joined May 23, 2021

submissionscomments
leucineleprec0n··on Instruction Sets Should Be Free: The Case for RISC-V [pdf] (2014)
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

leucineleprec0n··on Making Linux Syscalls in Fuchsia
Surprisingly this page looks like it’s been updated more recently. They also added RISC-V support for Starnix recently.
leucineleprec0n··on Ask HN: Is it just me or GPT-4's quality has significantly deteriorated lately?
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.
leucineleprec0n··on US jet shoots down unknown object flying off Alaska coast
Yes. The whole “non-maneuverable” line is kind of a blurry one with modern algorithms/comms and the altitude adjustments possible
leucineleprec0n··on US jet shoots down unknown object flying off Alaska coast
Yeah it’s not new, people have known.
leucineleprec0n··on US jet shoots down unknown object flying off Alaska coast
I don’t think it was 50K in practice, published maybe but it was widely known it reach higher.
leucineleprec0n··on US jet shoots down unknown object flying off Alaska coast
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.

leucineleprec0n··on Is Apple letting another AI opportunity slip away? – Macworld
Can you expand on this? Any links?
leucineleprec0n··on Interview: Fuchsia’s past, present, and future, as told by ex-director
"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...).

leucineleprec0n··on A Kernel Hacker Meets Fuchsia OS
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.

leucineleprec0n··on A Kernel Hacker Meets Fuchsia OS
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.
leucineleprec0n··on A Kernel Hacker Meets Fuchsia OS
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.

leucineleprec0n··on A Kernel Hacker Meets Fuchsia OS
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.

leucineleprec0n··on If Apple keeps letting its software slip, the next big thing won’t matter
Frankly if the drivers didn’t suck hot shit I think many of us would.
leucineleprec0n··on If Apple keeps letting its software slip, the next big thing won’t matter
First party bloat is arguably worse.
leucineleprec0n··on If Apple keeps letting its software slip, the next big thing won’t matter
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.
leucineleprec0n··on Decreasing service fees on subscriptions to 15%
God willing.
leucineleprec0n··on Decreasing service fees on subscriptions to 15%
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”
leucineleprec0n··on Decreasing service fees on subscriptions to 15%
Of course.
leucineleprec0n··on M1 Inside a G4 Sunflower iMac
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”

leucineleprec0n··on Samsung and AMD will reportedly take on Apple’s M1 SoC later this year
Indeed and the reported Exynos GPU utilizing AMD IP is likely a bit hot on phones but the sustained leaks for 3D games look promising, if they are accurate in that they were recorded for sustained activity then it sets a sort of upper bound on the power draw given it’s in a phone.

Peak:

https://twitter.com/fronttron/status/1430192491450363913?s=2...

Sustained:

https://twitter.com/fronttron/status/1434492507283279884?s=2...

leucineleprec0n··on Samsung and AMD will reportedly take on Apple’s M1 SoC later this year
Edited for harsh tone.

The TDP is a non-standardized marketing term. You know what is fairly standardized? Watts.

Please Read The TDP is not the wattage consumed during peak load when these chips — or the constituent cores I should say — actually hit these single or multithreaded benchmarks. It’s merely a “hey this is roughly what this chip will consume at the base clock rate or the system is capable of dissipating with said chip after turbo boosting” and even then with cTDP of recent years it’s not invariably worth that much.

It’s not even funny how far ahead Apple & ARM reference cores on high-density/low-power libraries are in this regard.

leucineleprec0n··on Samsung and AMD will reportedly take on Apple’s M1 SoC later this year
Lol they use off the shelf ARM cores again, and the major issues since the custom cores of years past have dissipated. Sure, Qualcomm adds a slight bit of low-level code and has a different power policy on the 888 vs the 2100, but it’s not actually that different and both are on the Samsung 5NM (by nomenclature anyways) process, which is what actually draws criticism in terms of “Samsung” in the context of SOC’s as of 2021. The reason is simple: the density of the process is solid (EUV and all come in handy) but the leakage is rather disproportionately poor for given points toward the upper range of the voltage-frequency curve e.g. 2.7-3GHz, where mobile “big” or “huge” cores tend to run such as the Cortex X1, Cortex A78 which are both found in the former two SOC’s from Samsung and Qualcomm.

In other words: Samsung and Qualcomm are both behind Cupertino in CPU single-threaded performance but it’s worth noting why this is especially bad: ARM still optimizes for performance per area/efficiency with reference cores & furthermore the implementations of these cores by Samsung and Qualcomm do not utilize remotely as much cache that ARM recommends for the Cortex X1 nor L3 (4MB, but they could go to 16!) which is typical, and the 888 actually reduces the maximum frequency of the X1 (2.84GHz - as ppposed to topping out at 3.09/3.1 like ARM spec or as with their last SOC, the 865) presumably because they deemed the power trade-off not worthwhile for their mainstream flagship chip. Throw in Samsung fab inferiority (to TSMC) and the engine lights here just stack up.

Microsoft is reportedly using an X1 & A710 on a TSMC 5NM process, which is odd given they ought to use an X2 but whatever. Qualcomm and Samsung’s X1’s score 1000-1100 on Geekbench 5’a Single thread test, which is indeed an excellent ledger of general performance. With TSMC 5NM & more cache, this chip is going to have phenomenal performance per watt and accounting for the Windows Geekbench penalty probably have X1’s hitting 1200 in single thread tests, which is about 500 off an M1, but also at less power - ARM quotes the X1 on TSMC 5NM (which Microsoft will be using instead of Samsung 5NM) as a 3.2-3.6 watt core at peak. The A710’s? We’re talking about a 1W profile (and 800-100 GB5 performance if the A78’s are anything to go by, and an absurdly high performance to area ratio).

And really, this is just about providing a decently performant ARM option that retains the ever-obvious performance per watt advantage. The Qualcomm 8CX is just not powerful enough, because it uses old Cortex A76 cores, as does Microsoft’s dogshit SQ1/2. Battery is life is reportedly solid though.

This is one big step in actually hitting “good enough” for ARM on Windows. It’s about competing with X86 and keeping the Windows ecosystem competitive with Apple’s offerings, not necessarily beating them overnight.

leucineleprec0n··on AMD’s Lisa Su
It flies and stops halfway in the face. Apple’s developer tool chains (at least, for iOS and the world of mobile apps and games, Metal notwithstanding) are decent, their codebase is at least a cleaner implementation than what Google have with the combined GPL & refactoring nightmare of the Linux kernel & Android (to be solved by my beloved Fuchsia in time, surely) — but it’s not as if Apple are really a shining light on software overall. To be honest, they absolutely suck. C+ tier stuff. iOS background management, iOS & MacOS UI since iOS 7 & Big Chu—Sur respectively, woefully inadequate security defense on all systems, an AWFUL file manager on MacOS dubbed “Finder”, garbage implementation of Bluetooth and WiFi antennae status on control panel, no iOS option for reasonable DPI scaling (zoomed doesn’t count), excessive font smoothing only modifiable via Terminal as of MacOS Big Sur — excessive use of advanced animation and sickening transparency leading to poor performance on hardware that makes Android or Windows fly. Oh, no option to delete all messages at any given time via a simple “select all” button in the edit bar for Messages, nor an ability to export all messages to a fricking plaintext file or HTML.

The list continues, and is a long one worthy of a short documentary. Apple excels at a few interface consistencies and at selling premium hardware with high margins in part due to an admittedly deserved proficiency with supply chain consistency & scale, and with convincing customers to pay with their kidneys for marginal upgrades e.g. 400% up charges on RAM and Storage.

The M1 is impressive, certainly agree, but it won’t be too long before others catch-up. Still, let’s not get ahead of ourselves about Apple and software prowess. It’s been a long time since I preferred Cupertino’s code to Redmond’s or Mountain View’s.

leucineleprec0n··on M1 Icestorm cores can still perform well
Yeah, no. The libraries used can and do differ.
leucineleprec0n··on M1 Icestorm cores can still perform well
Indeed, thank you. It's plainly pathetic this has to be said so often, especially here FFS. Every time this topic comes up "AMD can do the same, 15W" as if the "15W" figure was a terminating value from a set of industry-standard "TDP" figures. It is not, and the "TDP" listed at best offers a clue as to the power draw. Not much more. Hell, it can even differ by motherboard config. Intel encourages it.

The next emotional preservation tactic usually cites the old GF IO Die, but that was only on H/desktop series chips anyways and furthermore they still lose to Apple in sheer performance per watt.

It's August 2021 and we still have to have this conversation. Sigh

leucineleprec0n··on Google Pay team reportedly in major upheaval after botched app revamp
The moment I downloaded the new version, without even having used Gpay for years — I knew — I knew they used some web-based or write-once bullshit just by the latency in the tab swipes alone, I can discern it distinctly and am sensitive to these deficits in performance (unfortunately).

Then I thought, "ah shit" searched "Flutter Gpay" and sure enough.

Sigh. When will they learn.

leucineleprec0n··on Apple's child protection features spark concern within its own ranks: sources
It's arguable Android, even stock, is better for privacy
leucineleprec0n··on A Guide to RCS, and Why It Makes Texting So Much Better
Ah that's kinda what I meant but incidentally elided that they had convened on Google's implementation in particular.
leucineleprec0n··on Do you like to read? I can take over your Kindle with an e-book
Dialing in the precise transformations needed for every copy got so annoying I eventually accepted the botching.
Page 1 of 3Next →