This is such a clueless take, and I see it surprisingly often. Declarative UI does not inherently mean virtual DOM nor does it "automatically" mean slower than UIKit.
The abstraction is huge advantage, especially when targeting different devices and screen sizes. We (and that includes Apple) have been learning the value of those kinds of abstraction boundaries for years, well before React.
It's also important to note that SwiftUI and UIKit are composable, so if some small part of your app needs low-level, finer grained control, then go ahead and use UIKit/Core Animation/Metal and SwiftUI for the rest.
Yes, declarative UI is just an abstraction of imperative code. :)
The rest is properties of the internal implementation.
The VDOM way obfuscates the internals more. Doesn't let you control rendering appropriately.
It is so because the diffing and reconciliation algorithm have to be able to remove any subtree of views/nodes from the UI tree.
Then you can only have islands of either paradigm within each other. UIKit and SwiftUI do indeed compose, albeit coarsely.
I can't blame them, they got influenced by react.
Don't even blame react, it was a good attempt. Basically trying to build a UI from a snapshot of a tree. Except this is too simplistic a model.
They designed it as if you could equate the number of games and the number of positions in chess. Like a markov chain.
Except playing chess has side effects. A mere snapshot does not encode those.
Java can still be used but it's no longer the recommended choice for Android apps. For any new Android apps nowadays you start with Kotlin and Jetpack compose (made by Google).
In fact, I think Google's been saying this for 6-7 years already.
This is one of those 'hey, I can vibe code this in a weekend' projects. Just look at how the AI decided to the entire map in dark mode, making it nearly impossible to tell the ocean and the land apart.
I think people still read, but the problem is largely that people read older literature, meaning anything older than 5-10 years at the very least. People are very hesitant to read something recent because it may very well be AI slop.
Never heard that this is stopping anyone from reading recent books.
Maybe someone whose only method of selecting books is to scroll through Kindle and look at the titles, maybe they need to pay attention to publication dates. But the rest of the world picks books because they get a recommendation, they look at reviews, they know the author, etc.
NYTimes said that the new Marlon James book might be the book of the century so far. Hyperbole, I'm sure, but it's now on my reading list and I'm pretty sure it wasn't written by AI.
It is not so unusual to read books that have stood the test of time at least somewhat.
Newness is not really a valuable quality when it comes to books, barring some exceptions like books on subjects that change frequently and meaningfully.
Diminished quality however is a meaningful signal, and would give most serious readers pause.
Preferring books that have stood the test of time is totally different from just avoiding everything published in the last few years because you're worried it might be AI slop.
Haven't properly burned myself yet. I've just avoided books based on skimming through online or in bookstores. Some had pretty clear telltale signs of AI slop (although usually quite subtle).
At his point I think that one has to assume that almost every author is using AI to some extent. And even if they don't, their editors will apply changes, no doubt using ChatGPT and other tools.
> People are very hesitant to read something recent because it may very well be AI slop.
I cannot imagine this is an actual trend that's preventing people from reading, so please bring a couple citations.
Reading has been on the decline for more than a decade, far beyond when AI was invented. I'll go with the 2008 Steve Jobs quote:
> In January 2008, Steve Jobs famously claimed that "people don’t read anymore," specifically asserting that 40 percent of Americans read one book or less the previous year.
AI generated text isn't so hard to detect that people could get away with it. As long as you are reading a well reviewed book the chance of AI slop is very low.
Seeing that you already know programming, I'd say it'd be less risky for you. But the only reason you're able to pilot an LLM to do programming for you, is because you understand programming and architecture.
But what about the future generations skipping the step of learning the OCaml's, the C's, the Python's...? It's quite concerning.
Why should it be? In my experience it depends on the case, and in my case it seems like an absolute technological overkill to version the site and have statichost regularly pull from some repository, as I update it perhaps once a year.
I mean, versioning is basically free from a technical / storage / time spent standpoint, and my experience says that if you don’t do it you likely will lose your code at some point
Simpler. Or you work/collaborate on projects with people who really shouldn't have to learn Git, even via a GUI.
I'm a programmer by trade and do plenty of versioning via _v1 and so on when working on music with others, we basically send .zip files over Telegram and append some label at the end. Not gonna ask these people to learn something when basic "have many copies" does the trick sufficiently good.
Thanks. I know the Amiga version took a long time. It was very hard to even look at the assembly code I wrote after so many years. AI was the hero that explained everything and helped me to package it for releasee. Enjoy!
How was Baghdad like in 1993? All I remember from that time was the Gulf war, Saddam and much conflict. I can only imagine how it would be finding hardware, books and resources such a time. That was hard enough even in parts of Europe.
Yes, it was a tough time after the war, but the main difficulty was the economic sanctions, which hit us hard. There are a few interviews and news articles published after I launched the mobile version back in 2010 that discuss our experience in the 90s. You can read more about it here: https://babyloniantwins.com/story/ I am happy to go into more detail on any aspect. I will be watching this thread regularly.
The abstraction is huge advantage, especially when targeting different devices and screen sizes. We (and that includes Apple) have been learning the value of those kinds of abstraction boundaries for years, well before React.
It's also important to note that SwiftUI and UIKit are composable, so if some small part of your app needs low-level, finer grained control, then go ahead and use UIKit/Core Animation/Metal and SwiftUI for the rest.
reply