Routing would be the hard bit I expect.. if the person you were communicating was 10 hops away how to find the route? Things like BGP do that naturally, but really you don't want to burden potentially nontechnical users with BGP..
Strikes me as way too early. Large parts of the country are stuck on copper because upgrading to fttp is deemed too expensive (I am, and I'm not exactly out in the sticks). Maybe in a few years .. I'm lucky I restarted my line when I did.
I've been getting it on and off for a couple of weeks and that's my experience too.. you get a 'we want to enable this exciting new feature' and you click no. They'll ask again.. which may push me to use firefox more.
It's more about bing being built into windows I think.. but I suspect they may get away with it just because it has little market share despite being built into windows..
So apple is saying they don't have 45 million active monthly users in a market of 750 million people and a 34% market share?
I'm sure 'most of our customers don't use our product' isn't what they were going for..
TBH though I suspect the EU will see through it - the purpose of the gatekeeper legislation isn't really about numbers, it's about market power - no one company should be able to dominate with a proprietary system. Which is precisely what apple is trying to do with imessage.
They've been talking about replacing NTFS for a long time. 10 years ago they put ReFS in the server builds and.. show of hands anyone using it?
I think they were trying to make ReFS compete with things like zfs but 10 years later it still doesnt support compression, encryption, quotas or booting..
I once saw a drinks bot at a festival.. Just a conveyor belt that moved the glass past various incredients and dispensed them at the right time. It was quite cool. Also the drinks were free, which made it cooler.
Something like that could be made commercially, if there was demand.. trying to make something using AI and robot arms just looks like overengineering for the sake of it.
You're not really tied these days because PD exists (and where that's not possibly they'll install dialysis machines in homes), but yeah a quality of life improvement to just have a portable thing.
I remember failing an interview once because they wanted me to know all sorts of obscure c++ tricks. The kind of stuff that most people skipped over when they read about it because it has almost no use case. Had travelled 200 miles for that interview too.
No idea who they wanted.. someone who had a photographic memory to memorise a textbook, maybe?
We tend to give practical tests when interviewing.. 'go away and write this thing'. We're not testing whether they write it, or how they found the solution.. google is there to be used.. but the questions they ask about the (deliberately) interpertable spec and what the code looks like.
I have my doubts.. kidneys are complex beasts, which is why even dialysis doesn't entirely replace them (it stops you dying, which is nice, but lots of systems get fucked up).
Routing would be the hard bit I expect.. if the person you were communicating was 10 hops away how to find the route? Things like BGP do that naturally, but really you don't want to burden potentially nontechnical users with BGP..