HNHacker News
TopNewBestAskShowJobs

GrilledChips

72 karma · joined June 2, 2022

submissionscomments
GrilledChips··on More on whether useful quantum computing is “imminent”
the funny thing is that nobody will ever do that. The moment someone uses quantum computing or any other technology to crack bitcoin in a visible way, the coins they just gave to themselves become worthless because confidence collapses.
GrilledChips··on More on whether useful quantum computing is “imminent”
In the 60's we actually had extremely capable, fully-developed computers. Advanced systems like the IBM System360 and CDC 6600.

Quantum computing is currently stuck somewhere in the 1800's, when a lot of the theory was still being worked out and few functional devices had even been constructed.

GrilledChips··on More on whether useful quantum computing is “imminent”
tbh they could just be pushing for people to adopt newer, less-tested, weaker algorithms. switch from something battle-hardened to the QuantResist2000 algorithm which they've figured out how to break with lattice reduction and a couple of GPUs like those minecraft guys did.
GrilledChips··on More on whether useful quantum computing is “imminent”
It turns out they're not so useful for chemistry. https://www.youtube.com/watch?v=pDj1QhPOVBo
GrilledChips··on More on whether useful quantum computing is “imminent”
I will never get used to ECC meaning "Error Correcting Code" or "Elliptic Curve Cryptography." That said, this isn't unique to quantum expectations. Faster classical computers or better classical techniques could make various problems easier in the future.
GrilledChips··on More on whether useful quantum computing is “imminent”
More recently it's turned out that quantum computers are less useful for molecular simulation than previously thought. See: https://www.youtube.com/watch?v=pDj1QhPOVBo

The video is essentially an argument from the software side (ironically she thinks the hardware side is going pretty well). Even if the hardware wasn't so hard to build or scale, there are surprisingly few problems where quantum algorithms have turned out to be useful.

GrilledChips··on Statement from Scarlett Johansson on the OpenAI "Sky" voice
It's also possible that any such enunciation is being hallucinated from the text by the speech model.

AI models exist to make up bullshit that fills a gap. When you have a conversation with any LLM it's merely autocompleting the next few lines of what it thinks is a movie script.

GrilledChips··on Why Rust cannot replace C++
"There is now a bullet hole in your foot."
GrilledChips··on Helios: A distribution of Illumos powering the Oxide Rack
You'd have no idea that it isn't Linux. You don't run code on this OS, you run code on VMs that it provides.
GrilledChips··on Helios: A distribution of Illumos powering the Oxide Rack
This isn't NetBSD. NetBSD broke off loooooooong after the release of BSD that Sun used to build this OS.
GrilledChips··on Will the new judicial ruling in the Vizio lawsuit strengthen the GPL?
The reasoning of this case rests on the intentions of the FSF when they wrote the licence. If the person who wrote the licence didn't intend you to be able to get benefits, you can't.
GrilledChips··on Fedora Asahi Remix
afaik there has always been the option to install alongside during the installer. It might not even be possible to do otherwise if you're installing from macOS itself.
GrilledChips··on Fedora Asahi Remix
The page has per-machine lists of available and unsupported features. The only mac that doesn't have audio right now are the M1 imacs, due to their speakers working differently than the laptops. They're not that different though, so I expect they'll be working in a couple of months.
GrilledChips··on Intel Itanium IA-64 Support Removed with the Linux 6.7 Kernel
It wasn't the technical side that caused the schedule slips. It was constant competition with other aspects of the business, especially the VAX lineup. The VAX 9000 in particular was a $3 billion money pit that didn't make back even 25% of it's development costs and was repeatedly chosen over development of prism and later alpha. Even when it came down to the embarrassingly fast NVAX chip vs the even faster Alhpa, DEC still couldn't get the story straight and lost valuable VAX customers when they could have offered a faster VAX and an upgrade path to Alpha.
GrilledChips··on Intel Itanium IA-64 Support Removed with the Linux 6.7 Kernel
It wasn't the cost of alpha. It was the bleeding all through the rest of the company.

DEC's terminals? killed by PCs. The VAX lineup? killed by RISC chips, and the VAX 9000 consumed a huge chunk of their cash reserves before embarrassingly being rendered obsolete by their own NVAX.

This was a time of change from minicomputers to microcomputers and DEC made costly decision after costly decision. They kept selling off profitable "non-core" portions of the business that in the process incurred a loss.

GrilledChips··on Intel Itanium IA-64 Support Removed with the Linux 6.7 Kernel
Sun was one of the few processor makers who were sceptical and decided to wait and see before cancelling plans for their architecture, and it's nice to hear that worked out for them for a bit before 64-bit x86 ate their lunch.

Of course, it's also possible that by that point Sun was already paralysed by infighting between various splinter groups, with no big bad DEC to fight against.

