lol. JSX isn't even the worst part of React IMHO.
Posts by Mastro.{js,ts}
I assume people do those only for SEO?
To the Mun or bust! π
Agreed that React was a great innovation for its time. But things have moved on.
In every other major client-side framework there are signals now. And browsers have caught up with SPAs: they have MPA view transitions, bfcache etc: mastrojs.github.io/guide/client...
Which is React Native π
3. Profit!
Yeah, I'm even okay with some things landing later in Safari (or never), especially if the end result is a better standard. But it would be great if there wouldn't be so many bugs in the features Safari claims it does support.
+1 for the chef analogy π¨βπ³
you have my vote! iPhone 5S was peak iPhone.
Nice! Unfortunately my muscle memory is now dead set on interactive rebase π
Yeah, I suspect this also depends a lot on the environment. If I feel I have control over and am empowered/allowed to change the codebase/tools etc I am way more likely to switch into active mode than if someone else dictates the setup.
Fully support your other initiatives as incoming CEO, but βnoβ to more Chromium monoculture!
Yeah, they also fill in a lot of details for you. Something LLMs tend to do as well for better or worse (i.e. hallucinations). As a beginner-friendly way to get started, why not? But I feel there is a reason professional productivity software doesnβt greet you with opinionated templates on startup.
But itβs still using React and Vite under the hood, right?
intentionally posting your horse a few seconds _before_ Andy posted his? well done!
screenshot of my timeline with parent post and another one that has an image of a horse labelled Claude
π±
Nice! I assume the project is unaffiliated with the non-html version?
Were people really waiting for RSC support?! Or that announcement just pushed Tanstack Start into the spotlight and more people using it, but without RSC?
I love everything is a file as much as the next guy (especially plaintext/markdown files). But the file system is terrible at handling concurrent writes, so you need one central process to manage that file (e.g. the editor app) and keep the OTs/CRDTs in-memory only. What would we lose by that?
(3/3)
Whatβs the big difference between:
- syncing remote to a local .git folder and then "backing up" the current state of the main tag to the checked out folder vs
- syncing remote to a local SQLite blob (via CRDTs) and then backing up current state to some local folder?
(2/3)
Thinking about this a bit more: the .git directory in your local repo is actually also just a database, and the syncing is even quite manual (running git commit/pull).
(1/3)
Thatβs why I donβt write coding comments ;-)
It seems you either start with files, then add something like git to collaborate, or you do CRDTs, and then sure you can add a file-based backup, but it will always just be a backup after passing through the real-time-synced database π€·πΎββοΈ
Agreed. The pro is just heavier and has a fan, neither a plus for me. Neo is nice, but the limited RAM would make me doubt itβs as future proof.
Looks like silica to me! Ah, you mean not the thinking kind?
True, still need to figure out what to make.
Some people prefer to make a pen and paper sketch of a statue first, others go directly with clay or the casting. But I tend to agree that no serious sculptor stays on paper and hands it off to some engineer to make 3D.
You can do that with Mastro as well (running a dynamic server I mean) And nothingβs stopping you from being as degenerate as you want!
Mastro is so cool repost if you love static site generation
Not sure I understand. What kind of error is it? The Service Worker fails to call respondWith(), or why else would you have a white page?