How true hackers write JavaScript
news.ycombinator.com
How true hackers write JavaScript
1–10 of 342 posts
Re: How true hackers write JavaScript
#2...for a site as simple as hn
Yes!
Re: How true hackers write JavaScript
#3...for a site as simple as hn Yes!
True
Because hackers need much more code lines than those.
Re: How true hackers write JavaScript
#4That might be one of the most readable pieces of code that I've ever read.
Re: How true hackers write JavaScript
#5...for a site as simple as hn Yes!
Most bloated sites don't even have an excuse to be more complicated than this.
Re: How true hackers write JavaScript
#6 function onready () {
recoll();
}
document.addEventListener("DOMContentLoaded", onready);
Just attach recoll() directly. There's no benefit of going via onready().Re: How true hackers write JavaScript
#7Neat
Re: How true hackers write JavaScript
#8https://twitter.com/triskweline/status/798443082740023296
> Valve's Steam Store renders on the server, uses ancient jQuery 1.8, loads 12 unminified JavaScripts.
> It moved 3.5 billion dollars in 2015.
Re: How true hackers write JavaScript
#9function onready () { recoll(); } document.addEventListener("DOMContentLoaded", onready); Just attach recoll() directly. There's no benefit of going via onready().
`recoll(apse)` is a verb. `onready` is an event condition. They are not interchangable. (Though it might be combined into a single line with an anonymous function argument to addEventListener.)
Re: How true hackers write JavaScript
#10No ES2046, is that legacy?