/s
7,094 karma · joined March 20, 2017
/s
Being able to write cutesy SaaS apps faster is neat, but not like, essential, the way water is.
I used to dread seeing the EAC splash because it inevitably meant frequent crashes on windows, with no such issues on Linux.
Got all those tokens, isn’t that the point of auto research and friends??
(Only sort of joking).
“Oh no it’s not our fault!!1! ~~My dad works at Nintendo~~ the govt told us we weren’t allowed to release it”
Get to Tuesday, restriction is lifted. Get to Friday, restriction is back on. Confusion reigns.
Interesting scenario though: do the other labs attempt to “dodge” the import restrictions by claiming their models are “dumber and not a threat” thereby maintaining larger market access.
If so, doesn’t this basically force a stall in US-based development? EU will keep doing its thing at its pace. Chinese models will get a boatload more popular, but will probably slow down as they can drop to whatever pace they wish.
cynical follow-up: if they’ve plateaued, is this a clever way to avoid the negative consequences of the market implosion that a substantially substandard model release would cause, thereby giving them an “out”?
- “instagram is better with MetaAi: yes/ask-me-later”.
- updated ToS which bundles a “we’ll use our own ai, and do whatever we waaaaant”
Lying, gaslighting and underhanded “growth hacking” tricks are their bread-and-butter, and you can be sure that whatever they’d have you install would blindly slurp up as much as they possibly can with zero regard for user privacy.
Which Facebook and instagram will present as “tee hee updated terms of service” in the first 15 seconds, and people will tick it, because they’re not interested in reading T&C’s, just want to message their friend about dinner, and aren’t suddenly expected be deceived like that.
Gaming, as a market, dislikes Live Service games, and many recent ones have basically flipped right out of the gate.
Stadia was the exact flop everyone predicted, and simply throwing bigger compute won’t help. That market, simply, does not want that product offering.
By far and away, linear.
The task tracking features you actually use, it’s fast, you don’t waste a billion years playing “who knows how to do this and has the permissions hell” that you would with Jira. The integrations work properly. The layout and UX makes sense, and all the nontechnical people I’ve used it with liked it and had no issues with it.
I’d much rather pay the prices corrected-for-supporting-livelihoods, than the artificially inflated prices used to line the pockets of the rich.
“Oh but businesses will leave”
Yeah so what, if they do, we either didn’t want them, or they _actually won’t_ despite the squealing, or they will go, and if their segment of the market is useful, will get snapped up by new/local versions which do respect local constraints from the get-go.
All of these are better outcomes than not doing anything because “what if”.
But the highlighted examples demonstrate the complete opposite. Shuttling things between a model isn’t engaging with another human meaningfully.
I don’t know, what you’re outlining there is pretty grim. Especially as we could elect to just…not destroy people’s livelihood’s en masse?
Sounds heinous, please never design the UX for a product I’ve got to use.
And if it isn't already, you can be that they're probably to start.
All those "difficult to program but easy-if-time-consuming-for-human" tasks, will 1000% be farmed out to models at unprecedented scales.
You can also…turn it off.
Chrome silently elected people into it _and_ downloaded the model without asking because they decided that’s something they (chrome) fancied doing.
The difference should be pretty obvious.
They’re saying that the emoji usage is telling them that very little effort was put into the PR and that they’ll treat it accordingly.
The solution is just to spin up the machinery you need for your solution, rather than making S3 cover all possible bases.
Or you’re getting the model to do the polishing, thereby developing no skills of your own, and we’re back to the start.
You would be appalled at the kind of stuff I have seen teams stuff into parquet and iceberg tables.
S3 is an object store. Treat it more like a KV store. As other comments have pointed out, the solution here is pick-your-favourite-metadata-store, be it Postgres, or what iceberg does, and other data on S3.