ianhowson

26 ms·

241.
by ianhowson 10y ago
I do both embedded development (day job) and web development (night jobs(s)) and it's not that embedded tasks are simpler, it's that you don't have to deal with a ridiculous stack of third-party code that is constantly changi
242.
by ianhowson 10y ago
Of course you could design a machine that can run for 60 years. It's just a bad idea to depend on it. A nuclear reactor has regulatory oversight and a risk management plan. It must survive the failure of any single component, no matt
243.
by ianhowson 10y ago
There are lots of building and HVAC systems with uptimes in the decades. 'Course, they're not running Linux.
244.
by ianhowson 10y ago
It's the former. You'd be insane to design critical infrastructure under the assumption that a single machine is going to stay up nonstop for 60 years.
245.
by ianhowson 10y ago
Cell is dead. There were a few similar machines -- Intel IXP comes to mind. They were universally difficult to program and did not provide a significant performance advantage once multicore x86 became cheap. ARM chips took the many-independ
246.
by ianhowson 10y ago
I studied with the Goethe Institute in Sydney and highly recommend it.
247.
by ianhowson 10y ago
On Cherry Browns, my managers believed that I was more productive because they could hear lots of key noise. I have Cherry Blues at home but wouldn't dare use them in an open-plan office environment - far too noisy.
248.
by ianhowson 10y ago
Story time. I transitioned an md RAID1 from spinning disks to SSDs last week. After I removed the last spinning disk, one of the SSDs started returning garbage. 1/3 reads are returning garbage and ext4 freaks out, of course. It's
249.
by ianhowson 10y ago
If your memory is error-free already, you'll be fine. If it's imperfect, ZFS will occasionally calculate a checksum wrong and write this to all drives in the array. At some point in the future, like when you read the file, the che