Fun blog, but I was left hanging as the author never found the issue with the OS level driver (and instead <spoiler>used a workaround library</spoiler>).
It's easy to just blame the FTDI driver, but FTDI is used all over the place in the arduino community on MacOS, so I would have have assumed it was working.
But we're moving the emissions in a "more solvable" direction. By consolidating the emissions from millions of cars to hundreds (thousands?) of plants, we're making it a MUCH easier problem to address.
Maybe I'm missing something, but no matter how efficient a heat pump is, doesn't it have a limit on how much heat it can pump as ∆T increases?
Even here in western NY we occasionally have to deal with -10 F (-23 C) weather for a week and so that's a pretty big temperature delta if you want a comfortable 68 F (20 C).
Combine that with the fact that gas is still quite a bit cheaper per unit of energy than electricity (in my area) and a heat pump just doesn't make any sense.
The ability to have a single unit heat and cool is definitely nice, but without a geothermal-like ambient temperature to work with, I just don't see this working out, even with all the insulation in the world.
But that comes at the expense of complicated software. Sure, once you've gone through the effort of procuring all that hardware, configuring it to run Kubernetes, reconfiguring your software to run in containers... you're good to go.
Mainframes allow you to easily scale your software vertically (but at the expense of complicated hardware). That might seem silly in today's world, but a lot of the software running on Z was written decades ago and the risk of rewriting it is extremely high.
I was wondering the same thing myself. I'm guessing they tested it and found that it hit every coordinate at least once and said "good enough". Meaning, I don't think it's guaranteed, they just picked one that did.
The interesting thing is that you're guaranteed to always have a different number because otherwise the cycle would restart. So you just need to find a sequence that's long enough.
Egress pricing for Google and AWS (sans Lightsail) continues to be one of the biggest price differences between them and smaller hosts such as Linode and DigitalOcean.
I think Google missed an opportunity here. They should have cut the prices more significantly for standard tier (sacrificing performance) to make this more competitive.
Right now Linode's and DO's smallest $5 plan offers 1TB of transfer, which would cost $85.00 on Google's new standard plan.
He's trying to make his audio easier to listen to by using various effects provided by Ardour. The most significant of what he listed is the compressor, which is great for spoken podcasts. It will take any sound that is over a certain threshold and start to to reduce it's volume (eg. compress it), so if he's talking really quietly and then yells something really loud, the person listening isn't subjected to as large of a volume range in their ears.
The limiter just limits the maximum volume, and I'm not sure why he's using an expander.
Do you expect everyone that rides in the back of your car to have read your owner's manual? I realize in this case they also happen to be the owners, but I don't think that's the point here.
Hiding a manual release BEHIND a speaker isn't exactly obvious. I have no opinion on if they deserve $1 million, but I do think Tesla needs take function over form in this case and make the manual override a lot easier to find.
Not to sound pessimistic, but as more and more people get forced into metered bandwidth, how is using a plugin that generates extra random traffic "sticking it to the 'man'"?
Edit: Yes, I know this is supposed to mask your actual viewing habits. But security through obscurity has never really panned out for anyone in the end.
I think that Swift as a language has a lot of promise and if it can be proven to work well on the server, it's something that one of the thousands of iOS developers can easily migrate into.
You cut off the rest of my comment, I said the Fn key turns it back into the Backtick/Tilde key.
Other than "Shell" programmers, I don't think the backtick is really that popular. System and embedded programmer would probably be frustrated without simple access to the tilde for bit flipping, but overall, I think having ESC back make the most number of people happy.
I think the missing ESC is probably the majority of the issues the nay-sayers have.
I bet if they had just moved the ESC key to the tilde and had the Fn key turn it back into the tilde key, people (developers) would have received the touch bar a lot better.
Just one more to add to the other replies. When I'm developing, the Touch Bar is basically useless, but that doesn't bother me because having to use anything up in the FN "row" is an annoying hand stretch for me.
However, for all the other random apps I use (Keynote, Photos, etc) I LOVE the Touch Bar. Finding the particular operation I need up there without having to go to the menu/toolbar/mouse feels awesome.
I honestly don't see how any of these implementations are better than simply using a bool to track whether the queue is empty or not (as suggested in one of the comments on the original article). You could even use the highest bit of the write index to store the bool value if memory was an issue.
It's easy to just blame the FTDI driver, but FTDI is used all over the place in the arduino community on MacOS, so I would have have assumed it was working.