My experience, with the latest models, they do write code that looks correct/polished, but often do not fully solve the problem, or solve the wrong thing, or introduce un-needed complexity. By often, I mean at least 10%-15%, which is still a high enough error rate, that you don't want to let loose in even a trivial service, let alone a service that is on the critical side.
I still use my M1 Pro Macbook... for iOS development. It still works amazing well, and the battery still is holding strong. For large apps, compiling can be a tad slow, but for medium and small apps it still works amazingly well.
Eventually I will upgrade, but for me the M1 Pro Macbook (14") has to be the best computer of the last two decades.
Before that, I had the butterfly Intel version, and that was a disaster. Apple just cooked with the M1+ line...
My 14" M1 Pro out of nowhere just died on me in May after 3 years and 11 months. 'Bad luck' was the verdict of the Apple store. This never happened to me since my first G4 tower. I now have the M5 Pro since i'm stuck in the ecosystem, but i'm still a little spooked.
This is silly.... most of the world didn't live in england.
All cultures (including mine), have a way to warn kids, or adults for not to stay too long in the sun.
From normal sunburn, to feeling light-headenes/fainting due to heat excaustion, etc.
In the winter was the opposite. (stay in the sun to get some sunlight and not get sick).
So, they knew, and had nothing to do with 'class'. Also, they knew some sun was good/beneficial, especially during the winter.
Pale beauty is a phenomenon across geography. What correlation a society works out is largely lost in the cycles of avoiding the sun being a relative luxury until you get expensive air travel.
Again... you are confusing second order effects, with the primary reason.
We have an old saying "te rafte pika e diellit", may you get a spot, sun spot, aka cancer from the Sun.
People knew excessive sun is unhealthy.... if you could you avoid it during the summer. It was not necessary to make you look 'rich'. Ability to avoid it, meant you were rich. And people wanted to be pale, because you look rich, that is a second order effect, that came because of the original reason (aka, too much sun is unhealthy).
The correlation looks right so all people who have rituals like telling their children not to look poor really understand and later communicate the truth? Is this true for religious stigmas related to food too?
I think you are retro analyzing and presuming individual intelligence because this collective result looks right to you. Really, some people understand some risks and many people who can follow taboos they can afford are not exactly sure what they would learn first hand and what part is superstition.
Of course. When I went remote, I could work from Miami during the winter, and escape the NYC cold months. Going for a swim to your buildings roof pool after done with the day, was the best feeling ever.
SwiftData is just a framework that you can choose to ignore and not use at all. Even CoreData.
You can go straight to the source, and use some small layer on top of SQLite, and ignore that noise (most large apps just do that).
But, SwiftUI is being pushed as the way to do UI, and as a replacement for UIKIt/the future of apple, where it is not even near feature parity with it. That's the most troubling part of it.
I wished apple just made it as a Template Rendering framework, and integrated wit with UIKit, and just modernized UIKit a bit.
Just use manual layout / frames dude, like a caveman. (ps. Many successful large apps do just that, including Instagram, and some of Spotify, where I worked).
But, he has been part of Apple for too long, and probably has internalized that style.
Hope he brings good change though...
reply