> 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.
Exactly. If I were to update this code, for IPv4 blocking, I would allow it to block /32 (single IP) and /24 networks. For IPv6 blocking, I would allow blocking a single IPv6 address, a /64 range, and (for extreme offenders) a /48 range.
One way to do this is to have multiple hash tables: One for single IPv4 addresses, one for IPv4 /24 ranges, one for single IPv6 addresses, one for /64 IPv6 ranges, and one for /48 IPv6 ranges. Note that while the hashes have (generally speaking) a “big O” of 1, we need to perform one additional operation per range size. IPv4 /32 and /24 blocking requires two lookups, and IPv6 /128, /64, and /48 blocking requires three lookups.
You forget laserdiscs, smaller videocameras, DVDs, and online payment systems ...
It's also probably the only thing really using VR/AR right now to any significant degree.
It used to be that there was a porn convention at the same time as CES in Las Vegas. For a lot of years, the porn conference was the better of the two from a technology standpoint.
Don't forget the role in testing censorship laws. It is fantastic in a way. Always a wet finger in the air to see in which direction it is blowing, constantly asking "how can I make money from this?".
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.
Alternatively, they should have made it more backwards compatible and, most importantly, heavily pressured implementers not to be complete slackers about usability. The cycle I've seen most frequently was something like this:
1. User gets a simple XML file and writes XPath, XSLT, or other code which says `/foo/bar`, which fails.
2. User notices that while it's written as `<foo><bar>` in the source, it's namespaced globally so they change code to use `/ns:foo/ns:bar`, which also fails.
3. User does more reading and realizes it needs to be `/{http://pointless/repetition}foo/{http://pointless/repetition... or something like repeating the document-level namespace definitions on every call so their `ns:foo` is actually translated rather than treated as some random new declaration.
4. User does something hacky with regular expression to get the job done and at the next chance ports everything to JSON instead, seeing 1+ orders of magnitude better performance and code size reductions even though it's technically less correct.
That experience would have been much less frustrating if you could rely on tools implementing the default namespace or being smart enough to allow you to use the same abbreviations present in the document so `<myns:foo>` could be referenced everywhere you cared about it as `myns:foo` with the computer doing the lookup rather than forcing the developer to do it manually.
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.
Are you talking about the CenturyLink CO in downtown Spokane? Google "AT&T Long lines" for more info.
The main IX point for Spokane is not that building, because it's not carrier neutral, but rather is the US Bank building right in the center of downtown.
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).
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):
There really isn't anything magical about that building, somewhat smaller versions or larger versions are in every city in the USA and Canada. It's a CO (central office). If you see a building in a central location with a suspicious lack of windows, lots of air handlers and generators and a few local telephone company trucks parked outside, that's what it is.
Back in the day those were the central points for switching of all analog dialtone POTS phone lines. Now they are of course major fiber sites for whoever is the ILEC (incumbent local exchange carrier) in the city, which in this case is Centurylink.
Other local examples would be:
Bellingham, intersection of Chestnut street and Forest (centurylink)
Everett, 2604 Rockefeller Ave (frontier)
East Wenatchee: on Eastmont Ave, between 10th St NE and 11st St NE (frontier)
Olympia: Corner of Washington St NE and 8th ave SE, northeast side (centurylink)
