TillE

Generously, Musk has never been serious about making predictions. When he says stuff like this he just means he's excited about it.

It's a portable computer that does a bunch of useful things. I really don't understand the fraught relationship some people have with their phones. Just don't install social media apps and other time-wasters?

The ideal form of the flight booking interaction is that it's basically a computerized travel agent. So it could theoretically ask questions or listen to your objections and refine the request that way.

That could be fine, it's probably more comfortable than using a complicated website at least for some people, but again this is a feature you stick in a phone app, not a dedicated hardware device.

InvalidOperationException means "the object is in an inappropriate state". That does not describe a parse error.

C# conventions for exceptions are admittedly a bit confusing. There are a handful of very specific scenarios where you're supposed to use a built-in exception (most commonly ArgumentException). For everything else, you want to define your own type.

I suspect the iPad will remain the best option for stuff like RPG books. It's relatively cheap, the screen is large, it's fast and responsive, etc. It's not pleasant for reading in a dark room, but otherwise it's close to the ideal.

I'm relieved that the GitHub repo has finally been restored. I was just about to make a commit to fix our liblzma dependency, which would have required a vcpkg overlay to use a different upstream repo.

My experience with ARM64 Windows (in a VM on a Mac) was that Intel binaries run just fine, including some truly ancient VB6 stuff. Maybe there are performance issues with high-end games, I dunno, but for general use it seemed perfect. I was running Visual Studio back when it would give you warning messages that ARM wasn't supported, but it still worked.

Native code is strictly required for drivers, so I'd imagine the support isn't great for USB audio devices that use custom drivers for fancy features.

> you created a non-trivial project from scratch

I think a lot of people overestimate the amount of effort it takes to create a moderately successful, useful project. Like, make a plugin for something. Demonstrate that you can solve a real problem competently.

If you have any kind of outside interests, you probably have an itch that can be scratched this way.

This is pretty thin. Some Japanese cryptography researchers happen to have some very common syllables in their surnames.

I still like Hal Finney as Nakamoto, just because those bitcoin have never moved, and his being dead is the best explanation for that.

Germany loves endless bureaucratic paperwork which absolutely must be done in person (and good luck getting an appointment in Berlin), despite the many years of bleating about Digitalisierung which has apparently amounted to nothing.

> specifically offering support for currently sold games/systems

This has absolutely zero legal relevance.

Given the policy, I'm still really unclear about how ScummVM was allowed into the iOS app store. Maybe it was a mistake, but it's been up there for months.

There's no conceptual difference between interpreting SCUMM bytecode and interpreting 65816 machine code.

Google is vague about this, but the easiest solution to protect the quality of the ngram viewer is simply to only use books from known, non-vanity publishers.

Every game programmer needs a strong math background. Every good game designer cribs extensively from history and literature. Having a sense of art is important even if you aren't an artist.

There's very little in school that isn't directly applicable. Like, not even just "it's good to be a well-rounded human", but you can literally directly apply almost everything you learn to your craft.

Ultimately autotools isn't doing anything magical, so it's not unusual for cross-platform package managers like vcpkg to simply ignore all that and write their own clean CMakeLists.txt.

In this particular case xz-utils actually did support CMake for building liblzma, so that's what you use if you don't care about the command line tools.

Wikipedia itself isn't ideal for this, but I keep waiting for some major news institution to migrate away from the ancient newspaper article format and towards something more wiki-like for covering stories.

I think you could productively fit any kind of news coverage into a wiki article plus a stream of recent updates.

Several years ago we crossed the point where everyone is on Discord because everyone is on Discord. Also it's free, of course.

And there's a bunch of neat features that are somewhat unique, like using roles to sign up for specific types of announcements. It can be a chat room, or a forum, or voice/video chat, or a substitute for email notifications, or all of the above. I think that versatility is important too.

Games would probably be the biggest, most common scenario where C++ isn't going anywhere any time soon.

More generally, if you need to use existing C++ or even C libraries, Rust is at best an awkward fit unless someone else has already built and is actively maintaining the necessary bindings.

Yeah zstd is nice on its own, but a proper dictionary will give you several times the compression ratio on top of that, plus super fast decompression. It's just absurdly good for specialized data.

That's a little surprising; 6502 assembly is a fairly popular hobbyist thing, so I would expect the data is out there. It's also mostly pretty simple, but you do have to watch out for quirks like rotating through the carry bit.

My favorite know-nothing gamer meme these days is "bad optimization". What they mean is that the performance is worse than what they would expect (?) on a given hardware configuration and game settings.

They haven't poked around with RenderDoc, they don't have the debug symbols to profile the CPU code, they have zero idea what kind of work the software needs to do, they simply know the lazy devs have failed to "optimize" their game.

I've found that LLMs are most exciting and useful when factual accuracy is irrelevant, like as a personal tool for creative brainstorming. Or searching for information that you're going to immediately validate anyway.

It's definitely something more than a toy, but I'm not sure that you can build a trillion dollar industry on that kind of stuff.

Every time you want to iterate over a map, for example, you're using std::pair<T,U> or std::unordered_map<T,U>::iterator. This gets very annoying without auto, and making an alias doesn't really address any of the complaints the article has.

As far as I've seen, the big tell for LLM-generated essays is that they're still largely fluff with little information.

My memory of college essays is that you find your handful of sources, extensively cite them, and you're pretty much done. It's not even the same kind of thing that current LLMs create, because they're not able to pull accurate quotes from articles, books, etc.

> The release tarballs upstream publishes don't have the same code that GitHub has. This is common in C projects so that downstream consumers don't need to remember how to run autotools and autoconf.

This doesn't seem really vital to the attack, but it's a silly outdated convention. Nobody is manually downloading and compiling tarballs these days, and those who do can figure out how to use autotools.

It's rarely mentioned, but a major casualty of the Reader shutdown was Google Listen, a perfectly good podcast app which I think was just somebody's side project. It used Reader as a backend, so you could also manage your feeds in a browser. Really cool.

It's just another example of Google failing to even keep their options open to take advantage of future developments. "Serial" would make podcasts mainstream just a year or so later.

> Voice Engine preserves the native accent of the original speaker

I sort of understand this as a goal, but the American-accented German is weird. Like they nail some difficult "r" sounds but botch the easy ones. An odd hybrid between a fluent speaker and a total beginner.

Google Wave is an interesting case study because they identified a real problem (email sucks), came up with some really cool open technology, but never quite put it together in the right way. The web client was slow and clunky, and they probably weren't focused on the right things.

A few years later, Slack comes along solving the same problem in a different way, and now platforms like that are the overwhelmingly popular choice for group communication.

I don't know what "ruling" you're talking about. The DMA is a law, and it will be enforced despite Apple pretending to comply with it. There's nothing like a judicial proceeding as yet, much less a ruling.

This really underscores the point, and it's not just Gruber and random internet commenters opining on EU law while having zero clue about it, it's also Apple fans I respect like John Siracusa and Jason Snell who have a lot of opinions without familiarizing themselves with the facts.

Even if you're not much of a tinkerer, Ben Eater's videos are massively helpful if you want to truly understand how computers work. As long as you come in knowing the rudiments of digital electronics, just watching his stuff is a whole education in 8-bit computer design. You won't quite learn how modern computers work with their fancy caches and pipelines and such, but it's a really strong foundation to build on.

I've built stuff with microcontrollers (partially aided by techniques learned here), but that was very purpose-driven and I'm not super interested in just messing around for fun.