skysight-inc/HackerNews huggingface dataset:
I've seen this story before, and the root cause is almost always the same: too much unpaid technical debt. Certainly I have to grant that you have to take the quick and sloppy solution from time to time. But do it too much and you end up with a team that works its ass off to get very little done.

And the person in charge's response is predictable: "We have to hire more people!". If the business is lucky enough to be successful, you end up with a hundred developers doing the exact same thing since hiring began: working very hard to get very little done.
Really? (I'm being slightly sarcastic...)

I spent a couple of hours on this late one evening a few months ago, delightedly fired off my details, and - never heard anything back.

I'm still pleased that I actually jumped through all the hoops, but the utter silence from the other end? Not sporting at all.
I was waiting for the disruptive argument in this thread.

The fact of the matter is that Javascript is currently (and for the forseeable future) client side language that runs without a plugin. If you want your entire stack to run on Javascript, then server side programming is the only way.

Projects like CoffeeScript are the earmarks of disruptive technology - getting something that doesn't fit most peoples needs to grow up quickly, fit everyone's needs, and destroy its competition before the competition even realized it was there.
Or alternativly the Met did not learn the lessons from 15 years ago when they left the default passwords enabled on their main switch.

Huge bills where run up by phone preaks dialing in and then out again - I even got asked to post to alt.2600 as BT's official spokesman (the Met where claiming it was our fault) but BT Security stooped that.

worrying after the NI revelations I do wonder if its time for the UK to have a proper FBI style police force for serious crimes (and the Grunt end of CT work) and demote the Met to the same level as any other constabulary
CASH Music - open platform for musicians
How to get amazing people to join your projects
In addition, if you want to know which font a glyph is coming from, this extension adds "Show Fonts in Selection" to the context menu, in addition to letting you list every font used on the page and where they come from:

https://addons.mozilla.org/en-US/firefox/addon/fontinfo/
I used to ride the stress to some extent to (temporarily, partially) overcome the distraction. This no longer works -- a caution to younger readers: I have found it to be a recipe for burnout.
Change back/forward to three-finger swipe. Problem solved.

It should be that way by default, hopefully that changes in an upcoming patch or 10.8.
His comment about node.js only being able to use a single core is bullshit, and has been for a while:

* Before native support: https://github.com/learnboost/cluster

* Now, native: http://nodejs.org/docs/latest/api/cluster.html
Goodbye Delicious, Hello Pinboard
This is part of a much bigger evolution occurring in the UX space. This whole change is part of Apple trying to unify their UX across tablets (where "paging" with a swipe is nice) and laptops. One of the most core tenets of UX is consistency and this is an attempt to start to add some UX consistency between Mouse pointers and Gestures. Long term this consistency is a good thing. Short term its going to cause some pain.

Here's the thing its only going to get worse as more and more devices and interaction models start working their way in. My company does bespoke app design and development across a lot of emerging platforms. We're building apps that work on connected TV's, Game Consoles, and mobile devices. Right now we have a project which has an app on LG/Samsung connected tvs which need to be navigated via a traditional up/down/left/right enter remote and the LG TV "Smart Remote" (basically a Wiimote pointer - or a mouse). We're porting this app to the Xbox, on which we need to support the console constroller/Kinect Gestures and Voice. As well as parts of the design are making their way into tablet devices with gestures. One App/Design - 5 different input mechanisms.
Actually if there business is cloud services, and APIs, then it might be a good idea NOT to hire a sales guy if they can't understand the basics.
I wouldn't be surprised if there is a system and your name popped. Years ago, going through US customs wasn't a big deal for me. Now, I've got loads more stamps and visas in the passport I get questioned more, every time. They'll ask about countries I've been in 20-25 flights ago. I give them the "fuck if I know" face.

Legally, they can't prevent me from entering the US, but they sure love to slow me down.
We've had an informal relationship with Carwoo on Twitter. I @'d them this morning, we'll see if they're interested: https://twitter.com/nicksergeant/status/165451476800507905

We've always been a huge fan of CarWoo and thought it'd be a neat partnership with them.
Neither are true.

Non-blocking evented IO is mostly attractive from a usability point of view: it's much easier to write programs that aren't multi-threaded. It can also use much less memory than a threaded model in certain situations.

Non-blocking, evented systems tend to be single-threaded. Single-threaded systems don't automatically scale across multiple cores. To scale, you spawn a separate process for each core (for example, this is the suggested practice for node). You must then find some way for the different processes to communicate with each other, which is usually through a database (or some crazy pub-sub thing).

Node can scale just fine if you design your program to do so. It just scales in a different way.
I think many people on hacker news recognize good design skill takes years to develop, but this is an extreme. They took a simple four word sentence and printed it in red. Do you think the public benefits by having this designer have a ~150 year copyright monopoly on something as simple as this sentence?

It's a simple poster people were excited about and when it was unavailable went out to make it themselves.
Show HN: backup Route53 DNS data to S3
Yeah. I was thinking more about the physical scope of it and the variety and amount of traffic.

I imagine it would be far less expensive for the U.S. and Canada to just open the border and spend some of the savings on policing any problems from that, but I don't really expect that to happen in the near future.
Amen - I quickly learnt node.js to build http handler for the callback element of a tool I am building using authority labs - for what we need its the dogs nuts.
Daily Mobile Minute #99: Follow Friday Version: Asif Khan
The problem with scrolling in Lion is not so much that it's "new stuff" but rather that it breaks a convention that people (even Apple users) have been used to for decades. All of a sudden, by moving your pointer down, you scroll up. It is freaking annoying.

I don't know, I don't like most of the changes in Lion. They look like a really bad "first step" towards something that isn't there yet. Like removing your car's wheels just because you imagine that at some point people will want flying cars that work on antigravity. And then you get the inconsistent bits like making the window buttons smaller. Just... crap.
Hard to put a value on it. If you paid someone to build the site the way it is, you'd be well over $30k with wireframes, design, dev, market research, etc.

We were around 100-200 uniques daily before we pulled the site a few weeks ago.

Maintenance costs are about $250/mo - photos + basic linode server.
This Barry guy is seriously mad about a sign using his unoriginal slogan?

Here is a solution:

I release the following to the public domain:

STAY FOCUSED AND KEEP SHIPPING

There you go, just copy and paste this into your design program of choice, pick a big font, and send it to the printers.

Crisis averted
I recently evaluated Node and Scala for a presence server for an iOS app. With my naive understanding of both platforms, it was way easier to do this with Node. It would be interesting to hear more detail about how Scala was used and why it was better.
Trolling is prohibited on Stagecoach wifi
The user undertakes [...] not to use the Hotspot for the transmission or posting of [...] any material [...] in such a way as to cause annoyance, inconvenience or needless anxiety;
No, the worst is each application remembering your open windows. Particularly Preview.

Let's say you view a sensitive image in Preview, then use Cmd+Q to quit. A week later you open a new image, directly from the Finder, to show a work colleague, and it opens in Preview.

First Preview loads up the previous sensitive image (restoring the state of Preview), and afterwards your work image. Work colleauge sees sensitive image. Embarrassment all around! (Well, actually just lots of laughs, but it could have been!)

Moral of the story: always use Cmd+W to close all documents individually in Preview, and only afterwards Cmd+Q.

Bigger moral: Apple really messed this one up. Opening applications via documents in the Finder shouldn't restore previous application states, because the whole point is that you're starting with a new, specific document.
"Don't use query parameters to alter state"
"Don't fall into RPC with your URIs"

I can see the benefit of doing some of the things on the list, but I never understood what's the motivation behind these two suggestions. What are the practical benefits? (Specifically, what are the benefits for a web application, rather than a web app?)

I can give you some considerable benefits of doing the opposite. My favorite URL scheme looks like this: "http://example.com/?Class.method.id.parts&param=x.

It enables automatic routing without the need to write explicit, case-by-case routing logic or .htaccess files. It doesn't mess up the base path, so I don't need to do some magic when writing URLs. Moreover, it's straightforward. It's easy to see what's going on on the web pages, in the code and in the logs, because knowing a URL means immediately knowing which controller and action are involved (which is not the case with clever resource-mapping schemes).
That's correct. You don't need a unique idea to make money. You just need months of development, followed by a streak of good luck.
Last month I was forced to use a netbook for a week and decided to install Ubuntu with Unity on it. I was really impressed with the user experience. I was probably just as efficient (if not more) than on my macbook!
Because it was a conference call, not a 1-to-1 call!
Node is not for every use case,

This tech talk on node is pretty interesting

http://sna-projects.com/blog/2011/08/nodejs/

I watched it last weekend, and from what I understood/remember from the talk the reason the node people picked javascript was not because they liked javascript. It was because they wanted to do async programming, and they found other languages had too much synchronous baggage. In javascript, node.js could start from a clean slate and build a pure async culture and environment.
Node is not for every use case,

This tech talk on node is pretty interesting

http://sna-projects.com/blog/2011/08/nodejs/

I watched it last weekend, and from what I understood/remember from the talk the reason the node people picked javascript was not because they liked javascript. It was because they wanted to do async programming, and they found other languages had too much synchronous baggage. In javascript, node.js could start from a clean slate and build a pure async cultural and environment.
What is Node.js? (video)
If inertial scrolling were actually implemented everywhere, I might be alright with it. Instead, it exists for the normal case of scrolling content, but when you go to use spaces you hit right and the content goes left. The same thing happens when you scroll to the side to go back/forward, though this is only true if you conceptually represent your current web page as the rightmost of a sequence.

I have liked that Spaces is no longer incredibly broken, but it's a bit annoying that I can't have any configuration other than a really long line full of virtual desktops.
The Graduates.
this is fantastic- great work!
They both contain some truth and some falsehood.

Essentially the first one is most right. Non-blocking IO can get a lot of work done as it is never hindered by doing nothing while waiting around for slow IO. It never blocks so it can always do work.

However, if a non-blocking system has too much work to do it can still max out a CPU. At this point you, ideally, need as many worker threads as you have CPUs.

However, a threaded system that doesn't use non-blocking IO runs the risk of having many blocked threads eating up a CPU & memory instead. This is largely dependent on the light-weight-ed-ess of the threads.

Both these systems are effected by how much work the server has to do to create a response, thus even non-blocking IO can become swamped if it uses a slow language, too much memory or the wrong algorithm, plus all IO must not block or else the non-blocking networking ends up waiting around for blocking files.

There are other complications too like the number of file handles a process can issue that can also impede a server and the number of clients it can simultaneously serve.
Both.

If you're working on a project where I/O blocking is your primary performance issue, Node has a lot to offer in the form of a framework that helps and encourages you to structure your code in a way that works well for such tasks. Javascript's performance and its being single-threaded will have minimal impact, because those concerns are absolutely dwarfed by I/O costs in the situations Node's designed for.

On the other hand, if you're worried about how many threads you can run at once, then you're working on a task where CPU performance matters. That's not what Node is designed for. If you use Node anyway, you've decided to try hammering screws into place - and you should absolutely expect that it won't work out very well for you.
Approaches that become popular and highly publicized definitely impact everyone else's work in that field. Teams decide to migrate to those approaches, discarding others, based on perceived popularity, shallow impressions, small amounts of experimentation. Often, this is all we have to go on. But team members who have an intuition that the approach may have more problems than are first visible now have a choice, to either silently go along with the new decision, or to document their reservations. The anger is an issue though. It's a product of when you perceive a waterfall of hype crashing over your own perception of better judgment (please note: perception. subjective viewpoint). It's worth it to try adjusting those perceptions since anger doesn't really get you anywhere.
I agree, dammit - the entire web should be formatted so no horizontal scrolling is ever required on my 800x480 eeepc!
Node solves a problem I don't have in a so convoluted way that if I ever have that kind of problem I won't be using node for sure.

Is there a need for webstackers to go play at the server side? YES! but node is not THE solution, it is just ONE solution. I venture to say, as javascript evolves more towards a coffeescript flavor, then a coffeescript flavor on the server is what is needed.

And I'll support something along these lines.
This article on how to design a RESTful API is really great: http://www.ibm.com/developerworks/webservices/library/ws-res...
Nonsense. Perhaps your choice to use Node.js is suboptimal? That isn't an indication of Node.js's quality, it's an indication of your inability to choose the right tech. People choose tools that make it easier to do something, Node.js accomplishes that for a wide range of tasks.

I just spun up a IM API we needed in an evening thanks to Node.js and community contributed packages. It's humming along great, I even wrote up a piece about it: http://news.ycombinator.com/item?id=3547664
For what it's worth, setting up a C corp in the USA as a non-resident, which is technically legal, will almost certainly flag you for further interrogation by DHS. If they can find any reason to refuse entry, they will. It's happened to me. [I'm now a US citizen.]
What's Your Personality Type? Insights for Lean Entrepreneurs
"The Ruby and Python communities are just now, many years after the hype has faded, learning that stuff like dependency injection and proper modularization are actually good things"

WTF?!
The rant surprised me at first because it doesn't happen on my MacBook. But sure enough, I disabled it (as well as reverting scrolling back to normal).

I also dislike that the "delete" key backs up a page. It should not be so easy to accidentally move pages, especially since it potentially messes up form data.
Peter Pachel probably stopped by recently and noticed how much the comments are becoming like Reddit, and felt compelled to make the connection and post it on Mashable.
Fullscreening an app on a big monitor was never very useful in the first place.

We use a mac mini for a 'display wall' monitor... which it turns out sucks because OSX doesn't like you fullscreening things.

Then there's the good old 'everyone gather 'round, I want to show you how this works' type thing.

Then there's wild differences in the visual area available on a 13" screen vs 27"+

There's plenty of use for fullscreening programs.
Music possessing these qualities can often provide just the right amount of interest to occupy the parts of your brain that would otherwise be left free to wander and lead to distraction during your work.

Finally - someone who recognizes that there's a curious & busy part of the brain which must be kept preoccupied during complex tasks, and mixes music just for that purpose.

"Trance" music podcasts are a great approximation for this. (See "The Vocal Trance", "Above & Beyond: Trance Around The World", "The Perfect Mix", "Push The Night", "Perfecto Podcast", "The Sound of Trance", "Shakedown Podcast")

ETA: Alas, too many managers don't understand this; they think you're getting distracted by the music, and can't comprehend that it is necessary to facilitate focus.
I know you're being facetious, but realistically the vast majority of websites can be designed to display on lower-resolution displays. It's not a fun experience to read text by scrolling in a Z pattern.
Programming with Node's async model makes it extremely powerful and fast to run database queries and file functions in parallel, but the downside is the potential for huge callback spaghetti indeed.

But the callback spaghetti problem can be largely solved by dropping in, for example, the IcedCoffeeScript fork:

http://maxtaco.github.com/coffee-script/

Or the previous JavaScript TAME functionality:

http://tamejs.org/

There are of course many other async helper solutions as well, and if you're doing serious Node development, it's kind of insane not to use one of these.
Should Apple take more action against march of the iOS clones?
Why is it inappropriate to wrap? It might need some language specific code for old Fortran versions but should be doable...
Never take life advice from someone who responds to hype with a compulsion to "punch faces" while donning "rageface". To be fair though, I bet this is just a casual blog entry that the guy didn't know would hit HN.

http://meyerweb.com/bkkt/okaythen.gif
How hard is getting the work permit (or whatever gets you in in the first place)?
derekja,

thanks for your feedback. Basically, we are getting alarms whenever ReconstructMe pops up (Google Alarms). That way, we found out about your discussion group and we love to communicate and give support.

Best,
Christoph
It depends largely on what your scaling issues are. If you have requests that take a long time because of waiting for replies from web service calls, database calls, and the like, it will be a huge boon to scalability. If your CPU-limited, on the other hand, the non-blocking IO won't help you.
Why do companies hire management consultants?
This is a much underrated point - side-swiping fingers is easier than vertical-swiping them.
HN meetup / pick up a peek to hack today friday at 5pm in nyc
I think the truth might actually be worse. I don't think that `the startup boom is really a disguised job fair for big corporations`. The dirty little secret is that startup scene is an arena and entrepreneurs are the gladiators. Big lumps of money, that seem imaginary to them are dangled in front of their eyes, and they're introduced to former gladiators that have attained fame and glory and were able to buy their freedom, all for the purpose of encouraging the gladiators to fight to the death.
Some die and some succeed and are compensated nicely. Very few attain fame and glory, but enough to keep the ranks of new recruits full.

But of course, it's the owners of the arena, the big corporations who make the real money. Not necessarily from the gladiators themselves, but from the fight. The startup scene is a testing ground, a lab, for Big Corp. It tells them which way the market is going, it tests risky territory. And if something seems to work, Big Corp. snatches it right up. If in the past big research divisions had to test new ground, all on the company's dime, now startups are voluntary crash-test dummies, shooting for a big prize.

And the economics are simple: if the king wants to find a big treasure buried somewhere in the woods he could pay a thousand villagers $1000 each to look for it, or he could offer $0.5M to the one who finds it and let the villagers volunteer for the job. He gets the same work done at half the cost, one villager turns rich and inspires the poor masses, getting a lot of love and attention, while the king still gets to keep the treasure while giving the villagers a fake hope of changing their fate. Simple, really.

So the dirty big secret is this: the startup scene isn't a job recruiter for the big companies, but a way to get workers for free. It's a far worse form of exploitation.

Sorry for all the metaphors.
My first thought was "maybe we should back up and emphasize that resources are nouns before going further", but if you scroll up you'll see that this was actually the original question asked (how do I avoid naming them with verbs?).
Show HN:96% of the Top Newspapers RSS are useless: We fix that
Anonymous pokes fate bear, leaks FBI conference call about Anonymous
I found this: https://discussions.apple.com/message/17468919#17468919

(It looks like he's just unlocking that plist! - I haven't tried it myself as I almost never restart my macs and I'm on my iPad right now.)
I decided to try Gnome 3 (still on Ubuntu) and I am more satisfied with that right now. ( also think it's more aesthetically pleasing) I had some issues with the side dock but gnome's version is a little less intrusive.
Kingdom Rush for iPad on Sale
This is going to make a great movie someday, but I fear in reality it's going to end up with another Bradley Manning (remember him rotting away?)
I have to say that I'm a bit conflicted about this.

On the one hand, there's nothing wrong with "splitting" HN, especially by geography. The main reason being that news that would interest only hackers in a specific region/country wouldn't see the light of HN's front page, as global readers just wouldn't care as much. As a matter of fact, I even run an "HN splinter" myself, for Israelis (https://bitorama.com), and I'm pretty hopeful about it.

That said, the EU is a pretty big and diverse place. Would a guy from Romania or Finland be more likely to find stories that interest him in an EU-wide site rather than in HN? I'm not convinced. Maybe a more regional approach is required.

Then again, I could be proven wrong. So best of luck to the guys running the site!
Then Firefox also copied poorly (wouldn’t surprise me).

It’s a bug in Firefox and Chrome, nothing else.
I couldn't agree more about the Trance podcasts. It's great that these podcasts have no breaks (mixing each song into the next). Music like that with a good beat and lots of crescendos/decrescendos can be ideal for tuning out everything around me and staying focused for a long period of time.
LOL ... guilty as charged. :-D