skysight-inc/HackerNews huggingface dataset:
I do, I hate when I do it. It also doesn't add to the conversation. Especially when I do so on items that are questionable, as this one is. What bothers me most is that the level of snark I use is dependant not on the level of offence, rather the number of times I've encountered this varian of low quality comment during the day. This example, although I stand by it, clearly is not one of the greater offences, and yet has maximum snark. The greater problem is these conversations actually often surpass the quality conversations being had in the thread.
Facebook Reach 2014: How Facebook Is Killing Itself
Does this study have any bearing on "hammock-driven development" vs. the compulsion to start writing code (with or without TDD)?
Performance — It May Not Be The Database
Luckily most locations in Amsterdam worth their salt is connected to AMS-IX, https://ams-ix.net/connect-to-ams-ix/colocations

If AWS setup deployment in Amsterdam, I can't imagine it wouldn't be in one of those places.
The "natural state of man" is to work from sunrise to sunset to find enough to eat, and still sometimes going to sleep hungry. The hunter-gatherer lifestyle wore people out so they died at 30! The natural state of humans is to be active. The question in the modern world is what activity.

Incidentally, my experience of job sharing is that it doesn't scale. You get 2 or 3 people, they arrange the job share among themselves, everyone is blissfully happy. Then one leaves and how do you fill the position, when it was tailored for one specific individual's lifestyle? The other sharers then find themselves having to adapt again, and maybe that's incompatible with the other commitments they've picked up thanks to the arrangement. 9-5 is actually the least-worst option all things considered.
Pretty sure that is the only reason that this hasn't been fleshed out into a fuller anti drm system. It is easier to get it drm free from other sources and they get it sooner.
>Getting rich is necessarily hard, otherwise everyone would be on the road to becoming rich. People are unlikely to get rich by doing work which satisfies. But if they make it, then at least life won't suck anymore.

The whole point of an economy is to make it easier and easier to become wealthier and wealthier.
I've shocked myself badly a few times and to me at least, I'd much rather wallow in self pity for a while than do it again.

Probably the worst was one I didn't expect, I slipped when opening a plastic case and caught my fingers over a fully charged high capacity 350v capacitor. The initial hit makes every muscle in your body hurt, then a wave of panic when you realize you could have died from the moment of stupidity.
The question "Why Kallithea" really should be why "Why Kallithea over Github, Gitlab?"
Where are the aliens? Where are the dragons?
I think the real problem here, and it is a true problem with Haskell development, is perfectionism.

Code in Haskell can be so elegant, and examples of beautiful code are so abundant, that hacking together a bunch of hacks to see if they work doesn't seem like a conceivable way of doing things.

But of course, Haskell can be used that way to figure out and explore your problem. You can throw IORefs around, do everything with ugly IO effects, pass tons of parameters around, etc.
It seems almost pathological to commit to continuing to do something even when you don't want to do it anymore. And there's no way to predict how you will feel in that regard a couple years later. What is the point of making a promise like that? I'm not arguing for the parent's more lax stance on the commitment of marriage; I'm just saying I don't see why people choose to marry to begin with.
I read somewhere that they used device with 9V battery. We used to lick both 4.5V and 9V batteries as kids. I found 4.5V hit to be quite pleasant and I would repeat the "experiment" a lot. Licking 9V battery was less pleasant, but not really too uncomfortable. I did that multiple times too even through my room was full of toys.

Their device could generate less pleasant feelings, sure. But I am kind of skeptical of big conclusions people take out of this study.
And given that I'm currently borrowing (and conveniently forgetting to return) swombat's copy of the aforementioned book, I would have to agree.

I've been recommending it to everyone as a counterpoint to the Lean Startup stuff. It's hard to make a real decision if you've only got one voice in your ear.

Probably my favourite book I read this year. Well worth the time.
Pretty cool, I wrote a utility in Go [1] similar to this that also extracts and compresses related CSS, JS and images for offline use.

[1] https://github.com/johnernaut/webhog
I completely disagree with what you have said.

I have meet a lot of wealthy/successful people and trust me, they are way more happy than the poorer people I have meet. They've achieved their dream and can continue doing so. They have traveled, they given back, they create things, they are loved and they're happy.

>On your death bed you probably won't be looking over your life and decide whether it was worthwhile or not, and give yourself some report card on it. Instead you more likely won't even remember more than bits and pieces, and then eventually die and forget it all.
You're wrong about this one. The biggest regret for people on their death beds were having gone through life with goals unfulfilled. http://www.theguardian.com/lifeandstyle/2012/feb/01/top-five....

I've always found it funny how others like you label rich people as having a shit life. That they can't find true love and have to hire escorts etc.

Success is what makes you happy. That could be making a billion dollars or milking cows.

