If the AI is going to lie and cheat on the code it writes (this is the largest thing I bump into regularly and have to nudge it on), what makes the author think that the same AI won't cheat on the proof too?
Dude I think the whole "we're going to fire you" thing is weird on Apple's part. Look at how good the color picker became once it became yours. A bunch of resource string names should not be a big deal.
What's old is new again. Some of the same techniques used to keep pre-MacOS-X applications responsive, back when MacOS was cooperatively scheduled, show up here.
This begs the question of what is a reasonable programming model? In the MacOS case, the forcing function was buying NeXT, using their Unix kernel for MacOS, and literally firing the OS engineers who disagreed with preemptive multitasking.
For these browsers, is there a programming model that could be instituted where processing in these handlers didn't hold up the main UI thread?
This looks fantastic. I particularly love how cool things look at the different perspectives -- presumably this is because you did the hard work of making the planet at realistic scale? Thanks for sharing the process. It was fascinating!
This is great and all, but will we be addressing the fact that the acceptance rate of these institutions are all artificially low? The size of freshman classes are the same or smaller than the same in the 1980s, and the population of the country is much larger.
Tuition isn't the only problem here. If we want a country with social mobility, our higher ed institutions should reflect this and not create artificial scarcity.
Yeah I saw this process unfold over my decade there as well. I'm very grateful for my time there, my colleagues, and the great work we did (go Monarch team!). The latest evolutions there make me sad.