skysight-inc/HackerNews huggingface dataset:
Intuit owns Mint. Not sure how the banks are going to know the difference between Mint users and Express Web Connect users. Maybe they shut them all down?
This post is a load of shit, serious shit.

Claim 1:
> Promotes excessive executive compensation

You can not claim executive compensation in a SRED claim. If you do it is fraud.

It is an excluded expense see here:

http://www.cra-arc.gc.ca/txcrdt/sred-rsde/clmng/ttlqlfdsrdxp...

Claim 2:
> We’re paying foreign entities to take IP and profits out of Canada. Not a very good use of taxpayer dollars, is it?

Actually that is illegal, see this:

http://www.cra-arc.gc.ca/txcrdt/sred-rsde/clmng/ttlqlfdsrdxp...

Claim 3:
> Removes emphasis on sustainable growth

It isn't meant to be sustainable, it is mean to fund the initial R&D in something that is risky. As you grow, and you slow down R&D, yes it gets smaller -- by design.

This is a really weird post and seems to be spreading FUD.

SRED is not a perfect program, but the main faults outlined in this article are complete wrong.
PageFair hack effecting Economist.com
Mr. Bozart testified briefly at the Abel trial, but the nickel, while a mesmerizing prop, was not essential to proving the case.
I'm hypothesizing that dark matter can interact with itself, just as our matter can interact with itself.
Feature creep, over optimistic estimates, business needs changing, and misunderstanding the requirements would be at the top of my list.
Three Recent Tech Talks from the Zürich Gophers Meetup: Go from A-Z
CIA chief's confidential information published on the Internet
A workflow I think would be extremely useful would be to take serialized data, live program some sort of data transformation, then visualize the result (and maybe the initial data too)

Then for anything that is an arbitrary data transformation it could be done live and in isolation.
Right, but I think using paper instead of plastic wrappers is more environmentally friendly. Plastic is made from byproducts of oil refining. Its really nasty stuff that doesnt biodegrade as easy as paper. Paper is renewable and it also helps the environment by taking out CO2 (trees).

Fun fact, Ted's Montana Grill actually uses paper straws as a conservation effort IIRC. They can get soggy but it is something unique I haven't seen before.

Also wrapping straws in something is a health code issue. Some places even in the US do no require it to be done.
Hasn't this already been done? It's called a web app using html, css and javascript
Actual REST may well not be the right solution for quite a lot of the problems people have with APIs, so its good that people should not always feel obligated to use REST.

OTOH, actual REST may well be the solution for other problems, and its a lot easier to talk about solutions if we use "REST" to refer to Representational State Transfer as defined by Fielding and let all things that aren't that get names that reflect what they are, whether its JSON-RPC-over-HTTP or something else.

Its a lot harder to talk about the merits of different approaches if a wide swath of unrelated approaches that are not similar except in not being SOAP+WSDL (or, possibly, in that plus also not being Fielding's Representational State Transfer) all get lumped together as "REST".
> ... for the technological progresses ...

You've answered it yourself :-) It's not a technical problem, it's a social issue.
I don't think there's ever been a social network that has successfully charged users to use it.
[Windows phone users laughing/crying in the distance]
> Ansible/Chef/Puppet is a package manager oriented at deployment at multiple nodes, which works with multiple GNU/Linux distros.

These aren't really package managers, but configuration management, orchestration and desire state configuration tools. You can use them to execute package manager tasks (yum, apt-get for example) across one or more servers at the same time.

Learning one of these tools is worthwhile. For example if I want to deploy a bunch of files to a specific locations across a farm of 100 servers then these are the tools for job. I'm learning ansible right now. The reason I chose it was because it's fairly lightweight and has a low barrier of entry compared to Chef or Puppet (for me anyway). The documentation is also very good. The sysadmincast chap recently knocked out four (free) videos introducing Vagrant and Ansible, they're quite good:

https://sysadmincasts.com/episodes/43-19-minutes-with-ansibl...

https://sysadmincasts.com/episodes/45-learning-ansible-with-...

https://sysadmincasts.com/episodes/46-configuration-manageme...

https://sysadmincasts.com/episodes/47-zero-downtime-deployme...

> Vagrant is a package manager. A wrapper around Ansible/Chef/Puppet.

No, Vagrant is a tool for standing up virtual machines with repeatable builds. It's mostly used as a development tool so you can quickly build an environment on your desktop (e.g. VM's running on VirtualBox). You'd then, for example, pass the Vagrant script for your build around your team so that you're all developing against the same environment. It's also handy for rebuilding exactly the same VM again where you've maybe trashed it by accident.

