You say this but I've seen countless videos of Apple stores getting raided by thugs who steal all the devices. We all know those devices will shut down and be inoperable but they don't know and/or care.
Came across this piece from Discord on how they scaled dbt for petabyte-level workloads and a big engineering team. Some interesting ideas around environment isolation, faster compilation, guardrails, and CI/CD patterns that data and analytics engineers might find useful.
Though, to be fair, my kids steal my Steam Deck from me more often than I try to get the Switch from them. The family share features of the Switch leave a lot to be desired.
People rarely buy a platform for the platform, they buy the platform to do the thing they want to do. A game is just a genre of software.
It is far, far better to have tons of high quality software available for a platform, than to have an amazing platform, but a limited choice of software.
I would guess that the overlap between people deeply concerned about display response times and those excited to buy a Switch 2 is tiny. Most Switch buyers aren’t chasing cutting-edge codecs, they’re buying it for Splatoon, Zelda, Mario, and Animal Crossing. Nintendo’s audience has always prioritised unique first-party games and portability over hardware specs.
Speaking from experience, I've been thoroughly enjoying the Switch 2. Even if I knew about this information before I bought the console, it would not impact my purchase decision.
You say this but I've seen countless videos of Apple stores getting raided by thugs who steal all the devices. We all know those devices will shut down and be inoperable but they don't know and/or care.
reply