That’s already happening. Slightly different example, but Home Assistant has an integration that gives an LLM of your choice control over your home automation devices. Just talking to your home in natural language without having to memorize very specific phrases is honestly pretty powerful, as long as it works correctly. You can say stuff like “hey it’s a bit dark in the office”, and it just knows to either switch on the office lights, or make them brighter if they’re already on

Seems like clients vary wildly in how they interpret this markup. This is how it shows on Sync:

Yeah, but by generating with AI you’re incentivized to skip that initial research stage into your own code base, leading you to completely miss opportunities for consolidation or reuse

Oh, that sounds really cool! At what time does this validation happen? While you code, or later at build time?

I’m not talking full blown ORM here, not a fan of those either. I’m talking about some light weight wrapper that basically just assembles SQL statements for you, while giving you just a little more type safety and automatic protection against SQL injection, and not sacrificing any performance. I’m coming from the JVM world, where Jooq and Exposed are examples of that kind of thing.

As the other commenter said, the Jetbrains IDEs do this perfectly fine. Although I’d also argue that if you’re working with SQL from within another language already, a DSL wrapper is probably gonna be the better way to go about this.

Well then use all-caps keywords whenever working on those systems, I don’t care. But an edge case like that shouldn’t dictate the default for everyone else who doesn’t have to work on that, that’s all I’m saying.

My ide isn’t limited to color when it comes to highlighting, so being color blind generally shouldn’t be a problem. Set keywords to underlined, bold, italic, whatever works for you.

Your other examples I can see, but at least at my work those are rare edge cases, and I’d rather optimize for the brunt of the work than for those. Of course at other places those might be much more of a concern.

I understand it as an attempt to get very basic, manual syntax highlighting. If all you have is white text on black background, then I do see the value of making keywords easy to spot by putting them in all caps. And this probably made sense back when SQL was first developed, but it’s 2023, any dev / data scientist not using a tool that gives you syntax highlighting seriously needs to get with the times

Never heard of that, thanks for bringing it to my attention!

Just gonna leave this here: The coming war on general computation

Check out this one: https://thegradient.pub/othello/

In it, researchers built a custom LLM trained to play a board game just by predicting the next move in a series of moves, with no input at all about the game state. They found evidence of an internal representation of the current game state, although the model had never been told what that game state looks like.

Windows: “Time for updates! Stop everything you’re doing and please wait…please wait…please wait…please wait…”

How am I hearing about this all the time, but it has never happened for me? Every windows update for me so far has always gone the same, unintrusive way - when it’s time to shut down the PC in the evening, I notice there’s an “Install Updates and Shutdown” option next to the normal “shutdown” option, which I use if I’m not in a terrible hurry right now. Takes a little longer to shut down, next boot will also take a little longer, but that’s it. I’ve literally never had these unwelcome interruptions I hear so frequently about.

For note taking, you might even get by without self-hosting, looking at software like Obsidian which works perfectly fine with just SyncThing to sync between devices, or just literally any other file syncing solution, self-hosted or otherwise.

Genuinely curious, why do you not like PWAs?

I don’t think it’s quite that bad/simple. Viewing your main instance as the Controller and other instances as Processors in GDPR terms won’t work, because instances don’t have the necessary control over each other for that, as you say.

However, you could circumvent that issue by making the case that each instance actually acts as an independent Controller. By participating on a federated service, you are explicitly agreeing to the data you provide (your profile, posts, comments, etc.) being made public and shared with other compatible services. That should be enough as the basis for other instances to reasonably assume you want your data to be processed by them, which (I think, not a lawyer) is sufficient justification for processing the data independently, as long as it’s in line with how you generally expect the fediverse to work.

This would mean that each federated instance is its own, independent entity that processes your data, and to make use of your rights under GDPR, you need to do that with each of them individually. They effectively become their own “original data collection point”, in your words, even if that data collection was not explicitly triggered by you.

The only thing missing for that to be legal (again, in my layman’s view) is transparency about who’s processing your data and how, which is necessary under GDPR. Every instance that receives your data via federation would need to let you know about that, and make available to you information on how exactly your data is processed and how you can make use of your rights under GDPR with them. That, in turn, would probably be easiest if the protocol spoken between fediverse servers were extend with automated and standardized ways to propagate GDPR requests from your home instance to any other instance that is processing your data, so that you don’t have to actually deal with every single server yourself to get your rights enacted. Defederation in the meantime might be a problem, but there’s ways around that, too.