skysight-inc/HackerNews huggingface dataset:
GMOs, nuclear power, space travel, health care... all things that you can create testable hypothesis for. Climate "Science" can create computer models, not real tests and they're always wrong (none predicted the last 15 year hiatus in temp). It is always the same person collecting and analyzing the data. Nobody releases the code to their models. There are millions of variables in the climate, and we can't isolate and test a single one because of the scale of the earth, let alone all of them like we can with nuclear reactions. And yet, we're going to halt economic development that benefits real people, right now? If you asked the average New Yorker in 1900 what they'd worry about if there were 20 million people living in New York City, they'd ask you how the city could possibly dispose of all the horse shit from 15 million horses. We can leverage fossil fuels to lift billions of people out of poverty or we can worry about all of the horse shit on the streets.
The sandbox is a false or perhaps in your case imaginary sense of security.

Malicious packages are still possible

Its still unsafe to run software from anyone you don't trust

Worrying about getting root is beside the point when almost everything valuable on your system is whats available to your user

A app store situation where alternate repos or ppa need not exist because everyone can just add packages to some huge store is a horrible horrible idea.
> You can never build enough housing in a high-demand city without destroying the city; the demand is too elastic, the incentives between neighborhoods/culture and developers too misaligned.

Come on. Say what you mean. You don't want things to change, because then things would be different and you'd have to have Those People in your wonderful inclusive life.

And that would be bad. So down with inclusiveness!
sooo tax dollars go into the pockets of the land owners....and that extra money bids the price of land up more....and the land owners have a further incentive to vote against any zoning changes.
Thank you for the information and the fast reaction.

However, I'm also worried about the state of the quality of comments on HN.

You see puns and non-serious comments on many places.

Downvotes are misused to block controversial but serious, respectful and constructive discussions.

HN feels too much like reddit.
> here's a hint; a 150-year old facade isn't historic

Eh, anything older than 1906 in SF is historic.
Reminds me of Logan's Run....
I haven't noticed this, strangely most who have commented have, but I and my colleagues feel the opposite. At the company I'm at now, everything is angular. Mobile, main site, ancillary sites, and administration dashboard. In this case Angular is a HUGE productivity booster as we are sharing modules between multiple projects. This is great for a number of reasons, but I think whats always undervalued is it makes code reviews much easier, allows better use of CDNs and is more secure (less custom code = less attack vectors).

At a previous job in a major corporation we wouldn't use it in production, but given the chance others would always use angular for internal tools/portals/mockups etc. I think mostly because it was the fastest way to make something, with Visual Studios support of Angular syntax, and similar MVC style to what the team was used to. There is also something to be said about being able to reason about your code long after you wrote it. I think Angular is by far much easier to read than any other structure I've seen so far (yes even React). Also until Reacts testing libraries can catch up Angular is still the winner here - not the best but not the worst.

On reflection, I think Angular really shines in Enterprise software, with large teams. I agree it might be wasted time on one-off projects with 1 or 2 people. I've even been in a board meeting where the big emphasis was it's auto sanitization in application with lots of user input/display would save the company hours of baby sitting jr dev's. So you can see why verbose/defensive-programming can mean a lot on big teams.
I know Michael from other parts of the Internet. He tends to write essays and blogs on all sorts of things.

He is very picky about what company he will work for, for example he doesn't like Amazon's labor rules so he refuses to work for Amazon or any company with labor rules just like them. He doesn't want to work with Windows, instead he focuses on Linux and Mac OSX. He has Java skills, and lists them on his resume, but he doesn't want to do a Java job.

His resume was once four pages and he had to learn to trim it down to one page. He sometimes lists obsolete technology on his resume as well.

He wants to write drivers and system level programs in C/C++ and he favors Codewarrior 8.

He has a point about the ADA protecting the mentally ill from discrimination, but there is a stigma about the mentally ill by managers that they can't trust them enough to hire them for a job. They see people in wheelchairs, blind, and deaf as disabled, but mental illness cannot be seen and thus not considered a real disability.

I share schizoaffective disorder with Mike, it can cause communication problems and having trouble getting social clues. Just by typing or talking a person can pick up on that you are mentally ill. We communicate in word salads sometimes when we get into a bad mental cycle. Where the words are all mixed up like a salad.
Hmm, maybe I'll do a poll over the w/e - my impression was that a majority of people on HN take anthropogenic climate change seriously as an issue.

I agree with the rest of your post about an excess focus short-term interests hurting our long term strategic position.
I remember par2 from usenet, seems like similar/same concept http://www.quickpar.org.uk/ and something i've been wondering about for a while for storage; glad to see it being implemented at such a scale! makes good sense. Though I would be curious how corruption/rebuild plays out over time.

