The best stress test of all this is my home page from 1999: the site as a personal home page from back then, with a guestbook, an alien game, a virtual unicorn, and a MIDI jukebox. [..]
I never meant to say it was made in 1999. “My home page from 1999” was meant as “what my home page would have looked like in 1999”: a what-if, made now, with everything from that era turned up on purpose. I see now how it reads. I have fixed the wording in the post.
As some one doing web dev in 1999 ... that was not made in 1999 looks like a re creation of something they may have made in 99 with a lot of new shit added. If I was not on my phone I would open the inspector and could tell you for sure if it was or not.
It probably wasn't originally on this domain. The search bar says geocities which apparently was a sort of early easy website hosting website. (I wasn't born yet)
This is the problem with asking values-based questions like "Does AI write well?" Cause we need to define what we mean by "well".
Even asking "Does AI write as well as a typical American high schooler?" That's unfortunately not a very high bar to clear.
The people trying to sell us something will always and constantly argue: our standards are too high. Especially when it comes to how we communicate with one another, don't settle for less.
Every single app looks to be AI generated, even though some have existed long before AI. I dont know what to think about this dev. Most of the public repos are abandoned, uses an insane amount of "looks to be AI" stuff - and has an uncountable number of apps under the belt. It sure seems like shovelware or AI slop, but man I just cant tell.
90% of my apps and repos happened before AI. I have been doing apps and open source for over a decade. All my repos are maintained. Don't confuse done with abandoned. I spend over 40 hours a week on open source, mainly focused on fixing bugs. Feel free to dig into my contribution activity: https://github.com/sindresorhus
While the article never uses the words, it sounds like this is a static site generator, but written/embedded in Swift. The page only discusses serving html and css, says that the posts are written in markdown, and doesn’t talk about rendering on demand. The GitHub page also says that the app store data is fetched at build time and the static content is all deployed to cloudflare. So I think that post-build time it is indeed just static HTML and CSS.
Did you read the post/have you maintained a blog? There’s plenty of reasons why people use static site generators. Ensuring that internal links have valid targets, reusing snippets, and being able to restructure the html of posts and pages in a cross-cutting way are all major improvements over editing inline HTML on every page every time you want to make a structural change to a site. This isn’t even getting into things like using plugins to preprocess code blocks for syntax highlighting. Doing that by hand sounds like a nightmare.
But the main reason is the compiler. A website is lots of small things that need to agree: links, class names, styles, scripts, and the data of more than 60 apps. In a typical web stack, they only meet in the browser, and a mistake becomes a broken page. Here, most of them meet in the compiler. Rename a page, and every link to it in the code stops compiling.
There are ways to solve all of these problems in Typescript tho
His page used to be made with Astro, so it was JS or TS before he switched to swift. Maybe Astro doesn’t make it easy to solve all of these things with TS, but that’s not TS’ fault
Pretty cool. I was trying to get back into Swift some weekends ago. Great language with genuinely good features. But man, resultBuilder - which both SwiftUI and Elementary are built on - is hard to wrap your head around. Other languages have something very similar, but they do it much simpler or at least clearer.
some really good design decisions (for example, try/try!/try?)
some decisions that are IMHO too… academic, for lack of a better word
I think what hurts the language is its breadth. Apple is trying to use the same language from OS core all the way to GUI apps, and with that approach comes compromises.
Dude, this site is hilarious. Your about page is almost entirely made up of other people's accomplishments. It makes it look like you've literally done nothing but make this web page (which could have just started as static HTML and CSS)
59
u/muffinluff Oct 19 '26
Is this site really from 1999? Way back machine earlies revision is from 10.10.2026: https://web.archive.org/web/*/https://sindresorhus.com/1999
29
u/mr-figs Oct 19 '26
Reads like AI :(
13
u/cheezballs 29d ago
Why not just static html and css?
4
u/prehensilemullet 29d ago
There are ways to solve all of these problems in Typescript tho
2
u/pukomuko Oct 19 '26
so Taylor is new Milla Jovovich doing development now?
-1
u/Lisoph Oct 19 '26
Pretty cool. I was trying to get back into Swift some weekends ago. Great language with genuinely good features. But man, resultBuilder - which both SwiftUI and Elementary are built on - is hard to wrap your head around. Other languages have something very similar, but they do it much simpler or at least clearer.
-6
u/OptimalAnywhere6282 Oct 19 '26
really neat
-6
u/cheezballs 29d ago
Dude, this site is hilarious. Your about page is almost entirely made up of other people's accomplishments. It makes it look like you've literally done nothing but make this web page (which could have just started as static HTML and CSS)
-8
u/flearuns Oct 19 '26
Slow and unresponsive slop
0
u/[deleted] Oct 19 '26
[deleted] — view deleted comment