GrilledChips··on Intel Itanium IA-64 Support Removed with the Linux 6.7 Kernel
It's kind of funny. There are lots of architectures it killed (Alpha, PA-RISC, basically everything except SPARC because Sun was sceptical) but basically all of them have outlived it in the linux kernel.

It killed their manufacturing based on hype, where as they all established a firm install base before itanium ever got rolling, which has ensured they continue to be (halfheartedly) maintained.

GrilledChips··on OpenAI has quietly changed its 'core values,' putting greater emphasis on AGI
openAI self-selects only people who drink the AGI koolaide. Its the only way to get a job/keep a job there.
GrilledChips··on OpenZFS 2.2: Block Cloning, Linux Containers, BLAKE3
There's fuck all that ZFS can do if hardware lies about what has or hasn't been written to disk yet. There have to be points where ZFS blocks until something critical has been absolutely, totally, 100% written to disk before continuing. Unfortunately, USB devices lie all the time.
GrilledChips··on OpenZFS 2.2: Block Cloning, Linux Containers, BLAKE3
There's fuck all that ZFS can do if the drive lies about what has or hasn't been written yet, journal or no journal. USB devices are known to do this all the time.

If the drive lies and says that part of the journal has been written when it hasn't yet, and ZFS goes ahead and writes the next part of the journal, then when you unplug the drive and the first part of the journal goes away (which the 2nd depended on) you're hosed. There have to be places where ZFS blocks until something critical has definitely, absolutely, been written to disk.

At that point the only thing ZFS can do is try to unwind back to whatever it thinks is a consistent state, but this isn't 100% guaranteed. (it depends on what old data is still hanging around)

GrilledChips··on OpenZFS 2.2: Block Cloning, Linux Containers, BLAKE3
It would go against a fundamental principle of ZFS' design for changing a setting like that mid-flight to not be safe.
GrilledChips··on OpenZFS 2.2: Block Cloning, Linux Containers, BLAKE3
This is a bad idea.

If you want repair, you need to either set more than one copy in ZFS (still pretty dumb) or use multiple drives in a raidz (or mirror, though raidz is more efficient).

When you try to partition a drive like this (or configure ZFS to write multiple copies) you loose everything in the event that the whole drive fails. Honestly, it's a far better plan to just use multiple drives in a raidz so that whole-drive failures can be reconstructed in addition to data corruption.

GrilledChips··on OpenZFS 2.2: Block Cloning, Linux Containers, BLAKE3
Use raidz.
GrilledChips··on OpenZFS 2.2: Block Cloning, Linux Containers, BLAKE3
A scrub can both detect and repair damage. You don't need to set additional copies. If you don't want to buy 4TB of drives to store 2TB of data in a mirror, use a raidz instead.

In a raidz with at least one parity disk (and any number of data disks), corruption found on any data disk can be repaired immediately. For non-overlapping corruption a single parity disk is enough. If you have corruption of the same block on two different disks (extremely unlikely) then this can be repaired if you have two parity disks. (Etc. for three identically-corrupt data disks and three parity disks)

You can have eg. two parity disks and eight data disks (or more) and so long as no more than two disks are corrupted in the same block at the same time then a scrub will repair it completely.

The system of parity disks in ZFS' raidz is meant for reconstructing entire failed data disks, so fixing corruption is no big deal.

GrilledChips··on Raspberry Pi releases RP1 peripheral controller datasheet and block diagram
Decoupling. The raspi pin header is a defacto standard. The raspi foundation have to maintain a very high degree of compatibility with it. Have a look: https://raw.githubusercontent.com/pinout-xyz/Pinout.xyz/mast...

See all those various overlapping functions? It's the combination of functions on every pin that has to be mimicked too.

Even though the raspi foundation get a fair degree of customization from broadcom, putting peripherals on a chip gets harder for process reasons as you push for performance. This is the same reason why the M1/M2 implement the eUSB spec and have external eUSB repeaters, instead of putting it fully on-chip. The foundation clearly want to go in the direction of increased performance, so it makes sense to push all that messy GPIO stuff off onto a custom chip, get additional cost reduction from including ethernet and USB (fewer chips), and also continue to build their chip design acumen.

I wouldn't be surprised if arduino go this way too. They're already severely limiting themselves in performance and ram by selecting a 5V ARM chip, and matching the exact peripheral combination of the atmega328 is just as much of a millstone around their neck too. They could go with a much cheaper and faster arm core communicating with an AVR chip to manage the IO pins and have a significantly more capable board. Lots of 3rd party AVR+ESP32 boards already do this.

GrilledChips··on Qualcomm shook down the cell phone industry for almost 20 years (2019)
This is a common misconception about patents.

They were never intended to reward innovation. They do intentionally grant fixed-duration monopolies.

Patents were intended to encourage companies to disclose trade secrets, forwarding public knowledge. In return, that company is granted continued exclusive use of the idea, as if it had never been revealed. This is also why ALL patent drawing are in the public domain.