skysight-inc/HackerNews huggingface dataset:
I'd say that it would be quite against what most would individuals would want. And if ownership/possession is indeed a natural concept that we as a species have, then you'd probably have to resort to some sort of pervasive government clamp down on instances of it occurring. And that would hardly be a utopia that most proponents of such a concept would make it out to be.

Whether it hold us back in general is not something we could easily answer. You could look at the communist (or any communal ownership concept for that matter) communes and mini-experiments that have been attempted in isolation over the years. As far as I know, they were all failures.

And these communal-ownership ideas can only operate and possibly chug along if they were to operate in complete isolation. Otherwise, free trade (as a black-market if it were banned) would quickly ruin the entire thing. You could argue that free-trade isn't even possible under a system of communal ownership, as there is no private property to trade with.

Back to your initial point about no possessions requiring no jobs. I'm not entirely sure what you're proposing there.
Raspberry Pi inspired autopilot
I recently read a similar case in Simon Singh's book Fermat's Enigma http://www.amazon.com/reader/0385493622?_encoding=UTF8&query... about the 14-15 puzzle. It was similarly unsolvable and provable the same way.

Interestingly, his account is rather different than that on wikipedia http://en.wikipedia.org/wiki/15_puzzle
Singh claims that Sam Lloyd created the puzzle, secretly proved it was impossible, and offered rewards to anyone who could solve it.
Use Firefox mainly due to it's ethos and it isn't part of the ever expanding google-sphere. Chrome is a nice browser which I think UI-wise is a bit nicer than Firefox (not much though) and I also like the process per tab design. It's nice being able to kill individuals tabs instead of having to kill the application.
Hey folks, writer here. Thanks for the great comments! Part 2 is already up talking interrupts (same blog) and i'll be cheating even more when the SD card interface comes online.
In-Q-Tel as an investor doesn't mean much, IMO. It does mean the product is of interest / value to the government, but that doesn't imply any sinister motive (or a ton of control). I work for a company that was invested in by In-Q-Tel, and the only influence I've seen from that was really to benefit the users in the community and develop a project for RBAC in Big Data - which is something I really hope the NSA has in place internally.

edit: and I'm a Libertarian, so I'm biased against reaching this conclusion based on my own observations.
JavaScript Is the Most Popular Language for 2014
> If there can't be any common sense exceptions to the 90-day policy, that's just bureaucracy by itself.

Its worth noting, as pointed out upthread, that the only reason it was released in January at all was because when Microsoft asked if their planned February release was going to cause a problem with the 90-day deadline, Google informed them the the 90-day deadline for that bug was 11 January and that that's when disclosure would occur. Clearly, the fixed deadline already achieved part of what it was intended to -- encouraging vendors to fix security issues more quickly.

And I'm not sure that there even exists such a thing as a "common sense exception" to that policy, but extending it simply to accommodate a vendor schedule that delays releases of security fixes to predetermined dates isn't such a common sense exception even if any exist. Its simply favoring the bureaucracy of fixed patch schedules over the purpose of the disclosure policy, which is encouraging vendors to more timely release fixes for security bugs.
Which sounds like blackmail to me. What did Microsoft have to put aside to move this up in their schedule? Maybe now the release date for Microsoft's new browser slips, giving Google the upper hand? Should corporations force their competitors to move like this? "If you don't drop everything, we're going to release vulnerability details about your product"?

I work in information security and patches are important, I understand. But it worries me that what we're basically seeing here is corporate warfare using security vulnerabilities. What gives any company the right to publish vulnerabilities about their competitors, especially when it has the chance to impact their competitor's performance? Does Pepsi have the right to demand Coke rotate the tires on their trucks within 90 days or they will publish the recipe for Coca Cola?
Another additional bonus of doing that is that you can serve "true" 404 pages (i.e. not soft 404) for invalid URLs when the page is requested with the _escaped_fragment_= query parameter.
Flask is too minimal. Using DRF is like having code written for you. Because, you know, the code was written (and battle-tested) for you. Why start from a log every time when you can get a wheel for free?
The US 'manufacturing renaissance' doesn't exist, says new report
This is exact my thought as well.

If OP is more worried about maintenance of project, Django gives foundation to build upon with sane conventions.

Anyone who reads few pages of Django Docs should be able to pick up quickly.

PS. I happen to currently maintain project written by other people with no docs.
Maintainability is a big one for page speed optimizations. You can easily get 95% there but that remaining 5% often comes at the expense of maintenance, and the ability to see/make changes easily.

Agreed. You might be able to gain a percentage point by inlining some vital CSS rules, but without hellish attention to details, that way madness lies.
Love DRF. Really easy, super flexible to modify (we did a lot of stuff with RBAC), the API browser is an amazing feature.
Oh no, flashbacks of C++

