Live data from Hacker News

Elbowing JavaScript out

blog.ikura.co

61–70 of 100 posts

Re: Elbowing JavaScript out

#61
post #31

If I'm on reddit and had to reload the page for every upvote/downvote, comment expand/collapse, show more comments, and reply the ux would be significantly worse. And thats not even a site that has that much user interaction.

Indeed, Hacker News' one piece of JavaScript is for the upvote mechanic.

Re: Elbowing JavaScript out

#63
Judging from Ikura's web page as well as the lack of Internet presence and name of the interviewee here (Amy G. Dala... Get it, amygdala?), I'm inclined to think this interview is fake.

In any case, I've noticed a tendency to conflate JavaScript with what I'll call "JavaScript abuse". I'm guilty of JavaScript abuse and I'm sure many of you are as well. But to attribute this to any programming language, regardless of bad parts, is the sort of blame-shifting we should try to avoid as developers. "Never use X" might be a solution to a problem but it won't necessarily guide you to good design patterns.

We've all heard the old adage "use the right tool for the job" but its just as important to do a good job with the tools you have. It's possible to write pages that use CSS and JavaScript to enhance your users' experience while also being small and rendering perfectly in Lynx. If you're having so much trouble with JavaScript that you eschew it completely, maybe there was an issue with how you approached the problem rather than with the language itself.

Re: Elbowing JavaScript out

#64
The entire argument against JS fell apart in the last paragraph. As long as it's not me who is writing JS but some 3rd party library which I just pass data along, then what I have is no JS.

Re: Elbowing JavaScript out

#65
post #11

I think I understand that this article was trying to represent an interview of someone who is successfully creating complex web applications without JS, but it was written as though all of the readers already understand how to do this. Where's the "why" and "how" behind this? What's the advantage of leaving out JS? How do I do client-side interaction without it (the interview seems to imply that we do everything serv…

For example, the article references "OTP" but doesn't define it. Is this Erlang's OTP? Apparently it is because Cowboy is an Erlang HTTP server.

Re: Elbowing JavaScript out

#67
post #59

I'm coding JS now professionally for 20 years (so, quite from the beginning) and I love the language. That said, I think, current frameworks are, with all due respect, rather over-engineered. – A tool chain consisting of at least 8 items, a multiline CLI command to compile a hello world that comes at a mere 19.500 lines of code? (Some may remember when early Java versions were made fun of for a 2MB hello world object…

But maybe it comes down to the fact that many developers simply like over engineered solutions and sprinkle some complexity to often boring problems? Not saying that it's always the case but surely many of us can recollect related stories :)

For me, its more about the frameworks shoving between you and the presentation layer. It's not realtime and interactive anymore (rather about packed and delayed update/repaint cycles). Consider what could be done alone using the canvas 2d-context with the current API. There isn't a visual thing that couldn't be done with this. Some may remember the creative wealth of CD-ROMs in the 1990s – we may have all of this, but better. Instead, it seems more about a glorified mark down presentation layer. We really could do better.

P.S.: Maybe, this is just an old man's rant about the old days like when PostScript was all written by hand and typo came in stars. But I'm really underwhelmed by the state of creativity on the web.

Re: Elbowing JavaScript out

#68
post #3

The worst part of JavaScript is that the relevant committee is simply failing to acknowledge that there are lots of bright computer language designers out there who'd love to have a chance to bring their creations to the web.

Sorry, what? The relevant committee is a bunch of bright computer language designers, doing the best they can while navigating a maze of legacy, backwards compatibility, community, and bureaucracy concerns with every step they take.

Re: Elbowing JavaScript out

#69
post #22

It's pointless to be a contrarian on JavaScript. It's here to stay, but it does appear there's a big push to be able to write something other than plain JavaScript (that produces JavaScript) to bring more sanity to the development process. That Microsoft is pushing a superset that produces JavaScript ( https://www.typescriptlang.org/ ) and Google is also behind Dart ( https://www.dartlang.org/ ) that produces JavaScr…

> In a few years JavaScript will most likely be the 'bytecode' of the web

All major browsers are working on WebAssembly as a bytecode for the web: https://webassembly.github.io/ I expect we will skip JavaScript for TypeScript/Dart -> WebAssembly in the future.

Re: Elbowing JavaScript out

#70
post #19

We can only hope more people lose javascript. Please ?

Javascript is a great language. Transpiling another language to run on the browser (looking at you , zombie GWT!) will NOT make CSS and event handling any less complex.

not worried about complex... i miss being able to surf the internet on smaller systems than it takes to run entire clouds stacks on
Post reply on HN