The blog post has a section called signal boost where it explains framework authors everywhere are landing on knockout observables as their reactivity model, but they are called signals now since #Solidjs got popular. #Vue is also using a very similar mechanism btw 👀
Signals are everywhere
Will they every come to the browser? 🔮
Btw, I think #Angular and Svelte share a lot of the good bits in common, it's just Svelte is just the good bits 😋
For those interested. My end of year OS roadmap is as follows:
- Deliver WC DevTools UI Rework (with #shoelace )
- Deliver a more reliable WCDT (and v3 for Firefox)
- Look into supporting #solidjs Element Custom Elements in CE Lang Server
- Rewrite & finish JS Crawler
@cferdinandi I don’t thing the svelte team were saying it was ground breaking, they clearly reference #knockoutJS and #solidjs for their signals implementation. It is interesting how the most popular frameworks (except react) have converged to use signals. I do wonder where this is heading and if any other framework can/will knock react if it’s perch.
> Like every other framework, we've come to the realization that #Knockout was right all along.
I could have told y'all this in 2010
Dziwi mnie, że nie ma szału na #SolidJS. Toż to taki React, tylko szybki niemal jak czysty JS i ze świetnym zarządzaniem stanem na bazie sygnałów.
Dobra. Jako, że po dłuższym riserczu w międzyczasie doszedłem do wniosku, że muszę przepisać apkę póki jeszcze mogę to bezpiecznie zrobić, pytam społeczność Mastodona o werdykt. Nie mogę się zdecydować, bo w każdym wypadku przyjdzie mi uczyć się nowego języka :D
1. Apka jest zrobiona we Flutterze, ale ponoć ten niezbyt sobie radzi na desktopach, a to jeden z targetów mojej apki, więc nie mogę sobie pozwolić, by kulał
2. Pierwszą opcją jest Tauri. Backend i logika przetwarzania danych po stronie języka Rust, frontend na SolidJS lub ReactJS. Mam wiele lat expa w JSie, więc o jakość się tutaj nie martwię, bardziej martwi mnie sama "webowość” i jej potencjalne ograniczenia
3. Druga opcja to chrzanienie wieloplatformowości i koncentracja na iOS + macOS, tutaj naturalnie wchodzi Swift cały na biało
Chętnie poczytam argumentacji osób bardziej oblatanych w pisaniu aplikacji natywnych i quazi-natywnych.
Hello all! This is a new account I'm trying on a new Firefish server I've deployed. My main account is still @firstname.lastname@example.org.
Re writing my #introduction here:
Hi! I'm Pablo, a software engineer from #ElSalvador but now living in The #Netherlands! I'm also the author of https://felte.dev, a "framework agnostic" form management library.
I work mainly as a front-end developer with #ReactJS, but I love keeping track of the new things such as #SolidJS and #WebComponents!
Looking forward to see more people around the #fediverse ❤️
“React Is Not Modern Web Development”
The most tiresome thing in #webdev is picking the techstack. So many choices to make: plain #javascipt or a more restricive language like #typescript , which ofc is often depending on the overall frontend framework to use: #svelte , #react , #preact , #solidjs ?
So many questions to answer and that still is only the js side of things, you then have to think about your css framework (if you want to use something like #tailwindcss ), your font choices, and ofc if and what styling library you actually use ontop of our frontend framework; e.g. #bootstrap , #blueprintjs , #tabler.io and so on.... which also often depends on your framework of choice!
I still do try to keep up on new things and evaluate them in toy projects, just to make sure I’m not missing anything. Right now I’m playing around with #solidjs, but it hasn’t sold me quite yet.
Follow-up on my delve into SolidJS and Svelte:
I recently completed a rewrite of the first game I wrote in Svelte, to port it over to Solid instead.
Everything is much tidier and more modularized. Some of that is probably due to me not having used Svelte perfectly the first time around.
But also, I feel like Solid nudges me ever so slightly towards structuring my code better than when I was writing the same functionality in Svelte.
Anywho, your mileage may vary.
I've started toying with SolidJS today and this is reallllllly neat! The documentation is great, the API is awesome and the TypeScript integration is perfect. I played a bit with Sveltekit last week-end but had to fight with the magic types in neovim and was also not convinced by the syntax.
So far SolidJS gets it right and fast :).
@fogoplayer This is a more nuanced look at reactivity in different frameworks 🔗 https://www.builder.io/blog/reactivity-across-frameworks
I’ve been looking for this link for ages! I saw Miško Hevery give this blogpost as a talk live a few months ago and I think it’s very well put together
Why don't some people like CSS-in-JS?
Is it because code written in CSS-in-JS don't allow you to take advantage of the "cascading" nature of CSS?
Is it because you can't take advantage of selectors?
Is it because there might be some compilation steps required when employing CSS-in-JS? And if compilation isn't used, there might be some render-time slowdown?
Regarding JS: you don't need to touch it explicitly in those frameworks, BUT: it is still used to manipulate the #DOM.
I am building a little web app to support a new article that I am currently working on. I decided to take the opportunity and learn the basics of SolidJS. Let me tell you, I absolutely love it!
This course by The Net Ninja is a great place to start
Porting React-Admin to Solid. To explore the differences between #React and #SolidJS, my colleague Gildas implemented a basic CRUD framework, inspired by react-admin, in Solid. Introducing: solid-admin. https://marmelab.com/blog/2023/05/11/porting-react-admin-to-solidjs.html
We offer completely custom websites using these frameworks. All we need from you is a figma design, or an example website you want to clone.
Contact us at https://blurrybit.com/#contact
if you are interested! 🙌
At work, we have been kicking the tires on a game I built in SolidJS. It is now in internal beta. Thus far, my experience has been:
– Solid is much more pleasant to work with than React. To the point where I feel like a schmuck for all the years I wasted on React, and hope to never be in a position where I have to work with it again.
Want to know more about #SolidJS and the person behind it?
This is a good read about when React jumped the shark.
Q: "Were React Hooks a mistake?"
⚠️ Spoiler: Yes.
I especially like this summation, which resonates with why I prefer SolidJS nowadays.
> "People aren't switching to these frameworks just for the performance. They're switching because these frameworks offer a fundamentally different programming model."
@ro Good question.
React.js does everything at runtime, they say they are working on a compiler but it is atleast a year away.
I think next.js is the same...
Good article about reactivity and how SolidJS handles signals. This is by far my favorite aspect (along with stores). Its approach is objectively better than React.
Solid makes working with app state a simple and pleasant experience. Rather than the myriad of approaches in React, each one essentially being a kludge no matter which.
I feel like Solid guides me towards good decisions, by nature of how the framework itself is architected.
@MerriNet @d3x7r0. Yeah it was #solidJS that reminded the community of an older pattern of fine grained reactivity that existed in older js libraries like knockoutJS (from 2010 ish). SolidJS showed how performant that pattern of authoring JS is. If you want to learn more about SolidJS this repo is a great place to start - https://github.com/one-aalam/awesome-solid-js as it has links to lot of SolidJS resources.
I like #reactjs I make money professionally because of it.
So I mean no disrespect & hopefully for future if we learn new tech it should be an exciting experience not a religious one.