skysight-inc/HackerNews huggingface dataset:
Open contests would be meaningless without vast financial backing to launch those world-changing projects. And the contributing party would want some kind of financial reward.

Never going to happen, for a truly innovative idea, because the risks are too high.

The world needs a benevolent Bell Labs type of institution, with commercial intelligence, that channels profits back into its growth (like Amazon). It should employ tens of thousands of scientists - engaged in 'blue sky' research - and aim to solve problems that are currently considered 'too big'. The usual stuff, like climate change, clean energy production, and political reform (backed by hard political science).
Ask HN: What's the best online method to contact a company?
I mean for seek job
Social media icons by Kieran Hunter
that says it all: the most framework specific part of the article are the links in the end to other articles.

Its good to have feedback from the community, but I wish some of these posts would get down to the specifics, we would all benefit much more. Something like: "I tried to this (details) in Angular and it was difficult, tried to do it again with this other framework and it was much easier".
Wow, those are all terrible.

Although I guess the first guy's idea was ok (even if the design itself was terrible) as google actually do something similar now
A Grammar of Graphics (2007) [pdf]
I was talking about iOS. I've never heard anyone "shriek" about this issue in regards to OSX.
The post said it happened in real usage, and was then reproduced by this contrived example. Whatever the original use case was, may have still been reckless or absurd, but I think it's also worth noting that it was not originally found by intentionally throwing pathological usecases at the system.
I think this approach would still fail if the program is not behaving as expected by the user.

For instance, I didn't know until reading this article that 'less' on ubuntu went through lesspipe, but the people maintaining the tools know that. If for some legitimate use case lesspipe needed access to the internet, the local database could allow that behavior without any warning, but as a user I would still be dumbfounded that a 'less' command ends up generating network connections.
> expect people to hold you on that promise

What promise did github make?
I'd generally take a config file failing to update (this may happen anyways from the looks of it, e.g. if "/proc/sys/fs/inotify/max_queued_events" isn't available) over the box dying with a terrible crash report.

I'd much prefer to accept the patch with a followup request, tracking issue, or TODO. There wass good reason to not consider the issue resolved, but I'm not of the opinion there was good reason to reject the patch either.
If Angular is not The Thing (a premise which I have no trouble believing), then what is a Good Thing to perform the task of, for example, consuming Django Rest Framework endpoints and making a frontend of them?
Yeah, same silly things programmers do in real world statically compiled code. Bad choices for something like data type and bad compiler options. A JIT can figure out negative numbers can't happen and optimize accordingly. It might know about the CPU model that didn't even exist when the static code was compiled.
From what I've understood, the reason the low carb diet seems to work is it reduces the intensity of the hunger signal.

This is purely anecdotal and YMMV but I used to be ravenous by dinner time inspite of eating breakfast and a large lunch. Completely eliminating sugar from my diet helped a lot. Drinking green tea and other NON SUGARY liquids throughout the day also helps.
I used to do that with vimpager (a better implementation of this shell script). Unfortunately this cannot work as it doesn't process data as it arrives, you need to wait for input to end. So it's only good for fast & short commands.
I'm assuming the link was posted since the one at the bottom pretty closely resembles what we're at now, with Google Now available everywhere
Yeah, I do wonder how long those 21 bits will last. They clipped it down to ensure it'd remain UTF-16 compatible, but I worry if we might need to extend UTF-8 in future to support more codepoints, and add some horrible new set of surrogate pairs, encoding using surrogate pairs, to UTF-16.
Shellshock didn't have anything to do with C. gotofail looked like an SCM merging bug, which could have happened in any language. Security issues in the Rails world are often caused by libraries that do more than they should, just like less does (YAML comes to mind).

Yes, it would be nice to get rid of one class of errors. But proper sandboxing would get rid of them all.
Ask HN: How do you imagine the future?
In these fields:
Technology
Internet
Web
Computers
> If you want to view yourself as having no more agency than a cat or a separate person in order to deflect blame for your own choices, I can't stop you.