Also impressive how they shaved off all that extra power requirements and built-in expected unreliability. And really, utility is pretty darn reliable anyway, mixed with non-customer facing storage. Good move.
> But I'm often told that, if my apartment was in New York, he'd be taking a loss even at $2000 a month. Why is that

One explanation is the huge upfront investment. The median apartment goes for $900k in NYC these days [1]. According to google's mortgage calculator[2], a 30 year mortgage for $900k will mean a monthly payment of $4.2k.

That means somebody buying an apartment on mortgage will have to rent it for $4.2k a month just to break even.

Then there's also opportunity cost. If there are people willing to pay X for something, you are technically losing a lot of money by selling/renting for less than X.

[1] http://www.nytimes.com/2015/01/18/realestate/what-750000-buy...

[2] https://www.google.com/webhp?sourceid=chrome-instant&ion=1&e...
it amazes me that everyone still uses ubuntu. It's not the 'stable' operating system that everyone thinks it is. I mean, it is stable, but not more than the dozens of other distributions that have far more up to date repositories with more packages, and are more lightweight.

I'm far from a distrohopper. I don't think they're all so different. But when considering the minute differences between linux distributions, I find that ubuntu generally has more disadvantages.
Of course! They MUST be up to code, or the whole thing will crash!
There are developers that have 4-5 years of node. Most senior nodejs developers have previous experience working with different language(s)
Yeah, soups are awesome! :) My partner is studying 20+ hours a week on top of a normal job at the moment, so I've been tasked with doing all the cooking - soups certainly make up a decent percentage of the meals! Good time:quantity ratio, and hearty.

For anyone asking about recipes: this book is good : http://www.amazon.com/Soups-Over-Best-Recipes-Hamlyn-ebook/d...
> Many people prefer bleeding edge. For me, I prefer Debian's definition of stable

Having maintained Debian, Fedora, and ArchLinux machines over the past few years, I've found ArchLinux has vastly improved in terms of stability recently while still maintaining close to bleeding edge releases. I don't see it get enough credit for this. This must be the result of having a high quality team of package maintainers who know how to push out new packages properly.

Fedora on the other hand also promises bleeding edge - but for years I found it broke far too often, and yum is certainly not helpful in those situations.

As a result I no longer see it as a "bleeding edge vs stable" dichotomy. You can have your cake and eat it too if you a) choose your software stack wisely and b) use a distro with a smart team behind it. Switching to the Debian boxes always feels like stepping back 2yrs in a time machine, which has a high cost for a person who likes to keep up with progress in software development.
Free point releases like OSX?
Google's a lot bigger than you imagine.
An MIT student who filmed his own brain surgery
I've used distributions w/ systemd on a number of virtual machines, but those have mostly been non-critical machines.

I was slowly moving back to FreeBSD from Ubuntu/Debian. Systemd has moved that timing forward. Boot up time and monolithic systems don't do it for me -- managable sure -- but not my cup of tea.
Yeah, it's pretty unbelievable. Is the idea here that they're keeping these storages as general-purpose as possible to serve many different use cases and survive the test of time and change?

Or do they specialize these data centers for ONE specific feature? I wouldn't want to be in the shoes of the people designing the full integration of the system in the latter scenario, imagine your use-case changes... that's a whole new level of refactoring, especially once you go into special-purpose hardware.
When will SSD drives catch up in storage capacity and price to traditional spinning platters?

Never. Someone did calculate that if you can get flash that lasts 15 years it would be cheaper than disk, though (because the disk has to be replaced). I can't find the links on those.

Also what about the life cycle of drives that get powered on and off repeatedly?

We wrote a paper on that topic where we treated start-stop cycles as a resource to be rationed with a token bucket filter: http://storage-conference.org/2011/Papers/Research/10.Felter...
And yet, we're going to halt economic development that benefits real people, right now?

I've heard a few people argue that growth is the problem, but they're fringe economic thinkers. Most green types I know want to see dirty ofssil fuels displaced by a cleaner more effective solution that will support continued growth, The more serious ones see nuclear as part of the toolset for that.

Your argument about the deficiencies of models involves a number of unsupportable assumptions, particularly the assertion that because the climate is so big and complex that it's impossible to validate any part of our model. On the contrary, we're able to do very rigorous measurements in multiple dimensions on things like glaciers and polar ice density. I don't think you'd take me seriously if you said cosmology was a fundamentally doomed enterprise because the universe is so big. If we are willing to invest in space science to further the aim of travel and seeking life on other planets in the solar system (which aims the science committee does favor), then it's not unreasonable to think we can do at least a good a job of studying our own planet as exploring travel to others (an aim I also support).
That's because cat is unixy. You can concatenate any file to any file with it. That doesn't mean those files are unixy, it means the program is unixy.
I've watched many applications hold up adding new features that require newer dependencies that don't exist in debian stable and RHEL. So I'm in favor of some sort of solution that keeps the base nice and stable, but still allows new apps to to coexist with it.
Thats part of my other questions. How small is the current GaN technology? How much can it build on silicon technology?
I don't know much about go, but taking a quick look at implementations - they seem to be written by a programming novice, and the are quite primitive. Don't mean to be negative, just my opinion.
Did you see the parent poster's question?

