skysight-inc/HackerNews huggingface dataset:
But, the Facebook philosophy has always been, of hacking together what works today and think about other things later. HTML5 allows rapid fluid UI(as in feed based UI) development. The native app would have taken atleast 4-6 months for a barely tested app( As an Android Developer, I can vouch for that). They got the HTML5 app running in much less time. Having a lot of resources doesn't mean better quality work. More often than not, small teams are deliberately allotted such tasks to maintain homogeneity in design and code architecture. A mobile app is special type of software where the UI is very close to the other components(i.e Event Handling, Models etc.). Putting a large number of developers on it won't make it go any faster. Think of that scenario: 200 people working on a mobile app, pumping out features and testing sequentially!!How would that even work?
BlackBerry Drops in Number of Stores to Zero Sales
Google unveils its YouTube app ahead of iPhone 5 launch
We make a time series database service: http://tempo-db.com Although not open source, many people who've struggled with open source tools end up using us.
List of NASAs Habitable Planets
What is it like to be funded by Andreesen-Horowitz?
Even if they could duplicate the SMS at that moment, you would still be protected if you use the app.
Yes, they would look the same as on a non-retina MBP. The point is that when placed right next to the Retina apps, the difference would be jarring/distracting.
Zuckerberg Talk Drives Facebook Stock Up 4.6% In After Hours Trading
Ah too bad, I wasn't aware of that since I just get it through my package manager.
Because people really, really like Facebook apparently...
Forget Craigslist, Zumper Will Find Your Next Apartment In NYC Or San Francisco
MP3 is getting very long in the tooth, not to mention the fact that it's encumbered by patents. A new codec would be nice, but hardware adoption of the codec will take a while. Long enough, dare I say, to kill it dead in the water.
I suspect history will show their three biggest mistakes to be:

1. Allowing an IPO that was vastly overpriced.

2. Keeping Zuckerberg in the CEO role for too long.

3. Taking their users for granted.

Obviously the first has seriously damaged their credibility, and with it their ability to hire and retain people who could solve their problems and grow the business.

I believe the second has a similar effect. Aside from the catastrophe of the IPO, Facebook don't appear to be going anywhere strategically. The cat is out of the bag in terms of cost effectiveness (or lack thereof) of Facebook ads compared to alternatives like Google. And generating ad revenue on small-screen mobile is bound to be harder, whether you're using HTML5 or anything else, because the physical screen size only provides so much space.

The third will probably be what finally kills them. As long as they can maintain the critical mass of users, the "everyone's on Facebook because everyone's on Facebook" effect, they can get away with a lot. But no-one using Facebook goes there for the ads, and no-one really likes all the privacy invasion. These things are merely tolerated, and only up to a point, because people like being sociable and right now Facebook lets them keep in touch with their friends and family more conveniently than anyone else.

So when Zuckerberg says "Over the next three to five years, the biggest question on everyone's mind is really going to be how well Facebook does with mobile"[1], I think perhaps he's getting ahead of himself. The biggest question I would ask, if I were a potential investor, is whether Facebook will still have that critical mass of users in three to five years, or whether, like every popular social forum on the Web before them, they will have been disrupted by the new shiny.

[1] http://www.bbc.co.uk/news/business-19565937
Rails developer here, I am thinking of changing jobs right now but am put off by the thoughts of going to bullshit technical interviews where I need to implement / modify some obscure algorithms or concepts which I last saw 12+ years ago in a computer science class.

I would be much happier if the interviewer gave me a small app to create from home (which was relevant to the work they actually do) & then discuss my implementation choices in person with them.

What is the point of having me spend most of an interview doing things with dijkstra's algorithm if never, in the history of your company has this been used nor do you plan to use it & then spend the last 5 minutes asking a few vague questions about what I like about Ruby / hate about Rails.