Agency is not separate from biology; Social pressure is also not agency.
Right, but JITs only have the runtime information after a slower warmup period, and even then recording and exploiting this information has a cost too. The real divide here is between client/server: fancy JIT techniques can benefit long-running apps on beefy servers, but won't help a Java app launch faster on a smartphone.
Maybe next time reading the full post before commenting:

> I should point out that this is not theoretical. I went through all of the above because some real machines hit this for some reason. I don't have access to them, so I had to work backwards from just the message logged by init. Then I worked forwards with a successful reproduction case to get to this point. I have no idea what the original machines are doing to make this fire, but it's probably something bizarre like spamming /etc with whatever kinds of behavior will generate those inotify events libnih asked to see.
Prodotti per l’ufficio: la Top Ten di quelli più artistici
the author actually has a series of "Angular Bad" articles on his blog which are more or less specific:

http://www.fse.guru/angular-bad-parts-part-1

http://www.fse.guru/angular-bad-parts-part-2

http://www.fse.guru/angular-bad-parts-part-3

http://www.fse.guru/angular-bad-parts-part-4

http://www.fse.guru/angular-bad-parts-part-5

http://www.fse.guru/angular-bad-parts-part-6
The GearVR only works because of the external sensors on the HMD and the low latency display driver among other things.

This doesn't seem to have any external sensors, no low level / latency access to display driver, and with an iPhone6 720p-ish display, I can't see how there will be enough resolution - the GearVR with its 2560x1440 display appears low res enough - if this worked, and I highly doubt it, we would be regressing to DK1 levels of quality at best. You wouldn't be able to read key labels on a virtual keyboard at that resolution.

The 60Hz refresh is fine. Latency >>> refresh. Even 30hz gfx update with 60hz timewarp actually feels "fairly" comfortable with gearvr if you can put up wth the slightly swimmy image - as long as you dont drop frames. 60hz with dropped frames is a far worse experience.

This is google cardboard in a pretty skin.
I often need to wash up after particularly messy system administration tasks. That sink will come in handy.

I'd be curious to know if systemd is tickled by this one weird trick to crash your server. It does work with inotify (and other fun newish kernel techs), so it would be subject to the inotify queue length...but what'll happen when it hits it?
Devs are going to use the hell out of Search Google for Errors Option. That's a game changer.
What's wrong? Why did you title this "Ruby programmer trying out Meteor.js" while the original article is simply "Meteor.js: Getting Started" ?

Also, the article does not mention Ruby even once!

Also you've just done that 3 days ago -> https://news.ycombinator.com/item?id=8641719. You posted this same article with this same wrong title. And I had already commented you on that.

Oh wait, wasn't it you? Right, my bad, it was another username posting that...

What a strange coincidence we have here, two different users both using a brand new HN account, who submit exactly the same article naming it exactly the same wrong way in a 3 days time span...

That's not good.
What are you trying to do?
(2001) RFC 1149 implementation – IP over avian carrier
> that says it all: the most framework specific part of the article are the links in the end to other articles.

Having to click a link to reach the information you need, isn't a big deal IMHO. It's the content that should be discussed. Personally, I don't see anything wrong with posting links to prior (or other) blog posts.
31C3 Ticket Shop Has Opened
It seems to be mostly the same, except that "Changeset" is now called "Commit" and "Current directory cache" is now called "index", but they are functionally the same.

It's actually really great to see that the model hasn't changed much (there must have been a long phase of thinking before though)

If you want to go deeper, you can check out this page:

http://www.git-scm.com/book/en/v2/Git-Internals-Git-Objects
Same opinion here. I think angular hit an inflection point on the js frameworks, proof is the rapid growth that angular had. Granted, there's some bad parts but I would say it's mostly leaky abstractions; I'm wondering how angular2 will be, but I surely don't understand why all the hate around angular.

