kenOfYugen

Maybe it's time browsers improve the decoding performance of HTML5 videos.

Well it was a literate response to a mother asking Einstein for tips. Surely it can be interpreted your way too. A strong imagination is linked with creativity anyways, which is good for 'hackers' to have. In my honest opinion imagination is useful for everyone.

“If you want your children to be intelligent, read them fairy tales. If you want them to be more intelligent, read them more fairy tales.”

  ― Albert Einstein

Let him grow and make his own choices, just be a good loving parent and have faith in him. Forcing knowledge and skills can backfire, make sure you mediate your passion for hacking to him ;)

Would love to see more examples. Are there more references available? Any similar projects?

JS

  var result = exclaim(capitalize(doubleSay("hello")));

ES7 Proposal: The Pipeline Operator

  var result = "hello"
    |> doubleSay
    |> capitalize
    |> exclaim;

CoffeeScript

  result = exclaim capitalize doubleSay 'hello'

I'll take CoffeeScript.

You should check out the "Guidelines"

https://news.ycombinator.com/newsguidelines.html

and the FAQ

https://news.ycombinator.com/newsfaq.html

For when I was starting school, I wish the Web had existed :P

> "Did I experience the concept beyond the technical definition?"

Thanks Kalid! Wish there were more resources in that notion available when I was starting my Telecommunications studies.

lwan is king in JSON serialization. Can't wait to benchmark the node.js integration project[1]

[1] https://github.com/raadad/node-lwan

Brings back memories ...

"Severed hands in an occult context occur as early as Herodotus's 'Tale of Rhampsinitus'"[1].

In the "The Invisibles" as well [2].

1. https://en.wikipedia.org/wiki/Hand_of_Glory#In_literature

2. https://en.wikipedia.org/wiki/The_Invisibles

"A FLIF image can be loaded in different ‘variations’ from the same source file, by loading the file only partially. This makes it a very appropriate file format for responsive web design. "

Awesome! I have been toying with custom png 'container' ideas in the past offering similar 'responsive' features (i.e various resolutions, lossy-lossless versions)

I would like to see the ASM.js version of the decoder and see how that one performs.

JS win and Go win. GopherJS was the reason I was considering making the transition to full-stack Go.

Seems like the io - node merge is working well so far. Frequent releases in the non breaking stable branch are the way to go.

Would it be possible to update node.js to v4.0.0 and rerun the Express Cluster benchmark? node.js v0.12.x was slower than v.0.10.x, while v4.0.0 is supposed to be faster than both. Sorry for making this request if it's out of your field of interest, but couldn't resist asking :)

EDIT: My mistake, I thought you were the author of the benchmark

All websites look the same because they rely on 'best practices'. If you have a 'better practice' go ahead and implement it, thus inspiring the best practices to come.

That's how the human world evolves, slowly blending the old with the new.

Yeah, being a happy drunk and not smoking a cigarette is tough, and 'accidents' do happen. For me that's the toughest part of the psychological addiction to drop completely. But it's fine, like you, I get back to vaping when I sober up in the morning.

In order to quit smoking you really need to want to. Else don't even bother.

Best way to get off smoking is to start vaping. Get two high drain 18650 batteries, a quality charger, a dripping atomizer and a mechanical or regulated device.

Actually vaping can be much more fulfilling than smoking, whether you are looking for a nice flavor or a nicotine high.

Building and wicking coils yourself, mixing glycerin with flavoring to produce your own blend, as well as maintaining your equipment clean, are part of keeping your mind interested and occupied when it comes to getting your fix which in my opinion is key.

Nicotine absorption is much more efficient and you end up ingesting less of it when you find your sweet spot.

Then you must replace smoking with vaping in activities that are linked with the smoking addiction, (like when waking up, or during coffee, or after lunch, or after sex, when having a drink, etc.)

Then before you know it, you won't be craving cigarettes any more as the psychological addiction would have been cured. After that you can either continue vaping or slowly stop vaping as well. Some people keep vaping just flavoring and drop the nicotine completely.

If you stop vaping, keep your vaping equipment around, because triggering a smoking habit in the future due to unforeseen events, is highly probable.

That's anecdotal information of course, but works for me and a lot of other people it seems.

Enjoy using it in my terminal and sublime text editor. I slightly prefer it over Manaco/Menlo ..

From a more academic approach [1], if you care about efficient concurrency and no context switching between frontend-backend, the node.js platform is an excellent choice.

Figure: http://imgur.com/NnQ9M5v

