skysight-inc/HackerNews huggingface dataset:
Google Chrome Developer tools has a nice "Pretty Print" feature. It makes the JavaScript readable without the need for an extension.

http://imgur.com/e51Hk1o
Tested on macmini 2009 (or 2006? the one without hdmi anyway , 2GB ram, Core2 T7200@2.00GHz, Intel 945GM onboard GPU >_< etc) running Debian wheezy and compton. Surprisingly html5 was the smoothest of the two, but with no sound. Conversely, sound was crisp but the game itself seriously 'choppier' (with regards to FPS) in Flash 11.2.202.258 .

Obligatory htop screenshots:
http://666kb.com/i/cc6jh5a4d3wqopmqu.png < Flash
http://666kb.com/i/cc6jhhh5ywa8qrlgm.png < html5

Browser in use: Chromium 24.0.1312.68

Not sure if the compositor (compton) is responsible for the lag or something else entirely. I don't really have the time to test any further :S
At the risk of giving away a million dollar idea; nobody's gonna wanna really edit things in the browser. Too risky and missing features of whatever their favorite editor is.

But how about letting people push their code up via git? So you could have a runnable browser window open, push your changes up to your runnable repo and then hit run?

If this does turn out to be the key that breaks this open please remember it was my idea.
The View From Outside the International Space Station
I get a strange line that goes down the flash version every few seconds, nice and slowly. Chrome, rMBP.
Godspeed you pioneers who are venturing forth and coming back to report on your successes and failures. Many of us ObjC/XCode types that love Ruby are carefully watching... But feel its still too early to take those chances.

I wish that I had watched PhoneGap more carefully. Had I paid attention, I definitely wouldn't have chosen that route. I make that comparison because the gotchas aren't apparent until you've fully invested. I think that same might be true for RubyMotion. I'm happy to be wrong!

Would love your comments here: http://news.ycombinator.com/item?id=5344037
CodeMirror's creator's Tern.js reaches its funding goal
My comment was in response to this idea that Russians were crazy to think there were underground spy networks of right wing Jews in Russia. But right wing Jews openly boast of doing this. I generally come to this web site to read about B-tree algorithms and VC funding and have no desire spending too much time debating the USSR circa 1970. But anyone who is interested can Google "chabad underground" or "chabad underground russia" or "chaba underground ussr" for starters. As I said, these are not third parties, but actual Jewish participants bragging about these underground spy networks in the USSR in English - in documents and on Youtube. If you know Hebrew you can read and hear even more. I don't have too much interest in spycraft, but their open bragging after the collapse of the USSR belies the notion of the top poster that these spy networks did not exist.

As far as my comment history, anyone reading it can see this poster is full of nonsense as I never discuss the Russian air force in any respect. As far as "distaste for Jews", the reader can play a mental game if they wish - again one can read my comment history and conjure up a mental image of a theoretical Jewish person in the US. They are assimilated, secular, educated, intellectual, deracinated, grandparents were labor organizers, older cousin has stories about the Hashomer Hatzair kibbutz they once lived at. Then conjure up a mental image of an orthodox/ultra-orthodox, religious, insular, Zionist, anti-communist Jew. THEN conjure up an image of a fundamentalist, evangelical, religious, insular, and Zionist, anti-communist Christian goy. I have met people in my life who could be categorized in any of these three categories. I would say I enjoyed being with one of those types of people, and had a distaste for the other two. The above post says I have a "distaste for Jews". I leave it as an exercise to the reader which one of these types I enjoy spending time with, and which two I have a distaste for.
A lot of these success stories with RubyMotion seem to come from newcomers to iOS development like the creator of Jukely in this article. I can understand that it must be a large benefit to adoption to be able to use Ruby rather than learn Obj-C and at the same time XCode. Despite this, what I would like to hear is the opinions of Obj-C iOS app developers who have used RubyMotion in their projects.

I can't really see RubyMotion working in an app dev team at the moment. In my last iOS job for instance, I was working on legacy Obj-C code. Can this easily be ported over? Does it deal with retain/release well?

