skysight-inc/HackerNews huggingface dataset:
It's closed-source; we can't fix things like the crappy crypto (shared key), and can't spot backdoors or see what it's actually doing without a lot of effort.
FCC chairman revises fast-lane option in net neutrality
> They're successful because they're the best.

lol. If that were the case, then I don't understand what kind of technology they're gonna benefit from buying Beats. I mean, the internet is full of reviews stating that Beats headphones suck.
Our Climate Is Changing, And NASA Has The Proof
Top 10 Spots for Tech Acquisitions
Fieldman's work doesn't exist in vacuum. He talks about HTTP, and HTTP has the verbs it has. It's hard enough to find consistent behavior in HTTP servers and proxies with "PUT" and "DELETE" let alone anything else. But even ignoring that, the verbs the spec talks about are limited. And that's a big problem.

As for RPC, essentially any communication between machines is a RPC. It's message passing ("call") and if the message arrives on the other end it's processed by a message handler ("procedure").

No server can just reach into another server's RAM and get or modify a resource directly. The interaction happens entirely by the will of the message receiver, and in exactly the way the receiver wants (not the sender).

So if we'll be building everything on an appropriate abstraction, it better match what really happens (messages, message handlers) and not some wishful thinking abstraction layered on top (resources, resource modification).

RPC is not REST's problem. The problem is the limited commands (PUT, POST, DELETE) and the single possible query type (GET) that we need to work with.

When a payment gateway has to represent a simple "process payment" command with a series of bogus abstractions like a "POST /payment/transaction/new", you know REST is the wrong tool for the job.
Works for me on 64bit Fedora. I use then nvidia drivers from rpmfusion.
Ask HN: What are some must-see talks for new SAAS entrepreneurs?
GM: Add a 4G Data Plan to Your Car for $10
HN hellbans, so you might not realize you're not being heard.

I'm seeing [dead] markers from matrax6 and mantrax7 (although oddly enough, not consistently).

Can't comment on the quality of the code. Your problems sound atypical.
Big Cable says investment is flourishing, but their data says it's falling
Is Snowden a CIA limited hangout op?
Beats is a perfect addition to Apple's portfolio: a product that caters to the uninitiated and non-tech-savvy, is overpriced, and sucks compared to true audiophile/professional-grade headphones made by other manufacturers.
My name is an uncommon one: "Leland Batey". However, pretty much everyone pronounces it correctly.
You'll not only have to manufacture them, you'll also have to make sure the shipping isn't routed through any country with a creepy spy agenda.
https://www.hackerrank.com/tests/530697662bd88

It's closed. You can still take the test but they won't review it. I did like the format.
> Whereas if someone's wearing Beats with the screen flipped out.

IMO you've hit the nail on the head here. Initially it's going to be weird having people with this 'always on' aspect. Think how people feel when having a conversation/meeting with someone who is constantly looking at their smartphone or even wearing sunglasses. An item like a flip down screen will allow people to show they are paying attention and not recording everything, at least while society gets used to this tech.
The analogy is not 1:1, but consider a few observations.

Firstly, OpenStack is not a thriving open source community in the usual sense. It has succeeded in creating a vendor ecosystem, it has not succeeded in creating a large volume of customer successes. An OpenStack deployment is notoriously hard to get right in practice and hundreds of millions of dollars have been squandered to date on failed projects. In this way it has a lot of similarity to CORBA, which was a vendor love fest far before customer adoption, which took years of failures before the initial successes.

Secondly, you may want to look into how the OMG operated (and still operates), which not as a top-down standards body, it is more of a community facilitation organization. OMG set out RFI/RFPs for set of component/facility/service-level specifications with competition in the form of RFP responses that are voted on by the membership and then consolidated. The OMG would have been much better served by having an open source reference implementation for the various specs (avoiding many of the design flaws and ratholes the OMG ran into).

That said, once the OMG picked a recommendation for an area, customers or vendors tended to use that or implement that, and ignore alternatives. This is not much different from the OpenStack Foundation, which can and will control the direction of the OpenStack software for the (debatable) benefits of its leadership and members. The startup community is risk tolerant enough to just "try something else" that's open source without a support contract, sure, but in my experience most enterprises won't mix and match things that aren't "approved" or "recommended" by the mothership and supported by the likes of EMC, VMware, HP or IBM.