It seems that the poster got bitten by some problems and blames it on angular. I recommend an exercise to current and future angular users: really try to understand HOW you would implement angular features such as two-way binding or modules or directives. If you do this you will understand that problems such as described by the poster in http://www.fse.guru/angular-bad-parts-part-3 are really due to his own misconception about what the framework should do and what it really does. I've been working with angular for two years and never had the problems that the poster reflects. I've had other problems but I would argue that for the most of it, I like the way angular is designed and like the compromises they took (mostly dirty checking to make two way binding work automagically).
Probably the same way people like Instagram got around the 100 device limit - multiple developer accounts

e.g. from 2011, http://online.wsj.com/articles/SB100014240529702034791045771...
That's a common misconception and it's quite easy to fall for. Please read http://www.moserware.com/2009/06/first-few-milliseconds-of-h...
Tesseric – the first true 4D arcade/puzzle game
My front-end guy is totally sold on react/flux.

He came to that decision just after we committed to angular... :(
I think that Apple is, on the whole, doing the right thing. But it's unfortunate that these three things (kind of) coincide:

* The Mac App Store's business model, i.e. no upgrade pricing, no trial versions; content-wise, nothing that you wouldn't sell in Disneyland

* Paying $99/yr for a developer account, even for free apps

* App sandboxing

And even then, this still doesn't mean that all apps on the App Store are safe. Because you used to be able to submit unsandboxed apps; as far as I know, they have never been removed? Sigh...

But at least many of the currently un-sandboxed apps are moving to the browser (MS Office & Skype being my biggest worries).
HTML and JavaScript?
Ask HN: Tried something different for the home page, any thoughts?
I wanted to do something different for my new startup, the home page is a strip down version of what is possible with the full (paid) version.

https://proceed.io

I would appreciate any thoughts or feedback regarding this decision. It’s a project proposal management SaaS. The home page immediately allows a potential customer to try the proposal editor.

My goal / thinking: I wanted to let new visitors quickly try the app and see how it would fit (or not) in their current workflow. Instead of having the typical screenshots / video, hook text and call to action button page layout.

Until the end of last week it was in a private beta and for the tiny number of visits, the invitation request rate was good (~ 9%). It’s hard to draw any conclusion, and I don’t have enough traffic to perform A/B testing atm. That’s why I’m trying to get as much opinions as possible.

Thanks for your time.
She doesn't know why it happened.

I would argue that it was almost certainly a pathological use case, as I suggested above. i.e. Something was already broken, and it triggered this crash; had it been left to its own devices, it probably would have triggered some other bad behavior eventually (disk full, OOM killer, etc., many possibilities). I don't know it, of course, since she doesn't have the details on what caused these inotify events on such a massive and rapid scale, but I'm having a hard time imagining why /etc/init would be receiving thousands of events, short of something already being broken badly.
There's absolutely no reason why there needs to be a warm-up period. You can cache the JITted binary code to disk. CPUs really don't care how the code was produced.

A sampling profiler can be pretty cheap. Just record stack state every n milliseconds, no need to instrument everything.

Actual JITting can be done on those other cores that would otherwise be idle anyways.
I disagree greatly. I've used Angular in a team project that spanned several months and went into production at a startup. After reading this article, I realize how much of my experience is reflected in it. I personally experienced each of the problems on his "bad parts" list, except for the name clashes issue (#3). For the last few months I've been telling people that Angular is powerful, but it has an extremely steep learning curve. I've been reluctant to tell people to try it because, why you can do a lot with it, you must baptize yourself in the framework before you can write anything half-decent. It's a little depressing to see someone with deeper experience come out and say it does not get better. But I know that as much as I want to like it, Angular imposes too much for me to actually recommend it.

So, this article is definitely not generic. Maybe, if you're reading at the bottom of the article, you can call it generic, because the advice for future projects is good. But otherwise, it's spot on. I can only hope that the Angular dev team sees this blog post and incorporates the recommendations into version 2.
Depends how well integrated it is into the system. I tried to add any MAC to my Arch and discovered that: 1. doing everything from scratch for Tomoyo, including plugging it into grub config and creating your own policies is easier than even getting proper tools for selinux 2. Tomoyo behaves like Apparmor (policies on names not inodes), but can do more (ioctls, devices, more granular network controls) 3. Nobody uses Tomoyo and I really don't get why...
And how do you expect a JIT to "figure out" negative numbers can't happen and optimize accordingly where a static compiler could not?
Now if one could easily export to a map format supported by games... I have been dreaming of playing Counter Strike in my hometown since ... Counter Strike was fashionable...
You would need to go through their careers page and follow the listed procedure or a recruiter for the company if they do not have a careers page for applying for a job. Even if you know someone who works for the company you normally still have to go through the formal process of applying for the job.

If you have met with someone that has suggested you apply for a job, especially someone in the top brass of the company they will normally have their HR team create a job listing with a specific requisition id or jobid for you to specifically apply to. You will apply and still go through the hiring process and interview but you may or may not already be pre-approved (normally they will not let you know this in advance so you still go through the procedure like everyone else (nervous interview or interviews or great to watch and are still a good step to help insure you have what it takes even though you may already have the job before applying for it).

You may also see some companies that want you to just email your resume or use their contact page. Be sure to read the instructions as some tech companies want you to just email them your resume in all text (no word, pdf, etc.)
Why is the site named that way?
I have been messing with this this morning and I think I may have found the todo list that a will actually use. I love that it's basically text but with smart features added around it.
While most of the arguments presented in this article are somewhat valid but I hope with the release of Angular 2.0 majority of the issues will be addressed (though does it make sense to make such drastic changes in the upcoming is another debate and already taken care of at: https://news.ycombinator.com/item?id=8507632)

I'm currently working on a comparatively large webapp built in Angular and it was after about 7 months into the project that we started realising it's pitfalls, and it was very difficult to abandon it then.

So we worked it around by:
1) using one-way binding (or bindonce to be exact) to reduce watches
2) avoiding un-necessary $apply() and using $digest() carefully if required
3) using ng-boilerplate for scaffolding
4) defining our own style guides/coding conventions/design patterns to overcome Angular's bad parts
5) frequent code-reviews that made sure new team members are upto speed with the above techniques

