skysight-inc/HackerNews huggingface dataset:
That is a fair point and well reasoned.

I look at the issue less conspiratorially than some of the other posters. Whenever the law is changed, a party somewhere, is always quick to claim the political elite will benefit.

In it's current guise I support the ability of people to have inaccurate information about their character removed from search rankings/indexing services.

It boils down to the oft-thorny issue of what is reasonable?

I do not think it is reasonable to have cases removed records. I do think it is reasonable to have published media that portrays an innocent party as guilty removed from publication.

I don't know how that is accomplished but this legislation seems to be moving in broadly the right direction.

I can see it being used to right more wrongs than vice versa but I am an optimist.
That's not necessarily true. My own site is a Jekyll site. To host that on S3, I'd need to generate it first and upload the generated files as opposed to my source files. Now that's not really a big deal, but I do enjoy the convenience of only having to do a `git push` to deploy my site on Pages.

That being said, I notice times similar to another commenter above, around 1-2s usually. I don't think I've seen a five second load time.
I also found this useful since it has more diversity of content:
http://codingstyleguide.com/lang/ruby
The title of this post seems to be rather out of date.
I was at a meetup where the speaker suggested react is great for business-like apps, but for things with an insane amount of dom objects like html games, it tends to get bogged down.

Since React claims to be super fact, has done a performance comparison to see in what situations and how much better react performs in certain cases, compared to say, angular.js or more vanilla frameworks?

(Also I hear that there is a really great speedup that using OM gives you, but I haven't seen any comparisons with om either)
The DHH Problem
Slides and audio from a lightning talk by Tom Stuart at Scottish Ruby Conference 2014.
Yeah, this is a great description of how our errors package helps a lot. You can tie user-facing status codes and messages to errors with stack traces, and only show the user-specific message to end users.

Moreover, since you can bind arbitrary values to error types with our error library, internationalization is easy. Instead of binding a string user message, you can bind a locale->string map user message
I don't think he was talking about using Git for graphics files. I assume he meant html/css/javascript files.

As a designer who codes (or a coder who designs, not sure at this point), I can see what he means about learning Git. It was tough for me to grasp until I saw this:

http://nvie.com/posts/a-successful-git-branching-model/
Any ideas about the habits of the brilliant programmers of past and present? e.g. Trovalds, Sysoev etc etc?
6000 seconds. That’s still about 2 hours. :)
What I Learned in B-School (Part 1)
This is not based upon any particular knowledge or expertise, but upon many years of casual observation, general news reporting, and anecdote from friends and whomever: Given their position as well as long-standing ties both politically and militarily as well as economically, I have to -- in my own mind -- seriously question the independence of anything of real interest to the U.S., that's happening in Taiwan.

I don't mean that the Taiwanese aren't their own people with their own interests; nonetheless, I would expect to find their various systems rather thoroughly and effectively infiltrated.

Again, I don't have any real knowledge in this regard. I'd welcome more knowledgeable comments in response to mine.
Having given it 69p and a couple of attempts, it's not much good. Maybe it just doesn't like the camera in the 5S but I got either everything in focus with no refocusing or nothing in focus and minimal refocusing from "very blurry" to "merely blurry"
React has a much richer notion of what a 'component' is. To date, most JavaScript libraries lack shared assumptions about how you will build your UI. jQuery plugins make only the extremely minimal assumption that you will apply the plugin to some DOM element - beyond that, how the plugins behave, how they manage their state, properties etc. is not defined by any standards or even assumptions.

The confirmation popover you link to is a good example. It's a black-box component which exposes a fairly minimal interface. The constructor for this component works like this:

new ConfirmationPopover(msg, [title])

To attach the popover to an element you need to do:

popover.show(el, [fn])

However, if we take another component from the same library, the swipe component[1], we see different conventions. Its constructor:

Swipe(el)

It also has a show method which takes totally different parameters:

.show(i, [ms], [options])

