> Video games tend to use UDP for the same reason everyone else mentioned does: timeliness. You want the most recent position of the various game objects now, and you don't give a shit about where they were 100ms ago.
This is only true for games that can replicate their entire state in each packet.
There are many situations where this is infeasible and so you may be replicating diffs of the state, partial state, or even replicating the player inputs instead of any state at all.
In those cases the "latest" packet is not necessarily enough, the "timliness" property does not quite cover the requirements, and like with most things, it's a "it depends".
With those requirements raw datagrams also don't fit the bill, so you'll need to build some sort of reliable stream abstraction over UDP (with optional unreliable delivery for the state which you can replicate quickly)... and now we're closing in on QUIC territory
Is there a relationship with the "Build" component of Knative here? ... It seems they were working on a very similar abstraction of CI/CD... This seems like a more general abstraction of the same problem
I'm really happy Google are giving a go at making ChromeOS into something more than browser on steroids. I really believe this is a path to a decent Linux Desktop future.
I'm def considering getting a pixelbook for my main machine this year now.
Which is a shame, because of how incredibly authoritarian the tracking of credit cards is. Credit/debit cards are a proof of ID in Australia (40 points) and so with every purchase you are uniquely identifying yourself to the seller.
Unfortunately making cash digital is quite hard (you could argue that zcash and zcoin will solve this problem but I'm not so sure).
In Australia we have a "points" system for proof-of-ID. In order to get certain things (open a bank account, get a passport, so on) you need to have a certain number of "points". Most things require 100 points of ID, and there are different classes of IDs (passports -- 70, credit card -- 40, water bill -- 35).
The purpose was to make it harder to commit fraud, though it also makes it kinda difficult to legitimately bootstrap your ID when you're a minor (or if you're an immigrant).
> makes it kinda difficult to legitimately bootstrap your ID when you're a minor (or if you're an immigrant
Or a slacker: I somehow scraped up 100 points to get a passport, then didn't have photo ID to collect it from the post office. I had to point to the packet & say, I need to open the packet to be able to show you the photo ID you need to see before you can release the packet to me.
As surprised as I am to say this; I think Google could steal a large chunk of the developer market overnight with some slight changes to Chrome OS.
I needed an emergency machine last week (My 2011 Pro finally died), and I opt'd for a £200 Chromebook (EDGAR), thinking all I need is a browser and a terminal right this second and I'd worry about what Apple is doing later.
A solid Linux laptop with working sleep, working wifi, great battery life. Tad underpowered but hey it's £200. I'm _really_ impressed.
If Google relaxed the constraints a little on the OS, or supported a Crouton-like workflow for containers without having to stick it in dev-mode, they could make A LOT of developers very happy.
I can't recommend Dell's Developer Edition laptops enough. I switched from a MacBook Pro about 6 months ago and haven't run into any of the usual obnoxious Linux-on-a-laptop headaches like sleep or wifi.
It's not as good as the force trackpad on the current MBP, but it's not bad, either. My only real gripe is that the physical click is a little heavy & loud. I'd put it in the same ballpark with prior generations of MBPs that physically clicked. You can always go play with one at a Micro Center or other box store.
You do, and xiwi (X11 in a window) is almost magic in letting me spawn a proper terminal emulator integrated with ChromeOS's window manager (Aura?).
...but it feels like a bit of a hack. I have to have the laptop in dev mode and there's a slight fear that an automatic update might prevent the chroot from working, or that my stateful downloads directory might disappear.
My thought was that ChromeOS is kinda where OS X 10.0 was... a great UI on top of a great base that just works. That's what drove many of us to Apple when we got bored of re-configuring linux, it's what made many of us recommend Apple to friends/family.... Apple have dropped the ball, Google is in a pretty good place to pick it up.
I like how the Signal app (at least on Android) also works for insecure SMS to give me one place for messaging... well apart from everyone who uses WhatsApp at least.
What I'd love is if they could also make it an email client too. Letting me send/receive insecure emails or (if the recipient has Signal) encrypted email using the same key management. I'd much prefur to give out an email address (totally in my control) than a phone number (could be taken away from me at any moment).
> His prediction was that everyone would dress in uniforms. But that’s the complete opposite of what has happened. And I don’t think people will be dressing in uniforms anytime soon.
OK, here's a potential prediction that could bring about "uniforms"...
If we end up with some kind of ubiquitous augmented reality, we may end up styling ourselves like you would a game avatar, and even "themeing" everyone around us. In that world, it might make more sense to just all wear comfy grey onezies all day.
Of course all predictions like this are hilariously off... it'll probably be more like the entire earth bizarrely becomes a comfortable 23C and everyone just walks around in socks.
Last weekend there was a man in a green onesie with a yellow unicorn tusk at a bar, so it may be a continuation of the theme. Certainly stood out, but not only because of the outfit; Self-cleaning clothing can't arrive soon enough.
This is only true for games that can replicate their entire state in each packet.
There are many situations where this is infeasible and so you may be replicating diffs of the state, partial state, or even replicating the player inputs instead of any state at all.
In those cases the "latest" packet is not necessarily enough, the "timliness" property does not quite cover the requirements, and like with most things, it's a "it depends".