luckily we haven't ran into much issues after that :)
Personally, I use Angular for Backoffice tools and Backbone.Marionette for customer facing frontends.
"And whar are no-no factors for angular?

Teams with varying experience.
Projects, which are intended to grow.
Lack of highly experienced frontend lead developer, who will look through the code all the time."

I am greatly interested in learning what is the alternative that would be a 'yes-yes' in these bulletpoints.
I was fairly sold on react/flux after trying it because it is very simple and you can build very quickly. I've been trying Mercury.js over the last week as I thought the 'cycle' of flux/react was a bit more than necessary. Your front-end guy might be sold on Mercury next.
It's ReactJS. See my previous comments and surrounding comments for some discourse.
How we Increased our User Response Rate by 2,600% in 16 days
>I'd generally take a config file failing to update (this may happen anyways from the looks of it, e.g. if "/proc/sys/fs/inotify/max_queued_events" isn't available) over the box dying with a terrible crash report.

I'm not entirely sure I'd agree with that line of reasoning, to be honest. While the crash is a big problem and falls into the category of "obscure enough" problems that might leave your sysadmins scratching their heads for quite some time (especially because of the contrived and terrible crash report message), I would much prefer my system to crash and halt instead of failing to recognize/load a config file. Not loading config files properly (and failing silently, at that) means that you might be exposed to security attacks, your system might be in an inconsistent state until the next reboot and you might not even know it. I'll take a failure over prolonged inconsistent state of a machine any day. That's what redundancy solves after all.
I like keys with passphrases, although their security is somewhat questionable as you say. At least it prevents the scenario where the key is accidentally exposes somewhere via a lost storage device / bad scp command / whatever. And sometimes, for one-off non-prod servers, I don't bother with setting up AuthenticationMethods to require a separate password.

