skysight-inc/HackerNews huggingface dataset:
I learned something interesting about NFC recently that I hadn't considered before: for all the wallet kind of applications, where the phone acts like a VISA/Msatercard/etc credit card there has to be a trusted module that takes care of the authentication - e.g. the SIM of the phone. This module is very restricted in who can write things to it, and there's all sorts of power struggles between carriers, manufacturers and service providers about who should be in control of letting apps add things to the trusted storage.

Before that is sorted out, I think that mass adoption of NFC is unlikely, and it's very likely that we'll end up with either the carriers or VISA et al in control - not a very promising prospect, IMHO.
node.js isn't really that fast for traditional apps, but if you were to compare, it's pretty much on levels of nginx and it's actually slower serving static files. only in few cases node.js shows its power, i.e; real-time apps/games. i wouldn't build any full-blown websites in node.js. only a certain piece on the site i'd do it in node, like a widget or something.
You forgot !g (google search). That is at least the shortcut I think is most important. With it, DDG is always at least as good as google, while it provides a better interface.
If it's about higher request capacity, PHP scales horizontally with its share nothing, no application server architecture. I'm not advocating, just sayin'.
Flying in from Paris. This is very cool.

Is it a good idea to rent a car / a motorbike -- how good is public transportation?
Accepted,I am a biochemistry postgraduate in Hong Kong. Looking for other biology guys who is accepted to attend 2012 YCSS?
Most "normal" folks are thinking what Hacker News was thinking 6 months ago ;)
Richard Branson’s Six Secrets to Productivity
I disagree with the author of that blog post.

If you think something should be built, go right ahead. Ignore the naysayers and write what you enjoy writing. Don't listen to people that tell you how you should spend your time.

[I'm somewhat puzzled why this post is on the first page of HN in the first place but that's another topic]
I think the character Barney of the highly successful US TV show "How I Met Your Mother" is a pick-up artist.
I check the "new" section and "popular stories" section once every 3 minutes.

Well, okay, not that often. But close.
> Maps - which honestly is a huge capability regression
> for the end user.

Oh no, on the contrary: with iOS 6 I got turn-by-turn navigation, and not a bad one.
This is using checkboxes ??
Structural Fixes
He did not, it is an advertisement spot.
I assume the OP is complaining about the RailwayJS article on the HN frontpage. Meh.

Personally, wish someone would implement Erlang's OTP in node. That would be useful.

http://www.erlang.org/doc/design_principles/users_guide.html
SENNA by Collobert + Weston do SRL.
It's free for non-commercial use.

Hoifung Poon's unsupervised semantic parser can be used for SRL. It's available as open-source (I think?), but will require more work out of the box to get it working. Namely, you'll have to train it on your data, and convert semantic parses to SRL.
Don't you think it makes more sense to contribute to existing open source projects than rewrite one without offering anything new? DRY?

Don't we have way too many MVC frameworks? Time to consolidate imho.
psssst... shhh... hey guys... Railway.js is right next to us on HN right now, they might hear... sssshhhh
> I've been doing iOS dev for the last 1.5 years

I very much doubt this, but if it is true I am glad you are moving to Android—I wouldn't want to use any app developed by a person who hates Apple that much.
Announcing SproutCore 1.9
Module Oriented Programming: An OOP Alternative?
I also used Turbo Pascal at university (around '90 / '91), and while I can remember some growing pains in terms of learning to program I can't recall any such problems that you experienced. My memory is fuzzy on the detail, but I think there was a time in the mid -> late 80s where Turbo Pascal was greatly improved, and become close to the Object Pascal language which is still in use today.
I'd be guessing you were using the 'pre-improvements' version of TP. I have to admit, I have a soft-spot for Object Pascal, and still use it fairly often (in a project for a long-standing client; the software was originally developed in TP, and was eventually moved to Delphi 7 which is what I use for maintenance to this day).
A general note on TDD: I love it.

TDD encourages better APIs and more testable code. I don't use TDD to prevent more bugs. I don't even know if this is really true.

