Blog post and the whitepaper don't contain anything novel, just a re-hashing of the current state of agent based coding. Was hoping there would be something actually around a new pattern of SDLC.
The Musescore app is just a minefield of subscription farming, it was somehow miserable even with an existing subscription the number of times it tried to get me to also get their weird AI learning platform. Now I've left it entirely.
This is an interesting project and it's always neat to see things that are able to compile down to WASM for running in the browser. However, looking through the docs for Flavour and this feels like it would get very painful very quickly trying to write anything of substance.
MS owes people a working basic Windows ecosystem. We need to find the Middle Manager Driven Development that's responsible for this nonsense and put an end to it.
Really like how they were so excited to release this that they managed to break existing SKUs and cause a bunch of GCP customers to get billed at 100x rates for text tokens as flash image generation tokens.
The first big AI disaster has already happened and it is the thousand little cuts from people putting faith into systems that aren't built to be trustworthy. It is the software dev missing a critical safety check because "ai coding tools" at work have promised 10x delivery results and now they must use them or be seen as falling behind. It is the engineering manager throwing concrete flexural strength questions into the unaccountable void of ChatGPT because he doesn't want to pay for the overtime of asking someone accountable. It is the foolhardy amount of money being shoveled into the entire ecosystem that absolutely cannot provide the returns people need for any of it to make financial sense.
Don't forget the also fun classic "what you want to do is not possible with scoped tokens so enjoy your PAT". I think we're now at year 3 of PATs being technically deprecated but still absolutely required in some use cases.
I will never not be forever saddened by the fact that Apple killed their Xserve line shortly before the App store got big. We all ended up having to do dumb things like rack-mount Mac Minis for app CI builds for years and it was such a pain.
Normal people don't want to have a conversation with their Alexa device. They want simple, reliable commands to do the common things in their household. Anyone who's tried to order something off Amazon through a screenless Echo knows the pain.
Skills were always dead in the water the minute they required an AWS account and a Lambda deployment to get going. That's a miserable thing to develop (and an AWS account itself being a looming financial liability) and maintain even if you're familiar with all the inner junctions of Lambda and IAM.
My son has now done many months of homeschooling during Sydney's lockdown via Google Classroom and this feature request is completely unsurprising as the product is a complete joke.
It's a very bizarre and false claim that Google doesn't "use" news content and that they are doing this as some sort of altruistic system of "allowing these publishers to make money by showing their own ads". Google itself serves ads, runs a massive ad network and makes a ton of money in the process. Every point in this process that they touch, be it search results or AMP pages or even destination pages that use Google Analytics are of some benefit to Google either directly as ad revenue or indirectly as data capture.
A very decent breakdown of some more modern obfuscation and deobfuscation techniques. It's nice to see some Rust getting used as well, I wonder if it's made things easier or more difficult for the krunker.io dev in the long-run.
This is interesting from both a technical challenge point of view as well as a neat introduction into the various differences for ECMA run-times, especially for the module scope. It's impressive how small this polyfill ends up being, even with the Object.prototype munging avoidance.
While it's great to have a link to the charts themselves, you'll definitely want to also inline some screenshots of the charts in action. Pages of code samples are handy as examples but you'll need that first impression to draw attention.