I developed Android apps for an EV charging platform for 5 years. Now working for Mapbox to integrate a navigation app into cars. Quite complex environment. Most Android topics are exactly the same as on a phone, it’s quite fun though because your app can control car functionality

(Germany/Munich)

This is about 3 people in a meeting room joining with their laptops, without a meeting room audio setup (or it being bad)

Probably just above normal b2c backup services, and below company requirements

Syncthing will do a 1 to 1 connection if possible, else it will use a relay server. Traffic is encrypted. Open source. After the initial setup of marrying the devices together, it's just a matter of starting the application. Pretty much what you want?

Doesn't it still need a public relay server? I understand that's nitpicking, since even with tailscale, I need someone in the cloud to handle the IPs.

There are community-contributed relay servers that you can use. Check out the syncthing website, they explain how all of this works. It's a very good piece of software.

Do you need a CDN for a static html, no images? I would guess no, even if you.are being bombarded with requests

I would guess yes, unless you have a server with unlimited file descriptors and flawless connectivity to every other AS...

But CDNs are made for static content so your comment means I can't run a dynamic website unless I have unlimited file descriptors and flawless connectivity.

"Need" is a strong word. But I think the point is that if you expect wildly spikey traffic/don't want the site to go down if it receives a very sudden influx of requests, going static is a very good answer, much cheaper than "serverless" or over-provisioning.

I really hate my bakery, the buns are only edible for some days, after that, they grow mold!

Without sarcasm, it is entirely reasonable that when the OS is EOL by the 1st party, software support for it by 3rd party also ends soon after that.

I think it's more like your gen1 wi-fi enabled Philips screwdriver stops working because it's EOL as opposed to because nobody uses Philps screws anymore. Sometimes it's the latter, but not always.

A more direct analogy is right there; your Phillips head screws cam out more easily than Torx. Everyone who wants screws that don't shred as easily moves to that weird 6 pointed star pattern, and your Phillips head screwdrivers are suddenly EOL'd.

Unlike buns, software doesn't deteriorate

It does, especially at the scale of operating systems.

Bugs and vulnerabilities are always being found, with fewer and fewer people in the pool that might even theoretically want to pay for fixing them.

Also, hardware does deteriorate, and the story is the same for adding software support for whatever is currently available in hardware.

> Bugs and vulnerabilities are always being found

none which haven't been there from the beginning

On Android you can use split screen apps. Either some apps are broken (including some I was part of writing...) or it's really annoying to put in text when both apps are open. It's really just useless almost alway

I end up using it a lot.

I'm always fascinated at the threshold where people will decide something just won't happen ("useless") because it's not comfortable enough.

I'm more in the camp of pushing the limits as far as technically possible if it means I'm neither walking around with a 13" screen at all time nor need to be home to be able to look at two things at the same time.

So I'll be fine with readjusting a bit the window to input text if it means I can do the thing now instead of 6 hours later. At least I don't want Google to kill the feature just because it requires working around some quirks.

Some apps are buggy on iOS without split screen mode enabled, too.

I rarely use split screen mode on my Android phone but I am rather annoyed when I'm on iOS and I can't keep two apps open at the same time.

Some vendors do a much better job than others, though. Google in particular doesn't seem to offer more than the bare basics.

...except when it is really handy to have so why lock it down? I use it quite often on a 6” screen - small by 'modern' standards - and would not want to see our disappear 'to protect me' or for some other bullshit reason. This, b.t.w., is one of the many reasons why I vastly prefer Android-as-it-was over anything from the fruit factory and probably also over Android-as-it-will-become. I don't want my hands to be held by some vendor who thinks I'm too stupid to cope with some complexity to achieve my goals and would rather I buy yet another overpriced trinket from them.

It is my feet and my gun and it is up to me if I want to risk shooting the former with the latter.

It doesn't exist, because it's complex to set up and up until 5 years ago almost no one wanted to do this. Now some people want to do it, and they can use an Employer of Record via facilitating companies. But the visa situation will probably still be difficult, it's pretty much a gap

I was scrolling and scrolling, waiting for the author to mention the new methods, which of course every Android Dev had to migrate to at some point. And 99% of us probably thought how annoying this change is, even though it probably reduced the number of bugs for Turkish users :)

Unrelated, but a month ago I found a weird behaviour where in a kotlin scratch file, `List.isEmpty()` is always true. Questioned my sanity for at least an hour there... https://youtrack.jetbrains.com/issue/KTIJ-35551/

well now I wanna know what's going on there!