skysight-inc/HackerNews huggingface dataset:
It appears to work on Java code, not JVM bytecode (similar to GWT), so you'd have to decompile/disassemble the JVM bytecode first.

IT appears to follow GWT in other ways as well such as JSNI-ish interface (can even combine JSNI and native ObjC) and some optimized runtime classes for the ObjC environment.
If you use ruby with bundler you get same behaviour. Something like bundler should have been built into rubygems in the first place.
It would make sense for Microsoft to invest in tools to run C# or .NET code in general in JavaScript, because letting people use Microsoft dev tools that they are familiar with (Visual Studio) + letting them generate code that runs on the web without plugins = win.

There are already some tools for this, Script# from Microsoft, JSIL and so forth. Would be nice if Microsoft decided to officially support this approach with something very robust.
Spoiler alert

The highest I can find after some research is a 7. If you want to see it, Rot-13 this: Jvyyvnz Ehshf Funsgre

Edit: I promise this isn't a Rick Roll.
Rewriting working production code is not something to be done for fun at a hackweek. It's a very serious thing. And since it took a week they had a significant amount of code to rewrite.

What new bugs were introduced by the rewrite? Did they open the door to any XSS attacks? Who knows.
Why are you bringing reduce() into this? Seems to fly in the face of its common purpose, stated on the MDN page: Apply a function against an accumulator and each value of the array (from left-to-right) as to reduce it to a single value.

By doing it this way, you've introduced another symbol for us to consider (hash) and by departing from the standard for loop format, you've made it less idiomatic, which means more people will have to expend mental energy parsing it.
Cramp is based on Rack, just like Rails... there is nothing stopping you from using the two in conjunction.
We have a few, but in general it's large foreign firms and government agencies. Looking for internships through the school co-op offices is near-pointless here in BC; I had to reach out myself to Grow Lab to find anything interesting (although I ended up doing another semester of school, instead).
"web browsers" that support TLS compression or SPDY (which uses TLS compression)

It's quite possible to use a browser that supports neither. Indeed I'm using one right now.
If you're unable to deal with broken, buggy, or poorly designed things, that makes you a bad developer.

Just deal with it and move on. It's really not worth trying to achieve some sort of "Wow I love this language the best it's brilliant" state. It's far better to achieve a "I'm creating some cool stuff that solves a problem" state.

Language syntax is simply not very important. Every single language has quirks. Learn them, and move on.

If you're unhappy working in a particular language, maybe you're not cut out to be a software developer. You should be happy you're creating things that solve problems - if you're not, reconsider your career choice.
I'm thinking it doesn't happen that often, and I would counter with having you think just how much more cognitive effort is used in parsing and debugging the syntax of CS. Remember, debugging and reading "old" code dominates our days, so it doesn't add up for me. As well, if you and the many others that like to claim keystroke reductions, there is no difference in "fu<tab>" for "->" and numerous other comparisons.
Model Trains, Pope Pranking, and Other Passions of the Rich and Famous
Do not blame ruby for the failings of rails.

Personally I have never had any problems with speed when developing large projects with Ramaze, Sinatra or Padrino. In my experience this only happens to Rails. No clue why though. Maybe some gems used by Rails take too long to load.
Last I checked out Django they had just added a bunch of features from Rails 1.2. (Edit: sorry, Rails 2.1)

Python suffers from their web framework community being too fragmented, so none of the projects are as mature as Rails.
Top 3 features that the iPhone 5 learned from Android
That one social convention will probably destroy google glass as a product, making It as popular as the borg bluetooth phone clip earpieces of yesteryear.
CoffeeScript will write that if you tell it to:

[1, 2].forEach (i) => alert i
"If it can be moved to the line above, without any other changes, it's not its own line of code."