Most of people have huge dreams and goals they want to achieve, its just that most don't care and don't try.
Considering this, what are the odds of MS ever shipping IE clients for OSX and Linux?
It's not about "hate".

There's no emotion involved, in fact.

It's about rationally looking at a given tool, considering its capabilities, considering how it can be beneficial and harmful in a given situation, and considering how it compares to similar other tools.

Sometimes this analysis is in favor of a given tool. PostgreSQL is a good example of this. It excels in many different ways, including some that overlap with MongoDB and other so-called NoSQL databases.

Sometimes this analysis is not in favor of a given tool. MongoDB is a good example of this. It has some pretty serious issues, and there are often better alternatives.

When people suggest to not use MongoDB, it's generally not some emotional response due to "hate". It's usually because they've considered what it can do and how it works, and it turns out that in pretty much all cases there is a better alternative available that should be used instead.
slightly off-topic but I am pretty interested in learning about SOA architecture using Node.js apps. Can you refer any guides/links ?
Web Applications that Scale Forever and Upgrade Seamlessly [video]
Must be an unfinished or deleted button. The image is standard `NSAdvanced` system image, which is usually first in the drop-down lists in Xcode. When a developer does not have final graphics and needs to pick just anything they often click the first one in the list, this one.
Exactly. It isn't that money isn't good or useful, but that it takes effort to earn it. Nobody should say no to free money but if it has to be earned, then there is an optimization problem at hand.
This seems like a poor study to gauge peoples' desire/aversion to thinking. You put me in a room with nothing but a button I'll probably press it out of curiosity. Put me in a garden with a enjoyable drink and I'll happily contemplate whatever comes to mind until I want to get a refill.
AutoIt and Malware: What’s the Connection?
Poppy Project - Open Source 3D Printed Humanoid Robot
Many, many people willingly meditate ("alone with their thoughts") on their own will in order to focus and clear their mind, including me. And that's despite I do have traumatic events in my past that float up from time to time.

No thoughts of self-mutilation or electroshocking myself so far.