This is why I describe such systems as package managers or library managers - they're just a way of importing and exporting code and don't do anything to aid reuse. They're not particularly likely to play well together, lack standard interfaces and are almost certainly not composable in any meaningful way.

React components are different because React defines some standard details of how components behave, how to extend them, how to inspect them and pass data back and forth. Components can contain other components, and all components have a relative place in the render tree. This makes possible standard developer tools that can be used to observe and inspect components in a DOM-like tree structure[2].

So, you could certainly use bower to distribute React components. What's different about React isn't how the code is distributed but the fact that you can have expectations about how, say, a React photo gallery component would behave that you would not get from some other JS library.

[1] https://github.com/component/swipe
[2] http://facebook.github.io/react/blog/2014/01/02/react-chrome...
That is pretty interesting. So using Fora you can jumpstart a new app by defining all your data models, and then select a bunch of components to build a skeleton view that makes use of those models?

If so this will be very useful, especially since it sounds like it will allow us devs to spend more time on the business specific logic, and making the interface beautiful, instead of spending lots of time gluing together components and models.
As mostly an outsider to the web front end development, React.js is probably the easiest one for me to understand among the typical "frameworks", especially Angular and Ember.

After all the excitement about Angular for example, I went to learn about it and just got lost with new concepts: DOM transclusion, scopes, services, directives, ng-apps, controllers, dependency inversion and so on. I can use it but need someone to hold my hand. It reminded me of Enterprise Java Beans.

But so far just learning how React is put together and looking at the tutorials it seems like less of a framework and easier to understand altogether. I suspect this might become the new way to build web applications.

Well anyway, don't take this too seriously, I as said, I am an outsider to this.
DevOps? Join us in the fight against the Telco monopolies
SendHub (YC W12) is looking for Systems Engineers.

SendHub is looking for a talented and determined individual with a track record of scaling highly available, geographically distributed, fault tolerant services with 100% availability requirements.

Join us in building a new kind of phone company and fight against the Telco monopolies.

About SendHub:
We're building tools to make it fast and easy for businesses to communicate with their customers and employees.

Founded to help educators in under resourced communities, we’re taking on the Telecom giants. Hate your phone carrier? Us too. Telecommunications is a duopoly dominated industry, which has systematically suppressed competition over its 150 year history, in order to keep prices unfairly high. We’re going to change this, starting with business phone service. We have a ~$1M annual run rate and closed a $3M Series A in September 2013.

Our Philosophy:
We believe in taking care of our customers and each other, so together we can build wonderful products. We work hard delivering the best to our customers and we wouldn't want it any other way. We're hungry and you need to be too.

We're based in Menlo Park, CA, and while we're flexible on working remotely, you'll need to be around the office and eligible to work in the United States. If you're interested, please drop us a line:

===========================

jobs [at] sendhub [dot] com

===========================

Benefits:
Health, Dental, Free meals and untracked vacation

The Role:
You’ll own and manage SendHub’s geographically distributed cloud infrastructure. This includes driving efforts to eliminate downtime, improve disaster recovery, perform regular maintenance and scale our services to support millions of users.
As a systems automation and architecture expert you will accelerate SendHub’s ability to respond to emerging issues and enable the team to make changes at scale.
You'll lead initiatives to improve our team's operational efforts and set the gold standard when it comes to participating in the on call rotation.

Requirements:
You are proficient in a virtualized Linux environment, and know how best to automate and monitor it.
You have experience in deploying and managing sharded and replicated postgres environments.
You’re comfortable with at least one scripting language e.g. Ruby, Python or Perl.
You have in-depth experience deploying and maintaining monitoring tools (Nagios etc.).
You are familiar with deployment tools like Chef, Puppet, or rolled your own.
You are comfortable configuring routing, firewalls, VPN and DNS
You have proficient communication skills and are comfortable interfacing with third party vendors.
You strive for mastery and value feedback from others.
You’re hands on, yet understand the importance of enabling others.