Under this logic, all Javascript files are 1 line of code.
Boutine had an Instagram integration already, but decided to use this instead. It was handy since it saved me from having to integrate with lots of third-party services myself.
I'm friends with Jose and quit developing my language Reia because I thought Elixir was better. I've since gone on to develop Celluloid and haven't looked back ;)
sure, but, if you chose to upgrade to Express 3.0.0, would your application still work? or are all the method signatures in Express 3 different from Express 2.5 ?
I think you're misunderstanding risk aversion as not appreciating success.

Risk aversion "why are you quitting when you have a great job" is an individual personalty trait, not one of a whole unrelated group of people. You can find plenty of Americans who would say the same thing.

On top of that, you can't appreciate success that isn't there. You quit your job to start something, that's not succeeding so they weren't appreciating success. Odds are that you would fail miserably.

No, my bet is that what your seeing here is your friends are happy you're trying something you've probably been talking about doing for a while. They're probably your friends because they share some of these same interests, so in addition to seeing a friend do something they want they have the same drive to do it and understand why you would take that risk. Others around you that are not so close are making a risk assessment based on if they were in your shoes what would they think. If starting a business wasn't their interest, that's a huge risk to take for little/no reward. None of it has to do with Americans or Canadians.

Actually, you're a part of why Canada has a struggling tech sector. You moved to the US to start a business. Probably for the same reason doctors do, if you make money, you'll make a shitton more in the US. Other than money, there is no real reason to move to the US from Canada to start a business.
I agree with both of you in some fashion. On one hand, to stop investigating and pushing is to stop breaking new ground. On the other, nearly good ideas can be just as bad or even more so then ones that seem automatically catastrophic. The minute I saw the diagram that showed the difference between the two types of scrolling, the "Oh, no" was already forming in my mind and working it's way through my synapses.

The reason gestures work so well is because they are so greatly different than each other. The flick, the pinch-to-zoom, the tap, all easily discernible gestures. The short flick vs. the long flick? When does it stop being a short flick and start being a long flick?

The idea of a bring to top of page gesture, however, is genius. Now we just need to find a gesture that would be best utilized for it.
Me too. And Google Glass looks a lot slimmer than the big rimmed glasses the hipsters are wearing today.
"Binary Compatible with Android" sounds a lot like "a fork of Android"...
(That was the point)
If you're working on Bananabread, can you check why it's not working on Chrome, the latest stable version? I get an Oops message. I use Windows 7 x64, Core i7 laptop with Nvidia 555m GT .Also just installed Nvidia's latest driver, though I haven't rebooted yet. Could that be it?
How good are you at maths now? I wonder how you compare to the other "brighter" kids on your class.
I've been writing JS for over a decade and never had a problem with it. I put off CoffeeScript for ages, because nothing was wrong with my JS code. "Besides," I thought, "CoffeeScript compiles to JS, it can't do anything JS can't do."

And that is true. Nothing is exactly wrong with JS. In fact many things are great about JS, which is how we end up with ClojureScript and CoffeeScript and x86 emulators. JS is very powerful -- maybe too powerful. There are a million ways to accomplish the same task, which means that during an initial look at a new JS codebase, the program flow is not obvious.

Some developers hate semicolons, some always put commas at the end of the line and some at the beginning, some always use braces and some don't use braces with single-line statements. One can never be sure where a statement ends, or what constitutes a code block, unless one hunts down all the trailing braces, parentheses, and semicolons. I'm not even going to mention all the possible inheritance patterns.

CoffeeScript is not nearly as flexible in syntax. There is one way to make a code block, one inheritance method. It doesn't need semicolons, braces, or parentheses because of its strict style. Therefore there is less to think about. There is less to go wrong. No one needs to use a CoffeeScriptLint, because CoffeeScript is not full of non-obvious 'gotchas'.

CoffeeScript code is more concise and more intuitive, because it reads more like an English sentence. When I read another developer's CoffeeScript I can begin understanding the meaning instantly, rather than having to spend time determining the structure and programming technique. List comprehensions, ranges, and other functional programming tools simply don't exist in pure JavaScript -- the JS equivalent is much more verbose and much less obvious. CoffeeScript encourages creating small flexible code blocks, which together make a powerful structure. This all leads to fewer opportunities for bugs to appear.

