Those vehicles don't meet US safety standards and are severely underpowered compared to anything on the US market (vehicles like the BYD Seagull and Wuling Bingo put out something like 70-75hp and have top speeds in the low 80s). Given that the primary aversion to EVs in the United States remains range and charging related, their relatively tiny batteries and low ranges are likely deal breakers as well.

Update it for the market, and you're probably looking at something in the low $20s or maybe just south for a barebones trim. I fully expect established automakers to be hitting those segments within the next couple years (or even next year, factoring in tax credits).

What I find more interesting at the bottom of the market isn't cheap cars; it's cheap car alternatives.

They've had 64-bit emulation for over a year. They supported 32-bit apps from launch, back in 2017.

They also released a new ABI called ARM64EC to aid developers in transitioning x86 applications to native ARM versions.

A base model Bolt is $26,500. More than fifty percent more expensive is not "slightly higher".

Yeah, but batteries and other components are cheaper, as is construction. It's not inflation that increased the price; it's Tesla's profit margins. Appears those are being slashed in order to maintain growth in an increasingly competitive market, though.

Stevia showing up in reduced calorie "natural" foods has been happening for a while, but it has definitely accelerated.

The increasing use of non-nutritive sweeteners in foods not labeled "diet" or "reduced calorie" goes back further than the stevia craze, though. It was probably a decade ago when I bought a bottle of Lipton Brisk tea for my wife, and she said it tasted strange. Checked the label and it had acesulfamate potassium in it. Probably around the same time I bought a package of Thomas' English Muffins (one of the flavored ones, cranberry maybe?) and ended up not eating them because they has a weird aftertaste that turned out to be sucralose (which I found are also in some Pillsbury products, like their honey butter biscuits).

Health concerns aside, I just don't like the flavor of these things, and it is increasingly hard to avoid them, even in "natural" products.

The only thing that would make catching up easy is if they stopped making movies. I think I've seen ... 4 of the 29 MCU films, and none of the shows. And I guess there are another 15 in development? Plus all of the other Marvel movies that are not part of that multiverse, like the 13 X-Men films.

With all of the reboots and remakes and rights bouncing from one studio to another comic book movies are as much of a confused mess as their source material.

It's not just about storage and transfer costs. It's just a shitty ass solution for sharing documents.

Why the hell would I want a hundred and forty-three copies of slight revisions of the same document spread across a half dozen mail threads when you could toss out a link to an online document?

And frankly, people seem awfully dismissive of the cost of storage and transfer here. That shit absolutely adds up, and email is now a predominantly free service with high quotas, meaning it's either razor thin margins or a full on cost center. If you want MORE embedded ads, go right ahead and demand the ability to send 1GB videos through email. And then enjoy having ads injected into them.

If you have a library that simply assumes reliable transport and doesn't handle exceptions your library is broken. And I fail to see how Project Loom creates new opportunities for that kind of brokenness.

The whole point of the approach is that in maintains the same programming models as exist in Java already, with the same error handling frame work, and largely the same concurrency model. The advantage is preserving execution context (e.g. ThreadLocal variables) without unnecessarily coupling it to an OS level resource (i.e. "native threads").

The idea that an arguably more primitive and cumbersome approach is better because it "forces awareness" sounds like a rehash of the arguments assembly and C programmers have levied against higher level languages in general. I tend to think that expecting programmers to (mostly poorly) implement cooperative multi-tasking was never a particularly good solution to the concurrency problem.

It's only been macOS since 2015. Prior to that it was "OS X" for a few years.

I've been an IT professional for over twenty years, supporting exclusively Linux servers. I had a choice when I got my last work laptop, and took Windows over MacOS without hesitation. I can't stand the Apple ecosystem.

I also switched over from Linux to Windows for my last personal computer. I bought a Surface because it was the form factor I wanted, with the expectation that I would install Linux or at least dual boot. Once I started looking into the abysmal state of Linux support for things like high DPI displays, I decided not to bother.

Since virtually everything I do is on remote servers anyway, I've lived in a combination of browser and terminal windows for years. Being able to run Linux apps local with WSL was just extra gravy.

*shrug* It's my browser of choice.

I have a box mostly full of cords I will never use, plus a few I will be thankful I kept. Given that I don't necessarily know in advance which is which, and given that it really doesn't take very much space, this seems an eminently rational thing to do.

Not only is the commonly promulgated story of how QWERTY was designed almost certainly apocryphal, there is scant evidence that Dvorak has any appreciable advantage.

https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fwww.smithsonianmag.com...

If you actually look at the TIOBE rankings, it's #11 (not #12 as claimed in the article), and back on the upswing. If you look at RedMonk, which they say they looked at but don't reference with respect to Ruby, it is a respectable #8, being one of the top languages on GitHub and Stack Overflow.

We are certainly past the glory days of Ruby, when it was the Hot New Thing and everyone was deploying Rails, but to suggest that it is "probably doomed" seems a somewhat hysterical prediction.

I can unironically say that, from a feature standpoint, the original Edge has been my preferred browser for the last couple years, compatibility issues aside. Nice clean layout, built-in and accessible reading mode and translation, the ability to annotate pages and share them, the ability to save tab sets.

Some of those features are missing in the new version of Edge, but assuming they're in the pipeline I would jump on the chance to standardize my browsing experience between work and home.