Want some simple concurrency? Here try boost::asio... or boost::thread... or... libev... or libuv.

Now every project has a different concurrency model woven into it. Why isn't there a good solution in the stdlib for this common need?
Show HN: StarHub – Fast access to your GitHub favorites
It's important to make a distinction between (i) Chomskyan linguistics, (ii) 90s style symbolic systems, (iii) 90s/early 2000s style statistical systems and (iv) 2010s style statistical systems.

Chomskyan linguistics assumes that statistics and related stuff is not relevant at all, and that instead you need to find the god-given (or at least innate) Universal Grammar and then everything will be great. 90s style symbolic systems adopt a more realistic approach, relying on lots of heuristics that kind of work but aim at good performance rather than unattainable perfection; 90s style statistical models give up some of the insights in these heuristics to construct tractable statistical models.

If you look at 2010s style statistical models, you'll notice that machine learning has become more powerful and you can use a greater variety of information, either using good linguistic intuitions (which help even more with better learning algorithms, but require a certain expressivity as well as some degree of matching between the way of constructing the features and the classification) or unsupervised/deep-NN learning, which constructs generalizations over features.

The main reason that you won't ever see people talking about systems with great machine learning and great linguistic intuitions is that you normally want to treat one of them as fixed and focus on improving the other, i.e., it's more a practical/cultural difference than an actual limitation.
Every online business needs this
> So, who forces Microsoft to stick to (so called) patch Tuesdays?

Their tens of millions of customers who plan internal deployment, overtime, and other things around those specific dates?

> it's Microsoft internal schedule

It's their external schedule actually.
Many, but not android. Android sucks. Google helped people in china to search content what the Chinese gov doesn't want them to know; and google's attitude of content censorship.
Arguably, the fact that Google was going to reveal the vulnerability two days before the next patch Tuesday could have been considered sufficient reason to warrant an out of band realease.
This is not a attack on DH, it is a attack on the verification mechanism. So the trick is, the attacker does not need to break DH, he just needs to find two sufficiently similar DH parameters, that the verification still works.
I can hover over an element with its title attrib set, and one pops up on every browser.
x86 enforces (essentially) total store order across all sockets: http://www.cl.cam.ac.uk/~pes20/weakmemory/index3.html. The barriers are still useful for kernel code because other processors on the machine usually don't participate in the cache-coherency protocol.
That just means you haven't properly aligned your developers' interests with your business interest.

Limiting developers in which languages and technologies they can use is not going to solve that problem, it merely addresses the symptom. Developers make hundreds of little less obvious and visible decisions that have a long term impact on your business. Picking the tools should always remain a developer decision.

If you a) hire the right people and b) make sure your goals are aligned, your developers limit themselves to a few core technologies. If not, you're screwed anyway.