Technical tests, in my experience, are mostly (90%+ of the time) composed of challenges which have no relevancy to the work I would be doing for that company, its pointless ceremony over common sense.
Looks awesome - I'm wondering if the engine braking is reliable enough to depend on going down a big San Francisco hill?
The problem with apps developed in HTML5 that is not stressed enough IMHO is that the iOS API is good, while the HTML5 API to do a lot of advanced stuff is still limited. In short to develop a native application does NOT take more time than developing one in HTML5, at least for iOS devices. I can tell this first-hand as I used to advice an iOS/Android software company in the past, composed mainly of friends of mine, and in three years of projects the native approach always won: better responsiveness, more access to lower level primitives when needed, native look and feel, easy of development.

And I'm talking about a small startup. To take the HTML5 approach to develop a mobile application for a very large company is simply silly IMHO, and Facebook CEO is right that this was an huge error in their side.
Or they simply don't prioritize mobile. As has been extensively documented, they make virtually no revenue off of mobile use and see no easy way to improve that situation in the future. They're stuck in a situation where a great mobile experience is a near-term harm to revenue.
Javascript would be an obvious choice for anything centered around creating UIs. Palm-now-HP's nice WebOS platform is essentially a recent direct competitor to Android and did that.
Support Another PC Remotely using Soluto
(Went through all this stuff 5 years ago when it was passed in France, so I already went through most of the arguments/counter arguments)

The argument is that they don't care, it is the fault of the account owner if they are not able to prevent "illegal" usage. Account owner should be able to install "something" (they were always vague) that would help him prevent people doing illegal stuff.

By something we always thought it would be allowing ISPs to do DPI or something (and you would off course have to pay for it, because it's a service they offer).
Yes, yes, a million times yes. Facebook is very resource intensive (in terms of data+media loading over the wire) but there are certainly ways to work around this. Yahoo mail's mobile site (at least on my iPhone 4 with ios5) is a good example of this. The main problem with HTML5 media apps today is that they must be developed with a primary focus on optimization from the start. This is unfortunate, and will hopefully change, but it is possible. But seriously, saying "HTML5 failed you" when you don't even compile your scripts and initial resources to require a minimal amount of requests is just ludicrous.

To clarify: I'm not saying that facebook's HTML5 developers can't hold their own -- they produced a great looking mobile app with a truckload of functionality (and believe me, I understand code bloat). Maybe someday it will run flawlessly on mobile. But right now to produce a nice experience in HTML5 you must optimize from the start. Run your code on the device from day 1, not in Chrome with the vertical web inspector! Host your scripts on dev servers with artificial lag. Figure out what's slowing you down on day 1 and work around it! And one day you won't have to :)
Copyrights: How Much of Someone Else's Work May I Use Without Asking Permission?
Telerik buy Fiddler
I'm guessing that the majority of HN readers fall into three categories (note I say "majority").

a) Younger business guys

b) Younger hackers

c) Older hackers

I am also guessing that among the "c" group most are not that familiar with Trump back in the late 70's when he got his start all the way through to now (Apprentice days). I've followed him for many years so I have a different perspective. I can tell from the comments here that many people take a view of Trump based on their limited exposure to him in the last few years. (I'm sure even PG hasn't been following Trump since his start or thought much about him at all. PG didn't become a "business guy" afaik till the mid 90's, right?). As someone who graduated Wharton and has followed business for close to 35 years I can assure you that despite your impression of him now he does well deserve the attention that he receives and he has earned it. Yes, he is a showman and yes people make fun of him. Guess what? His TV show, The Apprentice was very very successful and helped him make plenty of money. He earned that and did something very few business people are able to do. But people tend to throw bricks at many people who gain success and Steve Jobs was certainly no wall flower either. He used his celebrity to achieve and further his goals.