I'm curious too, why you do the linking on your site, when you seem to be looking for work, and you suspect it's preventing you from getting it?
Krebs: A day in the life of a stolen health care record
Ask HN: How to build quality software in a fast paced startup enviorment?
I work at an Indian startup which has crossed the valley of death and is here to stay. Now we have to maintain our software quality while still delivering software at a high pace to achieve our targets. What are some tips to achieve this?
I must say that yours is much more complete than mine, though.
Why Windows 10 is the 'last' version of Windows
I think Angular is actually great for productivity, with the limiting factor being performance. Certainly, the initial learning curve can be painful, but after that I believe productivity is one of its strong points.

I’m trying to think about what part you think is 10x more lines of code than it should be and my best guess is directives. While directives can initially seem painful, if done right, they are perhaps the best part of Angular (along with 2 way data binding - ignoring the performance liability).

Certainly anything can be overdone or done poorly, so those may be factors. However, directives help turn HTML into your own enhanceable DSL with logic encapsulated in a new element.

Downsides of directives are one, the logic can flow from code to markup to code, which initially can be confusing and two, the setup required to create one. Perhaps I’m an Angular heretic, but I think avoiding excessive directives with a little jQuery in the controller isn’t always bad, especially when the code is still taking shape.

Other than directives, I’m not sure what part would be the 10x increase. Services don’t seem much different from utilities. Controllers or views? Our team must be somewhere around 1 million lines of Angular code and I think things are holding up well with productivity fairly strong. The primary issue I’d say we are seeing is regarding watchers and performance. It’s easy to let the number of watchers get out of control, but it's not that bad and only in areas where users can create 100s of custom widgets.
I think that's one of the important roles of a team leader - to know who is getting how much done (among many others). I wonder how Zappos will accomplish this now that they have no team leaders.
Currently, chess and ham radio. They are both low cost (or can be...you can go crazy in either), have plenty to do both solo and with other people, and can be enjoyed as a beginner yet have plenty of depth to occupy you for a lifetime.

Ham radio can be combined with other activities. There is a thing called SOTA (Summit On The Air), for instance, that combines hiking and mountain climbing with radio. You earn points by reaching peaks listed in their database and setting up a portable radio and making contact.

There are quite a few ham radio hobbyists on HN. Many checked in on this discussion: https://news.ycombinator.com/item?id=9445123

Any who were left out, reply and check in here.
> it sounds like they started out with a open house for everyone who applied, regardless of qualifications, instead of phone screens.<
I'm the CEO in the story. Oversimplifying a bit, we didn't invite everyone who responded to our ad to come to the open house, but put the responses into three buckets: those who get an invitation immediately (the "positive" email), those who get a second chance to say something interesting (the "negative" email), and those who were basically ignored because their background matched those who didn't do well in the past. As we have iterated and refined the approach, we emphasized the value of speaking to us in the first communication and dropped the negative email.

I understand your point about the phone screen, but found that this is a trade-off. The phone screen was very ineffective for us in letting people know who we are, our size, our location, what we do on a daily basis. The open house format lets the prospective employees see us as we are, where we are. Inevitably, people drop out of the process, and it's fine with us, as it opens up slots for those who like what they see. In an open house format, the candidates ask questions as a group, which means that any particular person benefits from the questions that others ask. They see our existing staff and can decide if this is a group they want to work with.

We are upfront with the candidates that we can't hire all of them, and therefore it seems like a fair exchange to do something for the "unchosen" as a bonus for coming in. Brooke and Noah have helped by providing guidance for them, and we have all tried to create a community of the unchosen.

The core concept being promoted here is that the current recruitment system is broken, and it is the fault of all of us who unquestioningly perpetuate it. My response is to experiment with different ideas until we find a model that works for all parties involved. I don't have a magic wand to provide the solution, but do keep notes on what hypothesis is being tested, what seems to work, what doesn't work and what possible improvements we should try.
Author here, happy to answer any questions or discuss further!
Only Half of Online Video Ads Are Viewable, Google Says
>> I find that ubuntu generally has more disadvantages.

Examples please?
Rust figures out what parts of the environment you are using and makes a closure or lambda. The compiler figures it out for you. This is basically the Rust philosophy.
FYI:
It's like Yelp, for Github repos:)
You can't get housing built in SF, Palo Alto or Atherton for the exact same reason. Using one as a reason to oppose housing in the other is a red herring.
We're still a few years off from worrying about schools, but it is the sort of thing that makes us toy with the idea of some variety of home-schooling. I'm sure there other nuisances around, but I'm a desert rat and I think this place is absolutely beautiful (although my opinion of the desert usually dips a little in July and August).
Doug McIlroy (the inventor of Unix pipes) included this in his description of "the Unix philosophy":