Either is this study flawed, or it was reported poorly (hey, what's new, right), but I'm so sick of shitty studies in popular media, I won't even try to figure out which one.
> If it's not natural for you to think ahead, create the structure you need before writing it up, Haskell is not the right language for you.

No, Haskell is probably even more fit here. Haskell is a godsend for prototyping! Because you throw any crap into the editor and with Haskell you'll know immediately what's wrong with said crap. And then when you refactor it later the compiler will guide and help you.

I feel like people just haven't got balls to see many compilation errors and prefer buggy, non-working, but “see! no errors, not like in those haskells!” code.
Booking.com misleads customers
Still Diet Project by Dan Bannino
"""I get the point that people may prefer external stimulation to internal thoughts. But I think the result of this study hinge on whether the electric shock was really all that unpleasant."""

All of these is beside the point.

An electric shock, mild, even pleasant is a BS diversion.

People prefered BS diversion (could be even clicking a button that did nothing at all) that spending a few minutes with their thoughts.

That's the real story -- not how bad the electricity was etc.
Mate is pretty cool and a lot of people I know jumped ship to it from Unity. Good luck with the project.

I personally use Xubuntu on my netbook, desktop and installed it on my parent's computers as well. Arch+Mate or back to Debian+Mate has been on my radar for a bit though.
Ie6 is ancient history now. Ie9 is the new ie6.
I'm certain I didn't. The article asks the question about spreading, and that includes all vectors and scenarios. Spreading, is all about reaching and establishing an infected base.

As far as if ebola can get TO the western world, that is a 100% chance that it can. Primarily, because there is always an underground movement of goods and people, often women and children into and out of countries, regardless of official lockdowns. Think of it like drugs in prisons. There should be no place more free of drugs and alcohol, and yet it's easier to get drugs in prison than in my town. The conversation then is about the remaining requirements to 'spread'.

When we take a look at spreading of other lifeforms, say for instance seeds in Darwin's Origin of Species, dispersal is only a tiny part of the equation with spread being about not just buoyancy, but rather length of sustainability once the seed arrives at a barren landmass.

This is again consistent with man and Mars. We've gone there with robots, and will one day go there with people, but until we establish a foothold, we have not yet spread to Mars.

Regardless of whether the article addresses the point and only the question, all examples of life (and disputed forms of life in the form of virus), do not spread unless they take root.
You mean ship IE for OS X again like they did before Apple made Safari? For a time, IE for Mac was the very best browser.

I could see them doing it if it was a gateway to an ecosystem the way Chrome is for Google. For "Linux" i.e. some specific variant that became popular with consumers.
That's not a very convincing example.

Let's ignore the fact that it's a trivially small example to begin with. I don't think it's very representative of larger apps, especially ones that are far more complex than a very simplistic blog system.

And let's ignore the fact that the SQL-based one is around 10% shorter than the MongoDB one, too, in terms of their line counts.

The SQL-based one makes the queries very clearly visible. It's easier to find the queries, and for anyone who knows SQL it's very clear at a quick glance what they're doing. It's much harder to isolate the queries in the MongoDB one. The visibility of the SQL queries makes maintenance easier, and performance tuning easier.

And I don't buy the dynamic query argument. Those are often the most fragile ones used, and should generally be avoided, if possible. It's better to have two or more similar queries than it is one that's built dynamically. Even then, it's often possible to write a single query with more complex filtering that can handle numerous very different cases.

At best, the MongoDB example is roughly equivalent to the SQL one. In practice, you're trading off a huge number of benefits of relational databases (SQL usually being one of them) for little to no gain when opting for MongoDB instead.
I think the issue is we've been slowly accepting that the node is the right way to do things. Five years of working with someone will do that to you. If you follow me on twitter you probably see me complain about it in various ways all the time, it's not that I'm bored with it, node's problems are real and some people just seem to ignore them, or maybe just deal with them because they know backwards compat can't be broken immediately. It has always bothered me that people would advocate such broken systems (streams etc) when real-world alternatives were better even before now, even C has a much better example of what a stream should be.

I'm definitely not the only one writing large systems, but I think the tolerance level varies per developer. Also plenty of people make a living/name from Node, of course they're more likely to praise it than to be honest about its faults, I'm definitely a minority in that respect. Having broken concepts is one thing, but resisting change when they're obviously broken is not a good thing. Many of these same people make money from consultation, where it's advantageous to have a broken system. I'm not trying to screw them over but someone has to be honest.

It took years to get .addHeader() in because no one in core believed in a progressive API, they didn't use node in real-world applications to see the need. This still happens all the time, take npm-www for example, Isaac is a rad guy but him aswell as most other "core" community members advocated building tiny little things and stitching them all together, and just recently realized that in practice this doesn't scale, thus ended up going with Hapi. This lack of insight is all over Node as a community.

It's hard to describe well, but I hope people will try Go (or similar alternative), you'll really see how much more robust it is. If node fixed its conceptually flawed event system, rewrote http so it wasn't awful to work with, and fixed streams then we'd have a pretty good system to work with. It's very easy to pass off problems with node as problems you'd have with any platform, but that's unfortunately just not reality.
I notice on the page they have licensing that supersedes the Windows licensing included with the VMs. Unfortunately, I've had these VMs for a while, and they've been complaining for activation. So, although they have provided different licensing terms, they didn't bother to inform the software of this fact.
> There are fine nuances about a programming language that you need to learn to be a good programmer.

On the other hand language is an investment. Switching a language in the same paradigm is more like maybe learning a local dialect of dialect of English, new words, new pronunciation. Say you are moving to Australia from US, you might have that issue. But if you think it worthwhile it is an investment.

But that is for when the paradigm is the same. Object oriented, functional, dynamic types vs static types, logic programming, declarative (SQL) those are like different languages French, Spanish, etc.
Think about the deeper implications of the experiment. Yes, people will shock themselves when there's nothing to do. However, that also means that when there's nothing to do, the majority of people will try to physically stimulate themselves because that's all there is TO do. To say that we're stupid because we would administer a painful shock to ourselves rather than sit in our own silence for 15 minutes is a very naiive way to approach the results. Come to a conclusion, dammit!
> One person pressed the button 190 times.

New study finds researchers trolled by subjects.
> With Node you can literally share your code between the front and back of a system.

I think sharing code is dangerous as it tightens component coupling and makes architecture less flexible and more complex.

An average web project nowadays seems to be a back with many fronts: end-user website, admin interface, iOS app, Android app, Windows app… Making all fronts equal in their separation IMO keeps the architecture more predictable and easier to understand. Like DRY but with design decisions instead of lines of code.

Also, I don't see how you can be flexible without making API the only point of contact for your back(s). That way you don't lock yourself in and can rewrite any component with another framework or language, once requirements change sufficiently. I imagine it's much harder to do if you have everything in one Node project.
I don't run one. I would like to know if Arstechnica's guide on how to run one is any good?
People can think anywhere. It's not often they're sat in a room with a little electric shock doodad. Humanities natural curiosity takes over.
Unless the 190 buzz guy was the norm, those people spent a lot of time not hitting themselves. Anyone who hit himself once did spent time thinking, then pressed button and then spent another time thinking.

The other thing is, I love spending time with thinking when I choose to and have something interesting to thing about. It does not mean that I will contemplate something cool at every random void moment or never get bored while waiting in queue.
How to Prevent Summer Blackouts
New study found short-circuits in study test materials.
Well said indeed. I may just quote you on that.
Do we really hate thinking so much we’d electrocute ourselves rather than do it?
I absolutely would prefer pain to boredom. I'm not afraid of being alone with my thoughts, but I am terrified of boredom.

With the shock, I can totally see myself locked in a room with the device and trying to see if I could condition myself to not react to the shock. As long as I had some sense of safety (they have a doctor and some paddles on hand) I would take days seeing how far I could push myself.

And to be clear, I hate pain. But I love to conquer that which would make me weak.
Dominica or Dominican Republic? I mean Dominica... Wandered into Roseau, there were people literally dancing in the street - asked what the occasion was and that was the response. All the cruise passengers stayed on their ships from what we could tell.
The Copyright Alert System is über creepy and should be stopped.
Indeed, "physically stimulate themselves", in every sense of that phrase. :-)
No, but there's still a decision made at some level in the organization which affects the sizes and budgets of the respective teams.
243 Game – inspired by 2048
I can't reply to gaius for some reason but:

