As a web application and zoomer myself, I haven’t the faintest idea what this article is talking about.
Wow, a web application posting to Hacker News. What tech stack are you implemented in?
Get in zoomer, we're saving React
51–60 of 251 posts
Re: Get in zoomer, we're saving React
#52>A templating language is mainly an inner platform effect. It targets a weird imagined archetype of someone who isn't allergic to code, but somehow isn't smart enough to work in a genuine programming language. In Strange sentiment. Isn't React templating as well? Besides one of the most famous use of templates is macros (in C as well as other languages). Would people who generate code be allergic to coding?
> Isn't React templating as well? Nope! You can make React apps with just a plain ol' JS file (and doing so is frankly instructive). Most folk add in JSX for extra syntactic sugar tho, so the confusion with templating is understandable.
Re: Get in zoomer, we're saving React
#53Earlier quoted context omitted.
I always thought the point of the template language was more to enforce the boundary of presentation and code. and thus any template language that grows too powerful is a bad template language, because it's no longer doing the one job it has. So I think a template language should have loops, (non mutable) variables and basic conditions, that's it. So if there's something you can't do in your template that you want to…
If a template needs loops or even conditionals, it is already too complex for my taste as it leads to wrong design patterns blurring presentation/code boundary. Something that just allows to access variables and call functions will keep the boundary while allowing a non-programmer or even the end-user to edit it.
Re: Get in zoomer, we're saving React
#54Earlier quoted context omitted.
As soon as I saw, "you should listen to your elders" being used as a reason to read this article, i knew it wouldn't be high quality
That's a pretty inexperienced take, out of context. People should absolutely learn from elders, even if they feel the elders are wrong. Which is pretty much, every young person who has ever existed. There are often nuggets of wisdom buried inside resistance to change. I often wonder how much further along we'd be as a society if we didn't spend the first couple decades thinking we know everything. Myself included.
If someone needs to say "listen to your elders" then they aren't able to articulate their argument well enough to stand without it.
(I've been programming much longer than the 32 years claimed by the article author. No one should listen to me because I'm old, except in the case where I'm talking about specific incidents I witnessed that younger people didn't.)
Re: Get in zoomer, we're saving React
#55Re: Get in zoomer, we're saving React
#56> Crucially, none of the React alternatives solve this FFS. The context is the web, nobody solves graphic problem like gaming for you, or need to. At this point it doesn't matter because HTML/DOM stuff is not going to suffice what you are talking about either. I honestly think after reading 50% of the article is all about bragging knowing history. I'm not old but I was there too. WIN32, MFC, QT, 8086 assembly whateve…
Yeah, I stopped halfway through the article. Don’t talk down and condescend to your audience for no reason I think the article should be rewritten and all the ranting removed It’s also difficult to follow where the author‘s going with all the side rants and unrelated remarks And yes, that is considered ranting, contrary to what the author claims in the beginning of the article
Re: Get in zoomer, we're saving React
#57Earlier quoted context omitted.
> Isn't React templating as well? Nope! You can make React apps with just a plain ol' JS file (and doing so is frankly instructive). Most folk add in JSX for extra syntactic sugar tho, so the confusion with templating is understandable.
You can, but who does?
Re: Get in zoomer, we're saving React
#58Earlier quoted context omitted.
> Isn't React templating as well? Nope! You can make React apps with just a plain ol' JS file (and doing so is frankly instructive). Most folk add in JSX for extra syntactic sugar tho, so the confusion with templating is understandable.
You can, but who does?
Re: Get in zoomer, we're saving React
#59This post ultimately seems to spend a long time complaining about other people not putting in the effort to fix the problems of React... while the author doesn't offer any solutions or even ideas for solutions. Also, the author makes repeated digs at React 18's concurrent mode work while at the same time complaining about the kind of stuff concurrent mode is supposed to fix (for example, React updates not happening f…
As soon as I saw, "you should listen to your elders" being used as a reason to read this article, i knew it wouldn't be high quality
Re: Get in zoomer, we're saving React
#60Earlier quoted context omitted.
I always thought the point of the template language was more to enforce the boundary of presentation and code. and thus any template language that grows too powerful is a bad template language, because it's no longer doing the one job it has. So I think a template language should have loops, (non mutable) variables and basic conditions, that's it. So if there's something you can't do in your template that you want to…
If a template needs loops or even conditionals, it is already too complex for my taste as it leads to wrong design patterns blurring presentation/code boundary. Something that just allows to access variables and call functions will keep the boundary while allowing a non-programmer or even the end-user to edit it.
I prefer having one big template for a view, when doing SSR. Some layout components will have to be their own template if they repeat on different pages, depending on the template engine you can either pull other templates in directly (in which case using loops is also valid here IMO), or have a variable with a HTML blob generated from another template.
I don't really think either of those things count as code, because there's only logic that is relevant to how things are displayed. It's just, if the user has an avatar, show an image tag, otherwise, show a placeholder image/nothing. repeat this HTML once for each comment shown. That's not code in any meaningful way. I mean technically all of it is code, but you know what I mean.