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...

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).

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.

https://pbs.twimg.com/media/HFZpJ9mWwAEfdhv?format=jpg&name=...

https://pbs.twimg.com/media/HIjqR2aWMAErm9E?format=jpg&name=...

Of course I am going to score higher in the well being department. :)

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.

MVC, the controller is the intermediary between the services/data models, and the views. That still one of the best / simplest way to build large apps. MMVC is just a variation of it, with the models being able to communicate state to views and bypass controller if needed.

MVC, is still one of those 'fundemental as simple as it gets, and it gets the job done' patterns.

What you described works only in super simple scenarios. Whink Web 1.0, when Javascript was used for basic form validation at best, and didn't change DOM that much.

it would have been a great language, meanwhile they decided to throw everything out and created a language that it is overcomplex, and it is failing to gain any traction outside iOS / Apple's ecosystem. Basically, if you weren't required to use it, nobody would, which makes it a failure.

SwiftUI, should have been a rendering template/library integrated with UIKit. Also, cleaning up some of the UIKit syntanx and framework (simplifying it), and use SwiftUI as a template for UI, would have been ideal.

SwiftUI instead was pitched as replacement, yet it is not near as capable as UIKit, and it is not feature parity even 7 years later.

Just bad leadership by Apple in this case. (probably many of these decissions were 'promo / resume padding driven' as it happens in many large companies).

In car terms:

UIKit - Manual Transmission - you control everything, but a bit of a chore

SwiftUI - Slushbox Auto Transmission - easier to drive, sucks for performance

UIKIT+AI Coding - Dual Clutch Transmission - both great performance, and easy to control/drive

It is a newbie trap. It is great at producing simple apps, or things that don't require intense scrolling, or anything with heavy animations and precise layouts, but when you do something smooth, it is not it. It feels more of a React Native competitor, than a true UIKit replacement.

Also, almost everything that Apple has re-wrote with SwiftUI, came out worse as before (Settings, Spotlight, etc), and that doesn't help.

With AI coding... SwiftUI lost its edge/advantage (easy to layout screens), as now you code less of that directly, and might as well just go fo the framework that allows the most flexibility and gives you the best results for your users.

Apple really needs to either double down on it, and make it such that it has everything that UIKit has (match both features and performance), or just turn it into another optional framework, just as Interface Builder (.xib files) back in the day of Objective-C.

Right now it heavily promotes it as a first class citizen, meanwhile the features are not even parity with UIKit. It is so misleading to newcomers to the platform.

Ps. The other upsetting thing about SwiftUI, is that it has hurt the Swift language as well, as the team has had to introduce all kinds of hacks, or obscure features to the language in order to make it work, which made even the Swift language experience worse and more complicated than it should have been.

The moment that Mandani said he will stay home and serve the people of NYC, what asked 'where are you going to make your first visit when elected' it made him a target. He showed he wasn't willing to bow down to a foreign power.

NYT still tries to put a veneer of modicum. NY Post is the one that is unbashingly always negative against Mamdani, full on attacks all the time.

I think people had enough of it, and saw through it and voted for him just in spite.

I know all the members of my soccer team voted for him. I had no clue who he was, but all the attacks backfired and made him even more famous.

Do you think they are lying just for kicks?

I have a 84 w123 300D, and would love to add some more power to it. Lightweight hub motors would be great, but any decent size battery would be at least 200lbs+, which is hard to do on a old chasy.

Anytime I let lose AI (Both Codex and Claude), they end up producing slop that is overcomplicated, and that looks like a generic tutorial interface. Great for toy apps but not for serious one.

When I do most of the architecture, and use AI to 'fill in the blanks' or just finish some functionality here and there, then AI is great.

The main reason is that it is trained by public code that is mostly tutorials, and simple apps, so AI can't build a great looking one by itself (or it doesn't how to do large apps). But for specific features, it is great.

TLDR: It is still a 'fill in the funcionality here' type of help. Folks that are successful with letting 'multiple agents' running in the background are mostly for backend work where the results are easier to verify.

Also, there is a lot of LARPING in twitter sphere exaggerating what AI can realistically do right now. But I can see how it can affect entry level jobs. AI is still like an CS intern, or very very junior engineer.

Can't believe they are asking 600k for this thing.

It is almost like Ferrari is trying to punk its customers.

Ps. Everyone is hating it on FerrariChat

I think the reason for dropping it, is more of a technical issue and user experience, rather than a 'desire' issue or company will. From my understanding, Zuck wanted this. The implementation was a mess, and folks have different expectations about messages to appear at every platform. Having messages disappear between devices/web, or having to back up encryption, keys, etc... it was just a terrible user experience. Even employees, disliked this feature.

This was not something actually asked by users, but more of a feature done in order to thwart all the types of legal issues created when folks use the platform.

At some point, I counted, there were 64 'leads', just to make this happen. Each lead, had a certain area, or surface/views, which means we are talking about hundreds of folks involved to make this happen (across fb and ig).

It was a boodongle, and it was something that users didn't ask.

Ps. I know, many here at HN really care about this, but the average user was not willing to put up with the degradation of the user experience in order to make this happen. All workarounds, require weakening E2E, which made it pointless.

Ultimately, If you want a truly E2E, you will have to use a platform specifically made for it. IG/FB are just not it.

Even Telegram, doesn't have it enabled by default, unless you specifiy it.

The Ferrari Roma, or Amalfi, are within that 600hp - 800hp range.

Simply, the new leadership thinks there is not enough market for it, and that's why. Mainly, because in the 2010-2015 era, when the pdk/dual clutch became popular, folks stopped buying manuals. But that attitude has changed, and folks are wanting for more manual experiences.

There is your list. https://carbuzz.com/10-most-powerful-cars-ever-with-a-manual...

You have cars from 600hp up to 800+ hp and safely can handle a manual transmission.

It is not a technical issue, just a leadership mentality issue.