skysight-inc/HackerNews huggingface dataset:
The list of nodes will be hard-coded at the genesis with known meatspace identities. It can only be updated by a transaction signed by >2/3 of the existing nodes.

I am writing the "validators contract" for tendermint right now. It will have this functionality.
Totally agree, big organizations need something integrated. With GitLab we include the issue tracker and build tool you mentioned as well as having git-annex for large binaries.
Spectrums is plural of Spectrum, as in Sinclair ZX Spectrum, the computer that 90% of British kids had in the 80s (http://en.wikipedia.org/wiki/ZX_Spectrum).
Perhaps it's semantics, but you're right - it's not a security hole.

It's worse.

Exceeding authorization is exploiting an existing hole.
Female mosquitoes must feed on blood to be able to reproduce so engineering a bite-free mosquito is impossible.
> Browsers could implement the same line breaking algorithm as used in TeX, but have decided not to for performance reasons. This is an odd reason — TeX was developed and runs on computers much less powerful than those commonly used in mobile phones.

Yes, but not at a speed that many would find acceptable for formatting a web page, even on a modern computer.

Nor need it be: you only have to generate your (La)TeX document while creating or editing it; a couple of seconds for a short document is thus tolerable. Whereas a web page has to be formatted by every visitor on every visit -- maybe several times if they resize their browser. It needs to be more or less instant.
When you don’t know what made you successful, you make new mistakes
Gogs (https://github.com/gogits/gogs) is a rather nice up and coming alternative to gitlab for self hosted repositories.
Considering the best practice for HTTP/1.1 is to create few very large files - why would compressing headers really make a difference?
This link was posted short after the keynote, this was announced, as well as more information about FastBoot, the thing you're talking about: http://emberjs.com/blog/2015/01/08/inside-fastboot-faking-th...
"What is the difference" I could go on for days about the differences between dogs and humans, if only the author had permitted comments to be left on the page.
You are always able to export to mobile with Unity Free (now Personal) but now the Pro Mobile features such as Static/Dynamic Batching, Code Stripping which is now included in the Personal version.

The only main difference is that you are paying $1500 to remove or have custom splash screen when you deploy to mobiles.
AI at Google knows which document to show for your query and which advertisement you are likely to click on. Goldman Sachs uses machine learned algorithms already. Running a company requires vision, creativity, leadership, human interaction and usability.

If we allow for a conscious AI to house in non-biological neurons, then we should also allow Turing-complete companies to have a consciousness. Visualize every Google employee with a two-way radio transmitting signals just like neurons would do. Would such a Google-brain be conscious and capable of new and unique mental states, or more familiar states like stress?
I think if there's a significant enough uptake on HTTP/2, we may get to a point where we start feeling that it's not worth optimizing for HTTP/1.1 anymore. Obviously HTTP/1.1 will still just work, but the HTTP/2 approach _can_ potentially work much more elegantly, when all the tooling is in place, and I definitely believe it will be preferable.

I agree that the existing approaches are very much valid though, but I also look forward to not having to concatenate javascript files anymore. We've developed a lot of tooling to work around issues that stem from that, and it doesn't address the problem of needing a varying set of javascript files on a per-page basis easily.
Can you elaborate in the github monoculture? What's the downside of github you're seeing?

(Just curious!)
It's also worth noting that we're getting to the point where fastest doesn't really matter. Both Ember and React will be fast enough. Performance shouldn't be a deciding factor.
​FREAK: Another day, another serious SSL security hole
IPew Attack Map
Hackaball – A computer you can throw
Awesome job. Just needs infinite scroll added to the article list :}
What about sharing - heavy - files with coworkers not using this app? What about uploading files? It feels to me like working in a bubble... but maybe I'm wrong.
The Production Clojure Checklist
Does a shell really exercise the use of data structures? To my mind it seems there's very little state, and all of it in substantially simpler formats than even e.g. JSON.
I wasn't thinking of personal computer when I wrote the comment. I was thinking about more of a state-of-the-art super computer type (in 2000 that would have been ASCI RED), which would have probably be the same magnitude in term of physical size with "computer" in Turing time! Prediction should be judged based on "the best it could be". Otherwise, it seems like an arbitrary pick (why personal computer and not tablet?), doesn't it? Anyway, since it's an exponential development, the line between "supercomputer" to "big server" to "personal computer" is only a few years off. So yes, it was impressive.

But that wasn't the point I was trying to make. I meant that even with access to computing power a gazillion more powerful than mentioning in the quote (again, not personal computer), we still couldn't pass the Turing test. The prediction was off on both the necessary computing resources, as well as the difficulty of the test itself.
I agree. Especially stuff like init, or non obvious non-trivial system services (and, of course, in the case of these distros, systemd).
This demo is taking up an entire core of an i5 2500k.
To update a table. It barely updates once every two seconds on a three years old phone.

My terminal is faster than that and doesn't even use 1%. A native application is faster than that and barely uses 1%.
I know this is a nice advance for client side rendering, but can we stop pretending it's in a good state ?

(Although if you're updating this many times per second your application, you might be having a problem already.)
> how `svn commit` can put the repository into a state that never existed on any developer's machine

git add -p creates the same issue for git (a commit that never existed on disk) and git rebase with squash and/or reodering of commits does as well. That's usually considered best practice.

The problem I often observe with git (pull -)rebase is that people have a hard time wrapping their mind around the fact that all commits change and when they change and in what state the checkout is are when they get a merge conflict (remote HEAD plus whatever was already applied). The conflict is often unavoidable and you can argue that rebase is making it easier to resolve the conflict, but it's harder to reason about than "ok, update does a merge and I get whatever is on the server plus my local changes".
Shipping a non-trivial app in Swift
Kind of hard to feel any remorse for their problems, their convention agency recently purchased the Riviera at the end of February and last I read it was to shut down by May displacing dozens of booked conferences and 150,000 booked room nights. If they were so worried about tourism you would think they would look to not pull stunts like that, but this quasi government agency really has no limits.
It still matters on mobile. Whether it is running out of memory or being too sluggish to be usable.
Apple buying a third of world’s gold to meet demand for iWatch
Some information can be seen at the PR for Glimmer: https://github.com/emberjs/ember.js/pull/10501.
I held out for the longest time on those grounds, and then finally tried it and it blew me away so much that I've compromised for this one tool
Great job. This is something I've wanted to do (test speed of themes). 2500 is more than I'd ever be able to handle, but this is great.
Incorrect. When you view a html page, the browser fetches the javascript, css and images in the page automatically.
It's the same idea as peercoin and others. Once you have amassed enough coins to control the vote, you're now financially dis-incentivized from voting in such a way as to undermine trust in the blockchain.
Hi HackerNews!

We're using TM consensus to create something more interesting than just a crypto "currency", so the website and github hasn't been updated in a while. But the algorithm is still sound (as far as we know) and we're looking forward to launching soon!
What I assume you are implying is so oversimplified, I'm not even sure how to respond.
The reason nice places like SF and NYC are so expensive is that nobody is trying to make more nice places. Tony Hsieh is doing a great thing to trying to make a new nice place.

It's too bad the blocks in Vegas are so large (looks like 380x480) and the streets so wide. It'll be really hard to ever make that appealing, especially given the climate.
Elon Musk, Bill Gates, and Stephen Hawking all agree AI research is dangerous. Google does not seem to feel there is a credible risk and is doing it anyways.
The original article addresses this.

"These are large, opaque files that, while not code, are nevertheless an integral part of your program, and need to be versioned alongside the code if you want to have a meaningful representation of what it takes to build your program at any given point."
Someone Better Call Saul
How much of our work in this business is just useless theater?

I couldn't stand working in a place where it was a significant portion of work. But it is probably unavoidable to some degree.

I see that code reviews for newcomers' commits often have these elements:

First review: "you did X. That's not smart. Do Y instead."

The new employee goes back to rework their commit.

Second review: "you did Y. That's not smart. Do X instead."

After a few weeks / months it starts getting reasonable. It's not as extreme, and it's well disguised in friendly demeanor, but there's still some similarities to what it was like in the army "boot camp".
Great article and a good wakeup call on what to improve in Git. I don't agree that git-annex is centralized by nature. You can choose to download all the binaries and upload them to another server. Not everyone might do that if it is multiple TB's but it is much easier to work with multiple remotes than in a centralized system
Did anyone actually say that superhuman machine intelligence is prima facie ridiculous? I followed the discussion pretty closely, both on hackernews and the quotes and discussion by prominent researchers, and I don't remember reading that. It's possible that one or two people somewhere in the discussion said the idea was completely ridiculous, but it didn't seem to be the common sentiment. The main dissenting ideas I saw said that it was too far away to be considered as a threat, and that most high profile researchers weren't giving it serious consideration.

I don't doubt that "otherwise smart people" have said that superhuman machine intelligence is completely improbable, but I don't know about the "many" part. There's always someone who will say anything. The closest I've seen to a consensus is disputing the timeframe for AGI/SMI, not the possibility.

For that matter, I don't remember seeing a lot of people say "Computers will never play chess" or "Computers could never drive cars" or "Computers could never compete on Jeopardy". I can't recall one prominent researcher saying any of those things definitively, much less "many" people saying any of them.

It seems like there might be some inserting of quotations into the mouths of others going on here.
In regards to taking up an entire core, it's updating as fast as it possibly can, it's basically a stress test. In practice, updating this quickly isn't useful, you would want to throttle it for production use.

It's reasonably quick on an iPhone 6 (though obviously slower than on a desktop). In actual use you'd obviously design things a bit differently. Again, this is a performance test, not a real application.
The One Hour Side Project
Unity's been free for years, you've fallen for their advertising to upstage Unreal.

"Finally offering a free version"

Honestly, it's been free for ages.

Not only that but Microsoft had XNA which was also a free game engine that they only discontinued last year so you're wrong thinking that html5 was the only option. I don't think you really researched the market much if you thought that.

Plus if you are serious about an RTS you should read about AI war, who used Unity. It's interesting as if you want to do multiplayer in an RTS you can't use Unity's collision detection as the float calculations are chipset dependant.
A nitpick: All the animated stuff in the properties sidebar is distracting and feels slow and annoying.

Also, I might be tempted to pay $29.99, but $49.99 feels like too much to me for such a niche product, especially since that's more than some full-fledged multipurpose image editors like Pixelmator.
Separate from the privacy concerns, what about network traffic? "a few hundred kilobytes" for every file you create adds up.
Regarding 1, 2 and 4: It certainly seems like a long way to create something like the human brain, but perhaps there are far simpler systems that yield general intelligence. We don't seem to be very good at predicting the invention of algorithms, so with all due respect I doubt experts can provide reliable predictions. Hardware as powerful as the simplest models of the human brain already exists and growing computational resources enable studies of neural networks at an increasing rate. I think, in that light, the claim that the breakthrough is far in the future seems to be about as strong as saying it could happen within the next ten years.

I've asked this question in the discussion yesterday as well, but I didn't receive any response: What kind of breakthrough do you expect after which it would be justified to be concerned about general intelligence? And how do you justify that it's unlikely to expect that surpassing human intelligence is not just a matter of scaling it up at that point, i.e. that the invention can be regulated quickly enough once it exists?
Is there a good way to make a website that's available over both HTTP/1.1 and HTTP/2 and does the right thing in both cases? I feel like it'll be many years before I can design a website that's available over HTTP/2 only.

For instance, is there an asset pipeline that will concatenate and minify all my JS for HTTP/1.1 clients, but minify my JS separately for HTTP/2 ones, and build versions of my HTML page that references the two different assets depending on which HTTP protocol is in use?
Top 30 Horror Movies Playing on Netflix Right Now
But gogs doesn't self-host its own development! IIRC gitlab didn't initially either. That it does now inspires a lot more confidence.
Eh, I'm not sure that I am using it right, but it hasn't given me a correct answer yet...

I have asked it complicated things like "What is largest unmanned artificial satellite", and "What is the combined population of Oregon, Washington, British Columbia and Alaska".

I have also asked it simple questions like "Who was the fifth vice-president of the USA". It answered this one "interesting person".

It answers everything as "interesting". The only question it actually answered so far was "What is the population of the USA", which it incorrectly calculated as 32 Million.

Good work though, keep working the bugs out of it.
Is there a standard synecdoche for the type of tech company that's better at 'thought leadership' than at its actual business?
"A third of the world's gold production", not "a third of the world's gold".
One of the motivations for this change was that a real-world application was too slow. As the original presentation says, choosing a technology and then finding out that it's limiting you is really rough when it happens to you.

Performance _does_ enable certain kinds of applications, and it does absolutely matter, even on the desktop.
I disagree with the "Dropbox, iCloud, Google drive" thing. Nobody is using them as a platform to work their files on, but more as a quick way of sharing files. not reliable to store or else.
My barrier to entry with Unreal is not knowing C++ - I picked up a few books and will be diving in shortly, but I'm already good with JS so UnityScript was easy to pick up (easy, but painful none-the-less).
Or set a dropoff only stop 50 yards from the designated stop. That way the people from the stop don't try to board.
When I was in school (not all that long ago), we had a couple large centos servers, and a ton of cheap workstations that did nothing but server as NX Clients for the most part. Everyone just logged on to their account on the cent servers for anything Computer Science related.

It worked pretty well.
From what I read, it sounded like they already built the thing, they just don't have the means to bring it to production.

Selling kits wouldn't require them to bring it to production, while at the same time letting people experiment and use their app. I don't want to re-create their product, but it would be nice for people who still want the product and are willing to do a little work.
HTTP/2.0 does not only compress headers, it also keeps a context of headers that were already sent. So if you want to include a specific header with the same value in multiple requests (like, say, a cookie), it won't actually be re-sent on the wire. The other side will know that the value hasn't changed.
Ember's “Glimmer” vs. A Simple Underscore Template
Although Unity is not 100% publicly open-source without requesting for their source code license, they have released a bunch of their source code to the public.

http://blogs.unity3d.com/2014/11/26/4-6-is-released-with-sou...

https://github.com/Unity-Technologies

https://bitbucket.org/Unity-Technologies/

Asset/Cache Server: http://unity3d.com/unity/collaboration/

Built-in Shaders: http://unity3d.com/download_unity/builtin_shaders.zip
"Best practice" can take a lot of work and often doesn't happen in real life. HTTP/2 gets you this advantage for free.
The other point is that TLB misses can be satisfied with a single cache line fill.

Or that is the theory, as told to me by a big inverted page table advocate a couple of years before of Linus's comments.

Personally, I tend to favor Linus's perspective. Particularly because making an optimal decision about how large the page table hash is, turns out to be pretty hard to do at runtime. Changing the size is even harder. This means that you either waste a lot of unnecessarily memory on the inverted tables, or you tend to take excessive page table misses, and waste a lot more than 3 cache line fills satisfying them.
Someone should warn cyanogenmod that their SSL cert is expired: https://www.ssllabs.com/ssltest/analyze.html?d=whispertool.c... (although I guess at 5 months over, it falls squarely into the couldn't-be-bothered bucket)
I should have added the caveat that there will always be a handful of cases where you do need absolute top performance. However, I do think that for the vast majority of apps we'll end up at a point where performance isn't the deciding factor. It doesn't mean that we shouldn't keep improving performance, just that being the fastest doesn't matter so much if all the options are very fast.
No jokes allowed on HackerNews. Only serious and totally informed discussions by people who have clairvoyance levels over 9000...
Really inspiring and look forward to hearing more!
Thanks and I agree that historical performance metrics would be a great indication of returns.

What I'd like to do would be to create a system that processes 5 years worth of historical data, gathers all symbols that have had spikes up or down by 10-75%, have good volume and liquidity and are affected by either news or an earnings report. I could then auto-construct the baskets that surround each issue and calculate returns on the long side or short side.

I like this system because it executes on 4 critical levels:

1. Works in a good market or in a bad market due to short and long positioning that can be taken whereas most trading systems (and Technical Analysis) only really work in good markets.

2. You don't have to be late in terms of buying into (or shorting) the direct issue. You buy into or short the indirect issues, which enable protection and diversification.

3. Nobody really is doing this today.

4. It's based on information arbitrage and hidden connections, not numbers.
> The long and short of it is; when you build a front-end to a website, and you know it's going to be served over HTTP2...

Well, that's the rub, isn't it?

When are we going to possibly be in a state where we know our website is going to be served over HTTP2?

Not for a while, probably? Not just wait until all the browsers support HTTP2, it's wait until the browsers that _don't_ support HTTP2 are a small minority.
On first glance, sign me up for the first batch!

When I started reading though... it's a neat idea with "meh" execution. It takes round photos and you have to rotate the device to zoom in and focus? What?
Too bad. I interviewed with these guys and have nothing but good things to say about them.
CommitStrip – Blog relating the daily life of web agencies developers
ahah sorry, about that @jkestner. Thanks for the clarification @robwilliams. Guess thats what I get for reading fast! :P
For the curious, here's a port of the Dbmonster demo to a simple Underscore template — the kind of base-level rendering strategy you might start with in a Backbone app. (And vintage 2009 technology.)

http://jashkenas.github.io/dbmonster/

Edit:

To head off grumbling at the pass — It would also be easy to do a slightly less-simple version that keeps the flickering impossible-to-read popups open (putting redundant tooltip DOM into each table cell isn't how you'd actually write this), and the server names selectable ... but those particular "features" don't really seem relevant to this particular UI.
McCain would of at least prosecuted torture, but it seems rather academic to argue which warmonger is the nicest warmonger.
> Resist commenting about being downvoted. It never does any good, and it makes boring reading.

> Please don't bait other users by inviting them to downvote you.

https://news.ycombinator.com/newsguidelines.html

Jokes are fine but please follow the guidelines.
Man, I feel bad for these people who were hired on for an experiment just to be dumped after a few months. That sucks.
Unlike your warp drive or teleporter examples, we're pretty sure human-level AI is possible because human-level natural intelligence exists. The brain isn't magic. Eventually, people will figure out the algorithms running on it, then improve them. After that, there's nothing to stop the algorithms from improving themselves. And they can be greatly improved. Current brains are nowhere near the pinnacle of possible intelligences.

> Far from being the smartest possible biological species, we are probably better thought of as the stupidest possible biological species capable of starting a technological civilization—a niche we filled because we got there first, not because we are in any sense optimally adapted to it.

— Nick Bostrom. Superintelligence: Paths, Dangers, Strategies[1]

1. http://www.amazon.com/Superintelligence-Dangers-Strategies-N...
The post was updated. See this comment: https://news.ycombinator.com/item?id=9140178
Plenty of alternatives are not necessarily a good thing. Repository/project software (and hosting even moreso) seems to be subject to tremendous network effects. One of the exciting things about gitlab is it seems the first such software (and with gitlab.com, service) since github took off to make a serious run at massive adoption. I doubt there's room to make an impact for another open source (excluding enterprise version) github-like that merely happens to be written in another language. The next next such project to make a serious run needs to innovate in some fashion.
To be clear, while we're using Handlebars syntax, the underlying runtime is not the standard handlebars.js, but a custom version for Ember.