(And yes, that does mean mutually accepting and respecting the fact that your developers' interests in exploring new things and your business interests in may not be aligned indefinitely.)
But is Elon openly libertarian? Relatively speaking, he always seems to avoid political talk.
The code can be made portable with a few simple macros (which is why they are implemented they way they are in GCC), though the optimizations will not be.

From the Linux kernel:

struct boot_params boot_params __attribute__((aligned(16)));

#if !__GNUC__
#define __attribute__(x)
#endif

I think that's a better way to do it than ASM (which totally hoses your portability).
React-Grid-Layout: a draggable and resizable grid layout system for React
ExecutedProgramsList: utility that lists the programs you previously executed
I'm coming to the conclusion that SEO does not matter anymore, at least not this basic stuff as everyone is doing this, including your rivals, so it is really not going to get you to stand out from the crowd.

Search engines make their money from advertising your site, _not_ from sending you free traffic via SEO. So fire up your credit card and buy some Adwords in key search terms for your business, that's want they want from you. I believe we are already in the post-SEO age of the Internet, maybe we have been for a few years now.
Rust recently added `if let` bindings, specifically inspired by Swift. But apart from that I agree.
Reinterpreting 12 Factor Apps for the Internet of Things
Atom – Git commit messages
Another additional bonus of doing is that you can serve "true" 404 pages (i.e. not soft 404) for invalid URLs when the page is requested with the _escaped_fragment_= query parameter.

For one of our sites, the Angular router redirects the user to a "true" 404 page if the in-app page cannot be found, along with the troublesome URL.

For example:

https://example.com/products/name-does-not-exist/

Will do a JS redirect to:

https://example.com/not-found/?url=/products/name-does-not-e...

The /not-found/ URL serves a "true" 404 response.

We're still in early days, and have very little data to back up the pros or cons of doing it this way.

All I can say with any certainty is that for the several months now we have zero "soft" 404s listed in Webmaster Tools.
I am of course guessing here. It's possible that I'm
completely wrong since I've never been in the working group and don't really know anyone on the working group. But given what I've read publicly this seems like a likely explanation:

Because not supporting Get would break a lot of current web applications and html5 had a pretty clear goal of being mostly backwards compatible. The previous form element didn't restrict the method and GET and POST are used everywhere. Restricting GET would have caused too much confusion to be worth it.
I resent the implication. Programming != introverted activity.
Specialized HPC workloads
Google is all about 'the algorithm' - it's organizational DNA.
It is done on PC as well, but we can't assume very recent instruction sets. We'll have to do with semi recent instruction sets.
Most of the time downvoting stands for 'Your comment hurts my feelings.'

This comment will be very light gray ;D
Fixed 500px width...
Yep. Uber apparently pays $1.50 per mile before its various surcharges [1], while the standard reimbursement rate for depreciation is $0.575 [2]. So employees, er, I mean "contractors" make less than $1/mi. Include the mileage driving between fares and the time waiting for a new fare, and I'll bet many drivers are below minimum wage. But that's what "disruption" looks like.

[1] http://drivingforuber.com/?page_id=20

[2] http://www.gsa.gov/portal/content/100715
I suppose you could always come up with some script that recreates the whole VPS and thus get a new IP address... but that makes it overly complicated for most people.
I wasn't posing the question to challenge him, just as an addition to his comment.
Does anyone know what's the percentage cut? The article (and all of the comments) don't seem to say anything about that.
What it’s like living in the coldest town on Earth
> I believe we are already in the post-SEO age of the Internet, maybe we have been for a few years now.

Could you expand on this? I'm interested in your thoughts.
Eh, I suppose it depends on what you consider "quality of life". The apartments are quite different in Copenhagen and Malmö. I strongly prefer the ones in Copenhagen, but I can see how someone might prefer the ones in Malmö.

In my opinion most Malmö apartments are just sort of drab and depressing. Where they are nicer is that they are newer, so have elevators, more modern bathrooms, etc. But the ones I've seen have a quite... institutional feel to them. They remind me of a school or government building: 1970s or 1980s concrete-and-tile construction, arranged into big housing developments with rows of identical-looking buildings. It's practical I guess, but doesn't have much character. There are a few renovated pre-20th-century buildings in central Malmö that have a lot more character. A friend-of-a-friend has a really beautiful apartment in one of those, an old brick factory building converted to housing, with floor-to-ceiling windows and interesting architectural design. But those kinds of places aren't cheap at all.

The main problem though is that in most of Sweden it's just impossible to get a proper rental without waiting years on the waitlist. All you can get are these temporary sublets, where you're always at risk of having to move. The only other alternative, if you don't have years to wait, is to buy an apartment. You can do that pretty reasonably in Malmö if you have the money, probably cheaper than Copenhagen (but purchasing in Copenhagen is cheaper than purchasing in Stockholm).
What a disingenuous comparison. It's not "accede to our demands or we'll publish this information"; it's "we're publishing this information in 90 days whether you like it or not."

If we ask "what gives any company the right to publish vulnerabilities about their competitors?" it's only a short step to asking "what gives journalists the right to publish scathing negative reviews?" The answer is the same: freedom of speech.

It's a fact of life that if you want to fix security bugs, that takes time away from working on other things. If you don't like it, fix the bugs faster, or pay more attention to security from the get-go. Microsoft should be thanking Google for finding the bug in the first place.
The "second-tuesday-of-the-month" policy is a completely arbitrary MS-only policy.

If Google (or any other group that discovers security issues) has to take into account every policy of every software producer it becomes utterly impossible to have any disclosure policy.

If MS wants to handicap themselves, that's their problem. The rest of the world doesn't have to bend to their will, those days are over.

Yes, this is about being an ass. And it's Microsoft that's being an ass by claiming the rest of the world should take into account their peculiar policy.
Uber and other similar type of taxi dispatching apps are facing new government regulations in countries like Singapore and India after the rape case involving an Uber driver in India last year.

It will be interesting to see what happens next.
Everything mentioned in the parent post is in the standard library.
One thing about the null checking stuff that I started thinking about... wouldn't it be more cleaner and less error prone if accessing subproperties of null classes always returned null instead of an exception? ie:

var someVar = class1.class2.SomeProp;

would return null, even if class1 was null. I have a hard time coming up with cases where you actually would want to force an exception. I realize however they reason for the new operator since they might not want to change how existing code works...
It's not really a stereotype if you're just accurately describing the inside of a cab (and not even mentioning any other ethnicity).
I'd take it a step further. Not only is there nothing that prevents it but that it's the natural order. It's basically a commodity. Margins on such things are thinner than razor thin.

In a great twist of irony I'm sure we'll soon see Uber lean on regulations to protect their foothold as that will eventually be their only competitive advantage.
New solutions to that “fixing mobile bugs” problem
There is some good technical execution advice here, but the basic premonition is wrong:

"From a development point of view SEO is the concern of how well a robot can read and understand your content. As we will see, a robot being able to read your content easily is normally a good thing for humans too."

I don't think we need different points of view of what SEO is. SEO is about getting your page ranked as high as possible for whatever keywords you're targeting. Technical execution is a tactic that supports that, not a different view of it.
> Now every project has a different concurrency model woven into it. Why isn't there a good solution in the stdlib for this common need?

Because every concurrency/parallelism approach has tradeoffs, and there is no one right implementation for all cases, and rusts intended primary use case is low-level and broad enough that there's not even one approach that's probably good enough for most cases.
My question is what are they talking about on the phone. I can't imagine sitting on the phone talking to my friends or family for 8+ hours a day, everyday, which is what seems to be happening.
Don't forget about UberKitten, or whatever it was called. I wish they'd bring back kitten delivery.
The quality of Uber/Lyft drivers and the service in general has plummeted so much lately that I've just switched back to local car services. I just had a nice conversation with a car service driver, who also does Uber, and he said he prefers the car service over Uber because they pay better and only uses Uber when he isn't getting anything else but the pay has dropped over the past year pretty significantly for him whereas when he had started it was pretty good. That's an anecdote so take it for what you will but I just don't see how lowering prices further helps anyone out long term.
I think their long-term goal is probably to replace drivers altogether with driver-less vehicles.

It might seem a long way off or even fantasy to some, but carving out a dominant market-share now will mean big profits if/once drivers are eliminated from the equation.
And the next company that comes along will ask for 3 days, and then 5 days, etc. Pretty soon we're back to serious bugs not getting fixed until the vendor feels like it. The power of a set timeline is the fact that its not up to the vendor when things happen. They have proven time and again that they won't fix things until they are forced to; this forces them.

It's just like being late for work. "But I was only 5 minutes late." Late is late.
For basic on page SEO when you are building a site, this is all good and useful information.

Developers should also know that creating good technical content and open source projects on your site will over time generate links and attention for your website. While those links aren't going directly to your product pages, the long term benefit of those pages linking back to your main company pages/products will help those pages rank, which makes you money. It's a bit indirect, but still is worthwhile.
clickable -> http://builtvisible.com/highcharts-generator/
It's a gotcha for anybody, like me, that expects a branch name to be 'just' a string.
I disagree with you, but I certainly would like to know your reasoning behind this.

Most people are going to use a search engine if all they get are paid ads. People go to Google for the organic results and sometimes the paid ads are useful for those people. It's still in Google's best interest to provide the most relevant organic results as possible.

Most businesses I've worked with still get more revenue from organic than paid and even if the percentages change, it's mostly from increased paid spend leading to more revenue and not decreasing organic revenue.
it's Microsoft internal schedule

Not entirely true now. Users of MS software have built up their own testing processes around patch Tuesday.

Patch Tuesday was one of the best things MS did when they decided to take security seriously. They realized that testing patches downstream takes time and giving their customers a consistent patch day let them also plan ahead.
If you enjoyed this article, you might also want to check out Agner Fog's optimization manuals and blog (which I decided were probably worth a separate submission): https://news.ycombinator.com/item?id=8874206
Objective-C does this. I've not used Objective-C enough in the wild to say how often it causes issues.
Looks very nice. Is Linux actually real-time enough to run autopilot code?
There is nothing that would prevent an implementation of Go's scheduler in Rust, and libgreen duplicated its functionality pretty comprehensively. Rust's scheduler was more advanced than Go's scheduler in some ways—it did work-stealing in a completely lock-free way, for example.

The only fundamental difference between Rust and Go here is in stack management. In Go, goroutines start off with a small stack, and they can grow because the language is now pervasively, precisely garbage collected and all of the pointers into the stack can be rewritten. In Rust, that wasn't an option because it isn't garbage collected; it used to use the old Go approach of split stacks, but the same problems were encountered. There was also significant backlash against the problems that continue to be an issue in Go and were an issue in Rust—the FFI (cgo in Go's case) was slow due to having to perform stack switches, most importantly.
The patch-day policy is not for Microsoft, it's for sysadmins who maintain the installations.
You can set/read your own cookies when developing on wordpress.

I usually us the jQuery cookie plugin for javascript.

You can set/read cookies using php as well.