Hackers tend to be less outgoing and more humble at least that's my impression. That's not a feature, it's a bug in achieving the success you deserve, like any "artist". Don't knock others especially people who are known world wide, have TV shows and command premium prices for their name and image.
I buy that. However, we're talking about suicide, not dangerous behavior in general.
Asana and Basecamp (37 Signals)
Exactly. 1999 was a lot like now. In 2001, I was calling recruiters and they literally had nothing. It's nice to think you'll never want for work and you can run out and find a great gig whenever you feel like it, but in reality you never know when the polarity is going to reverse so it doesn't hurt to keep an eye open at all times.
Ditching the HTML5 app was a good call but _please_ fix the atrocious way the new app mangles images with the resizing/stretching. It really kills the speed of the overall experience when I have to enlarge every image to have any clue what its a picture of.
I wonder what Krugman's calculation would be without buying into the "broken windows" theory. Though I'm no economist, a 0.5% GDP boost from a single version of a product from a single company seems crazy.
the recruiter charge is one-time, the candidate salary is recurring and it's hard to ask for a pay cut (much much harder than giving a pay raise)
What now is an API call that counts towards your quota? An API call to the Cloud Code from the client, or each call to a Parse method within the Cloud SDK?
Weren't the issues with their use of HTML5 more related to the lack of proper asset caching (CSS/JS), not so much the performance of the rendering and code execution?

When I used their app at the time, I always found myself waiting for the CSS for each view to load.
are those arrows or equality operations?
Ask HN: Why is there no f8 2012?
September is Facebook f8 time right? Except, apparently there isn't one this year. What's the deal? Is this related to the IPO? You'd think big press and buzz would be exactly what shareholders want, especially given Facebook's share-slide.
It'd be awesome to see use iOS library! This idea is really cool and I'd love to use this for my app.
Don't forget copy and paste.
That doesn't seem right. Facebook has an increasing user base focused on mobile, their main priority for the moment has to be monetizing mobile. It's not a simple solution but it's a long standing problem that they've recognized.
Mark Zuckerberg notes the huge potential in revenue from mobile here:
http://techcrunch.com/2012/09/11/zuckerberg-says-on-mobile-w...
I think your reasoning is flawed here, what is in the good side of HTML5 to develop a mobile app for Facebook, even assuming good HTML5 developers VS good iOS/Android developers? HTML5 is not faster to develop in environments like iOS that provide good API and tools, and the stuff you can't do in HTML5, you have to find a glue between the native side and HTML5 that is non optimal.

So anyway, if you put X efforts, the native app will always win, because it can do all the stuff the HTML5 app can do, but also more, faster, without intermediate layers, in a more native way and with more native look & feel.

Without to mention that for Facebook to use 2x resources to develop the application would be not an issue.

