Hacker News Reader

Comment by EvilEy3 | Hacker News Reader

Just when there are two arguably most important migrations in mobile world happening(Compose and SwiftUI), they decided to migrate to inferior tech.

View on HN

*According to you. Every 5 or so years there's an "important" transition happening. That's tech. There's been many stories written about companies that live on the bleeding edge. I don't remember any of them ending particularly well.

> Every 5 or so years there's an "important" transition happening.

Name at least one change in Android SDK that can come close to revolution that is Compose. And same for iOS/Mac and SwiftUI.

Compose and SwiftUI are doing to mobile what React did to web. It arguably single most important change that happened since the inception of mobile platforms.

> There's been many stories written about companies that live on the bleeding edge. I don't remember any of them ending particularly well.

What?

I agree the current one is a major change but it's not mature yet. It hasn't stood the test of time. Twitter was built on RoR when that was the coolest new thing to build things on and Uber's booking engine was on Node.js when everything was being run on Node. I'm sure there's more I'm missing. .

You seem to be missing my point. Compose and SwiftUI are React of mobile world.

React certainly stood the test of time.

That's to be seen. I very clearly remember when Angular first came out, that was clearly the way to move forward. People switched in droves. Then React came along and changed everything. React has also remained more popular than Angular has, but we didn't know that till years later. Some chose to remain in Angular (my old company) thinking it will blow over and we can swap to the next paradigm instead. Turned out React was flexible enough to last a while. Somehow you can perfectly see this is the React of mobile and not Angular?

Unclear on what you mean here React will always be inferior to SwiftUI and Compose. All Apple has to do is release a new port of Javascript<Whatever> version 2 with limitations and boom goodbye React

Compose is literally React. It has different execution model, but the same programming model.

Maybe you should first read about subject before arguing for the sake of arguing?

https://speakerdeck.com/lelandrichardson/react-meet-compose?...

I don't care that it's literally React. The react model doesn't work for every platform. I do know the subject. I'm no expert but I've lived long enough to know that one paradigm on one platform is not the solution for all platforms. Stop making assumptions.

Name one where it doesn't work.

Arent they just a copy of React.js? But in native

Reply on news.ycombinator.com