Everytime I think of a new feature I fastly have an API in mind. Starting with a test almost always shows me a better way to provide the functionality (easier, more failsafe). Thats one of my two key features of TDD.

The second key feature is that the tests you write are much more expressive than tests you write afterwards. I observe that everyday in my team and company. Writing tests after the implementation is done leads to a lot of mocks and just a static verification that the implementation works how it works. In the end, it is difficult to change the implementation and easy to break the specification. Writing your test ahead of the implementation means you test the specification and not how you implemented it. Tests become much easier to read as they express the specification instead of a 1000 lines test where every variable assignment of the implementation is checked.

As a last hint: I read here that people complain that TDD does not work with "prototyping". I agree with that - the problem with that statement is that a lot of people use their prototype as productive code later on instead of rebuilding it after the experimental phase. In my opinion that is a misuse of the word "prototype". A prototype is an experimental work to verify or learn some ideas and afterwards designing a better system.
Other people may state that testing everything is not possible - that there are situations where it is not possible to write a test. I would bet that in 90% of that cases, this is just wrong and means a lack of testing experience of the writer. I can really recommend the following book: http://www.amazon.com/Driven-Development-Embedded-Pragmatic-... I rarly do embedded system programming. My main focus are languages like Java and Go but this book is worth its money independent of your choice of programming language.
I agree. I would do the same but I couldn't find any examples of doing this on the web. One could potentially use Redis or a AMQP as a middleman to integrate node.js's push with a Rails app. If I get sometime on the weekend I would like to try this.
I use railway.js in production for a social bookmarking tool. I come from a rails background but a Rails API has some up and downs. I wanted to try node and have been very impressed. I use railway.js to serve up the iOS API (private beta) and the public beta website. It serves 800 reqs/min on a shared m1.small with one process and I've had no issues with it at all.

It plays a lot more smoothly with MongoDB and I find it far simpler to hook into more modern functionality with Websockets and client side JS rendering. I had a few issues with jugglingdb (which I forked and fixed) and it's all going smoothly.

I still use Rails for some sites but Node and railway.js let me bootstrap the whole API on MongoDB in a few days and get very acceptable performance.
"thefacebook.com/index.php"
IIRC, dukgo does do some of their own indexing, and their goal is to move onto their own indexes eventually. Indexing the whole Internet might have been a reasonable plan when google was a startup, that is a much larger challenge for a small company now than it was 15 years ago.
Isn't Akka inspired by OTP? http://akka.io/

edit: /oops Oh you meant in node, hmm.. /sorry
duckduckgo is a meta search engine, they are using results from Bing so it's as good as bing is.
AMD to Announce Another 5% Employee Reduction?
"Personally I feel like Google isn't doing enough to combat black SEO techniques and content farms. This may be because they are trying to not piss off their users or because those content farms bring them too much revenue."

If it makes you feel better, Google continues to roll out iterations of both Penguin and Panda, algorithms which are targeted at black hat spam sites and low-quality sites.

