Well, I'm currently writing a service and frontend, both in C# (Blazor for the UI), and using docker-compose to build and deploy them to a Raspberry Pi running Linux. So not only cross-platform, but cross-architecture as well.

This is not a new thing either. Since .NET Core was released almost 10 years ago, it has supported cross platform development.

Right now none of the native clients support SSO. It is a frequently requested feature but, unfortunately, it doesn't look like it will be implemented any time soon. As with many OSS projects it is probably a case of "you want it, you build it" - but nobody has actually stepped up.

Every lie we tell incurs a debt to the truth. Sooner or later, that debt is paid.

Baldur's Gate 3 (~600 hours), BeamNG.drive (~550), Cities Skylines (~300), Space Engineers (~300), 7 Days to Die (~250) and Satisfactory (~230).

These are all stats from Steam and probably not fully representative. Satisfactory for example I used to play on Epic when I got it as a free game over there, probably logged at least another 500 hours or so on that platform.

My most played game of all time is most likely TES: Oblivion, which I started playing at release back when I was a teenager and had almost infinite free time. I'm not sure if I still have my oldest save to confirm, but I suspect it would be at least 1,500 hours, probably more across several characters.

OpenTTD.

That also means we can still use the expansion cards for the Framework in any other device that also has a USB-C port. Need an SD card reader or a 2.5Gb LAN adapter? Not a problem, I'll just grab one from my laptop.

I've tried Copilot and to be honest, most of the time it's a coin toss, even for short snippets. In one scenario it might try to autocomplete a unit test I'm writing and get it pretty much spot on, but it's also equally likely to spit out complete garbage that won't even compile, never mind being semantically correct.

To have any chance of producing decent output, even for quite simple tasks, you will need to give an LLM an extremely specific prompt, detailing the precise behaviour you want and what the code should do in each scenario, including failure cases (hmm...there used to be a term for this...)

Even then, there are no guarantees it won't just spit out hallucinated nonsense. And for larger, enterprise scale applications? Forget it.

For digital copies, they could bury this into the EULA and make it a requirement that you agree to it before you make your purchase (IIRC some storefronts do this already).

However for physical copies I suppose there could be a case made if the duration of support was not disclosed at the time of purchase (or it was not printed somewhere on the outside of the packaging).

To clarify, I used to do more miles (which is why I bought the car in the first place) but in the last year I've moved to working from home full-time. Still need the car for occasional errands and long trips, but obviously tyre wear is now not much of a problem.

However, given the massive amount of torque you can apply from standstill, if you drive like a hoon at all times then yes you can absolutely tear through them.

I went from a manual to an EV. For an everyday use point of view there is just no comparison. Acceleration is effortless, start/stop traffic is no longer a nightmare, it's quiet and refined. It is the ideal daily driver. Even on longer trips I no longer feel fatigued after driving for 4-5 hours (the enforced charging stop helps with that).

I personally would not go back to an ICE car in general, manual or not, for everyday use.

From an enthusiasts perspective, however, this is a different question. I wouldn't rule out getting an ICE manual for fun/weekend use in the future - the kind of driving where you can actually enjoy the level of fine control and feedback that a manual gives you, rather than just wasting it in traffic. But it would have to be something pretty special.

I can't speak from experience as I don't own any Amazon devices, but I have read reports that it seems to work fine with the FireTV variant of Android.

The dev has only tested it against Chromecast with Google TV, with that said I'm using it on a Shield TV and a Shield Pro and it runs fine on both.

Sony-Ericsson W350i. Had it for about a year before I got my first Android device, an HTC Hero.