2,242 karma · joined May 9, 2015
Negative interest rates are supposed to spur investment elsewhere. However, negative rates have not led to the desired economic expansion in places like Japan that have had them for years.
Inflation is very low in Denmark, near a deflation point, which is generally considered bad. The bank is trying to spur inflation with these negative rates.
This takes you over Hayden Pass Rd. Here are some 4WD driving tips for the route: https://www.dangerousroads.org/north-america/usa/3939-hayden...
"It’s a real challenging road and a true test of your vehicle and your stamina because the road abounds in twists and turns with wheels sometimes hanging above the precipice."
"There is a very narrow section of shelf road before you get to the top that is very dangerous if icy. There are no rocks to stop you from sliding off the side. This section should not be attempted if there is any ice at all."
I'm a little surprised that Google gave this route to me with no warning. It's also comical to say you can get the drive done in 30 minutes.
I guess part of the difference is that you explicitly enumerate all hardware and drivers in a device tree on embedded rather than figuring it out on the fly like on a desktop/server machine.
At the end of the day, an OpenType font through substitutions can do far more crazy things than these "double glyph" examples. I once made a font that took a 3 letter acronym, substituted this for a hidden empty glyph in the font, then substituted this single hidden empty glyph into 20 glyphs. You were left with something like your U+1C4 in software where you could only highlight all 20 glyphs of none of them. And this was happening on text where all input code points were under 127. People often don't realize how much logic and complexity can be put into a font or how much the font is responsible for doing.
The HarfBuzz manual touches on some of this: https://harfbuzz.github.io/why-do-i-need-a-shaping-engine.ht...
I worked somewhere with a team of engineers who worked in LabView. They used LabView mainly for customized test equipment controllers and recorders and it worked well. They then branched into FPGAs for some straightforward dataflow signal processing and that also worked well. They then decided they were sick of how long it took software engineers to write device drivers for custom hardware and decided to do that in LabView with some tool that could generate C code from LabView. I got pulled into a meeting about it. I asked a couple important questions: how do you insert memory barriers and how can you write code that is ISR safe? It was clear the LabView folks had no idea about any of this. So I launched into a discussion about CPU architecture. They didn't really listen and everything was a hand wave, "LabView does that for you". It was clear they didn't want to hear my thoughts, so I let it go.
Fast forward 6 months and I get a frantic call from a manager if I had "bandwidth" to write a device driver in C for the same card where the LabView team was supposed to have written the driver.
I'd love to hear a credible source that says something on the lines of, "My understanding of the situation is that there is enough damage already done that a significant portion of the population, if not all of it, will be dead in the next half century, regardless of what's done."
There are crackpots on each side of the argument (skeptics versus doom). I think the truth is somewhere in the middle.