In fact, this past Friday we rolled out a change to reduce exact-match domains (EMDs), which are domains like "buycheapviagraonline.info" that put a lot of keywords in the domain name in an attempt to benefit in search rankings.
I know several kids who have, on their own, discovered and learned how to use SketchUp, without anything like access to a 3d printer as motivation - just a fascination with the idea of building virtual objects. It's a severely limited tool, but that's not enough of a turn-off to prevent them from learning the basics of 3d modeling. Since completed models can be readily shared amongst those who use 3d printers, I think it's safe to say that a lack of competent 3d modelers won't be a limiting factor for the growth of 3d printing. And as 3d printers become more affordable, the market for better affordable CAD tools with absolutely explode, with SketchUp racing to add more advanced features, and companies like SolidWorks trying to find a way to release an affordable product without completely cannibalizing their existing business model.
It's really the end result that matters, not the tools used.
I totally agree. Derby (http://derbyjs.com/) and Meteor are the only new frameworks out that excite me. RoR is close to ten years old and has thousands of man hours invested into it. Does anyone think a new project that has some of the same capabilities, but lacks the ecosystem/community is going to gain signifigant traction?
I think it completely depends on why you are doing it. There's no better way to learn about the internals of frameworks than to create one.
Should follow Apple's lead and call the next spec The New HTML
it's 2012, why don't you stop blogging
Except that you can't do the 'drag' style toggle on mobile devices. But if they had that, I'd agree with you.
So are you saying the current STM prototype should be put on hold until a "plain old locks" Python comes along?
PyPy (together with LuaJIT and tracemonkey) has been banned from shootout, partly because we complained about unfair rules. Looking at shootout to asses the relative performance of languages where you cannot compare high-performance implementations of a language is a very very bad idea. Looking at shootout to compare would very likely be a bad idea anyhow, but right now it's just completely useless.
Heading up to Stanford from Mountain View :P Originally from Sydney, Australia :-) Here's a post I did on "Things to do in Silicon Valley" and other Silicon Valley related stuff. Enjoy!
http://www.theroadtosiliconvalley.com/local-california/thing...
If anyone is looking for room/board be sure to check out
http://chezjj.com/

Several YC alum stay/stayed here.
I doubt it but you never know. However the original iPhone's aluminum back scuffed too, and it never bothered me one bit. Same with my iPad. I expect it will be a bit more noticible on the 5 as I got the black one, but at the end of the day I have much more important things to think about than some scratched aluminum.

More to the point, Apple tends to go for simple design and ignores fashion trends. They have the colored iPods but that's more to appeal to kids and people that want a little more personalization rather than because yellow and green are in.

Also, I'm going to slap the next pundit that refers to this as "scuffgate". Protip, guys: Watergate was a proper noun, not a random mashing-together of words.
This is not a helpful comment.

