Comment by corethree
2 years ago
>This article is just about CSS not the entire frontend web stack.
Why waste your effort to inform me something I already know? You know that I know.
>Curious though, do you consider server-side-rendered components "frontend?"
Why are you curious about vocabulary and categorization? If you know what I'm talking about by "front-end-stack" then who cares?
Oh, strange non-sequitur then.
I don't know what you mean specifically by "front end stack", so I asked (unanswered) clarifying questions.
> Why are you curious about vocabulary and categorization
Because the frontend/backend lines are blurring, and I want to define our terms before discussion.
You haven't answered my question. Why inform me on something obvious that I know? I know the article is about css. And you know that I know.
By front end I mean any technology directly associated with rendering and processing on the browser. The lines of this definition are blurry so I will adjust those lines and move them accordingly to fit the intent of what I'm saying here. But again you know my intent so why make me waste my time to specify something you clearly know?
I thought your question was simply rhetoric. I didn't realize how confused you were.
To answer: if there's an article about tomato slices and someone goes on a rant about hamburgers (tomato slices being a small part of the whole) it's not clear or "obvious" that they read or understood the article.
You haven't answered my question, do you consider server-side-rendered components "frontend?" They are "directly associated with rendering and processing on the browser." (Even if they aren't rehydrated.)
2 replies →