bnjm

SLA breaches have consequences, no big conspiracy there

> Does the code look pretty enough?

‘…readable, maintainable [and tested]’, ie. if someone else needs to modify or remove this code in the future, will there be friction?

Thanks for the response and great work on React Aria. That makes sense. To be honest the impression probably came more from tweets about the article than the article itself https://mobile.twitter.com/search?q=https%3A%2F%2Fweb.dev%2F...

I can see the appeal of web components when your interop issues are as large Adobe’s must be. On the other hand if huge portions of your apps are canvas / wasm then web components’ DOM-centric component model might feel awkward or constraining

I would love to hear from one of the Adobe team members about this. Are there separate React teams and WC teams? What’s that dynamic like? It feels like Photoshop on the web has been framed as ‘powered by web components’, rather than WCs being a minor detail. This post mentions “islands of React code” as if React is a legacy thing they have to put up with https://web.dev/ps-on-the-web/

They moved the Museum Art Hotel in Wellington in 1993. At 3000 tonnes it's half the weight of the Zurich building, but they moved it 120m, which is twice as far. Pretty impressive!

http://www.stuff.co.nz/dominion-post/news/wellington/9054381...

Interesting, did he mention any specifics? They seem to be aiming to create a general platform that's not specific to games. They also do have a few marketing / business managers which might be why it sounded like vapourware? As far as I can tell they have a lot of talent in the engineering department.