> Write programs to handle text streams, because that is a universal interface.

ESR expanded on this in the "Unix Philosophy" chapter of The Art of Unix Programming:

> Unix tradition strongly encourages writing programs that read and write simple, textual, stream-oriented, device-independent formats.

> Before devising a tricky binary format to pass data around, it's worth experimenting to see if you can make a simple textual format work and accept a little parsing overhead in return for being able to hack the data stream with general-purpose tools.

(And no, journalctl and systemd-cat don't fully replace the ability to run text-processing programs like grep, head, tail, etc. directly on the stored data.)
Those places all look to have been built way before the automobile was a thing. And while I agree with narrow streets, because they're safer and more aesthetically pleasing etc, you can't ignore that transforming to that design will be a little disruptive in the near term.

My point is that some of the great and beautiful narrow cobble stone streets in, say, Boston or Philly, to use US examples, weren't built to handle heavy street traffic. Transforming high volume automobile streets to the walkable ideal is inevitably going to cause some headaches.
Astoria is probably next up on neighborhoods to explode in rent. Hell, LIC of all places is starting to look like parts of Williamsburg.
Non-paywall version, direct from NASA: [1]

[http://ntrs.nasa.gov/archive/nasa/casi.ntrs.nasa.gov/2014001...]

It's a neat idea. It's really a pulsed fission reactor, pumped by a fusion stage that's below breakeven but produces a lot of neutrons that can ignite fission. It runs on U-238, depleted uranium, which won't fission by itself but can be pumped into fissioning. This is somewhat similar to the process that occurs in H-bombs, so it's well known nuclear physics.

Depleted uranium is about as hazardous as lead. Breathing or eating it is bad for you, but the risk is heavy-metal poisoning, not radiation. It's very heavy, so in water it will sink to the ocean floor. Launching over the ocean is indicated.

This looks promising.
GaN provides a couple of benefits compared to Silicon:

1. It offers a lower on-resistance for the same breakdown voltage as a silicon device [1].

2. It offers a lower gate charge which allows you to turn it on and off at a much higher frequency than Silicon devices [2]

(1) means you have lower losses in a power circuit with GaN vs Si (leading to more compact - smaller heat sinks - power supplies for example)

(2) means power supplies can run at much higher frequencies. At higher frequencies, you can use smaller inductors and capacitors which means more compact circuits.

A practical example of GaN in action is FinSix' Dart power supply [3]

[1] Slide 5 of http://www.irf.com/product-info/ganpowir/gangeneral.pdf
[2] http://m.eet.com/media/1179793/si-vs-gan-vs-sic-which-proces...
[3] http://finsix.com/dart/
On Mathematical Intelligence and How It Grows
Mistakenly linked with #comments. Although not sure why it should not be working for you. Cann't seem to edit the url. As there is no discussion in the thread will delete and re-submit. Apologies for any inconvenience.
Cydia has repositories just like Debian, but there are multiple independently operated ones in a default install; they accept proprietary software .debs, and don't take as active a role in shaping the system into a coherent whole as a standard Linux distro (to avoid clashes, packages get reverse-DNS style names), but they do cooperate with each other and with saurik (the developer of Cydia) - I'm sure other people could tell you more about what that looks like. They manually review package submissions before adding them, but they don't have the resources to subject every one to an Apple-like testing procedure. Adding custom repositories is exposed in Cydia's UI and is common. (Among many legitimate uses, this is also commonly used to add repos which host pirated copies of paid Cydia packages and App Store apps. Oh well.)

Cydia has some additional functionality compared to stock APT:

- Purchases - are basically handled as a separate layer; they're the only part of Cydia which is centralized, and are done through a web UI hosted by saurik. IIRC, once the package is purchased, Cydia's version of APT sends a device identifier header when requesting .debs, and repositories have to check with saurik's server to decide whether to return 403 or not. By itself this is pretty easy to crack, so many popular packages add their own DRM (yuck).

- In addition to the short textual descriptions, package metadata can contain a "depiction" header containing a URL which Cydia will display in a web view when the user navigates to the package. This is intended to (a) allow each repo to design their own UI and maintain independence, (b) provide richer package info more flexibly than a fixed description UI would allow, e.g. including videos, and (c) allow repos to display ads, which they need to survive as payments aren't handled through them.

(I originally had a somewhat long paragraph here on how utterly horrid a UX this is in practice, but it's not really on topic, so I'll leave it at that.)
PostgreSQL is coming up a lot and making waves, never thought much about it until recently it turns out to be more reliable than mongodb. Interesting phenomena.