Third, consider the popularity of RedHat Linux. It is a billion dollar company because they are the de facto go-to vendor for a Linux distribution, patch network, and support contract. They curate what packages and kernel patches are included in the distribution, but generally rely on Linus' governance for the kernel and do not deviate strongly from it. If Linus doesn't want it in the main kernel, it's an uphill climb to expect to see it eventually in RHEL.

I expect a similar pattern with OpenStack, with the caveat the governance itself is not user-centered, it is vendor-centered, which is not a good sign.
That's really unfortunate. I read through the RFC, and IIRC it is pretty consistent on those details. Can't stop people from badly implementing a spec :(
"Bitcasa’s proprietary block-level encryption..."

This phrase does not inspire confidence.
I'm curious, what are your complaints about Dropbox? Security, UI, UX, features?
So, honest question. I've been musing over REST and RPC for a while, and was trying to come up with some domains that were verb-oriented instead of noun-oriented. The only thing I could come up with was message passing, a-la XMPP or streaming content.

What are some other problem domains that are better represented in verb-oriented terminology?
The article is amazing.
Works "okayish" in Chrome for me.
> He talks about HTTP, and HTTP has the verbs it has.

Sure, but REST is not HTTP. Yes, it was created to describe the architecture of HTTP, but you can do REST over other protocols, and even HTTP is not truly RESTful. Indeed, Fielding's thesis devotes an entire section to this: http://www.ics.uci.edu/~fielding/pubs/dissertation/evaluatio...

> and proxies with "PUT" and "DELETE"

This is due to the HTML spec, not anything else. In fact, this was almost changed in HTML5, but the problems with adding arbitrary verbs to HTML.FORM weren't adequately addressed. You could make that case, if you felt you'd solved the problems.

> As for RPC, essentially any communication between machines is a RPC

This characterization of RPC means that _everything_ is RPC, which means it's not a very useful way to compare architectures.

> The problem is the limited commands (PUT, POST, DELETE) and the single possible query type (GET) that we need to work with.

HTTP != REST. That said, something very similar to this is called the 'uniform interface constraint,' and is definitional to REST.

By the way, HTTP can have extension verbs too, so you're not actually limited to that.

Anyway, you still haven't shown me how Fielding's REST is RPC, or at least, in the way that software architects talk about RPC. http://www.ics.uci.edu/~fielding/pubs/dissertation/evaluatio... may be instructive.
Well I mean, there is a lot of utility in programming with categorical concepts in Haskell. There's plenty of libraries in the Haskell ecosystem that wouldn't even exist if it weren't for drawing upon category theory for guidance. Pipes is probably the best example of this school of thought on library design. [1]

My point was mostly that I don't think there is a path to really understanding the full generality of category theory through functional programming alone, one has to go learn the pure mathematics as well.

[1] https://hackage.haskell.org/package/pipes-4.1.1/docs/Pipes-C...
Possibly the fact I was manifestly not applying for a job alleviated some of these concerns. Or maybe they are just cool people that believe in education and supporting the industry. Who knows.
A good way to wind up with Europe at war again is to lack the foresight and restraint to treat Middle Eastern terrorists as the relative nuisance they are instead of blowing our waning resources on reshaping the Middle East and building a domestic security state.
Have you reported these HN bugs?
Awesome Node Dashboard
While I agree with you that that's certainly an interesting part of the split between RPC and REST, you might be curious to know that Fielding doesn't think so.

> What makes HTTP significantly different from RPC is that the requests are directed to resources using a generic interface with standard semantics that can be interpreted by intermediaries almost as well as by the machines that originate services.

http://www.ics.uci.edu/~fielding/pubs/dissertation/evaluatio...
*They're successful because the end consumers believe the marketing propagation that they are the best.
Beats 'phones could be a recognizable and elegant adjunct to a headworn VR device if Apple has any plans in that area. I'd be rather surprised if they didn't and see this as a pretty clear indicator we'll see them enter that fray.
Dave is my go-to. Nice and sharp sounding.
If an always on device built into a big pair of headphones could interface with a pair of ordinary looking sunglasses, you could have all of the functionality of Google Glass in a completely non-dorky format. Or maybe both could interface with an iPhone. This would solve the antenna placement problem for both glasses and headphones. (Proximity to head)
Fetching-water Girl Metal Candle Holder
A stylish candle holder that is 100% hand-made of iron;
"Inviting women into the workforce" is #1 most creative?? It is brave, for sure, considering that was in Saudi Arabia, but... creative?
HTC, HP and Chrysler are using the Beats brand to make products that are not as 'cool' as Apple products, arguably cool. Buy Beats and Apple has a defensive play. Let yourself be outbid and watch Microsoft or Samsung or whomever drive the brand into the dirt. Defensive move.
There were some comments on this related thread: https://news.ycombinator.com/item?id=7719957

I wrote a micro framework called Mithril ( http://lhorie.github.io/mithril ) that has a similar single-direction-data-flow architecture. Here's a small snippet to illustrate how the flow of data works there:

//model
function getFoo() {
return m.request({url: "/visits", method: "GET"})
}
function setFoo() {
return m.request({url: "/visits", method: "POST"})
}

//controller
function controller() {
this.foo = getFoo()

this.save = function() {
this.foo = setFoo()
}.bind(this)
}

//view
function view(ctrl) {
return m("div", {onclick: ctrl.save}, [
"hello " + ctrl.foo()
])
}

m.module(document, {controller: controller, view: view})

Basically data goes from `getFoo` in the model to `this.foo`, which is used as `ctrl.foo()` in the view. Firing the `onclick` event on the view triggers a `save` action in the controller, which calls `setFoo` in the model. `setFoo` sends data to `this.foo` which is again used as `ctrl.foo()` in the view, and on goes the M -> V -> C -> M ... cycle. Within the context of the template, the unidirectional flow is seen by the fact that the data just gets consumed as we recursively go down the template tree, without reading stuff back from the template as we go. This is in stark contrast to jQuery, where we typically call a series of methods to read and update arbitrary parts of the DOM in a non-atomic, state-machine kind of way.

Flux uses different nomenclature (e.g. they use the term stores for model-like entities, and the dispatcher is analogous to controller actions that translate a UI event into a command to update data) and some of the implementation details as they relate to React are a little bit different from Mithril (e.g. React has the concept of a controller-view, which is a sort of "root subscriber" in view land, props to pass data down the component tree, etc), but the idea is that application state can be thought of as a monolithic blob of data that mutates atomically as it gets corecursively passed through an MVC-like system, rather than a state machine that gets incrementally tweaked by a bunch of ad-hoc commands.
Technically speaking, I agree that it's a not a single solution and can be flexible. That said, it fundamentally presumes VMs, attachable disks, and networks as "the objects that matters" for your cloud. It's a good assumption for now, but maybe not for 5 years from now.

My post was mostly about the funding and political context that is driving OpenStack momentum, and its similarity to past attempts for vendors to gang up and try to take on the market leader (AWS). The community is all about the vendors, currently. Users are growing, but still the minority. And that's a warning sign, because it may mean the users really just don't care as much as the investors in OpenStack think they will.
And yet, Apple has a very low marketing budget with respect to their competitors...
To expound on this comment: SDL1 defaults to fully software rendered output. You can hack in opengl hardware rendering, but it's fairly common for SDL1 games and such to be fully software rendered and run fine.

SDL2 in general is hardware rendered.

SDL1 is a good counter-example to "software rendering isn't quick enough anymore". You can make perfectly performant 2d games with sdl1's software rendering... 3d, not so much.
Limits to Paper Folding (2012)
Widgy: Open Source Python/Django CMS Framework
There are constraints to asm.js that are restrictively difficult for a human to maintain. If your code doesn't pass the validator it runs as normal JS.
Http://www.aphrodisiac.com.tw
http://www.aphrodisiac.com.tw
Considering the family (Violaceae), I'd guess pretty shallow (<30cm).
AT&T Courts Satellite TV With an Eye on Growth
Is there a corollary to this quote? Something about how you have a problem that can be solved optimally with a drill and adequately with a hammer, so you decide to choose the hammer because you're already pretty decent with one and you've never really used a drill. So even though you're not using the optimal tool, you've gotten the job done and moved on to the next one while you'd still be learning the drill. Is there something like that?
Is this actually true? I've heard Galaxy marketing is fairly saturated in the US, but in Australia I see at least twice as many Apple commercials than any competing OEM.
Check out Steli Efti's talk on customer validation & sales. With SaaS, getting a handful of paying customers is the most important criteria for success. Getting it without even having the product built is pure genius.

https://www.youtube.com/watch?v=IfKMsdI9wJM
Found after 500 years, the wreck of Columbus's flagship the Santa Maria
Online Multiplayer has been hands down the biggest problem I've had to deal with while working on Wyv and Keep (plug: htp://www.wyvandkeep.com). It's still buggy as hell, because I still have no idea what I'm doing, I'm spending plenty more time fixing it before we release on Steam, because the current implementation is Not Good Enough.

I'd estimate it's at least doubled the dev time, if not more, due to the amount of stress and extra work it's caused, having to refactor the codebase in order to support it (arguably resulting in much better code, but that's really irrelevant if the game works well), and added years to the dev time due to having to spend the odd weeknight and weekend trying to remember the complexities of it. And this is for a relatively simple game!

My single best piece of advice to rookie indie devs thinking of adding it, especially when they have no prior experience with, is this: Don't. It's not worth the trouble.
Can Laravel Save PHP?
Interesting, thank you; but in that quote isn't Fielding actually comparing RPC and HTTP, not REST?
and now visual studio potentially depends on java... (android) what a farce.
Yes, you're right, I was being a bit sloppy there. The Uniform Interface (and Layered System) is one of the ways in which HTTP does follow RESTful principles, though, so the thrust is still the same.
Chrome 35 improves JavaScript loop speed 3x
Are there any issues you suspect Syncthing could suffer from?
Just found this while doing some performance benchmarking around different ways to write a JS loop. The results were quite surprising: https://slack-files.com/T02874CDH-F029WFR7C-fc5594
So glad I'm no longer a .NET developer. Every year it's a new razor blade.
Regarding RPC, you're right, I guess I'm not quite following the classical understanding of it. I tend to work with actor systems, where everything (in-process or intra-process) is message passing, so I tend to see the message layer first, and anything else merely a protocol implemented on top of it. Hence my response.

As for HTTP, if HTTP itself isn't truly RESTful, the only protocol I've ever seen REST implemented on, I'll have to resign from this debate, because it becomes completely abstract.

I hope the right protocol comes along to show us what REST might really be.

I'm spotting a bit of a pattern in REST supporters, where if some understanding of REST is found to have faults, it's called "not truly RESTful". Reminds me of how Agile failures tended to be explained as "not truly Agile"... but that's another story.

I judge a system by the implementations, not by the theory. If REST is this beautiful unattainable ideal that almost no one can truly implement, I tend to think the fault doesn't lie with the implementers.

It's quite likely REST simply has very few applications itself, but the applications have the potential to become all-encompassing (like the web itself). But in this case the issue remains REST is not suitable for 99% of the services people expose on-line, as each of those services has a specific scope and application, where REST's "network effects" of uniform resource interface and so on don't apply.
Impressive: Time put the source code for the project on github: https://github.com/TimeMagazine/babynames

Not a fully replicable analysis, but still very cool to see.
Google Thinking to Change Gmail Interface Features
Are you also saying, like I was, that apple are Good At Marketing?
Which Team Do You Cheer For? An N.B.A. Fan Cloropleth Map
Lower end market at a mid-tier price. I'd imagine the iPhone 5c with Beats branding would sell much better than the current 5c. Plus the colors would match the headphones. Maybe Apple had the right idea but the wrong brand.
LLJS targeting asm.js may help but it still looks like an early effort.

http://jlongster.com/Compiling-LLJS-to-asm.js,-Now-Available...

https://github.com/jlongster/LLJS
This is quite well known, just a quick google will do:

http://www.tuaw.com/2013/11/04/apples-advertising-budget-dwa...

I think Apple recently doubling their marketing budget to $1b was taken with great fanfare, but still puts them far behind their competitors.

However, it is an open question whether Apple stores should be counted as marketing or some other kind of expense. It definitely helps promote their products, but the direct channel also helps with profits.
You're assuming that they are crackable, some are but it's not a gauranty that they all are. Snowden slack of capture suggests that properly used encryption is still good.

Korea, Japan, Russia, China, India and Brazil will all be spending tons more on encryption. The most fatal flaw in all of this is that I expect they will have their own secure protocols in the next couple decades and what's really ironic, our former "enemies" may do a better job.
I can confirm it's probably enabled by default, every network I see these days is spammed by Dropbox broadcast messages.
Well that seemed excessively pedantic IMHO. It actually didn't touch much on information theory, and where it did, many of the comments disagree. I'll cite the Landauer limit[1] as what (yes, arguably) connects the entropy of information theory to the entropy of physics.[2]

Also, I only mentioned physics because the article did, quoting Lamport "Most people view concurrency as a programming problem or a language problem. I regard it as a physics problem."

Unfortunately the article didn't elaborate any more on the precise type of physics problem in question (Maybe Lamport does elsewhere), whether the physics of computational complexity or the physics of information theory, or something else. But even those two sub-fields have many connections and similarities (as does pretty much everything in physics and math. such connections are the bread-and-butter of theoreticians).

1. http://en.wikipedia.org/wiki/Von_Neumann-Landauer_limit

2. http://en.wikipedia.org/wiki/Entropy_in_thermodynamics_and_i...
especially since its a blog..there's relatively little at risk...relatively ok for it to blow up...
There is a pure python mode http://docs.cython.org/src/tutorial/pure.html that works even in Python 2.
I would like to see more elaboration on why things like fold are not idiomatic Rust. The article mostly just states it without elaboration. If anyone can elaborate, please do.
> Services are naturally centered arounds verbs (commands and queries) and not nouns (resources)

Can you qualify that? Queries are presumably queries on resources, and which commands did you have in mind apart from creating or updating resources?
Seems pretty likely. John (M) for example was perhaps at 9% circa 1870. That's pretty dramatic, and definitely speaks to the lower cultural diversity.
That deconversion process will take another 15-20 years [1] if the Paducah and Portsmouth plants are at the planned utilization, which AFAIK hasn't been true since at least the 2013 budget sequestration. Our UF6 isn't going away for another few decades.

> Those uranium oxides sat in the ore bodies for billions of years without causing trouble.

We've found ground water that is contaminated not only by uranium from coal plant ash ponds [2], uranium mines [3], ore processing [4], and flooding [5] but from the untouched ores lining natural underground aquifers as well [6].

> There are almost certainly gigantic uranium ore deposits underneath the ocean. No one is worrying about them.

Any ore deposit is compressed for eons under pressure that is hundreds, or thousands, of times greater than anything we experience on a day to day basis, or even at the extremes of our technology. There's a huge difference between nature's long term storage and our temporary tin cans.

[1] http://www.nrc.gov/materials/fuel-cycle-fac/ur-deconversion....

[2] http://en.wikipedia.org/wiki/Uranium_poisoning_in_Punjab

[3] http://www.denverpost.com/ci_14894696

[4] http://www.epa.gov/radiation/docs/tenorm/402-r-08-005-voli/4...

[5] http://energy.gov/lm/articles/doe-releases-data-summary-repo...

[6] http://www.sciencedirect.com/science/article/pii/08832927949...
Build REST clients easier (use a general hypermedia client)
Well, they don't put a lot of resources into it, but they direct their resources very well. Their biggest marketing boon has been curating a really good reputation (not releasing products that suck), building a rabid fan base, and so on.
RMS reminds me of Ignaz Semmelweis. He is correct, but people stick their fingers in their ears and try to reject what he is saying because of how he delivers his message and because they are not comfortable with the implications of what he is saying.