The only thing I don't like about CoffeeScript, is that I didn't keep an open mind and start using it sooner. I think anyone who considers themselves a serious JS developer should give CoffeeScript a try. It's a much more relaxing, simple way to write powerful JS.

(Credit goes to Spine.js switching to CoffeeScript to finally push me into it.)

EDIT: Of course it is possible to write ambiguous, unclear code in any language. CoffeeScript is an opportunity to let go of old habits and find a fresh perspective on problem-solving: Maybe there is a better way to do things. (I had to let go of semicolons!)

CoffeeScript's functional programming style has changed the way I approach programming. My code is now more robust and less complicated. Less bugs and less keystrokes mean I ship faster. CoffeeScript is a better language because it's a tool which makes me a better developer.
Exactly, anyone who thinks this is an improvement is not thinking it through.
Bookitbee- alpha launch - would welcome feedback
Esquiar no Vallée Blanche em Chamonix - França
The idea of asset packaging, of course, is not innovative. Jeremy's original claim was that Rails was put on hold. Integrating an asset pipeline solution into Rails took time and commits, and providing an ecosystem-wide solution for something like this has a strong impact on the overall productivity of the ecosystem.
Is there anything in the public domain from Google on this?
Hm. My old professor has an Erdős number of 3. I should see about authoring a paper with him…
Just another datapoint, but contrary to the other comments here I find your reduce example a lot more readable than the original. This could be because it's fairly idiomatic ruby.
>def foo end

>0 lines of code.

