Why Vanilla JavaScript • Hacker News Board

Re: Why Vanilla JavaScript

#171

Post by austin-cheney » Fri, Jul 17, 2026, 11:22 AM UTC

root_axis wrote: post #169

brazukadev wrote: post #166

Earlier quoted context omitted.

it is confusing the way you are explaining it, so much that even you can't understand. You do have a build step, you just think that doing that using node script is the same as not having one, I guess.

Yeah, IMO they are just making stuff up. Even as explained what they're saying makes no sense. Ultimately, there needs to be some entrypoint into the client-side script, node has no built in way to serve source code it's type-stripped over http.

If Node is your web server then node does have a way to serve the code to the browser... or you could just have node write the stripped code to a file for your other web server. It sounds like you are not even trying to think through this. I recommend putting fingers on keyboard and just trying to find your way through the solution instead of complaining about how impossible life is.

Re: Why Vanilla JavaScript

#172

Post by root_axis » Fri, Jul 17, 2026, 4:56 PM UTC

austin-cheney wrote: post #171

root_axis wrote: post #169

Earlier quoted context omitted.

Yeah, IMO they are just making stuff up. Even as explained what they're saying makes no sense. Ultimately, there needs to be some entrypoint into the client-side script, node has no built in way to serve source code it's type-stripped over http.

If Node is your web server then node does have a way to serve the code to the browser... or you could just have node write the stripped code to a file for your other web server. It sounds like you are not even trying to think through this. I recommend putting fingers on keyboard and just trying to find your way through the solution instead of complaining about how impossible life is.

> I recommend putting fingers on keyboard and just trying to find your way through the solution instead of complaining about how impossible life is.

I recommend you stop making stuff up online. We're 10 layers deep into this thread and you still can't explain how any of this works in a coherent way.

If any of this is real, why don't you attach a link from the node documention or an article that explains this technique that allows node to serve type stripped imports over http.

I'm not asking for a link to the http stack, I'm asking you to explain how you run a node app that consumes your typescript source code and serves it over http without a bundler.

Re: Why Vanilla JavaScript

#173

Post by guseyn » Sat, Jul 18, 2026, 4:42 PM UTC

megous wrote: post #88

lenkite wrote: post #77

Earlier quoted context omitted.

Regarding puzzling design choices, I am wondering at the preponderance of data attributes like For custom web components, maybe the author forgot that you don't need to prefix attributes with data ?

You don't need it anywhere, unless you want to use dataset property.

All custom attributes must start with data, read the convention

Re: Why Vanilla JavaScript

#174

Post by brazukadev » Sat, Jul 18, 2026, 9:32 PM UTC

root_axis wrote: post #172

austin-cheney wrote: post #171

Earlier quoted context omitted.

If Node is your web server then node does have a way to serve the code to the browser... or you could just have node write the stripped code to a file for your other web server. It sounds like you are not even trying to think through this. I recommend putting fingers on keyboard and just trying to find your way through the solution instead of complaining about how impossible life is.

> I recommend putting fingers on keyboard and just trying to find your way through the solution instead of complaining about how impossible life is. I recommend you stop making stuff up online. We're 10 layers deep into this thread and you still can't explain how any of this works in a coherent way. If any of this is real, why don't you attach a link from the node documention or an article that explains this techniqu…

guy really think everybody is a JS-framework user so he can drop a few words and get away with saying things that doesn't make sense.

But in the last post he kinda explained that he uses a node script to convert TS to JS. He is just confused.

Re: Why Vanilla JavaScript

#175

Post by megous » Sun, Jul 19, 2026, 10:01 AM UTC

guseyn wrote: post #173

megous wrote: post #88

Earlier quoted context omitted.

You don't need it anywhere, unless you want to use dataset property.

All custom attributes must start with data, read the convention

The browsers disagree.

Re: Why Vanilla JavaScript

#176

Post by groundzeros2015 » Sun, Jul 19, 2026, 8:10 PM UTC

swatcoder wrote: post #4

benoau wrote: post #2

Some good history of the JS ecosystem here but the underlying message is all the same, frameworks scale and provide structure but you don't need them. Very easy to agree up to this point. Author then elaborates in the absence of using a common-knowledge framework you can create some tighter solution that achieves just the part you need. This is "fun" programming, and the author is suitably impressed with themselves f…

We practice engineering. As engineers, we need to understand the realities of each project we take on. Those realities are not limited to the marketing bullet points we might apply to the imagined product someday, which is what early career folk might naively call "the requirements". Among the most critical realities to consider exist outside the product definition entirely, and have to do with the environment in whi…

As computer hardware has become more capable we should have been able to build even more web applications on a single machine. But there are few people even pushing on that boundary.

Some engineers learned it works fine and are quietly maintaining a stable system well under capacity. Or building the most insane distributed systems ever conceived.