The videos linked to above will give you a sense of where and when to use Vagrant and Ansible.
I like that it's near field, drawn with particles that zoom through the player space. They aren't "far" away, yet have a nice feel.

The end result is a really great sense of motion.
Thanks for the example of California. I expect there may be more. However, the main thing I wanted to point out in my post was OP's confusion, shared by many, regarding what entities are prohibited from infringing on constitutional rights. Only government (or in some cases quasi-government) entities are prohibited from infringing constitutional rights. Private entities can in most cases do whatever they want, unless a statutory law (i.e., a non-constitutional law) has been enacted prohibiting their action.

Also, I don't know much about the CA law you quote, though I wonder whether it prohibits political discrimination in the _hiring_ of employees at all. Section 1102 definitely prohibits firing based on political activity. I don't see anything that says you can't discriminate on a political basis in _hiring_. Perhaps that is in a different section. I tend to think, e.g., that the Democratic Party organization would not be forced to consider hiring Republicans equally with Democrats, not sure how that's dealt with.
Thanks, I had forgotten that I had ever played that game. As soon as I saw the hyperspace navigation reticule I instantly flashed back to memories of fighting to keep it centered.
Not quite, polymorphism is a bit iffy in Go (there is interface, and it's doable but not great). Type inference is extremely limited (this is also due to a weak type system, with comparison point being ML-family languages for examples) . Global type inference is off the picture without generic/ polymorphic typing.

I don't think Go achieves the look and feel of working with Python and the like.
On a consumer OS if a feature is not enabled by default it might as well not exist at all. The vast majority of people won't discover it.

This is fine for OpenBSD, you are assumed to know what you are doing when you install it. But Windows gets installed for all sorts of people, many of whom will tell you to your face that they are "not computer people", and will be very annoyed when the OS doesn't magically do what they want.
Yes, one of the design goals was to blur the gap between dynamically and statically typed languages by creating a language that is safe to run and fast to compile, read and write.
> aren't there standardized ways to analyze circuits?

There are basic quantities (current, voltage, time), and every component has an associated formula that model how they behave. But software is similar in that every instruction (eg opcode, function, or program statement) has equivalent well-defined behavior.

> electrical engineers ... often go right to work professionally

Sure, but they still start off slowly and work under someone more senior. They certainly don't come out of school with an understanding of what circuit topologies are practically used or a great intuition of which factors actually decide designs.

> Whereas APIs and packages ... change constantly

Only if you constantly change them out! Chips have revisions too. All of these differences strike me as being about scale of complexity, rather than full on new phenomenon. And it's true, for electrical engineering complexity is bounded by cost, even though there can still be a lot of complexity in a cheap chip (but the manufacturer is incentivized to get this exactly right, too). Whereas with software we're often burning GHz chips to perform the same function that 5MHz micros handled just fine.

So I think the root of the disagreement is whether you approach it "from the top" or "from the bottom". My above argument is coming from the bottom - EE battles a lot of similar facets as software, just a lot less complex.

If you take software engineering as being fundamentally about managing complexity (and therefore imply that it couldn't really get started until we had horsepower to waste), then I'd call that viewpoint "from the top" in a sense. Which is probably more appropriate, especially as complexity grows and grows.

But that doesn't mean that the "bottom" "fundamentalist" viewpoint is useless, either. It's not that engineering principles are inapplicable to software, but that they are ignored as a result of the environment the discipline finds itself in. One way to change that environment to encourage more rigor is to change the culture of the field, which IMHO can be helped by calling it "Engineering" and pushing it more towards so, rather than modeling the culture around eg flaky webcrapps.
This describes pretty much every type of project ever. Not saying everything lags 100% of the time but most significant projects miss initial schedules. Software has some unique characteristics to be sure, but it's not atypical. (And things like large construction projects tend to be even worse.)
Suicide Girls? NSFW ("Come for the boobs, stay for the community").
I once had a mentor who was fond of saying "Git doesn't solve human problems", in reference to git-conflicts while explaining the system to less technical team members.

Technological advancements have, to this point, had fairly limited effect on mitigating error in human input.
My assumption was that writing the handful of sCU I think you'd need is simpler than handling coordination. You seem to have a reasonable understanding of the tradeoffs.

> At that point, it seems you're not necessarily any better off than you would be with a more traditional, event-driven architectural style

Not having to implement the dom state updates and rAF update batching are fairly big wins. The only other way I know of doing this is via data binding and the difference there is that individual updates are more efficient but establishing the bindings is usually O(n_size_of_input) and in practice every app I've worked on that did data binding eventually broke the approach. Having the shouldComponentUpdate escape hatch has allowed me to push much larger volumes of data through the system without it breaking.

I've implemented a number of reasonably complex apps but the two largest have been on immutable datastructures where React's assumptions always hold unless you screw something up. The largest non-immutable app I've written was a 25k LoC layout builder where the two shouldComponentUpdates for vdom pruning were pretty straightforward.

Good luck with your app.
Nice writing, and my 'knowledge' about the state of affairs is way less (near zero), but for me, you do not refute that it is a ghost town now. At the speed that China builds 2009-2010 is ages ago. They may have filled the space between those islands of activity with still empty buildings.
I like this chart better for sous-vide eggs:

http://www.cookingissues.com/wp-content/uploads/2010/02/eggc...

It's accurate and has served me well. The only downside of making eggs sous-vide is that it takes forever. If I sleep in on a Sunday morning, set up the water bath, then wait 45 minutes for egg equilbrium, it's almost lunch time...
Bogarting unadvertised IPv4 space is common. A lot of people don't understand that it's not just public IP space that is in short supply in IPv4. IPv4 also has inadequate space to number large private networks in a non-conflicting manner. Causes all kinds of crazy headaches with VPNs and distributed networks too... try linking two sites that both use 10.0.0.0/16 sometime. It's hell.
ProtonMail Statement about the DDOS Attack
Day Before Bombing, U.S. Asked If Any Taliban Were “Holed Up” at MSF Hospital
Default to Empathy
Mastering C#
You might check out Starting and Sustaining: http://startingandsustaining.com/
Go doesn't have type inference "even at module or function boundaries"; this aims to.
Probably little directly but it will help US companies remain cost competitive in the global marketplace (and remain profitable) which does mean that a lot of the high level jobs (marketing, supply chain, design, etc) are still in the states.
Application creation (programming, design) are creative processes. If you want a brick wall, you sum up the materials, job size, and labor. Not so with software.
It's not about the liberal arts degrees, it's about the liberal education. I have a CS degree. I also have a liberal education. I was exposed to a wide range of people, viewpoints, and concepts in the process. It has been more valuable to me than most of my actual CS education, and is as applicable as anything else in both daily life and in my job. And the self-styled "auto-didacts" who I know do not show the sort of breadth that my college education thrust upon me and for which I am better off.
I think you missed a piece of the article: "by a person of another Party".

So for example the Japanese government cannot force a US company to release source code as a condition to allow its use/import/sell in Japan. But the Japanese government can write/finance as much GPL software as it wants, and can import as much GPL software as it wants. The Japanese government can even mandate all software for its own procurements to be GPL-only.

What Japan cannot do is outlaw the sell or use of closed source foreign (by a person of another Party) software on its territory. So say if Ford wants to sell cars in Japan, the Japanese government cannot force them to release the source code for a mandatory code-audit as a condition for import...

I really don't think it's a good article.

(IANAL, of course)
https://en.wikipedia.org/wiki/Currency

https://en.wikipedia.org/wiki/Fiat_money
In my mind, any language that demands a package declaration and a main function doesn't qualify as a "scripting" language.
Part of the difference is that the EU is a very different kind of negotiating partner than the East Asian countries involved. While in TPP the concern was about US standards being diluted by the transfer of economic activity to other countries, in TTIP the concern goes the other way around. EU consumer protections regarding things like privacy and agricultural products are stricter (though the latter include some IMO ridiculous things like a blanket GMO been). It's also a bilateral treaty; there's none of the wrangling of dozens of different negotiating parties, there's just the US and EU trade negotiators.

Also, there's the practical reason - the Asian partners don't know the contents of TTIP because they're not parties to it. TTIP covers EU-US trade, and TPP covers Asia-US trade. I think these flows are larger than direct EU-Asia trade, but if not, it's up to the EU and the TPP partners to negotiate between themselves. Which is part of the untidiness of these trade deals happening outside of the WTO, but those global deals seem to be pretty dead; there are just too many parties involved with too many competing interests to come to a single deal that everyone's happy with.
One other thing to consider is that of trauma/PTSD. Things that we find exhilarating in more traditional media may in fact be too stressful/terrifying in VR. Horror experiences in particular seem to be proving this out, but I could see the same for the type of extreme violence that currently seems fun or exciting onscreen.
Respect the Other Players
NetCrunch 9 network monitoring system video overview
Anecdotally, I think I see a new post about this topic every week or two on HN. When it comes to software culture, this has to rank pretty highly in terms of how much discussion gets generated.
The clinical work they're doing is great, but the code is problematic. Its a bunch of Perl and Python duct taped together with shell scripts.
From the github repo:

Shell 84.3%
Perl 8.9%
Python 6.3%
C 0.5%

Check out the source
https://github.com/chiulab/surpi
If true, that makes it even stupider. If they're adding even more unnecessary bloat to the browser they should at least be compensated for it.
Because the end goal is maximising utility, not perfectly enforcing an imaginary version of property rights. Inequality should exist in as far as it is necessary to incentivise utility generating endeavours. Beyond that it's abhorrent.

You don't get to steal things because that's not an equitable way to redistribute wealth, but the government might tax the rich neighbour and use the money to provide free public transport.
The usual approach is to take a conventional house design, and then design a solar supply to meet its needs.

This results in a crazy large system due to our appalling wasteful house designs (which in turn are due to historically cheap electricity).

A better approach is to decide how much you can spend on solar, then design a house which will function within that limitation.

To succeeded you will need to change house designs, select different type and size of appliances, and most importantly, make some personal sacrifices.

If you can live within these limits, then yes, you will enjoy having Solar. If not, you would be better to continue with your existing expensive lifestyle.
The go philosophy is that inheritance "does not scale" and they deliberately went another route: https://golang.org/doc/faq#inheritance
That and being able to understand other people and more importantly, what they value, how they value it and why they value it the way they do.

People who can translate tech into basic human terms as well as business terms can demonstrate considerable value. And that value goes both ways. One might be selling the tech, and another might be taking the human value perception, linking that to basic needs and communicating back to the team what is worth what. Considering an expensive feature? Will it pay off? Opportunity costs on something like that run very high, as do the risks and rewards.
I'm interested in writing a fairly bare-bones, standalone application for note sequencing, patch selection, and controlling the master clock of external MIDI synths and drum machines. Is this a suitable framework, or is there something else that might be more appropriate? I feel like the current DAW offerings are A) too complex/big for my needs, and B) focus a lot on MIDI in and not very much on MIDI out. That said, I'm really new to this so I'd appreciate any suggestions on existing software I might have missed.

Edit: As far as existing software is concerned, I'm on Linux and I'm not interested in moving to Windows or OS X. I realize software for Linux in this domain is somewhat limited.
That's usually called constructive dismissal.
I think the counter argument is that the carriers must be automatically cutting back their use of the spectrum when they detect other devices, so if unlicensed devices were allowed on the carrier licensed bands, it would reduce spectrum available to the carriers.

Though it seems fair, if they want to eat into the public unlicensed spectrum, they ought to give the public access to their own spectrum.
You know... I'm not so sure I completely agree. I mean, yes, the analysis is the bottleneck. Since about 2012 it takes more time to perform the analysis than it does to generate the data. And even though all of the raw data -> BAM -> VCF or counts steps is automated, nothing after that is (or can be, since that's where the science happens).

But, the $1k genome really is significant. Costs matter.

Researchers will only sequence what they can afford. So, when sequencing a genome was $10k, there weren't too many 30X whole genomes sequenced. Instead we had exome sequencing of individuals or low-depth sequencing of populations.

Fast forward a few years, and now the costs have gone down significantly. Because of this, we are now starting to see more whole-genomes. Now, the costs of to sequence a whole-genome at 30X is about the same as targeted exome sequencing (due to the extra capture costs). If it's almost cheaper to just sequence the whole-genome and skip any extra capture probe biases, why not just sequence the whole thing? This is particularly true when looking at complex diseases where the underlying cause(s) may not be in the coding part of a gene.

So, in that regard, cost really was a bottleneck. With all of the new whole-genomes available, we can start to ask even tougher questions. And with more data available from more people, we can start to get some real confidence behind our predictions.

But, you are right in that it does all lead back to the data-analysis bottleneck. Before we had as more data than we could deal with. Now, we can process data faster, so that's good. But we also have significantly more data to process, so in the end, it's about even.

The other issue then becomes data storage. What do you do when you have a few hundred terabytes or a petabyte of sequencing data? S3 can get pretty expensive at that scale. Instead, it's probably just cheaper to store the DNA in a freezer, and if you ever need the data - just resequence it.

Edit: reworded a bit
Release of the Full TPP Text Confirms Threats to Users’ Rights
You can do a UPS pickup; they come to your door. You can leave the package in the mailroom at work for free. You can drop it off in a random UPS store by walking in, making eye contact with the clerk, then setting it down on the counter. It's a 3 minute process to rebox, particularly if you have a tape gun from the last time you moved (seriously, buy one of these!) http://www.amazon.com/Duck-Standard-Includes-54-Yard-669332/... (amazon link, natch :D)

or you can spend 40-60 minutes driving to best buy or some other store. Even if the drive is 10 minutes each way, that's how long it costs from the time I touch my car keys to the time I'm back in my house -- walk to the parking lot, drive, park, walk, counter, stand in line, reverse the process.
Psychology used to study the behaviour and cognition of undergrad students. Now it studies that of Mechanical Turk workers. Progress!
"Permanently deforming" and "flexible" are different things. The crumple zone of a car isn't flexible, but does deform.

But yes, this probably would either limit what you can do there or necessitate design changes (just like it would glass with some new properties)
Pocket (Read It Later, Inc.) has nothing to do with Telefonica.
Why We're Crowdsourcing the Law
Match Report – Rubin Kazan 0-1 Liverpool
How are people who are starting from zero on this supposed to understand it in 60 days? This disclosure only a little more than a transparency fig leaf.
Yes it has been done and to a greater extent than your dismissive comment. It still doesn't detract from the noteworthiness of the OP.