It can generate something well produced, but it's really bad at applying taste or direction in the way a human does.
The workflow feels wrong. it should be closer to a DAW with chat, where the model outputs stems, samples and arrangement parts instead of one finished track. Then you could target a specific sound, section or idea and actually develop it.
I suspect Five Eyes already has backdoors into Apple and Google and can remotely push compromised updates to specific targeted devices. How do you know the version of Signal you get from the App Store is the same as everyone else? Australia can compel engineers to implement backdoors, they can't refuse or even talk about it due to gag orders. They can then share that info with Five Eyes to bypass their own laws like they did with ANOM. Australia ran the operation specifically to bypass stronger privacy laws in the other countries. The Snowden leaks with PRISM, showing governments getting data straight from Apple and Google servers. Australia's latest encryption bill lets them force companies to give access to encrypted comms. Seems pretty plausible to me.
Don’t agree with this take. Sacrificing the performance for all my users so a minuscule percentage of them can poke around a little easier? All the JavaScript is likely transpiled anyway. They can use dev tools to unminify most of it. Deploying with source maps for production might be a better ask?
I actually really enjoy React Native with Expo. The over the air updates allowing me to bypass the app store approval process for minor changes are a game changer. React Native renders Apple's UIKit which looks and feels much better than Flutters attempt to emulate it. It's also much easier to make Android Apps look like an Android app with Material design while iOS apps look like their made for iOS. Flutter for web just draws everything in a canvas so it's not accessible and the resulting file size is massive. While with React Native I can leverage Solito to run the same code base as a Next.js application for the web.
Don't forget to keep an eye out for drop bears too! They're a particularly aggressive species of koala that are known to jump out of trees and attack unsuspecting humans.
This is really good, I wish I saw it before I built something similar. Mine is server-side rendered at the edge. It allows any value but still has no where near the functionality as yours. https://github.com/jmcmullen/qr-kit
I'd rather not have to provide my ID and verify my identity like on certain crypto exchanges to watch a youtube video or like a friends post on instagram.
I can't see any other implementation of this working, instead we'd have 2 popups now every time we visit a new site. One for cookies, the other to say "yes I'm over 18".
You're underestimating how terrible internet connectivity is in rural Australia. A lot of places will only have 1 provider that offers service, if any at all.
You don't directly query your database from GraphQL. Similar to REST, you read the parameters from the request and build your database query using the object–relational mapping library of your choice. A popular one at the moment for Node is Prisma.