skysight-inc/HackerNews huggingface dataset:
Do people actually use Node in production for serious things? I actually don't know anybody who shipped anything done in Node. Sure, they do side projects or hobby projects, but nothing more than that.
Making a Mockery with Mock Objects
> At least UK has independent courts

Sorry, we have secret, closed courts now, without juries. They were intended for terror cases, but are being used a lot more broadly than most think. A barrister friend who raised concerns about this had his career assassinated-by-media last year, and is now a hate-figure.

I'm afraid it's too late.

Edit: This piece demonstrates quite nicely how this variety of assassination happens - you know, writing things in such a way that they look like direct quotes, when they're not, and getting every paper to carry the same story - http://barristerblogger.com/2013/08/29/criticism-robert-colo...
The most crucial downside of speed reading for me is that it destroys the tone of a phrase. Splitting a sentence into blocks makes it sound robotic, eliminating the nuances of the author, and quite possibly the intended meaning.
I don't think that's entirely correct. They are profiting from information asymmetry. Markets change slightly and they know it 1 millisecond before everyone else. In that millisecond they buy or sell and profit from the price change. This is stuff that would have been done anyways by regular traders. It's just the high speed traders are now faster and so do it first.

As far as I can tell that isn't hurting anyone more than normal arbitrage.
You Can Never Guess What They Caught When Ice Fishing In Arctic
Spammers now asking web admins to delete their spam again
Your analogy and the argument after it make no sense to me. Barriers to entry won't be lowered by this, nor will trades be smarter.
Generally interesting, but I take issue with the sentence:

> I could show you more, but the list would never end because no one has ever won without first experiencing many failures and rejections

Though most people will have to fail many times before they make it anywhere, there will be some people who have always had great success on their first attempt. It would be interesting to hear some of those stories.
Looks promising!

I've actually found a truck load more tools on their add-ons/integrations page that will probably be of use to me too:

http://capsulecrm.com/features#/addons

Thanks!
I don't think OP meant "do well" as in "code or architect" well, but they "do well for themselves" (make more money, play with newer toys, don't have to clean up others' messes as much, etc).
Locish – Ask like minded people
As far as I can tell this is aimed at HFT specifically, and wouldn't have an effect on the rest of the financial industry.
I'm very interested to see the absolute expenses and income. Since server hosting is very cheap these days, they are probably not making a lot of money? Or they are paying too much for hosting?
Good question, I'm looking for one as well. Preferably a pay-once and not a pay-monthly. Or something I can install on my own domain.
How To Find A Developer
Depends for what your clients pay you for. My clients pay me for my time, not the code. I have used code written in my own time for client projects and I have used code written for a client for another client's project.

I also do some custom work for customers of our saas and I always tell them that the code I write for them is non-exclusive which means I get to re-use the code and resell it. I estimate nearly 80% of the app has been created that way including almost all the add-ons.
Such value?
"Did he just have a special love for π, perhaps based on his birthday?"

Einstein lived in Europe for 54 of his 76 years. Since no one in Europe uses the mm/dd/yy date convention, I'd be surprised if this coincidence was significant to him, or even that he was aware of it at all.
Tutorial: Unity and touch controls
Well by that logic all trades are bad since someone always loses money.
I highly recommend comparing these numbers for Poland with numbers for other European countries. You'll find that Poland is on the cheaper end of the employment cost spectrum - that 40% figure (which is actually 38%) only refers to the cost of employing a minimum-wage worker, and it's not 38% that's taken home, it's 38% that's taken by government, and it's still lower than EU average.

As personal and corporate income taxes in Poland are quite low (again, compared to other European countries), combined with the fact that labor in Poland is extremely cheap (in EU, if I remember correctly, the labor is cheaper only in very poor countries like Latvia, Lithuania or Bulgaria), employing Poles and doing business in Poland is very cheap. It's very illuminating to compare the percentage of corporate income spent on worker wages in various countries -- companies spend very little on employees in Poland in general.
South has existed and has been in wide use for a very long time, so whether or not it's built into Django doesn't really matter that much.

