that’s a very sad (and very real) interpretation of apple’s intent – i would like to believe that apple does still want to reverse the trend of souring dev-relationship (though admittedly it’s getting harder and harder to believe with all of the stuff that happened during the past few months).

imo just saying something related to allowing sideloading (with restrictions) or removing fees or allowing links or really just about anything, and then spinning it as if apple decided it itself for the sake of the platform would have made the crowd cheer

i do have to say, i was pretty petty on apple before the wwdc, i’m still petty, but i’m also pretty delighted with the ipados update

and a file system, and folders in the dock?! who would have thought! (i’m still happy and grateful)

imo it’s pretty interesting from what i see – they published the newsroom article already.

wait what is this for?! using lit and web components in a native macOS app?

did that actually work out?
i have a feeling that the <script type=module> will load the module asynchronously, so you’re nondeterministically have LitElement on window (globalThis) on the following <script> tags, depending on the module load speed.

i liked @thorstenball.com’s article on how they use amp: ampcode.com/how-i-use-amp explains generally how i use agentic llm tools as well, with a big reliance on version control to review llm-written code (which is why i don’t like aider).

making LLMs fly is going to depend wildly on your programming environment, but in general pairing one of the agentic tools (e.g. cursor in agent mode, claude code, or ampcode.com) with a tool that can report errors back (typescript, linters, rust compiler) as they iterate seems to work the best.