Solid.js feels like what I always wanted React to be • Hacker News Board

Re: Solid.js feels like what I always wanted React to be

#441

Post by smrtinsert » Thu, Mar 03, 2022, 3:36 AM UTC

oaxacaoaxaca wrote: post #93

parentheses wrote: post #82

This article hits on something I've felt for a long time. The idea that "hooks are superior" to me is ridiculous. If a linter is required to tell me when I'm writing a bug that is not immediately obvious, that is a failing in the framework to round those edges. Lints are not rounded edges! Solid is nice and _seems_ to fix the issues with hooks, but as another comment mentioned, the challenge is with building at scale…

I have the same complaint about hooks. Most people seem to ignore that tidbit, but to me it's really frustrating. Plus I recently hit more hook issues when putting a setInterval inside a useEffect. There's no way to do a normal didMount/willUnmount workflow without other hacks (i.e. useRef) just to set up a simple timer. Maddening! Edit: after writing this I went and read the article. Same scenario I was bitching abo…

My favorite accomplishment with react after not using for some time, was to set a conditional timer for app level event using hooks for a set of tiered conditions which should be ignored unless it passed a threshold.

Took me at half a week at least and I felt like a god after. Then I realized this was all phenomenal waste of time and I decided my next job was going to be cloud and backend focused. Only in the js world can you realize immediately as soon as your done that it's effectively worthless programming hassle.

Re: Solid.js feels like what I always wanted React to be

#442

Post by shynrou » Thu, Mar 03, 2022, 9:57 AM UTC

_fat_santa wrote: post #359

christophilus wrote: post #306

Earlier quoted context omitted.

I've been in the industry since the days of VB6 (which I loved). I've never been more productive than I was with VB6 and WinForms. That said, UI has always been a mess, even then. The more feature-rich you want your UI, the gnarlier and messier it gets. Everyone always likes to blame the front-end engineers for being slovenly, but my experience is that; UI is just messy. It's just hard to program cleanly. Not to ment…

Back when I studying CS and as Junior, I would laugh at memes about "Frontend vs Backend" where they described the Frontend as this pretty pasture and the Backend as this god forsaken place of spaghetti code. In a way I find this meme even funnier now because of how backwards it is. Often times it's the backend that's really clean and organized and the frontend is a hot mess.

I have worked in both kinds of projects. Those where the backend was the mess and those where the frontend was it. Good devs, who take care and are given the time to do it right, can create both in clean manner. I think usually the problem why frontend tends to get messy: There is usually a lot more pressure, unclear goals and instructions involved. And of cause a foundational technology that is already incredibly messy especially if you have a wide browser support goal.

Re: Solid.js feels like what I always wanted React to be

#443

Post by suction » Thu, Mar 03, 2022, 10:42 AM UTC

pygy_ wrote: post #350

suction wrote: post #151

Earlier quoted context omitted.

What JS framework would you choose to work with big datasets like, e.g. a data grid with half a million rows that should have a "filter as you type" functionality?

You shouldn’t do that kind of work from the rendering thread, and you should use occlusion culling to only render the needed DOM

Hence my question, is there a datagrid for any JS framework that does all the hard stuff for me?

Re: Solid.js feels like what I always wanted React to be

#444

Post by scotty79 » Thu, Mar 03, 2022, 9:00 PM UTC

recursive wrote: post #418

scotty79 wrote: post #406

Earlier quoted context omitted.

Normal for statement is more pure than that.

Functional purity? `for` can only have side effects. It has no functional purity. It doesn't even have a value.

Imperative purity.