The current Facebook app, if developed by competent guys, is a 3 months project by 2 people, per platform. A joke for FB. (Note: I'm talking only about the app itself, not the backend that is an invariant).
http://www.quora.com/Facebook-Engineering/Why-does-Facebook-...

Why does Facebook not need to produce particularly high-quality software?

By paying less attention to quality, Facebook has been able to focus on other things, like making the company a fun place to work at that can attract and retain talented engineers. Facebook would probably be less fun if it cared more about quality.

Facebook's product is a website, so it can fix things quickly. It has a process which permits rapid deployment of new code, and rapid rollback of buggy changes. This reduces the cost of recovering from bugs.

Facebook's product has a lot of momentum and lock-in. The barrier for users or businesses to move off Facebook is very high. This gives Facebook a wider margin of error to ship glitchy software. If Google was broken for a day, you'd probably go to Bing and might not come back. If your iPhone pissed you off all the time, you'd probably buy an Android when you're faced with the decision in a year or two. If you can't order something on Amazon, you can order it from somewhere else. If Facebook is broken, you keep coming back until it works again.
I like that paraphrase, mind if I nick it?
Nice. I did a timeseries db as well and just recently put it up on google code. I started trying to wrap rrdtool at first and got sufficiently frustrated with it's api that I wrote something that wraps sqlite3 instead. Works great and uses dygraphs to graph the feed.

http://code.google.com/p/gomonitor/
The Marc Andreessen scenario aside, sounds like the right direction for some future of consumer direct marketing... rather than the $s going to an intermediary... it should ultimately transfer to the consumer (assuming said marketplace is sufficiently designed to minimize the aggregate effect of people trying to hack the market without ever consuming).
The main problem with native development is how you are not as flexible as your HTML counterpart. Even with the massive amount of capital that Facebook has, a full native app would always be behind.

Obviously, I don't work at Facebook so I don't know all the details, but I remember when Joe Hewitt built the native Facebook app, while it was awesome, it was lacking many features 4 months after it's release.

Since developing on iOS can take as much as 2 times longer than HTML development (+ the release cycle with Apple approvement system), it makes sense, in my mind, that they opted to have as much of HTML 5 code as possible.

DISCLAIMER: My first language isn't english.
It could easily have been the other way around. Stephanie could have been in a meeting, and upon receiving a call from the author, could have responded by saying "just text me!"
While I agree with the fact that the title is misleading, I would have been even more disappointed if it was just a restating of "JavaScript: The Good Parts".
This would be awesome if the Jack/King/Queen/Ace etc had some neat playing-card style face design done with CSS.
Tell them the screen broke.
slovette: You seem to be hellbanned but I don't see why. Anyway the pro-tethering rule only applies to a specific 4g frequency band, and only for limited data plans.
> develop a native application does NOT take more time than developing one in HTML5

Unless you already have an HTML5 desktop app. In which case, the only thing you're doing is modifying the UI for touch-based input and a smaller screen ... which doesn't take much time at all.

Facebook's problem was that their app sucked. It didn't suck because it was HTML5. It sucked because it was done poorly.
Before someone chimes in with that XKCD strip:

How does Opus compare to other codecs?

Opus is distinguished from most formats for high quality audio (AAC, Vorbis, MP3) by having low delay and it is distinguished from most low delay formats (G.711, GSM, Speex) by supporting high audio quality. It meets or exceeds existing codecs' quality across a wide range of bitrates, and it operates at lower delay than virtually any existing compressed format. Further, the Opus format itself and the reference implementation are available under liberal royalty-free licenses, making it easy to adopt, compatible with free software, and suitable for usage as part of the basic infrastructure of the Internet. See the Opus comparison page for more details.

http://wiki.xiph.org/OpusFAQ#How_does_Opus_compare_to_other_...

Which is to say, this isn't (okay, isn't just) a case of having "too many standards"; Opus is legitimately impressive from a technical standpoint. Oh, and it's unencumbered by patents. That's cool.

EDIT: And here's the coolest part of the article that completely took me by surprise:

"The IETF recently decided with “strong consensus” to adopt Opus as a mandatory-to-implement (MTI) codec for WebRTC, an upcoming standard for real-time communication on the web."
I was wondering recently if there's an equivalent of inkjet-dots in popular digital cameras, either deliberately added, or accidentally in noise patterns, which would allow you to link two separate images to the same camera.

That could be interesting for finding people posting some photos under their real name, and then identifying their other interests they'd prefer to keep separate (legal interests or not).
Google Tablet - Nexus 7 Review
I think you misunderstood my point. Facebook has the resources to have a mobile and native app developed concurrently. I did not mean throwing more developers at a problem to get it completed faster.

In my opinion he was just issuing blanket statements to warm the cold reality that Facebook doesn't care about quality.
I'm not sure if DPI would help much if the torrent connections are all encrypted.

Perhaps you could do something by profiling connections, for example if a particular computer has a large amount of connections open to a large number of IP addresses.
But then again in theory you don't have to download very much to trip over this, downloading 6 separate 4MB MP3 files could do it if you are very unlucky.

The only thing I can think of would be to run everything through an HTTP proxy and then explicitly whitelist IP addresses of individual websites as and when you need them.

Of course this would break stuff like XboX games and any legitimate use of P2P networking.
I tried Stripe for a while and thought it was great, but AMEX charges kept getting flagged, so I had to go back to authorize.net. How's it going for everybody else?
From a design perspective this actually brings Harry Beck's inspiration for modern 'tube' maps full circle.

The 'electrical schematic concept' revolutionized the way these maps were drawn -

