Live data from Hacker News

Why Vanilla JavaScript

guseyn.com

161–170 of 176 posts

Re: Why Vanilla JavaScript

#161

Earlier quoted context omitted.

If you hire me as a consultant I will do it for you at $150 per hour.

You said: > I just write my code and then point node at the main file, and this even includes front-end code for the browser. Then you said: > I never said Node is did anything for the front end. So which is it?

Since you need just a little help…

Yes, I push all my TS code through Node for type stripping. No, Node is not executing browser code. No, I am not suggesting Node is running in the browser.

For extra extra extra clarity importing functions in JavaScript does not execute them. They still have to be called for them to execute.

I am still willing to fix your code for a consultation fee.

Re: Why Vanilla JavaScript

#162

Earlier quoted context omitted.

You said: > I just write my code and then point node at the main file, and this even includes front-end code for the browser. Then you said: > I never said Node is did anything for the front end. So which is it?

Since you need just a little help… Yes, I push all my TS code through Node for type stripping. No, Node is not executing browser code. No, I am not suggesting Node is running in the browser. For extra extra extra clarity importing functions in JavaScript does not execute them. They still have to be called for them to execute. I am still willing to fix your code for a consultation fee.

yeah this is a bit confusing. so you strip the types from the frontend and serve the .ts file as .js file? That's a transpiler/bundler.

Re: Why Vanilla JavaScript

#163

Earlier quoted context omitted.

Since you need just a little help… Yes, I push all my TS code through Node for type stripping. No, Node is not executing browser code. No, I am not suggesting Node is running in the browser. For extra extra extra clarity importing functions in JavaScript does not execute them. They still have to be called for them to execute. I am still willing to fix your code for a consultation fee.

yeah this is a bit confusing. so you strip the types from the frontend and serve the .ts file as .js file? That's a transpiler/bundler.

Confusing or not it works for me. No compile step and no build step. The application starts up in 0.2 seconds on Linux and about 1.2 seconds on Windows.

Re: Why Vanilla JavaScript

#164
post #69

Earlier quoted context omitted.

People keep touting react etc but I swear every mobile ordering app I use lags like hell.. I don't doubt it. People make terrible websites with React. However ... what might be happening is that you go to some websites, and some of them are great and others are terrible laggy garbage. When it's a bad one you open up devtools and see React, and that leads you to conclude that React is bad. But reality is that the good…

I've had someone tell me to not bother with list virtualization under React, since the 'computer's fast, it won't matter'. We shipped it like that. Turns out the computer's not fast and it does matter.

Your computer is fast and can display hundreds of thousands of divs a second. :)

Re: Why Vanilla JavaScript

#165

Earlier quoted context omitted.

What does the binding look like in source code? Do we hand-code every UI field with the code that updates the local model and then transmits it to the backend? Or is there a way to make the boilerplate as small as possible, relying on one bit of code to handle synchronization between UI, local model, and server? “Using WebSockets” doesn’t bind an interface element to its source of truth; it’s just the chosen transpor…

You are so thinking about this only from a framework perspective, as if you have no imagination. You can answer all your questions yourself by simply writing the code without a framework. Its not that scary. It is as simple as I am suggesting, but only if you have actually done it yourself more than once. Whether or not your application is error prone is entirely on how you execute regardless of the tools in your too…

And you completely avoided answering the questions I asked. If you don’t know or understand, say so. Don’t act like an LLM that has to keep talking even when you don’t know.

Re: Why Vanilla JavaScript

#166

Earlier quoted context omitted.

yeah this is a bit confusing. so you strip the types from the frontend and serve the .ts file as .js file? That's a transpiler/bundler.

Confusing or not it works for me. No compile step and no build step. The application starts up in 0.2 seconds on Linux and about 1.2 seconds on Windows.

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.

Re: Why Vanilla JavaScript

#167

Earlier quoted context omitted.

You are so thinking about this only from a framework perspective, as if you have no imagination. You can answer all your questions yourself by simply writing the code without a framework. Its not that scary. It is as simple as I am suggesting, but only if you have actually done it yourself more than once. Whether or not your application is error prone is entirely on how you execute regardless of the tools in your too…

And you completely avoided answering the questions I asked. If you don’t know or understand, say so. Don’t act like an LLM that has to keep talking even when you don’t know.

It sounds like you would prefer if I just write some code for you instead of doing it yourself. I don't mine doing that. I am willing to advise you with a consultation fee.

Re: Why Vanilla JavaScript

#168

Earlier quoted context omitted.

And you completely avoided answering the questions I asked. If you don’t know or understand, say so. Don’t act like an LLM that has to keep talking even when you don’t know.

It sounds like you would prefer if I just write some code for you instead of doing it yourself. I don't mine doing that. I am willing to advise you with a consultation fee.

So you have no idiom in vanilla JS for this. You just rewrite the boilerplate on every field. Any coder can do that. Do you have a proper abstraction for this or is it just "hurr write the code"?

Re: Why Vanilla JavaScript

#169

Earlier quoted context omitted.

Confusing or not it works for me. No compile step and no build step. The application starts up in 0.2 seconds on Linux and about 1.2 seconds on Windows.

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.

Re: Why Vanilla JavaScript

#170

Earlier quoted context omitted.

It sounds like you would prefer if I just write some code for you instead of doing it yourself. I don't mine doing that. I am willing to advise you with a consultation fee.

So you have no idiom in vanilla JS for this. You just rewrite the boilerplate on every field. Any coder can do that. Do you have a proper abstraction for this or is it just "hurr write the code"?

[dead]
Post reply on HN