Also, can anybody comment on app development times Obj-C vs RubyMotion (given that you know both)?.
Just FYI if you click on this link you will not see any pictures of bikini models.
Stay tuned :)
We already offer this in our private beta.
That may be a reason why, but far from the only reason why, Heroku is more expensive than a cheap shared hosting provider. Heroku provides a lot more than just hosting files and running server instances. They provide all kinds of value-added services in deployment, logging/monitoring, security and performance auditing, package management, git integration, database choices and plugin apps, etc etc.
Looks like the Streisand Effect (http://en.wikipedia.org/wiki/Streisand_effect)!
In a few short years, laws will prevent you from driving on the public roads without some level of automation.

There are something like >30k deaths on the highways per year these days. That's the equivalent of all American Vietnam war casualties every two years. The highways are more dangerous than any war the US has been in since the WW2. And a very large proportion of those deaths can be called "innocent" -- not at fault in their death in any way.

There really is only one reason this is accepted by the public. Because there is no alternative. There is no policy you can establish that would stop the deaths that would not also inconvenience everyone too much.

Once self-driving cars fall down in price enough to be a real possibility, every highway death where a non-automated car was involved turns from something sad, but inevitable into something that is squarely blamed on the existence of that traditional car. "This wouldn't have happened if Datsundere wouldn't have put his personal enjoyment above the safety of everyone else on the road."

Since car makers will be happy to lobby for this (why not, they get to sell everyone something new), since there will be enough relatives of dead people so the grassroots support is strong, since the federal government has control over roads, and since there are no strong lobbies to oppose it, this will pass as a law as soon as it's actually feasible to replace/refit all the cars on the road.

The best you can hope for is a car that will allow you to turn off the automation in situations the car deems safe, with the car automatically taking over if it feels like something is wrong.

Beyond that, the only place you will have a fun driving experience in the future is on the track.
> I can't imagine the car manufacturers will be able to handle the costs of the liability by themselves

Manufacturers are already liable for the damages caused by crashes, etc., due to manufacturing defects. Heck, several of the textbook cases on manufacturer liability for damages resulting from defective products involve automakers.

> I mean, nobody wonders who's going to cover the liability of a subway system.

Actually, they usually do, especially if the owner and operator of the system are different. The difference is, most people are neither the owner nor the operator of a subway system.

> Perhaps this will wind up a government service, out of reach of the personal injury lawyers.

Government transit services are not "out of reach of the personal injury lawyers". Heck, there are personal injury lawyers that specifically advertise about these kinds of cases, e.g., http://www.quellerfisher.com/vehicle-accidents/subway-accide...
What are you sorry about?
I don't think I implied otherwise.

Stating it a little bit differently, if it is ok to put "Some features require an internet connection and are only promised to be supported until Jan, 2015" on a box, then I think it is ok to put "Game requires an internet connection and will be supported until at least Jan, 2015".

A requirement for accurate labeling is reasonably simple, especially in comparison to hairsplitting over whether it is appropriate or allowable to depend on the internet for a particular feature.
New Money Ventures to Silicon Valley
>Edit: wow, thats a lot of hostility... didn't realize linode reached fandom status. I guess I should keep my opinions to myself then?

Sometimes, yes. In this particular case you were comparing apples to oranges.

Take for example your opening line: "I never quite understood the love for premium vps like linode".

The statement is absurd -- even if one includes the part about low cost VPS being faster.

The idea behind "premium VPS" (or premium whatever) has to do with support, reliability, them being around a while, etc.

Some cheaper VPS offering "more bandwidth" or "faster cpus" is not the same thing at all.

Now, if you had said "there are cheaper VPS just as reliable and with good support as Linode, and on top of it, faster also, so why _pay_ a premium", that would make sense. If you could also support it.

But a statement like: "I don't understand premium X" in general?
The big problem is that current liability is relatively limited by fleet diversity.

Toyota has enough variation in their fleet that even if a floor mat can cause a stuck accelerator, it's only an issue for certain models of certain cars. Similarly, GM only had certain models with sidesaddle gas tanks, so even if someone causes an outcry with a doctored video, it only applied to some models of some vehicles.

But if Google had a bug, would they have the same variation in driving logic to limit the scope of the fallout? Wouldn't it more likely relate to all their cars?

What if an unforeseen environmental event compromises sensors in a way they didn't code for? Say a rare particulate cloud due a mining operation, or building collapse, that doesn't blanket the sensors with noise, but merely distorts their readings such that a large spate of crashes occur.

What if a more mundane overflow or date bug causes enough slightly-less-optimal decisions to be made that there's a jump in accidents that can be traced back to that bug?

What if someone discovers a 'blind-spot' in Google's logic that could be leveraged to reliably cause relatively-low-risk accidents and black-hats use that to perpetrate a sudden and distributed insurance fraud scam. Would they even be able to withstand the fallout of a "massive jump in Google car accident rates" story, until the truth was ferreted out? What happens to Google if that gets shared online? Is Google going to be able to withstand the fallout of the public realizing their cars can be scammed unless they're diligently watched? (which defeats the entire purpose of having purchased a driverless car)
does changing editor imply not using the keyboard
Paypal launches simpler apis
Train Yourself To Become a Top Online Marketer
I did and it was terrible.

He brings up the idea that they'd be spotted and doesn't have a good response to it, he's basically just dismissive of it. "Oh well Sauron wouldn't be able to react in time." Ridiculous.
ZO+ will replace APC, only the user-cache from APC will be left (see also this comment: http://news.ycombinator.com/item?id=5343883).

Object literals and scalar type hints won't be in 5.5. Scalar type hints may be in the next version (it's a rather tricky topic). For object literals I don't see reason to add them at all (in PHP you can just use arrays ^^).
Amazing lack of critical thinking for a scientist.
Being on my 4th internship right now I would suggest to anyone hiring interns regardless of location that the best thing you can do to them is treat them as if they were a full-time. I know personally what I'm looking to get out of an internship is first and formost actual work experience.

We are looking for the same things any hire is looking for. (interesting meaningful work, have our opinions heard and respected, a culture that fits with our personality, good pay etc.) The only difference I would say is they will likely not have as much experience as your top employees so expect a bit of a learning curve.
I recently started learning EmberJS which forces the user of Handlebars. I thought maybe I was crazy, or maybe I was missing something, but your comment makes me feel a little bit more sane.

Why oh why would you ever use Handlebars over, say, Underscore's templates which allow actually logic? In my (admittedly limited) experience, both choices are equally as simple when writing simple templates, but Handlebars is a colossal pain in the ass when trying to do something significant.
Interview with "The Pregnant Hacker"
No one is going to use it while it has dubious copyright status anyway

By that measure everything has a dubious copyright status, as anyone can send out DCMA notices.
Get small business owners in every month to teach

I learnt how mega international corps did strategic planning at university without ever seeing someone who sold day to day
Glad I ran across this this week- I would have most likely ended up with a security hole in an app otherwise. (I had thought read-eval=false was an adequate safeguard...)
Yes. If self-driving cars significantly reduce accidents, insurance companies can use it as incentive to lower rates. The rates for cars that can only be driven manually might even skyrocket.
I feel like there are dark factors at play for dropping the XP support. Although the most thorough discussion of it is at http://programmers.stackexchange.com/questions/177732/why-wa..., the conspiracist in me says that Microsoft (pierre's employer) pressured him to drop support - even though it wasn't entirely necessary to do so.
KillerStartups.com along with Startups.com domain are for Sale
Can the Mods update the URL... it is http://zakelfassi.com/2013/03/08/all-googleio-easter-eggs/ instead of http://zakelfassi.com/2013/03/08/all-googleio-eater-eggs/
Big data startup The Stakeholder Company maps your influencers.
10 years of PyPy
TIL! What an odd requirement.
PayPal Launches Simpler, Mobile APIs And More
Wow my bad, I had assumed DMCA counter notices were instantaneous.
Your landing page needs screen shots or at least some information on how you're approaching the problem. As you already know, to-do apps aren't exciting enough for me to go "YEAH! Sign me up to hear all about it!" without some incentive (the approach/UI/something is interesting enough to want to see it)
executing code you didn't write is unsecure. news at 11.

...am i missing something? isn't this the same problem as with evaling json in javascript?
Universal Display to bank on smartphones until OLED TVs take off
I think this is an excellent write-up of the state of the world with Clojure 1.5: http://clojuredocs.org/clojure_core/clojure.core/read

In short, don't use read-eval at all if you want safe reading. Use the clojure.edn alternatives to read data safely in those circumstances.
>If driving becomes a feature of the car itself and that feature fails in a way that causes and accident, there's no other answer.

That is one answer but it is not the right answer if you want to encourage driver-less car use. A better answer is to put together a set of standards to govern the proper behavior of a vehicle operating systems (VOS). These standards could encompass, a proper dashboard, the ability for the driver to take control, how a car should act under various scenarios (e.g. some key sensor stops working on the highway). If the VOS follows the proper behavior, than there is no liability to the automaker, if it doesn't, the automaker is liable.
I think it's entirely likely he knew what was up with the suitcase. And nobody ever went broke overestimating the male ego.
This whole episode has underlined a few major differences among developers and (current) designers. Developers are more open, contribute code and discuss about bettering each other.

While Designers seem secretive, ego-filled and seeking pointless exclusivity.

Eg: Developers: HackerNews / Github, etc
Designers: DesignerNews / Dribble, Forrst, etc.

Any designer that has been open about his work and process has become a legend - Dieter Rams, Johnathan Ive, etc.
CTO for NYC Event-Recommendation App (Flyer)

This position could be ideal for an up & coming Ruby/Obj-C developer looking to grow into a CTO role, or an established CTO who feels like the excitement with their current setup has fizzled…either way, someone looking for a growth opportunity and great ride at a startup. We’re looking to replace our previously incoming CTO, who was promoted unexpectedly at his current full-time employer. We plan to pay salary commensurate with an established NYC startup, with meaningful equity…not a sub-percentage that you might find elsewhere. Flyer has been founded by two former finance professionals and is building out its team in advance of a July pilot. We've been funding to date on our own and have ~$1mm of capital lined up at ~$10mm valuation.

Our team is looking to get your advice, input and guidance on a range of important technology elements of our organization. Areas of focus over the next year will include scalability of the platform as we launch and grow the user base and volume of content in our system, and feature additions as we learn what users want/need.

Backend: we’re building our our Ruby-based API in the Padrino framework, which should allow us better performance than Rails, while utilizing a similar structure. We’d like to incorporate your vision as the API is developed, and want your input on solving a number of challenges around the database and data model, all of which tie in to Flyer’s core goal of delivering relevant event-related content to users.

Front-end: a native iOS app using native iOS tools, developed in Objective-C using the Cocoa framework. We will only use the most proven open source libraries to make the code reliable and enjoyable. My co-founder and I have been working on the UX for seven months: two full wireframing processes, weeks of FieldTest user testing and tweaking UI, etc. We're looking forward to getting these screens fully functional so we can continue to test and improve.

Overall, it’s been a very engaging challenge finding solutions across the many aspects of creating this product. We’re looking forward to adding another member of our team as excited about this project as we are.

Please email tadsmithflyer@gmail.com if interested!
This is basically what got Ruby with its YAML reader, isn't it?

EDIT: I'm not familiar enough with clojure; is read-line supposed to be safe?
Other than improving their API, PayPal should really join this: http://www.portabilitystandard.org/ but maybe they're too afraid that many will run away from them
Antigen is to zsh, what Vundle is to vim
+1 for RSS.
Well, if we are being pragmatic it sounds totally acceptable for any kind of business.

Except maybe if those outages hit them at the worst possible moments of the month (just before a major announcement or something).

Now, managers would froth at the mouth hearing 45 mins/month is acceptable. But those managers are idiots.

I haven't seen any major site that didn't have those (and worse) outages.

5-6 hours a year? Heck tons of sites had those. AWS had them (and thus Heroku had them), GAE had them, Twitter had them, Tumblr (well they had one-two orders of magnitude more), etc.

45 mins a month represent lots of lost revenue to you? Really? If you're not Google or something, then what exactly do you do?

Shouldn't that be like 0.1% of your revenue? And that IF you sell online and IF we assume customers aren't gonna come back. Heck, you lose more because of random fluctuations in buyer preferences than that.
SSL + CNAME + static files hosting on GAE: almost free
Google's Motorola Unit to Cut 10% of Workforce
Vifm also has windows binaries nice
Makes sense. The idea of using Handlebars instead of embedded Javascript is that the template can't actually change the model, just get data from it, so there's no real logic on the template. Of course this is all theory, as I said in the blog post, it was just an idea. Once I use this approach, I can definitely state the pros and cons.
I'm in no way affiliated with the project. I just thought it needed some more attention because it is awesome.
Someone who buys their games based on the principle that they should get their moneys worth within a few months of the purchase could easily overlook some bugs at the beginning.

People that spend $20 or $40 to go to a movie for 2 hours can't be that worried about maximizing the value they extract from a $60 game. I do look at it from the standpoint of not wanting games to work like this, but I can see how someone might not care much, especially if things smooth out soon.
With Positions to Fill, Employers Wait for Perfection
Totally right. I'll get the license sorted out asap.
And the title: "All the Google IO Easter Eggs (and How I Got Them)"
>Heck, several of the textbook cases on manufacturer liability for damages resulting from defective products involve automakers

The difference is that very few accidents are the result of defective automobile. In the hypothetical world where most(all) people ride in drive-less cars, the car manufacturer would be theoretically liable for EVERY car accident.
> People may object to insuring the manufacturer of the software responsible for the crash.

What people? The manufacturer either self-insures or buys insurance on the open market, just like everyone else that has a civil liability risk, and builds the cost of that insurance into the price they pay to the work. I mean, public opposition could, in theory, lead to a law against third-party insurance for this use (though its hard to see, given the wide range of things for which insurance is marketed -- if public opposition was going to ban insuring industries, there are a lot of existing industries that you'd think would run into problems way before vehicle-control-software manufacturers), but nothing can stop them from self-insuring. There is really nothing special or unusual about this.

> I'm thinking int he context where every car is driverless. It's probably even more complex when they aren't all driverless.

Its probably not at all that complex in either case. As now, the operator is probably liable for damages resulting from operation outside of the bounds of legal parameters -- including failure to maintain the vehicle in safe operating condition, and the manufacturer is probably liable from harms from manufacturing defects, and these liabilities often overlap.

The particular types of manufacturing defects that are possible change, but that doesn't really change the basic equation.
demosquared@ gmail.com
European Parliament blocks citizen e-mails protesting 'porn ban' proposal
I have to remember that line ;^)