2 ms·
Arguing over syntax is a bit sad. It mostly just doesn't matter. The author like so many is judging surface level matters more than anything else, and there's j
by jauntywundrkind 3y ago
Arguing over syntax is a bit sad. It mostly just doesn't matter. The author like so many is judging surface level matters more than anything else, and there's just not really big importance to it.
They try to stage a huge freak out over conditional rendering. This feels so low stakes. Personally the React solution of just using a ternary & passing null makes all the sense in the world, leverages the language well IMHO. But we get:
> Pardon my British, but what the schlocky-donkey rubbish is that? If-statements inside a view tree with fallback to null?
Without real explanation, just loaded unexplained opining.
And again, oh no, we made some system to handle dynamic cases, when talking about lists, but this time the author tries to scare us with it being invented, maybe gasp not stable!
> Fictitious syntax, templating, directives. And where is the guarantee that none of this will change in the future? There’s no such guarantee. And it has happened before, am I right mr. React and mr. Vue?
I'm less familiar with the others but Reacts solution has been the for-loop we see here for forever. These tools are respectably stable. Yes they invent ways of doing things but the author is freaking out because that's insufficient for them; the idea seemingly has to be agreed to by everyone then encased in concrete such that it will forever be exactly the same. Personally I love that the web can progress, that it's not a singular fixed platform like that.
And then a lot of their DOM solution looks like a more componentful React might, with some renderprops.
> Because you need to have a lot of time to experiment and be able to accept new realities and the failure of current approaches.
Agreed. And I do think the frameworks are stuck. But it's not the question of hacking out some html; anything will do for that. The real question is architecture. It's what do our data stores or signal lling systems look like, how do we figure out what to render well (or do we just vdom forever, and even that was greatly speed up & shaped by redux & other stores)? These at least also have good pokers in the fire.
But most web frameworks work almost totally on the main thread. Most don't do a good job with incremental loading. These are the real structural matters, are the depth we need to be exploring. But which this debate over how-do-we-rasterize-some-DOM debates, which have been going for so long, gloss over. We keep rehashing something that doesn't matter much, that hasn't changed all that significantly since mod_perl. The real question of how web UIs work, how they are made fast, off main, has barely been delved into.