Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Solidjs: Simple and performant reactivity for building user interfaces

solidjs.com

Post reply on HN
Print view View original

91–100 of 190 posts

Re: Solidjs: Simple and performant reactivity for building user interfaces

#91

Post by lelanthran »

sensiblecarrot7 wrote: post #55
mightyham wrote: post #2

Having used Solid on a largish web product for over a year, I am thoroughly convinced and will not be returning to React in the future. This is somewhat of an aside: I am aware that the creator of Solid has long been experimenting with adding laziness to the reactive system. I think it would be a mistake. That everything is immediate keeps state changes intuitive, fairly easy to debug, and is one of the strong points…

[flagged]

What does number of users have to do with it? That's a backend concern, largely.

When evaluating front-ends, wouldn't the concern be more "number of components active at a time", or "complexity of application state", etc?

Re: Solidjs: Simple and performant reactivity for building user interfaces

#92

Post by pandemic_region »

As with nutritional products, I feel that every JavaScript framework of library should have a 'Best before' date stamped on it somewhere. I apologize for the snark, but as an outsider to the JS ecosystem it really looks like a jungle from the Cretaceous period.

Re: Solidjs: Simple and performant reactivity for building user interfaces

#93

Post by lelanthran »

thomasfromcdnjs wrote: post #4

Portions of the react community are excited about how it's starting to feel more like PHP with the movement towards server actions in "client" code etc I personally don't like that direction so looking forward to exploring new frameworks. What I've generally liked about React/Next setups is that the code is generally explicit and less magic (I also have gripes with hooks feeling like magic). Things like Vue/Svelte wh…

> I personally don't like that direction so looking forward to exploring new frameworks.

I have a proposal for a new approach to front-end components. Even used it at a big client in production.

Want to put it on arxiv[1] before showing it to the world, but it's largely impossible to find an endorser unless you're active in academics already.[2]

Academics in a nutshell: the largest number of papers are authored by recent graduates with little to no industry experience.

Now, remember just how clueless your recent MSc graduate was when they started their first job in your organisation? Yeah - those are the types of authors driving state-of-the-art in SE.

---------------------------------------

[1] I have my reasons. If you're an endorser for software engineering, DM me.

[2] Academic gate-keeping got stupid, then pushed past to ridiculous, and appears to be now accelerating over the madness event-horizon.

Re: Solidjs: Simple and performant reactivity for building user interfaces

#94

Post by ivanjermakov »

vivzkestrel wrote: post #67

svelte is far far superior to this. Instead of the verbose JSX or whatever that weird syntax is called, you literally write plain HTML in svelte and feels absolutely natural to do so

Btw, you can use Solid without JSX and any build steps: https://www.solidjs.com/guides/getting-started#buildless-opt...

Re: Solidjs: Simple and performant reactivity for building user interfaces

#96

Post by thomasfromcdnjs »

josephg wrote: post #29
thomasfromcdnjs wrote: post #4

Portions of the react community are excited about how it's starting to feel more like PHP with the movement towards server actions in "client" code etc I personally don't like that direction so looking forward to exploring new frameworks. What I've generally liked about React/Next setups is that the code is generally explicit and less magic (I also have gripes with hooks feeling like magic). Things like Vue/Svelte wh…

I've been using solidjs (via solidstart) for awhile on a medium sized project. > Portions of the react community are excited about how it's starting to feel more like PHP with the movement towards server actions in "client" code etc Solidstart definitely pushes you to use their magic server functions. I used them at first - but increasingly I've been moving back to writing a normal, real REST interface on the server…

Thanks for the answer.

And http caching is definitely a huge factor for me too, graphql gives me similar sorts of pain. Sure, you can cache anything if you hack around for long enough, but in a real world engineering org (not the unicorns or uniquely positioned tech giants), it's so much easier for me to tell the CEO I can put some cache headers in by end of day and move on.

Re: Solidjs: Simple and performant reactivity for building user interfaces

#98

Post by rasso »

edoceo wrote: post #45
GolDDranks wrote: post #16

At some point, the creator of SolidJS, Ryan Carniato did a stint helping developing Marko.js, a fine-grained reactive / compiled / a bit HTMX-like system, and blogged about that. It's a framework that originated from eBay. I'm now quite interested about the next version of Marko.js, Marko.js 6, and I'm gonna try it for my new project. I'm interested in fine-graned reactivity so Svelte and SolidJS have been on my rada…

Amy thoughts on AlpineJS or RiotJS in this same realm?

Alpine.js in tandem with alpine-ajax has made me a very happy developer the last few years.

Re: Solidjs: Simple and performant reactivity for building user interfaces

#99

Post by division_by_0 »

imiric wrote: post #83
loxs wrote: post #69

Earlier quoted context omitted.

Funny. To me JSX is a much superior language compared to HTML templating. And I would say it's provably so. You can do JSX-in-JS-in-JSX recursively in a way that is "natural" and "safe" and "maintainable". And with TypeScript you get great IDE support, ability to refactor and whatnot. No need to trust my word, just look at the huge amount of code in JSX that the world is maintaining at the moment. I would say the onl…

JSX is a huge conceptual mistake, IMO. Sure, it gives you expressiveness, flexibility, and templating for "free", but this comes at the expense of the separation of concerns principle, which is a bad tradeoff. HTML is concerned with the content and structure of the page. JS is concerned with behaviour and interactivity. Using JS, or any programming language for that matter, to control how HTML is rendered introduces…

I totally agree about Svelte and the benefits of layer separation. I would say that philosophically, Svelte not only separates the layers, but gives HTML a special place among them, calling it "The Mother Language". [0]

Will check out Nue and Datastar.

[0] https://github.com/sveltejs/svelte/discussions/10085

Re: Solidjs: Simple and performant reactivity for building user interfaces

#100

Post by division_by_0 »

shhhhhplease wrote: post #68
vivzkestrel wrote: post #67

svelte is far far superior to this. Instead of the verbose JSX or whatever that weird syntax is called, you literally write plain HTML in svelte and feels absolutely natural to do so

Svelte is fun

Yes, Svelte's DX is just great.
Post reply on HN