I'm having trouble understanding your point here, how exactly is that 0 lines of code when you've actually written 1 line of code which directly changed the method definitions of a class?
Keep up awesome work Justin love the insight behind the scenes
Everything is incredible
I've also been using moqups.com a lot lately and must say that it's pretty amazing as well, although I must admit I'm a bit biased because I just love that it's pure HTML and JS.
I think the author may have misunderstood the claim. Intel was probably referring literally to low power computing (what happens inside Intel's chips) not to low power any-thing-you-can-do-with-a-computer(display, communicate with others, etc). In other words the processor.

Nearly all the power and heat problems in processors has to do with impedance mismatches between materials in the circuit. It's been about 5 years since I went to a conference called Beyond Moore's Law, but I remember a brilliant talk on a 5-6 order of magnitude decrease in power that is possible though impedance matching. (I couldn't find a link online, sorry!)

I suspect (rather arrogantly, since I have not seen intel's article directly) that this is what Intel was talking about.
> }); is not a line of code. Please stop counting it as such.

...then I hope that I never have to work with code you've written, because that certainly is given its own line for readability quite often.

What use is a LoC comparison that doesn't use conventional/reasonable formatting? Technically I can run a program of any length through jsmin and come out with one "line of code", but how is that at all useful?
Why should learning be a competition?
LIVE: Atlas 5 rocket launch
That post reads like a partial fleshing-out of Asimov's The Last Question, and it didn't end like Legends of Dune or The Matrix did although playing with similar ideas. Humanity dividing into 4 colonies also reminds me of the EVE Online backstory, in which humans stumble into a new galaxy and split into 4 warring factions.
So take them off?
I'm pretty sure you can specify the MIME types that the uploader will accept.
https://www.filepicker.io/faq/

Where are the files stored?
We automatically save all uploaded files directly into your Amazon S3 bucket. To make it easier to get started, if you haven't put in your S3 credentials we will store them on our servers, but as your usage increases we will ask you to move to your own storage.
Reminds me of Yvette's Bridal Formal, when it still existed, except about 90% less cluttered.
I think a large part of why people still use cases is back when phones used cheap/er plastics your device would look like garbage after a few months of life in your pockets/purse.

Old habits die hard and I had a case on my old iPhone (3G) and my current Android Phone (Samsung Admire) until I was impressed by how durable the Gorilla Glass screen is. Now I let my phone run "naked" and it doesn't seem to get nearly as beat up as the Razr and Samsung flip phones that predated my iPhone (both got to the point that the paint on the plastic rubbed off).

A buddy of mine who works with Granite has an iPhone 4S and just uses a case to keep the steel band from getting beat up and the ports from getting chalked full of Granite dust. He can slide his phone across a work table and the screen and back are just fine[1]. Gorilla Glass is an amazing material.

[1] Note that Granite contains mineral parts that are slightly to a good deal harder than standard plate glass so it can scratch glass. Gorilla Glass is ~9 on moh's scale. Standard glass is ~5.5. Yay chemistry!
http://www.rockhounds.com/rockshop/hardness1.html
http://chemistry.about.com/od/howthingswork/f/What-Is-Gorill...
"capable of running Android apps"

Assuming that means they have all the Android runtime Java libs and Dalvik, this would answer most people's questions[1] about whether this OS was an Android spinoff (causing Google to disassociate w/ manufacturers using it).

1 - http://news.ycombinator.com/item?id=4516833
jquery improves the crappy DOM API and its vendor inconsistencies, not javascript the language. if anything improves javascript in terms of syntax, it's underscore/lodash or coffeescript.
Ask HN: How do you fight depression?
Created an account just to post this, for obvious reasons. Feel free to downvote if it is not appropriate.

How to fight depression? I am in my thirties - stuck in a boring job, stuck in work visa, hardly know anyone in the city I live (extremely shy and awkward, to add to other problems). Most of the time I don't know what I am doing, or why I am even alive. Not a day goes by without thoughts of suicide, even though I understand it is wrong (I know millions of people are in much worse situation than me, so every suicide thought also brings thoughts of guilt - "if people with much bigger problems can live, why can't you?" type of guilt thoughts). Some days I go from total happiness (for no reason) to total depression in a matter of seconds and just stay there for hours or days. Not asking for sympathy or pity - just genuinely interested in turning my life around.
Developers aren't machines. "What should we work on today?" should not always be calculated as a function of "what provides the most immediate business value." Happy developers attempt harder problems, don't leave their current job to go work on $shiny_thing, and think about their latest project in the shower. All of which are of significant benefit to Dropbox.

That's not to say that you can't lose a lot of money refactoring working code — I dislike rewrites, they always cause unforeseen problems. But great software isn't a function of how many hours you've put into it. It's a complex result of developer morale, time, energy, experience, and skills, and there's a huge benefit to "hey I can think in a language that makes sense to me, instead of remembering weird bugs I have to work around." It's thinking on a higher plane. It lets you more easily load the program into your head. [1] And it can be all the difference if you want a truly exceptional product. [2]

[1] http://www.paulgraham.com/head.html

[2] http://www.paulgraham.com/power.html
Alex Payne, Peter Seibel, Jessica McKellar, more are Hacker School Residents
The reason to use CoffeeScript over JavaScript is because it is better software engineering.

Number of lines of code has been shown to be one of the few good indicators for predicting defects. CoffeeScript significantly reduces the number of lines of code in a project and therefore the number of defects.

CoffeeScript is cleaner and easier to read, which is better software engineering. CoffeeScript solves many of the issues with JavaScript. The fewer warts and plumbing people have to deal with related to the language, the more they can focus on the actual problems they wanted to solve.

This is a little bit like the architectural decision to program user applications in languages and platforms with garbage collection and built-in frameworks rather than using a language like C or C++ with manual memory management and minimal standard libraries. Sure you get less control over the lower-level details such as allocation and deallocation of memory, but those lower level details actually are distracting from the application domain and were actually repetitive and could be automated. So the best way to solve those problems is to move to a platform that abstracts them away or handles them for you.

The reason that developers don't like CoffeeScript (other than the fact that they haven't learned it yet, and don't want to take the time) is simple, psychological rather than logical, and its the same reason that they don't like platforms like the ones I was talking about above: it makes things significantly easier, and that is problematic psychologically for programmers for two reasons:

1) The whole point of being a programmer is that you are mastering complex ASCII codes that other people can't decipher. Making things less complex takes away part of your identity as a programmer (not for everyone obviously, but for many).