Nice to have: Experience with AWS, Rackspace, RabbitMQ(AMQP), Redis, Riak, and BigCouch(CouchDB)
The game worked for me. But the voice recognition of individual letters was abysmally slow / bad on my laptop. I guess it gives a better sense of how far back voice recognition is.
OP here, first article. Hope it's worth the read.
100% agree, pumpkinattwelve (btw, awesome username, sir/ma'am).

I started Product Hunt (http://producthunt.co, essentially a "Hacker News for products") and the popularity of "Show HN" is one of the signals proving people love this stuff.
>Just like the mafia system has it's downsides, so does the Somali system as evidenced by going on several decades of bloodshed now.

This is an incredibly ignorant statement. The source of bloodshed in Somalia is foreign governments via the UN/AMISOM and their largely Kenyan/Ethiopian troops trying to prop up a government in Mogadishu, as well as the foreign-funded al-Shabaab they fight. This is not some noble jihad for democracy, just various factions struggling for the benefits a monopoly backed by strong foreign powers will bring.

The political climate and level of violence in south and southwest Somalia is vastly different than the rest of the region. Beyond Galkayo, there is pretty much no war. In Puntland and Somaliland, Xeer and customary law trumps the weak governments of the autonomous regions.

You falsely equate Xeer to the mafia and where the Xeer legal order reigns there is peace in Somalia. A mafia system is identical to a state except a state has public acceptance of the hegemony. The Somali people want Xeer and not state rule. Even during the Barre regime they would not recognize decisions of state courts and would handle the bulk of disputes their own way and ignore state rulings.

The decades of bloodshed come from a minority group of western-educated democracy lovers and psychopath "warlords" who have been waging war on the Mogadishu area for the prize of UN recognition and the trough of foreign aid money it brings.
That problem of "negative moves" is solved by the Chinese rules. A point is scored under them for each surrounded intersection plus each stone on the board. So you can defend any supposed weakness without losing points (you still lose sente and points if you needlessly defend when the score is not settled yet). You can even reduce your territories to two eyes each if you feel like.

By the way, the Chinese rules let solve neatly all those cases handled by special rules in the Japanese rules. The bent four in the corner is the most notable one. Playing it out with the Chinese rules is a neat explanation why that corner is defined to be dead: the surrounding player defends any weakness without losing points and starts the ko. The other player has no ko threats and dies. Those defensive moves lose points under the Japanese rules so they have to make a special rule for that shape and many others.

The only problem with the Chinese rules is that scoring takes longer and completely destroy the shape of the game: you fill in the territory of one player, take out the other's stones and count by grouping the stones in convenient shapes. Furthermore if you want to count during play you must remember how many stones have been captured because prisoners are returned to their bowl and are not stored in plain view (the score penalty is paid by not having those stoned on the board). Japanese rules are a shortcut that makes scoring easy but the tradeoff is the dictionary of special cases at the end of the game.
worth pointing out github.com/spacemonkeygo/errors is 100% compatible, allows you to get a source and explanation, allows for error hierarchies, allows for arbitrary user-defined error details, etc.
No, since I expect our next batch will be our best yet.

That said, your point is true in two ways (though I don't think in the way you intended it). First, we try to make every batch better than the ones before it. That implies that it's always better to come to a later batch (I think it's certainly true that it's better to come to Hacker School today than a year or two ago). Second, every batch has been an experiment for us: we make lots of changes (big and small) and we never know a priori how well they'll work.
Cue – Deep Health Tracker
This sounds like the sort of thing that could easily be automated using a five-line Bash (Ruby, Python, etc) script.
Who cares about TOS? They're not binding to users in any way whatsoever, unless the users want it to be binding (i.e., as a contract to buy goods/services from them according to that ToS)

The service can disable their accounts (if any exist) and block their IP's; the service can stop doing any business with them if they don't like the ToS; but the service can ask them to comply, but can't really demand that they comply with ToS, it's not a law nor a contract that they've agreed to.
Microsoft lowers Xbox One price to $400 without Kinect
A Epice Selfie, that spanned 36 countries and 600 days
You can buy them direct from the manufacturer, Tranquil PC. http://www.tranquilpcshop.co.uk/ubuntu-orange-box/
£7,575.00 is the base price.
When your users show you new ways of using your own app
What's your source? Mine is the CIA.

"Contrived computer chips found their way into
Soviet military equipment, flawed turbines were installed on a gas pipeline, and defective plans disrupted the output of chemical plants and a tractor factory."
~ https://www.cia.gov/library/center-for-the-study-of-intellig...
Well, we know of at least some in government agencies involved doing so, because some of the information that has become public as a consequence of the Snowden leaks (not part of those leaks, necessarily, but information that was released afterwards) has revealed numerous instances of abuse of the surveillance system for personal purposes by people with direct access (not just using the information about the system for personal purpose, but using the surveillance systems themselves for personal purposes.)
you lose about 10% after 1 second, and about 5% every second after that. So yes, it is a very big deal.
AES-NI doesn't work on ARM, which is what we have.

>> Go TLS does not have wide support for backwards compatibility with less secure and older protocol versions (a good thing, until you have no other option).

> LibreSSL people beg to differ about this "feature".

Agreed agreed! Don't use old protocols!

>> Go TLS does not give much control over the certificate validation process, which makes it difficult or impossible to add additional checks and validations.

> What exactly is this about?

OpenSSL allows you to specify your own validation callback, to add additional checks to the certificate validation step. The only certificate validation option Go's TLS gives you is either InsecureSkipVerify or not.

>> Oh, and Go TLS is vulnerable to timing attacks.

> A mitigation is in WIP https://codereview.appspot.com/94850043

awesome!
Emails showing Google’s closeness with the NSA Director
The guilty often fall back to the thinking of, "If I can't have it, then nobody can."
Correct me if I am wrong, but maybe one way to look at the CFAA or situations like this one is that every website has the right to deny access to any particular user.

This can be done via firewall ruleset but also via cease and desist letter.

That seems reasonable.

But... for this type of approach to make sense with respect to a website that wants as much traffic as posssible, we have to make certain assumptions.

One assumption is that few if any users will automate their usage.

If hundreds of people began to write their own "apps" to automate how they use this website, then the lawyers would have a more serious problem that they might not be able to solve.

The website operators might have to reconsider their access model.

Could they move to a subscription-only service?

Could they use a whitelist of IP address blocks?

Could they still be competitive if they began to move away from open access?

In my opinion, the practicality of the cease and desist letter approach to website access (anyone can access except if we tell you to stop) is reliant on expected patterns of usage.

When kids learn how to program in school, should that day ever come, then they will learn how to automate. They wil be able to write their own "apps".

Will cease and desist letters and the judicial system be fully automated at that point? (The evolution of the DMCA comes to mind.)

The RIAA and others have tried to sue large groups of users all at once and it did not achieve anything except bad PR. Could website operators bring proceedings against large numbers of users and succeed?
You've absolutely been able to roll back with MSDeploy since it was released - http://forums.iis.net/post/1970816.aspx
Interestingly, there is an error in your code: number of seconds in a year is not constant, so you might get next year before a new year.
Here's a fixed version: http://jsfiddle.net/r8txd/4/show/
Very cool. It was a bit too slow on letter recognition which made it frustrating. Also it heard me wrong from time to time.
Unfinished Ideas
Functional Reactive Animation
Open source Node.js / JXcore messaging backend sends 600k messages/sec
I feel your pain. I'm a backend guy who has to learn front end all of the sudden. To my mind, React just makes sense. I understand that other modern frameworks like Angular and Ember "make sense" as well, in that they're current best implementations of well-understood best practice, but from my outsider perspective, it looks as complicated and baroque as Catholic theology. Yes, it's all very beautiful and such, but I don't know if I'll ever be able to instinctively grok it.

React? I grok that.
Note that sum(d) will generate a huge number, possibly using lots of memory and processing power. A better option would be:

def main(filename):
d = open(filename, 'rb').read()
result = reduce(lambda i, j: (i + j) % 256, d)
print("The answer is: ", result)

Note how this is similar to the squaring algorithm used in cryptography: http://en.wikipedia.org/wiki/Exponentiation_by_squaring
Not smart enough to get around region restrictions though apparently...

http://www.gmodules.com/ig/proxy?url=http://www.livestation....
More Insured, but the Choices Are Narrowing
Yes. Numerous reputable entities have published reports demonstrating that users notice quite a lot. Amazon claims that every 100ms costs them 1% of revenue. Google claims 500ms costs them 20% of traffic. 5 seconds is a fucking eternity, and anything you expose to users on the web with such horrible performance will suffer greatly because of if. One exception may be banks. Users are more forgiving of latency as their financial connection to it increases.
We are experimenting with a new feature on cdnjs.com where our users can submit the projects -> cdnjs.com/news
Delivering More Choices for Fans
This reminds me of Penis Landscape [1], a painting of his that was used by the Dead Kennedys in the album Frankenchrist [2]. Jello Biafra was trialed for distributing harmful material to minors, but was not convicted. He even went to Oprah [3] to talk about it and confront Tipper Gore about censorship and the PMRC.

[1] http://en.wikipedia.org/wiki/Penis_Landscape (NSFW)

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

[3] https://www.youtube.com/watch?v=ZpUeo6wR7M4&list=PL0BD020825...
I think it depends on whether it needs to be maintained over a period of time or if multiple people need to work on the codebase. If it's just being written for one paper then sure, just get it done as quickly as possible.

However, there's no reason not to follow some best practices. Using a VCS has pretty much no cost other than some initial learning curve, and the productivity benefits can be substantial. So - I think there's a balancing act in terms of optimal speed between writing good code and writing code as fast as possible.
I actually just created a baby name tracking/recommendation app for myself, and released it for free to see anyone else was interested. You can find it at www.BabyNameFaceoff.com.

The recommendation engine is David Celis' `recommendable`.
Bitpay Raises $30 Million in Series A Funding Round
I had to look it up. From wikipedia:

A proportional-integral-derivative controller (PID controller) is a control loop feedback mechanism (controller) widely used in industrial control systems [...] A PID controller calculates an "error" value as the difference between a measured process variable and a desired setpoint. The controller attempts to minimize the error in outputs by adjusting the process control inputs.
Really now a days these are really fast
Tips for Clojure Beginners
This comment from another HN poster does a good job of describing the difference between components in React and "components" in Ember and Backbone:

https://news.ycombinator.com/item?id=7738511

Long story short, React has a much more graceful system of making the components generalized instead of the adhoc system that Ember and Backbone use.

Ember and Backbone have features that are similar to components, but components from two different sources will rarely work well, because often one component will break another. Anyone who has tried to put a bunch of different Backbone views from different people together has probably experienced this pain first hand.

React is designed from the ground up to allow components to work well together.
Angular solves more than the UI problem,React on its own doesnt solve the architecturing problem , AngularJS does.

The big weakness of Angular is server side rendering,which involves heavy solutions like phantomjs,while you can render react components on the server.

Angular is not very good at rendering/managing svg either,that's a fact.

I would argue maintaining pure html templates is not that hard.

But frankly Angular solves so many problems these are minor issues.Writing complex lob applications is so easy with Angular I wouldnt want to use anything else.

The only case i'd switch back to backbone+react/vue/ractive and jquery is when i'm writing interactive experiences that are not CRUD apps.

So no,dont switch to React for the sake of switching especially since AngularJS just works. I mean people dont even bother learning javascript,they learn AngularJS ...