[1] http://link.springer.com/article/10.1007/s00607-014-0394-9 "Is Node.js a viable option for building modern web applications? A performance evaluation study"

The battle of front-end frameworks is powered by companies trying to lure new and inexperienced developers, as well as experienced employees already working with teams of developers, into a more unified thought pattern. For that purpose they are great. On the other hand, the underlying "magic" isn't optimal for all use cases. The author states:

"If you have a highly dynamic application that needs to rerender frequently, and you want to avoid the heavy weight of template diffing, [...] ReactJS’s virtual DOM will be super effective. However, if you’re site doesn’t have those needs, CHOOSE SOMETHING ELSE!"

Well choose a DOM representation implementation in this case. That's not what React is all about. And may I add that, "Virtual DOM" or however you want to call it, will never be as fast as manual DOM manipulation done right. It's just a well documented convenience magic abstraction.

We no longer have vast incompatibilities among browsers, so we no longer use JQuery. At the same time, threads pop up everywhere titled "how do I do [this] in [Angular, React, etc.], just like it has happened with JQuery in the past. And I won't even mention framework specific "plugins" ..

The underlying problem is, the majority of people involved with JavaScript for the web platform, are afraid and/or lazy learning it. And no framework can cure this, but at the same time frameworks help us hide the pile of ignorance we have under the framework carpet.

I'm not bashing anyone, frameworks can inspire and help organize vast amount of work. But at the same time they are hard dependencies, hailed by well known developers. Sooner or later there will be new ones [that got it right this time] and the cycle of hype-wow-sucks will continue. Well they are all built with JS, so how about you take your time to learn the language and philosophize a bit on programming, state management, application structure and the capabilities (as well as the bottlenecks) of the web platform? Then you may choose any framework you like at any time and you won't be shooting yourself in the foot because you'll be using it as a tool, and not the panacea for all your troubles.

oh what have you done to him? is he drugged on ADD/ADHD medication? ;)

Lovely dark teal gopher!

Gopher is a cool mascot, although I really enjoyed "The Autistic Gopher Hypothesis" I read some time ago.

For humor's shake: http://www.evanmiller.org/four-days-of-go.html

Related material, number of modules and average growth/day by [http://www.modulecounts.com/]

           count | avg/day

JavaScript..214,741.|.379/day.[Bower + npm]

Java..........114,860.|.108/day.[MAVEN]

Ruby.........106,195.|..50/day.[Rubygems]

Go..............86,512.|.299/day.[GoDoc]

PHP.............68,276.|..99/day.[Packagist + Pear]

Python.........64,865.|..56/day.[PyPI]

Modulecounts offers info for more languages, I just did a TL;DR

EDIT: is there a good way to present data on HN?

Well fortunately in the web we have already got standards committees. As long as those standards are supported there should be no problem.

Unfortunately current mainstream browsers don't comply with the standards to the fullest, although I admit compliance is orders of magnitude better than years ago.

Aren't Chrome only apps and web sites harming the web?

I agree with testing Linux software completely. It's maddening how much the notion of testing is ignored.

Well it's a win-win situation, build the ideal browser, then you have already built the "ideal" OS ;)

By no "browsing features" I mean something closer to a headless browser. Just a library. Is that what WKView is about?

Allow me to present an analogy between operating systems and browsers.

You can install Arch/Debian Linux or Ubuntu, and there is no collision there. You build your OS the way you want it or you run an automated installation and soon you are doing work, browsing, watching movies, etc.

My point is that if Debian wasn't what it is, you wouldn't have Ubuntu which offers additional value to a typical user, and be stuck with Windows forever. Choice is of value.

Do you want to be stuck with Firefox, Chrome etc. knowing how hard they adapt to real needs and ignore bug fixing in favor of new features?

A browser is not your 'typical' application. Browsers are in my opinion true virtual machines and should be treated as such.

Isn't WebKit the rendering engine itself?

The "ideal" core I was talking about should be able to use WebKit as a rendering engine.

Mozilla made a language in order to build their new browser engine, servo [1]. That language is Rust [2]. The reasoning was that we have been relying for too long on systems languages where memory safety [3] related bugs have caused a lot of exploits [C, C++].

In big codebases, like the browsers tend to be, bugs have many places to hide, and such bugs are very hard to spot. You can't rely on contributors being extra careful continuously, because everyone makes mistakes. So by using a programming language with a garbage collector or memory safety guarantees, like Rust, and enforcing extreme modularity, critical bugs are much easier to be spotted.

[1] https://github.com/servo/servo [2] https://www.rust-lang.org/ [3] https://en.wikipedia.org/wiki/Memory_safety