I think key + pass + OTP is the best of all worlds, except convenience. But in my opinion, it should be a pain to get into your servers, especially if they hold sensitive data. I am especially a big fan of hardware tokens like yubikeys; the best part is, you know when you lose them and can rotate keys. Even with Google Authenticator, you are not quite sure if the keys can be lifted from your phone.
Security loophole reported year ago still open and FB has no intention to FIX it
Can't wait to see wives and husbands coming back home to their kids after work and instead of twitting whatsapping and facebooking at the table during family dinner, the whole merry family puts on these headsets and dissolve into VR, eating soylent green (http://en.wikipedia.org/wiki/Soylent_Green), rendered as roasted chicken in full 3D splendor.

So what if the weather is insane outside, no big deal if we have to wear masks to breathe, we can always buy clean water at the supermarket and outside reality will be just fine.
We'll spend our life inside these programmed virtual worlds, were we can be Gods instead. Fuck reality, we're going Virtual.

I know it's not the most popular idea, but I'm just saying...
What is the purpose of this, except really cool entertainment ?

Why is it that so many extremely smart people work on entertainment instead of some real save-the-world-because-we're-fucked kind of problems ?
is it really work for you ?
As author says in the comment, these are valid for Angular 1.x so I'm hoping that angular 2.x will be more carefully designed framework.
Landed on your homepage and it was quite a shock for me. Not what I expected for a homepage - and I don't mean that in a good way.

I think that what Groove and promoter.io is doing with their homepage is pretty much how a SaaS homepage should be done. A clear, crisp explanation of what your 'paid' account can solve for a lost user such as myself.

I run a SaaS startup myself BTW (https://qeryz.com) just so you know where I'm coming from :)
Yes, modern C++ is far safer than the old style or passing pointers all over the place and wondering who was deleting them (not that I ever did that - you could pass const pointers to stop others deleting them anyway; it was only a problem if you didn't obey const-correctness and make certain classes "container" classes).

The addition of move semantics and using references everywhere makes pointers unnecessary for the most part.
You can use STL containers for putting your items into so shouldn't see raw "new" or "delete" operations in your own code very much; this is particularly true where you define your own move operators and move constructors.

It's a difficult habit to break though!

See Stroustrup's "The C++ Programming Language Fourth Edition" (the blue book) section 3.3.3 Resource Management and 3.2.1.2 "A Container", where in this early part of the book Stroustrup explicitly directs to 'avoid "naked" new and delete operations" and to "use resource handles and RAII to manage resources".

See std::move to force moving where it isn't clear that you're moving things.

Further reading:
http://en.cppreference.com/w/cpp/language/move_operator
http://stroustrup.com/C++11FAQ.html#default2
I'm guessing you live in USA. Here in Europe being a contractor in IT business pays much more than targeting permanent positions.

Also - if you have an idea for a startup then definitely it would be a good idea to release a free demo and encourage people to pay for rest of the work through sites like https://www.indiegogo.com; I liked this idea when seen this project: http://screeps.com/

Hope this helps :-)
> Upstart doesn't deal with the overflow,

Actually it's libnih that doesn't deal with the overflow. The difference is that any other application using that library will also abort on that condition. Let the new bug hunt begin!
I propose we change every occurrence of "disrupt" to "perturb". Or better yet: "Angellist is promoting perturbations" Seems more appropriate, and I'm sick of seeing "disrupt" everywhere.
Unfortunately nowhere near SF (Middle of England, UK!) but am definitely interested in what you're coming up with if you have any further info anywhere?