2) Many programmers instinctively and falsely believe that any system which makes their job significantly easier must automatically come with compensatory trade-offs in things like performance or flexibility. This is intuitive, but false.

CoffeeScript improvements: indenting two spaces and using -> plus no closing parens and curly braces makes nested callbacks much easier to read and write, fat arrow binds this making it easier to use classes, class and extends provide a standard, simple way to create and extend classes, iterating over arrays and objects is much easier and cleaner, control flow and function definition is cleaner, better variable scoping, simplified closer wrapper in loops, more straightforward boolean operators, existential operator for cleanly and simply checking for variable existence.

Thought of one other explanation for not liking CoffeeScript: plain old status quo bias. http://en.wikipedia.org/wiki/Status_quo_bias
Joel's excellent essay does not apply here. The Netscape re-write was a re-write. That is, it was not a translation. Netscape looked at their code base, and decided, "We don't like the design of the architecture of our code. We're going to throw it out, re-design it, and re-implement it from scratch."

The Dropbox team clearly did not do that. They translated it from one language to another; the design did not change. Much of that translation was with an automatic tool. Again, there is a difference between re-implementing something, and translating it.

Further, the examples in Joel's posts took years. This took a week. The situations are completely different.

Personally, I find it disingenuous to link to an article and say "He has my argument" without actually stating what your argument is.
I can't wait for his Metro review. As that article was year+ old -- his Metro rage shall be epic.
I agree with them on the readability issue mostly, but I don't understand the preference for parens-less function calls, especially where there are arguments.

Maybe it's a matter of training, but

@_update_status_position(e, files)

looks much clearer to me than

@_update_status_position e, files
You should ask this question on Quora
I unsubscribed, and a few weeks later I automatically got subscribed again.
The mozilla project has really pulled it's socks up of late, some of the stuff from the labs:
Very awesome Shumway - https://github.com/mozilla/shumway
Very awesome PDF.js - https://mozillalabs.com/en-US/pdfjs/
IHeartCode - https://mozillalabs.com/en-US/iheartcode/
Prospector Experiments - https://mozillalabs.com/en-US/prospector/
Gladius - https://mozillalabs.com/en-US/gladius/
EntropyWave - https://mozillalabs.com/en-US/entropywave/

And by all accounts FF itself has had some serious work done to sort close the performance gap between it and Chrome.

I love Chrome, it's a top notch browsers, only the omnibox (addressbar) seems be deliberately designed to inflict pain and suffering on the user. You could be forgiven for thinking that it's been deliberatly in some kind of bizarre social experiment. Does anybody here prefer it to the Firefox Awesomebar?

I'm seriously considering switching back to FF. God.
The headline here at HN really needs to add the word "Sky" between "Area" and "With", put "Skywriters" in place of "Arists", or both.
And... where is the creativity curriculum?
There is no such thing as "intrinsic" value. All value is subjective.
Japan May Phase Out Nuclear Power by 2030
Awesome job this guys are doing!! Taking CDNs to the next level!
If they really rewrote it in a week, then either it was trivial or they were able to reuse the bulk of it. The Spoelsky article applies to neither of those cases.
What you described is not the best programmer. It's some kind of superhuman programmer that you get when you combine the best attributes of every single programmer on the planet and spends five thousand hours a day doing computer science research so that they always think of every idea first.

I'll go point by point in a situation where you're just 'the best' and not some kind of demigod that steals ideas before they are conceived.

1. Every library has room for improvement. Even the libraries you make can be improved by average programmers that focus on specific aspects of it.

2. Do you honestly only ask people that are better than you for help? Everyone that can understand a problem can potentially provide insight.

3. Blogs will still have new information, new insights that you haven't gotten to.

4. Same as 3.

5. If the only standard for role model is who is the best programmer ever, then this can be a valid point.

6. Same as 3.

So sure, being a demigod might be boring, but I would be perfectly content being the best at something.