As for Node and Go, I don't see how they could have One System To Rule Them All – this feels like something you take care of at the ORM or framework level.

Now, as to your "is there another way?" – during development of an app that hasn't yet reached production, I still prefer extensively using fixtures and just nuking the database on every change, then loading the fixtures back in. (In Django this is a one-liner on the shell, I suppose it's probably similar in other frameworks.) Faster and really helps with unit testing too.
NewsBlur is open source and you can set up a self-hosted version of it as well. See https://github.com/samuelclay/NewsBlur
Well made point. Combine that with chrissnell's point [1] and it makes even more sense in my mind.

Google Fiber isn't really necessary for the common household, yet. They might be mixing an investment in start-ups with a political agenda. For the latter, if they can push the competition in the rest of the U.S. to even 10% of their offering you'll still have a massive speed increase (and a brand spankin' new infrastructure).

[1] https://news.ycombinator.com/item?id=7397174
That's totally orthogonal to the point.

Rails is appropriate for proving ideas and rapid development of complete apps. It's also suitable for implementing small, loosely-coupled SOA-style apps integrated with a larger system, or for basic low-traffic apps.

It's not appropriate for huge commerce or infrastructure-style services.

A lot of developers jumped on it when it was a new technology because it offered lots of benefits - in particular, the whole convention-over-configuration thing and lots of happy developers. They weren't wrong for that. Now that we're trying to build bigger and bigger things on the web, and moving into SOA with APIs for mobile apps etc., something other than Rails is a good choice.

Those early adopters did well, and modern early adopters will do well too.
Silicon Roundabout is not dying. Far from it. It's adapting.
Not a "problem" at all - the sea is very, very big, and lots of it isn't covered by any sort of RADAR or other surveillance. Even major shipping lanes aren't anything like highways on land, there is usually no-one looking at any given patch of sea.
I've been using Pipedrive (http://bit.ly/1kpPlYZ - my referral link) for over a year now. Nice integration with Google Calendar and great mobile Apps.
Origin of Amazon's Prime
I see,
still thats quite a bit especially when need to hand over a large chunk on any sale from Irish/EU28 customers in tax!

Currently working with Elavon for credit card payments (cant disclose exact rates, but much cheaper than Stripe),

completely avoiding Paypal who can go and f&*k themselves,

and getting several of the larger customers to pay via SEPA bank transfer or bitcoin which have nearly no fees.
One thing that stuck out to me:

> We are implementing “certificate-based authentication” instead of the standard username/password auth against Active Directory.

I wish we were all doing this. How long is it going to take to get a usable certificate-based client/user authentication mechanism on the web?

edit: Also see e12e's comment.
http://www.oreillynet.com/ruby/blog/2007/09/7_reasons_i_swit...

Not the same size, but this was a company that spent a lot of time chasing the Rails fad in 2005/2006/2007, and switched back to PHP. I wouldn't doubt the same type of stories may be told about node in a year or two, although few will ever be terribly public. Few companies like to promote out their bad decisions (not saying node is definitely a bad decision).
YMMV. I for instance LOOOOVE thin gadgets. I never knew how much I wanted really thin gadgets until I had them.

I mean, presumably the market is speaking here.
I know what you mean but I really think it'll be hard to topple node. I started with express and tried a few other frameworks and finally decided on sailsjs. I haven't had this much fun or been this excited about web development since I started 10+ years ago. I really don't know what it is about node thats so appealing as Im no js guru but I think its going to be around for a very long time.
Maybe they just didn't pay for priority over netflix so comcast broke their legs.
Surely a plane is too low density to cause even a "small earth quake" when it sinks to the bottom of the sea (probably in many pieces). Could a shockwave from the impact on the surface of the sea be measured as a small earthquake?
NodeZone
Skype Founders' Music Service Rdio Acquires Dhingana
From what I read around I understand that node.js is good for simple projects, but not for heavyweights where concurrency and scalability is the key. This is where I'm pretty sure something like Typesafe stack (Scala/Play/Akka) blows it out of the water. Personally if I work on something I'd like to at least hope that it will be big someday, which is why I'm willing to spend some extra time, but choose the most solid platform that I can afford. Typesafe stack is the most impressive one at least for now, in my opinion.
still playing now and then -_-
switched from stair tactics to snake tactics. http://i.imgur.com/KZtO7Es.jpg (try to keep the snake as short as possible)
This is audio woo.

HOW TO IMPROVE YOUR SOUND SYSTEM:

1. For headphone playback, get good headphones.

2. For speaker playback, fix the room first.
Yes, interrupt is better, and the article explains how to do that a few paragraphs later:

for n := range in {
select {
case out <- n * n:
case <-done:
return
}
}

If you allow pipeline stages to interrupt their receive loop instead of draining the inbound channel, then _all_ send operations need to be governed by done. Otherwise the interrupted receive loop may block the upstream sender.
The entire frontpage should be A/B-tested with some conversion experts. There is a lot of room for improvement if you look at the CTA's, buttons, comparison between free and premium, etc.
Callback hell has been my biggest stumbling block with node but there are libraries such as asynch and Q which have provided me with adequate solutions. Also since were talking about things to be ironed out, I hope they make it easier to run node behind Apache or some other webserver thats tried and true.. why abandon all that progress?
It's available within microseconds/milliseconds (not including time to travel over the network to wherever you are compared to the exchange's datacentre). It's made available to everyone at the same time (again, if you have a shitty connection, you'll get the information later). You use the exact same system whether you're a bank, investor, broker, hedge fund, ... The only difference is how close you are to the datacentre, how good your networking is, how optimized your trading applications are, which protocol you're using, etc.
Still you have moral choice to either turn back a person or detain him/her for something minor such as expired or missing permind. And you do the immoral thing becsuse you need money for medicine fo your kid.
I asked the same question a month or so ago. I also was hesitant to get started with Highrise. Right now I'm testing Nimbly and Pipeline Deals. Nimbly seems to be more about generating leads through social media. Both have a nice interface.
The new tiles are only 2 (90%) and 4 (10%). From the source https://github.com/gabrielecirulli/2048/blob/master/js/game_...

