HN user

skunkpocalypse

37 karma
Posts0
Comments25
View on HN
No posts found.

Why don't all silicon chips have glitch and overvoltage detection?

Reliability. This is basically the microchip version of Boeing's MCAS.

The circuit you describe is not only an analog circuit, but is in fact a noise amplifier. You're now shipping a chip containing a noise amplifier that drives the device-wide reset line.

What could go wrong?

The stuff you describe is very, very difficult to get right, and beast-mode insanely difficult to troubleshoot or even diagnose when it goes wrong.

It's also very sensitive to manufacturing variations. So if there is a problem with the circuit, it'll probably only affect a few batches. Which, Murphy's Law and all, will be the batches that wind up in the hands of your most important customers.

Stuff like this can bankrupt a chip company if you get it wrong, and there's no way to be sure you got it right. At most you put it in your super-high-end ultra-secure product line, so long as that line's sales are small enough that you can afford a recall.

I am convinced that DJB is actually the reincarnation of John von Neumann.

Seriously, how many other people make contributions in areas ranging all the way from number theory to hand-written machine code?

XML screwed the pooch by trying to add namespaces after the 1.0 standard was published.

Handling namespaces correctly requires that the parser API be changed in non-backwards-compatible ways. This would have broken every single piece of code that used an XML parser. So instead, people mangled documents by simply flattening all the namespaces together if you tried using the old API.

This was a godawful nightmare and made everybody who was around at the time absolutely hate XML namespaces -- even those of us who know why they are so important. Plus namespaces are not exactly an "ELI5" topic, so a lot of lazy programmers looked at this and said "that's complicated, I don't want to learn it, HEY LOOK there's this older deprecated API that doesn't have them -- I'll use that!" So the old APIs became immortal and in fact gained additional users long after they were deprecated.

They should never have let the 1.0 standard out the door without namespaces in it.

I'm talking about 501 W Second Ave; the building has changed hands a few times, and you need to use more than just Google to see what's going on. For a while it was owned by some nonprofit called "Telephone Pioneers".

Legally the building is currently a condo: CenturyLink owns a few floors, AT&T owns a few floors. The building is valued north of $9.5 million and yet nobody has ever paid any property taxes on it (except six bucks a year for the soil and weed control district).

https://cp.spokanecounty.org/SCOUT/propertyinformation/Summa...

Paying zero property taxes is a dead giveaway for undeclared federal government facilities. They're the only ones who can thumb their nose at state tax collectors and get away with it -- and they take such pride in it that they can't resist doing so, even when it attracts attention.

If you view this link in a WebGL browser you can see the spooky-looking microwave horns (since removed):

https://goo.gl/maps/b7Yjn4DkydmX8kmR9

Lots of IXes used to be phone company switching offices way back in the day. The small ones are ugly (cinderblock huts) and the medium-sized ones are designed to not attract attention.

And then there's that unholy behemoth in downtown Spokane, which until a year ago had what can only be described as 20-foot-tall devil's horns on top of it... which by the way is immune from property taxes (check the county assessor's website) yet nobody seems to know why. We're talking about a 20+ story building that takes up half of a city block here.

My "daily driver" is a chromebook running linux: Samsung Chromebook Plus RK3399. Keyboard feel is identical to the good old macbooks.

Also: feather-light magnesium casing, gorgeous 300nit 2500x1600 screen, and 100% open-source: no blobs, no IME, no PSP. Coreboot, baby. No stupid Google G-chip.

Even recompiled the Embedded Controller firmware -- and not just for geek points. I customized the charging+wake behavior so it will wake immediately when AC power is applied even if the lid is closed -- never could get my mac to do that reliably, despite lots of third-party hacks claiming to make it happen. So now when I get home all I have to do is plug in AC power and I can access files on the laptop over the network -- no need to log in to the laptop, open the lid, or connect an external display. If it's got AC power it's awake and on the network.

Bonus: they're so cheap I bought several, and don't have to worry about damage. They take abuse amazingly well due to the alloy casing and the fact that they weigh so little. I expect to use these laptops for the next 6-8 years.

Ew, gross.

Crates.io is already a security trainwreck in progress. Do we really need to add even more attack vectors?

It's also solving a non-problem. I modify source code downloaded from crates.io zero times per day, so I compile each crate only once. Compile times matter for code I write myself: I modify (and therefore compile) that code dozens of times per day.

PEG Parsers 7 years ago

They've become somewhat unfashionable over the last decade not really sure why.

Much, much larger memory consumption than LR/LALR or even GLR. They're called packrat parsers for a reason.

Although the time complexity is asymptotically the same, LR-family parsers have such a tiny memory footprint that they usually run entirely in cache. Packrat tables never fit for nontrivial grammars+inputs. In practice this makes a big difference in performance.

Unfortunately city planners are appointed by officials who are elected by the CURRENT residents, not the potential future residents.

Preventing adequate construction is in the financial interest of current homeowners -- it inflates their property values due to artificial scarcity.

This won't change as long as city planners answer to those elected by existing residents.