undefined | Better HN

0 pointscantSpellSober2y ago0 comments

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.

0 comments

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?

cantSpellSoberOP2y ago

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.)

corethree2y ago

Depends on the situation. They can be one or the other or both. It's meta, you construct code on the backend for rendering on the front end. There's no clear answer to your question other than the code being constructed is front end exclusively while the code constructing the code is hard to categorize.

>I thought your question was simply rhetoric. I didn't realize you were genuinely confused.

If the tomato is rotten, I'm saying that's the least of your problems if The entire hamburger is rotten. Pretty clear about my intent. Did you honestly think that I was being completely random or did you have another motive for saying something rhetorical?

cantSpellSoberOP2y ago

> the code constructing the code is hard to categorize

Agreed, I thought you'd have some insight. IMO you painted with too a broad brush in your OP. Articles that are specific get derailed by overly-broad replies.

This article is a decade old but sadly still relevant. I hope a day will come that it won't be.

> Did you think that I was being completely random

As I already said, I thought it was a non-sequitur.

Stop with the personal obsession, I just want to chat.

j / k navigate · click thread line to collapse

0 comments

corethree2y ago

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.

cantSpellSoberOP2y ago

I thought your question was simply rhetoric. I didn't realize how confused you were.

corethree2y ago

>I thought your question was simply rhetoric. I didn't realize you were genuinely confused.

cantSpellSoberOP2y ago

> the code constructing the code is hard to categorize

Agreed, I thought you'd have some insight. IMO you painted with too a broad brush in your OP. Articles that are specific get derailed by overly-broad replies.

This article is a decade old but sadly still relevant. I hope a day will come that it won't be.

> Did you think that I was being completely random

As I already said, I thought it was a non-sequitur.

Stop with the personal obsession, I just want to chat.

j / k navigate · click thread line to collapse