Regardless of how entitled to cynicism you feel, try to keep your feedback pragmatically optimistic. I remember when the founders of Heroku told me that they were going to build a web enabled Ruby on Rails editor, I thought that was pretty dumb, too.
What looks sexier on your resume though:
"Creator of backbone.js" (Not trying to pick on backbone since it's a great project, but you can read the entire source in an hour)
or
"Contributed to making AR 5% faster for certain queries"

I'd much rather see 10 people put their time towards making one project better, then seeing 10 people start 10 divergent projects with dreams of becoming the next DHH, but I recognize that there are other factors at play.
This looks like it's getting HN'ed, google cache is here:
http://webcache.googleusercontent.com/search?q=cache:srirang...
Actually, it's not just any tablet.. It's actually an iPad with safari browser open. Look at the image without the overlay (http://www.themobileplaybook.com/assets/images/cover_tablet....)
Seriously what the fuck is with all these articles lately that are just links to Slashdot?
5 Open Source Projects You Should Donate To
I think it would be easier to take the best stuff in the node ecosystem and port it to Erlang than the other way around.
What I don't like about PUA is that the general philosophy seems to be "try over and over to do things to women. It doesn't matter that most of them don't want it, because some will. Keep pushing until you get what you want." This philosophy is widely held outside of PUA culture, and I hate it everywhere, but PUA culture seems to really put this idea into overdrive.

What is glossed over by the PUA community, is that the practice leaves a wake of doing things to women over and over that they don't want. It's written off, like "you win some you lose some!" but you just made someone's day a little worse, and caused the general animosity between men and women to be turned up a notch. The reason a man can't just say hello to a woman and have it just be a friendly hello is because of PUAs and others who follow this principle.

Women walk around totally shell shocked because of the constant "numbers game" onslaught of men who are trying to "pick them up" and I personally think it needs to stop. There are respectful and disrespectful channels for meeting new people to date, and PUA literature drives people into the disrespectful ones. That they "work" doesn't cover up the collateral damage.
Factorie's a nice piece of work, I highly recommend it. The team at UMass has done a great job.
Not to mention that when I search for something like "football" I obviously mean AFL (Australian Rules Football).
Google shows the correct result on the top.
Duck Duck Go shows a Wiki disambiguation link and then at least 5 pages of either Round Ball or NFL.

Sometimes it needs to be: please.bubble.us
There's a glaring typo: "try in you browser"
I never expected to read an article urging a technology company to hold back on innovation. This is really the saddest piece I've read in a while (meatspace news included).

The author has some very misguided assumptions beyond the fallacy of the general idea:

1. Apple is not the only game in town: Android is gaining market share (and not just on the low end devices, either), Jelly Bean is fantastic. Nexus 7 has converted few loyal Apple fans around me already.

2. Apple needs an appealing device to get the masses to buy new phones: they can't pull another 4S. Has to have a significant enough change to get the sales they are after (and frankly, expected to deliver). The 5 is a very good compromise between not alienating existing iPhone users and catering to the owners of the 4S.

3. The screen size of the iPhone was no longer competitive. The market clearly wants larger displays and there's only so much that people are willing to overlook to remain with their favorite ecosystem.

Apple won consumers by radical innovation, disruption in its fullest sense. Apple has proved that you don't make middle of the road products to appeal to all users, but rather that you can actively reeducate the general population using wonderful products.

Just 5 years ago, an iPhone-like device would have been considered an overly technological and complicated relic with usage far removed from anything in the market, and here it is used by elders. This is not because Apple (well, Steve) aimed at what the general population wanted, but because they gave users something exciting and useful, and everyone embraced it.

This quote is usually attributed to Henry Ford - "If I’d asked people what they wanted, they would have asked for a better horse"
Apple shouldn't be giving us better horses, or locomotives or even cars. They should be giving us wonderfully designed and greatly usable spaceships that just work.
All the best orangethirty! My two cents…the obvious benchmark / status quo in search is Google's no-fuss solution - a kind of 'wham bam thank you ma'am' (before you urban dictionary it, I mean that phrase in the context of quick & to-the-point). So, what if you differentiated by being the antithesis of Google? It's so crazy it just might work. Be visually-rich and inject the principles of emotional design into search. Create 'clusters' or 'hubs' of results around the search term - a visual representation that deliberately includes a smorgasbord of websites, images, e-commerce, blogs and key social media pages. (If you went with value proposition like this, hackers wouldn't be the best target as early adopters; I know a visually-rich environment would resonate with the female, right-brained and design demographics, and there are certain markets in the world where this concept would have a particularly popular acceptance - South Korea, Taiwan, Indonesia and Japan come to mind).
Android had market-share, but will you get paying customers? Every article I've ever read on the subject is that iOS customers are far more willing to pay for apps than android users.

Of course, if you're making a companion app for some other service which makes money it's largely irrelevant, but numbers alone don't tell the whole story.
The web is pushing programming in a good direction, but it puts more pressure on the programmer. A good webapp not only functions well and looks good, but it's composed of components (the DOM) which are malleable and understandable by other programs. The important program is the Googlebot, but there are countless other, lesser programs (such as a bevy of bookmarklets, and even programs like Evernote) which benefit from having our applications be parsable.

The biggest thing holding back web programming is not JavaScript, but CSS. Making stuff look good is way too hard. I know a lot of programming languages, but CSS is by far the hardest language I've ever had to learn - the interpreter is a black box, properties are strangely coupled, and there is no error reporting or insight into the layout engine. Not to mention that it is difficult if not impossible to accurately know which selectors apply to an element short of actually running the page and checking in a tool! But I digress.

The fact is that we're paying the price now, but I think it's worth it.
Out of curiosity, why's that? Why do you need a browser for dev and a different one for actually browsing the web?
It's debatable. You can have perfectly valid reasons to develop your own framework:
- you want to propose something different compared to existing solutions in the field, where your vision is clearly incompatible with what already exists
- the coding standards for an existing, similar solution is not acceptable, and unlikely to change

On the other hand, many a "me-too" piece of software crops up simply because it can be easier to reinvent than to contribute (not implying that RailwaysJS is that). But TFA's point is also that server-side-heavy frameworks are a thing of the past, which is a fair argument.
Easily verified from app store links on my site:
http://www.plastaq.com

People like you are truly puzzling. Apple is just a business, not a religion.

If Apple drops these patent suits and starts allowing opt-in side loading of apps I'll happily come back.
Hey, I'm currently evaluating a number of Node.js web frameworks for a project I'm working on (I'll eventually publish the results on my blog). So far, I have reviewed: RailwayJS, Locomotive[0], Tower.js[1], GeddyJS[2], Derby[3] and Meteor[4]. It would be really great if you could give me your opinion on how RailwayJS compares to those (especially Tower.js, GeddyJS and Locomotive as they seem to be competing directly).

[0] http://locomotivejs.org/

[1] http://towerjs.org/

[2] http://geddyjs.org/

[3] http://derbyjs.com/

[4] http://meteor.com/

... more Node.js web frameworks: https://github.com/joyent/node/wiki/modules#wiki-web-framewo...
Contributor to a well known project > Creator of an obscure, unknown project
Take a look at Derby (which is similar to Meteor) as well (http://derbyjs.com/).
Perhaps I'm missing something but how is this a matter of opinion? If one wanted to avoid callbacks, which were the OC's original issue with node, one would break up the callback spaghetti into distinct, possibly prototyped objects, and glue them together with node's events. How is that any more difficult to maintain than, say, Python classes? If anything, I personally like the ability to choose the coding style with JS in this case, e.g. callbacks are great for quick prototyping when you can't be bothered to organize everything properly from the get-go.
Honestly, this blurb/blog post whatever it's supposed to be just gave me temporary brain damage.

Hands down the dumbest thing I've read (half of) in the last few years. Wow.

Let's compare it to the Mac. Wow. Jesus. Mind-blown. Titanic stupidity.

Who wrote this thing? Should be persona non grata from the Internet.
not sure which one you're implying sounds sexier, but if i were reading his resume, the AR contribution would definitely strike me as more significant. compare "wrote a fuse-based filesystem for whatever" versus "got several patches into the ext3 tree"
Yet the luminaries of TDD actually imagined it might be able to evolve good algorithms...

You might undersell it; they oversold it.
If I were a math grad-student type and actually had the talent and skills to get into a high-paying quant job, I'd consider doing the job for something like five years, saving everything I can, and then leaving for more fun jobs with the option to live off the investment income from the savings whenever I don't feel like working for a year or three.

If the salaries really go to $400k, saving up a million in the five years seems possible, and investing that with 5% annual return would give you a quite nice for the math grad-student type $50k salary for free.
Sure, but a lot of programmers' dream (not mine) is to be the creator of the next big thing and gain accolades from other programmers. That won't happen if you're strictly contributing to other projects.
In an industry that valorizes github profiles as a substitute for resumes, how is duplication of effort to be avoided? It's like expecting everyone to use a different word for "managed" on their resumes.
Very cool! Do you have any data on how long the "happening" lasted? Would be neat if you could somehow incorporate that into the size of the circle in the left graph, or instead of showing the number of happenings on the right graph, you could instead show the downtime.
It's very easy to lock a helmet up with your bike--just put the lock bar or chain through the "ear triangle" on the female clip side.

Sure, someone could still steal it by cutting that strap, but what is the point of a helmet that can't be clipped on? And if bike helmets are so unpopular, why would anyone steal one to begin with?

Finally, if your bike helmet is stolen, then you are simply biking home without a helmet--which is the condition you'd be in anyway if you didn't bring a helmet in the first place.
HTML, CSS, and SQL are all fantastic domain-specific languages. It's the split between frontend languages like JS and backend languages like Ruby that's the real problem.
The Chrome Omnibox tends to fill that role for me. If I type "cloj" and hit the down arrow twice in Chrome, it takes me straight to clojure.org. And it's integrated with my history - once I've done it, if I type "cl" and hit return, I go straight back.
Dating life in Silicon Valley compared to elementary school