https://en.wikipedia.org/wiki/Harry_Beck
Yeoman and Brunch have many differences. You can read the small essay on them here:

https://github.com/brunch/brunch/issues/408

Bower support is coming to brunch in the next release.
Ask HN: Who's right, the VC or the Enterpreneur? 
This topic Ask PG: Is There A Startup You Regret Not Funding? (Like Fred and AirBnB)(https://news.ycombinator.com/item?id=4477867) inspired me to write this.

How often is this gamed played?

The Entrepreneur goes to the VC and ask for money. The VC tells them what's wrong. The Entrepreneur "changes" parts of the company to fit the VC advice. They go back and forth and keep on going until the Entrepreneur is now running a company that has no foundation on what it first started with.

A lot of Entrepreneur have no business experience. The VC's are guys who are rich and thus the Entrepreneur by "default" listens to them for business advice. Until of course, the company runs into big trouble. They all chalk it up to "idea too early for it's time".

This would be interesting if it weren't for the fact there is another company four doors down that managed to succeed with the same exact idea. The difference? The idea itself was closer to the foundation before "expert adivce" started changing a good foundational idea into something they couldn't handle except the "expert" says they must go.

So, here's the question. How does an Entrepreneur with little business knowledge know if the VC is giving them good advice? How does the VC with little technical knowledge know if they should keep their mouth shut or intervene? How do you tell who's right?
Yes, I am saying in many cases we don't know cause of death. In most of the US we do a crap job of discovering cause of death in many cases. When you dig into the numbers specific coroners often have different old guy died in sleep dumping grounds. 'Hart disease' often ends up as a grab bag for any number of quiet killers such as: http://en.wikipedia.org/wiki/Pulmonary_Embolism.

PS: Perhaps the most humorous being http://en.wikipedia.org/wiki/Fan_death, but the sadist and most blunt is probably: http://en.wikipedia.org/wiki/Sudden_infant_death_syndrome which is literally 'death without obvious cause'.
I am still extremely annoyed that the Visual Studio team hasn't adopted something like tmbundles for syntax highlighting. The Fonts and Colors dialog is basically unusable, and the best way to do any sort of bulk change is to export the settings and tweak the very limited set of properties.
For an HTML5 desktop app to become a good HTML5 mobile app usually the changes are so big that you end anyway with a different set of code generating the output for the two "sides".

It does not matter that's HTML+CSS+JS both sides, the device, the interaction, the screen real estate, and the user behaviour when seeing this content in mobility is different.

Actually the risk is that trying to make an HTML5 desktop app also good for mobile is that you overlook a lot of good interactions that are not natural consequences if the starting point is the desktop app.
The iOS game "ten million" was built on unity as I recall. It has been kind of an indie hit.
Only applies to governmental restrictions on speech. Private organizations, like Facebook, are largely free to impose whatever restrictions they like.
Track Your App's Web Marketing for Free With Tapstream 
Do you know where your app's installs are coming from? Facebook, Twitter, Blogs, Oh My!...Where should you put your efforts?

Ben Fox tells us how to track web marketing efforts for apps for free using his product Tapstream.

This interview is chock full of value. Ben and I chat about install tracking and what works best for content marketing. He reveals a killer tip on how to name your app and someone finally gets the the Batman question correct! Check out Tapstream and meet the Derpies!
At 10mph (a more likely speed for this 2.5hp board), worst case, I jump off and run-stop (or roll)... twisted ankle/etc is possible. But at $1200 a piece, I'd really regret the loss/damage that might cause the to the board.
It's a shame this project chose to duplicate the name of an existing project/website:

https://github.com/stefanw/seriesly

http://www.seriesly.com/
It's pretty naïve to think that Fred Trump and his money/influence were not a huge competitive advantage for Donald Trump, even if Fred didn't literally bankroll his projects.
Do you, in fact, have small apps that you send to companies you apply to? Because I personally will spend time asking that flavor of "bullshit" questions if and only if the candidate can't show me any significant code they've written. I have to gather some kind of direct evidence that you are good at actually writing programs.