http://en.m.wikipedia.org/wiki/Original_affluent_society
Quote: studies show that hunter-gatherers need only work about fifteen to twenty hours a week in order to survive and may devote the rest of their time to leisure

http://condensedscience.wordpress.com/2011/06/28/life-expect...

Quote:life expectancy at age 15 is 48 years for Aborigines, 52 and 51 for settled Ache and !Kung, yet 31 and 36 for peas-
ant and transitional Agta.
Survival to age 45 varies between 19 and 54 percent, and those aged 45 live an average of 12–24 additional years
The modal age of mortality in hunter-gatherers can range from 68 in the Hiwi to 78 in the Tsimane.
Can we please make #hackernews on freenode a thing again?
Putting your hand across phases on a 415V industrial supply will do that as well (which should never have happened but that is why we have training to show people how not to make other peoples fuckups) fortunately I was wearing heavy rubber boots and the contact was momentary.

Lesson of the day when your co-worker/trainee/friend says the supply is isolated...check anyway.
Hmmm, I couldn't find any simple examples. Basically, all it means that you're running Backbone.js on the server as well. If you're just using Backbone.js models & collections it's pretty straightforward.

But if you Google for running Backbone.js on the server, you get links for people running Backbone.js views (as well as models and collections) on the server. That's a little more involved, but the work has been done for you by frameworks such as rendr.

A good starting place might be: https://github.com/rendrjs/rendr-examples

I'm only familiar with Backbone. If your models are written in Ember or Angular or (?) instead of Backbone, I can't help you but would be very interesting in knowing how myself...
> He believes Mars and Moon missions would be a great waste of money.

If they fail to inspire people to continue exploring, yes. I would prefer Moon missions because they'd be cheaper and, as far as inspiration goes, they'd achieve the same results. How many brilliant people have chosen to dedicate their talents to building web technologies because space is no longer cool?

Also, being able to build self sustaining off world colonies may prove handy if we end up unable to stop climate change...
For instance there will always be a market for custom computing and "PCs", and so non-locked PCs will (hopefully) always exist in a capitalist environment.

Unfortunately, that market is slowly becoming the minority, and because those "more free" devices may have limitations that make them incompatible with a lot of proprietary content (which is the majority) and circumventing those limitations could be illegal and difficult, there will be fewer users of them.

Reminds me of this https://www.gnu.org/philosophy/right-to-read.html and the old saying "If you outlaw freedom, only outlaws will have freedom."
Years ago I was traveling to Oakland for business. My flight was delayed so I hit the magazine store. Bought some gaming magazines, business magazines and one copy of Havard Business Review. There was an article in it that caught my eye, "Why do dumb people succeed more in business than smart people."

I dont remember exactly the title but it was an 8 to 10 page article that went into detail comparing high IQ people to average or low IQ people and why people with lower average IQ did better in business. The article was filled with graphs and case studies and was very interesting.

But the last paragraph really summarized it best, "Smart people consistently over analyzed risk and talked themselves out of taking risks while someone with a lower IQ didnt even think about the risk and jumped in with both feet and took chances."

It gets back to the saying "No risk / No reward".

I remember that article to this day and always do a gut check when it comes to evaluating new risks. Sometimes I second voice my old European grandfather who was all about hard work in a different industry but his life lessons hold true.

Turning off the brain chatter and clearly evaluating a situation is critical but it s very hard because intelligent people, and humans in general, like to avoid risk and the temporary unpleasant pain that accompanies it.
I almost asked you the same about DR. :) I was living in Morne Daniel at the time, doing a gold ecurrency startup.
It's not a button, and isn't supposed to be one. It even has a shadow underneath it - I'm hoping it's just a way of quickly being able to identify that a Mac is running a beta of Mac OS X, and that it will go away with the official release.