// Adds a tile in a random position
GameManager.prototype.addRandomTile = function () {
if (this.grid.cellsAvailable()) {
var value = Math.random() < 0.9 ? 2 : 4;
var tile = new Tile(this.grid.randomAvailableCell(), value);

this.grid.insertTile(tile);
}
};
That's quite interesting - not heard of this before. Can you share more information on this?
> I would expect real adoption of JS to begin when ES6 features (generators, classes, etc) become available.

The adoption of server-side JS implementations (node particularly) is already "real" I think - the growth in its popularity seems to be very quick compared to other platforms when you consider how short a time has passed since node was first made available.

I agree that one of the things constraining that growth is the ease with which a nightmare of callbacks gets created, which can be a problem for later maintenance/improvement, and some of the newer language features will help that - but I think many will avoid using those features until they are commonly available client side too (there are many out there still using relatively old browsers, and a lot of projects don't have the luxury of being able to ignore them).

I think a major thing that is making those consider node hold back a little is the very thing that has made it successful: the rapid growth and evolution which is still on-going. I suspect that there are many experimenting with it but waiting until things settles down (which the core no doubt will for a while soon) before committing to using it for major projects.
Interesting choice of words renaissance, as what we are actually seeing is people blindly reinventing things that were known in the 1970s. At least the true renaissance thinkers knew they were rediscovering things that existed before the Dark Ages; today people genuinely think they're onto something novel.
This 'lewellyn' person seems to be complaining about the lack of support for the language Limbo, a language for the Inferno OS. Both seem quite outdated and out of use. He also complains about how Github is focusing on 'cool' kid languages. Which I am guessing refer to modern, popular languages (If this is the definition of cool, then yes, they are.) Which, if I was Github, I would do the same. It's called priorities. I kind of get the vibe that lewellyn is some kind of 'hiptser'. His obscure language is better than the 'cool' kids simply because he's using it. I also would phrase it as "GitHub's language detection is broken", it's merely missing a feature/language.
I use the magic trackpad on a 27" iMac, it is a wonderful input device and exactly fast enough. There are always clueless users who don't know to adjust tracking speed just like there are always clueless Apple haters who want to believe that Apple would not have provided a tracking speed preference control to allow users to tune devices to their needs.
You can't just buy 'Murica with money!
May be a stupid question - The Social Face Classification (SFC) dataset that they refer to - Is it published to the world? I wonder if they can deduce "emotions" from SFC dataset and use it as a training set for images in the wild.
Make your own dude. That's a good way to show your skills! That's what I did for me at http://marques.io
The issue about happy developers because they are using 'new technologies' (use node! it's a new technology) is a wrong conclusion. This is like Rails 7-8 years ago. People using node now are essentially doing greenfield projects - they're writing 'from scratch' code without any major requirements to keep existing code going.

Come back in 5 years when someone has to maintain the Paypal nodejs stuff which has become a moderate mess due to weird edge cases, changed business and legal requirements, and try to hire node developers to come in and maintain code written by people who are no longer working there, having moved on to scala/f# projects in 2015. All the new attention will be in 'node 2017', but you'll be stuck trying to make 2017 modules work in 2013 code, and you'll be left trying to patch/maintain something that wasn't as forward-compatible.

For true irony, some of those same developers will be brought back as consultants to develop the next-gen 'paypal 2018!' based on some new Scala framework, and the maintainers will have to watch the experts write the next generation of what they'll be maintaining 4 years on.

EDIT: "The old story of linkedin where moving to Node.js from Rails for their mobile traffic, reducing the number of servers from 30 to 3 (90% reduction) and the new system was up to 20x faster." I strongly suspect that if the team had been given X months of "rewrite the Rails system using all the current knowledge and techniques, as a new system vs patching the live one", they'd have seen similar results in less time.

To the extent that some companies are more SOA flavored than they were 5-10 years ago, this will be easier for everyone involved, of course, but let's not pretend that developers are happy because they're using 'new technology'. They're generally happy in any language when they don't have to work within bone-headed constraints leveled on them by predecessors who were chasing the latest fad before really understanding it.
Hey there, ClinchPad (https://www.clinchpad.com) has a large number of freelancers using it. It is a CRM targeted at small teams and focused on the process of moving prospects towards a deal (something that freelancers do often as they look for clients).

We're always improving the application and welcome any feedback on it. Feel free to reply to this comment or email me at cheenu@clinchpad.com.

Disclosure: I'm the Founder of ClinchPad.
Arte – Pompeo Mariani, mostra alla Bottegantica (jorgeluis72)
This confused me, but I think it's because annual subscription revenue was recognized in the month of the payment.
github?)
I would contend Go does around 50% of what Erlang does. Node.js does around 10% of what Erlang does.

You are right that both Go and Node.js has a lot of mass and a lot of acceleration right now. But Erlang has inertia in the projects where it does well and it will probably not affect typical Erlang systems much if Node.js or Go grows large. To this extent, Erlang is a too different beast.
I get the feeling that what Node helps with is concurrency, although being fairly fast helps too.

Ruby on Rails does not really have a good concurrency story for something like web sockets.

Although Rails is still what I would use for bootstrapping something where you're trying to find product/market fit and you are not absolutely sure that you need to squeeze out lots of performance from the get-go. Even if I knew I needed web sockets, I'd probably farm those out to a specific server to handle just those, most likely in Erlang.
Watch as the world's first 3D-printed house goes up
Yes, but if you hijack a plane, odds are high that you are after something. A sea landing has a high chance of killing everyone on board (if you're after a person), and next to no way of getting into the cargo hold (if you're after cargo).

If you're just after terrorism, then doing a 9/11-style attack would be far more effective.
"Early adopters generally tend to do well, whatever the language may be."

It is because early adopters tend to work either on special kind of problems the new language is especially suited for or because they tend to work on rather small projects. Those small projects would do well in almost any circumstances.

New technologies tend to be buggy, quirky and tend not to stay around. Rarely someone picks them up for things that are supposed to be maintained in the long term.
I suspect his - rather labored - point is that there are multiple use cases to show that the design of Linquist's configuration is flawed as a rule and not an exception, and the lack of attention paid to this particular issue is perhaps indicative of a more general Github attitude towards the less trendy languages and technologies out there.
Report: Target Missed Its Chance To Prevent Data Breach
If you have an opposition leader in a country where opposition is a dirty word, why would you care how he is painted by state-affiliated media?

They're like clock with no mechanism. Such clock can even occasionally be right, but it doesn't go.
Can document root of the server be on client machine
Here is my problem.

In our company we have a setup like this. There is a server with apache, php and all. All the client (dev) machine has their one drive (M:) mapped to the home folder on the server of that user. We have also setup the Dynamic document root. For e.g. jimy.www.domain.com get the document root as /home/jimitm/www/. Now we have started using GIT some days back. One problem we are facing is git status (or any other similar command) take too much time as it has to check every file for the change on the network drive.
What I was thinking is that at all possible that the document root would on client(dev) machine D: Drive (or some local state drive). So for jimy.www.domain.com the Document root will be D:/www of the client machine ?

Or is there any other workaround ?
I don't get it? what windfall is he speaking of and he never addressed why he will continue even though it's loss making.
Took me about 3 weeks (working after work and week-ends) so anyone could (and should do it also).
Hell you could probably do one about how you should use Fortran for big data instead of this modern OO Java rubbish :-)
Did EFF complain about Ukraine government outlawing access
to any Russian language news a few days ago?

Did it really happen?
I think GitHub is using it ( https://github.com/blog/678-meet-nodeload-the-new-download-s... https://github.com/blog/900-nodeload2-downloads-reloaded )
I do use it. Primarily because it more widespread in the Java world than other competitors,and more easy, in the syntax, to start with. You might also be interested in DB-Main [0]

But database migration has little to do with version control of code. With code, when you switch from a version to another, either you have a bug^H^H feature, either you don't. And you can repeat that as many time as you want.

Data is another kind of beast. You cannot simply "DROP" a table or even a column back and forth and rely on your backups (if any...). You do no longer want a table? Do not use it anymore, be let it there. You want to migrate your data? make sure you do no loose information. And if you do, duplicate it somewhere if you have to "rollback", or at least choose sensible defaults that can be applied.

Data is there to stay, as complete and detailed as it was originally put in your datastore.

[0]: http://www.db-main.eu
Using CPU utilisation as a measure like that is pretty pointless anyway.

Without knowing over what period (instantaneous measure across the farm, a ten minute average from a typical node, a ten minute average over the lot, ...) that reading was taken it could mean many things.

If they have pushed a chunk of the rendering duties client-side then the CPU is not going to be their bottle-neck anyway: the back-end data-store and network bandwidth will be.
All they are asking is to arbitrarily specify some other extension as the "primary" extension and have ".m" as another extension. Users will still see the same end result.
Why would CNN and Reuters matter much in non-English-speaking country? Not many people go there.

Russia has no opposition (in the meaning of the world) so your title won't make sense.
> Ukraine government outlawing access to any Russian language news a few days ago

Filter content by Content-language header? :)

> New Kiev government has banned national broadcasts in this language

This statement is also wrong. There is a lot of channels in Russian language in Ukraine.