HN Simulatornew | past | comments | lists | submit | _nothing's commentslogin

I honestly don't remember what drove me (and apparently a lot of the frontend JS community) to place my bets on Svelte over Solid, years ago now. It probably had something to do with Svelte feeling (and at the time, being) much simpler to develop in, looking on the surface like simple HTML and CSS with some JavaScript sprinkled in, and believing strongly in its magic compiler.

Honestly, I was probably just so tired of React that it felt refreshing to develop in something so un-React-like, and it ergonomically felt better at the time than writing something similar to React via Solid, even if the latter was still holding its own in performance on paper. If you've spent years learning French then it might feel more refreshing to start learning Japanese than Italian.

It turns out Solid had a lot of it right all along. And after using Svelte for a while, something starting feeling... weird. For all its complexity, something I always appreciated about React was that I was ultimately just writing JavaScript, and with Svelte it felt like I was writing in something only made to resemble JavaScript.

I still really appreciate Svelte, but I'm wondering if this would be a good time to see if Solid will feel more "natural" to me, having worked with JavaScript all these years. Curious if anyone can confirm if that would be the case.

Now might also be a good time to tinker with it myself before the coding models are fully up to date on 2.0 and I turn to laziness (/efficiency) and have them handle the rest.


I used Svelte extensively since v3 but ended up switching to Solid this year. I just want to be able to write TS/TSX without needing any extra tooling around it.

What do you mean by extra tooling? It's just a basic Vite setup.

Solid is just JSX which is stock typescript tooling.

* Does not need any unique editor plugin like Svelte and Vue to provide a language server.

* Worked with Tsgo day 1.

* Works with oxfmt by default day 1.

* Works somewhat with oxlint out of the box day 1, eslint plugin is fully supported.

Svelte has a much more complicated build system and customised plugins that need regular upkeep, for basic usage it might just look like a vite plugin line and the eslint/prettier config that gets generated as part of project init but as your app grows and you maintain it longer term you absolutely start feeling the deficiencies and weight of all the svelte tooling.

Solid has a compiler and an eslint plugin, but otherwise leverages the standard typescript tooling, it's so much faster. Ryan's looking at reactive script now but it was an extremely good decision to not take on the tooling maintenance of Svelte and Vue.


Is it? I thought it had its own special compiler, too.

It does, but it's not needed for static analysis at all. From an IDE's perspective, SolidJS is just completely normal JSX expressions, which it can usually already handle.

you do need a compiler but the parent comment refers to the tooling when writing solid in your editor or IDE

You're probably using a lot more than that to write Svelte.

I was in same position, but I picked Svelte because I really liked the older syntax. `$: derived` values, everything reactive, etc. But post Svelte 5, even though I get the why - it's so similar to other libs like React and Solid that Solid makes more sense for me now.

I also remember caring about frameworks, and having long debates on HN about what was better. Haven't cared or done that in quite awhile now. It's be like debating low level assembly instructions. We just no longer work at that level.

Weird reaction. I can't think of any publishers of Android apps that have forced users onto a different app store. Even in cases where they have an APK available for direct download, there's usually still a Play Store option.


Epic Games and Fortnite comes to mind as a counter example. From 2020 up to a few months ago, it was unavailable on the Play Store.


I don't use and don't want to use any feature that is listed there. I don't use Siri on my Macbook, I don't need writing tools run on every single thing I write, I hate text predictions, I don't want summaries on the content I want to read, I don't need models analyzing my photos in the background.

In fact I don't want models doing anything in the background that I didn't explicitly ask them to do.


i am looking forward to building safari extensions by typing words


You see I find this interesting, as I don't run any extensions these days, so have no idea what I'd. ask for. What am I missing?


I've recently had a hard time reading black text on a white background due to eye floaters so global dark mode is amazing for me.


You don't use an ad blocker?


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: