Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Why Vanilla JavaScript

guseyn.com

Post reply on HN
Print view View original

21–30 of 176 posts

Re: Why Vanilla JavaScript

#21

Post by teaearlgraycold »

pianopatrick wrote: post #7
Gualdrapo wrote: post #5

I wish there was some sort of "use strict-typed" or something that let you use in-browser interpreted typescript

Well, you could use jsDoc to hold your types instead of writing them in typescript. The typescript compiler can still check types in jsDoc comments but you do not need a build step and the javascript you ship to the browser would be the same you write in your editor.

It works really really well. No one should be writing untyped JS anymore.

Re: Why Vanilla JavaScript

#23

Post by stana »

WhyNotHugo wrote: post #15

I appreciate the sentiment, but can't agree fully. I used vanilla JS for many years before AngularJS even existed (and I also tried AngulasJS when it was the new thing). Vue is just a huge convenience over raw JavaScript for large, complex view. Sure, I don't get to do direct DOM manipulation, but when I write C code I also don't get to pick which variable goes in which CPU register. I accept giving up control that A…

Writing programs in C has simplified developer experience over Assembly. Issue with JS frameworks is that many find them complex, i.e. complexity has not been abstracted away (which should be goal of abstractions). Maybe DOM manipulation has, but many new complex ideas had to be introduced to achieve it.

Re: Why Vanilla JavaScript

#26

Post by umvi »

Even better: vanilla TypeScript + golang middleware (esbuild) on the backend that converts to JS on the fly. Like vanilla JS but with all the benefits of a type system and no bundler or npm required.

Re: Why Vanilla JavaScript

#27

Post by lezojeda »

prokopton wrote: post #17

It’s been a minute since someone ranted about frontend frameworks. Take a shot.

And he ended up... creating frameworks himself. I fail to see the whole point of the article tbh. It's a rant against JS frameworks/libraries and the frontend in general all to end up admitting he did the same?

Re: Why Vanilla JavaScript

#28

Post by JBits »

WhyNotHugo wrote: post #15

I appreciate the sentiment, but can't agree fully. I used vanilla JS for many years before AngularJS even existed (and I also tried AngulasJS when it was the new thing). Vue is just a huge convenience over raw JavaScript for large, complex view. Sure, I don't get to do direct DOM manipulation, but when I write C code I also don't get to pick which variable goes in which CPU register. I accept giving up control that A…

Is it mainly the reactivity part of Vue that you benefit from, or are there other aspects which are important?
Post reply on HN