nevir

Wouldn't be surprised that the conversation is happening behind the scenes, and Google doesn't want to make a public fuss about it.

Happened before with Kindle, for example (that originally had a store built in …which Apple blocked so that they could release in-app purchasing a few months later)

Sinks are such a great example of what seems like a device with deceptively simple requirements for its design – but turns out to have so much complexity.

This seems so much more likely

Solved is a strong word here. They've certainly made a lot of progress

The size of the cut seems to be the main surprise: ~50% (25% to Horizon Worlds, and another 30% via the Oculus store)

On the trucking side of things, I think it'll actually be a positive for the industry in the short term (a decade or two), before the jobs really start to dry up.

Rail freight will probably be impacted by automated trucks sooner than road freight, weirdly enough.

My guess about the industry's progression:

* Automated trucks take over long haul routes (e.g. highway driving) between major distribution hubs, and previous long haul drivers move to middle and last mile routes.

* Shippers begin to shift freight away from trains and towards trucks (because price of trucks goes down, speed of delivery goes up)

* Automated truck centric freeways (or lanes) begin to show up, allowing for higher density and speeds of truck traffic. Price further falls, volume increases. More jobs created in short and medium haul trucking to handle increased volume of things being shipped.

* Automated trucks begin to be able to handle medium haul (inner city between warehouses), jobs start declining.

* Automated trucks begin to be able to handle short haul (last mile), truckers are a truly dying breed at this point.

For what it's worth, the author's CTO is the one that shared this article ;)

It's also worth noting that another way to reduce the cost to maintain your existing functionality (priority 0) is to actively _remove_ rarely-used or less valuable functionality

> They had a ton of spare resources that they only needed once in a while and figured out a way to make use of them.

Not actually the case. AWS was a completely independent stack (from hardware on up) - we couldn't use it internally for quite some time (years); and even then, only in a limited fashion (e.g. only S3 for some time)

Super skeptical that porting this to a new language is going to have the kind of performance gains they expect ... assuming they want to replicate all of tsc's functionality

The actual demo: http://gaugan.org/gaugan2/ (but seems to be currently falling over under load)

TBH it's a low bar for any software company – in general, we (developers) tend to dramatically over-engineer quite a few things.

Awesome to see projects like this!

Browsers have a large amount of overlap with operating systems - and with efforts to move more of web tech into userland (web components/etc all starting to rationalize HTML and other layers as being built on top of other more fundamental web APIs, etc)

And at Google

This has been a known bug for well over a decade: https://www.lighterra.com/articles/macosxtextaabug/

I wouldn't hold your breath on a rendering fix

Apple 'fixed' it in 10.14 by disabling subpixel anti-aliasing all together (what this post argues against)

TBH, I find the following from that site as "being a bit of an ass":

> You are a guest here. You can use IMGZ, and it'll always be great, because I'm great. I've even open-sourced it.

(in particular, due to the "because I'm great.")

> It's super cheap. Like, $5/yr. And that includes bandwidth. There's even a free trial because I'm nice.

(same theme: "because I'm nice")

---

past that, the honest talk is nice to see, IMO.

I'm pretty sure that nerds respond well to (marketing) blog posts that show how some new tech solves all of their problems by showing a simple example of that tech, while ignoring edge cases and future complexity.

That'll all be fixed/implemented in 1.0, anyway.

I don't believe it's actually the case that once you are infected by the delta strain your body has lasting immunity to that same strain.

It looks like that also is affected by age and other constraints: https://www.nature.com/articles/d41586-020-00502-w

Have we had any other mRNA based vaccines in the past? (genuinely curious)

IIRC, they still need to complete the regular review process. Normally that process takes several years

It sounds like they kinda ran morale for Tableau folk into the ground; and a bunch have/are jumping ship

> I wonder what changed and made them add the new terms of use.

CCPA's April enforcement deadline, most likely.

By doing all the calculation in memory. Disk is too slow

Amazon didn't want to blow up the relationship.

Though, Apple did eventually get taken to court for the book publisher pricing agreements:

https://en.m.wikipedia.org/wiki/United_States_v._Apple_Inc.

Back in the day, Apple simultaneously:

* wanted a 30% cut on all Kindle book sales (sold via iOS)

* had negotiated with most major book publishers that any book distributer (aka Amazon, Apple, B&N, etc) must sell their books at exactly a 30% markup.

---

Also, we had built a native store experience for the Kindle app before launching it.

Yet, after submitting to Apple (and not hearing anything back for weeks), Apple announced their intent to roll out in-app purchasing many months later

They also immediately blocked our submission and forced us to take out all references to the native store or even linking to the web store.

It's true that drivers don't earn much in the end when it comes to $ / year—but the "truck" does cost quite a bit: fuel, maintenance, insurance, equipment loans, etc.

The driver is still making ~50% of the overall cost of a truck (whether that amounts to a livable wage is a whole 'nother discussion).

https://www.freightwaves.com/news/understanding-total-operat... has a good breakdown of the cost structure for carriers.

I'm so sorry :(

Some fun tidbits:

Every Kindle had a unique phone number.

By the time your Kindle shipped to you, it knew who its owner was, and had already logged you in and downloaded all your books.

Any time we wanted to push updates to them, we'd SMS it (IIRC) and the Kindle would connect back to figure out what needs doing.

Original Kindles had an (awful) web browser (and didn't charge for data). It was not bad at Google maps

I'd be curious how that compares to Amazon's count of services (my guess is 10k+)