skysight-inc/HackerNews huggingface dataset:
Your half-implemented feature will never, ever make it into live code.

Ever.

Just delete it, you commented out code leaving scum. We all hate you. And you smell.

But seriously. Never commit commented out code. It's a cardinal sin and massive code smell. Never leave YAGNI, but maybe one day, hooks in code. Just delete it. It will never make it live and when someone actually comes to do that feature they'll usually half finish the feature before they even find your code, and then won't be 100% sure your code is supposed to do exactly the same feature and so they won't delete your cruft as they don't really know what on earth it's supposed to do.

And on top of that your code won't work because it hasn't been refactored along with all the live code, so all the property names are wrong, it references methods with signatures that have changed and probably even the names of the classes have changed.
this is a problem I know and understand well. And my advice to such startups would be: damn well hit the submit button. Sacrifice your sentimentalities, your fear of ridicule, your rightly held belief that the HN community will likely ignore you or worse ridicule you, and just get the word out now.

Agreed. I've submitted Fogbeam blog posts here before, and I name-drop my startup (Fogbeam Labs) quite often, but prettty much only when there's a reasonable "in context" reason to do so. The worst thing that's ever happened? I've been silently ignored. The best thing that's happened? We've had blog posts make the front-page and generate tons of traffic to our site, and I've gotten a few emails asking about, or commenting on, what we're doing.

So yeah, I would say don't be afraid to engage in a little bit of self-promotion here. But I'd argue that there's a line between that and outright spamming the site, and I try to avoid crossing the line into the latter.
NSA-Developed Technology Sqrrl is a Great Development for Enterprise
I think this is the culture shock of not working with a compiled language.

I mostly work in compiled, statically typed languages, and it can be a bit of a surprise in Javascript when you don't find out about a syntax error until execution just stops, half way through your application loading, because of some code in a function you didn't think was called.

It's a surprise. But that doesn't mean it's wrong. We just aren't using the right tools - unit tests, JSLint, etc.

Question to regular JS users - what do you do 'in place' of static checking?
Yes, but no.

Yes, as in of course you are correct.

However, this is an argument that Bjarne often uses in the context of C++, and it drives me a bit batty. For example, he'll wax eloquent on how it is fine that there is no multidimensional array type built into the language, because look how easy it is to write one yourself, or use one somebody else wrote.

And, at the first approximation, that is surely true. Heck, I'm taking time out to post this from working on a Kalman Filter class I wrote that uses a hand coded multidimensional array class.

But, the problem is is that there are thousands of string libraries out there, and thousands of multidimensional arrays, and so on. And they don't play nicely with each other.

Heck, we use char, std::string, CString, and QString all in the same project. You can guess the evolution - a bunch of old library code written 10 years ago who didn't trust/like the new-fangled std::string stuff. External library code written in C. Then code written in modern C++ with an aim to be portable (std::string). Then some MFC UI code, and more code written by MFC people that didn't care about strewing that dependency in places where it didn't belong. And now we are in Qt, and I have to really clamp down on the code reviews to keep QString from straying beyond the UI components. Ugh.

Hey, I love C, and this is not a rant against the language. C strings have their place. I can't tell you how many times I've written code along the lines of:

char* c = some_data();
c += header_size;
name = extract (c, ',');

You get the idea. At one time that was the state of the art way to do string processing without the cost of a lot of extra creation/deletion. You just use pointer arithmetic, move along a data source, scraping it as you go.

But these days we aren't so interested in that kind of scraping, and are far more interested in higher level problems. And we have no standard to fall back on, in C. Sure, I can elect to use a third party library, under the almost never to be satisfied requirement that every line in our project is written in house, or that every third party library either uses the library I chose, or that it can inter-operate with it seamlessly. Frankly, I've never been in a situation where either of those held. So we end up either reverting to the mean (c strings), or making endless conversion calls to switch from one form to another.
Seemed like a random assortment of cherry-picked stats and anecdotes.
its still WIP, once they provide framework authors with what we need, rest assured ember will land it.

We are actually working close with the firefox and chrome teams, to drastically improved general JavaScript developer ergonomics when debugging.
So, if the job post included the information you desire (the type of work, the ball park pay, the location, the level and the type of hours) AND then the following: "If that alone above sounds interesting and something you'd like to be a part of then inquire or submit your resume because we also offer numerous other perks we'd be more than happy to share with you."

Would that be the best type of job post? I would think so because then you know they aren't applying because they get X, Y, and Z but because of the work. X, Y, and Z might be nice perks if they enjoy them but if they don't care about X, Y, and Z you know they're still interested in the opportunity without them.
FYI, your blog doesn't render properly with the Disconnect extension:

https://chrome.google.com/webstore/detail/disconnect/jeoacaf...

(The code sections don't highlight or don't show up at all, etc).
I think that would be a much better title (minus the issue number).

As it is there's strong presumption that the bug is not in AOSP, so that's missleading. As for the "impeding science" part it's clickbait more than anything else IMHO.
What do you use for routing and models with react?
Borogravia, FYI, you have been hellbanned. No one can read your comments normally.
I think you generally just fall back to using normal website auth (cookies/session/etc.).

If you really don't want to do that, you could probably work up something like the author discusses in item No. 5, and generate query parameter "tokens", and append those query params to every link on the rendered page.
About the size of Texas with twice the population. So yes, it is a rather large country by European standards.
Sorry to simplify, but I remember when Google enabled,
For the really good stuff, you'd need pultruded carbon fiber where the glue sets with the fibers tensioned straight to really get good strength effects.

A lot of composite work is low volume production with excessive manual work at not very good quality.

Ultrahigh Molecular Weight Polyethylene (UHMWPE) might be a much more interesting material as it has a higher strength to weight ratio and as it melts at a lower temperature, 135 C. It is nontoxic too.

http://en.wikipedia.org/wiki/Ultra-high-molecular-weight_pol...
It might not be so much a genius vs non-genius thing so much as your particular app not needing the heavyweight app-state management that Ember provides.

It's worth pointing out that the Ember core team has been approached by the React core team with the intent of unifying React's view layer with Ember's application state management, which is a major component of what Ember offers relative to other frameworks. If you haven't had to solve major problems with navigation, routing, complex nested async logic, etc., for the particular app you're trying to build, then it sounds like React would get you most of the way there, but even the React team themselves realize that for medium-large scale apps, React's only going to take you so far.
I refuse to use SaaS products behind a .ly domain. That's the TLD for Libya, against whom the US government has sanctions. If that wasn't bad enough, the .ly registry can and will revoke your domain name on a whim based on the content of your site, e.g. vb.ly per http://en.wikipedia.org/wiki/.ly . Not exactly business friendly.
MitChat – new chatting experience
Avatar: A browser OS with built-in privacy and anonymity
You are assuming these films wont be 100% digital in the future. It's not hard to believe digital will equal reality in time. There are already plenty of digital boobs etc. Actors will be 3d mapped and fitted with Golum suits. Hello Holodecks/Ready Player One tech!
just get a galaxy note =P
Don't throw the towel yet, You can sell the technology behind your site. You can package the whole thing and sell it so that people with big software QA shops can use this on their own sites.
I hear this sentiment a lot, and I at least understand the sort of purity of deleting code instead of commenting it out, but that's the only value it seems to bring whenever I try it.

Scrubbing back into history (or remembering that there's even something to scrub back to) doesn't seem to ever be as convenient for me as it is for people that are peeved by commented out code.

I'm not that great at Git, but I'm also not trawling through history very frequently and there still seems to be a mental overhead associated with it compared to seeing some commented code a few lines away.

The article goes on to say:

> I wasn't sure whether we would ultimately keep the
> widget or not, so I opted to keep the above
> javascript code for the controller and view around
> for awhile so it would be easily available if I
> later decided to re-enable that UI element.

That seems reasonable to me.

In a file I was just working on before I decided to habitually check HN, I have two past versions of a function commented out above the final revision of the function. Next to each older revision, I've annotated some reasons why they were revised. When I continue to work on this function a week from now, I'm reminded of my efforts so far.

Someone would probably say that those annotations should be moved into commit messages and the git log should tell the story about this function.

But all that really seems to do is disperse my notes about this function across intermittent entries into this file's commit history. And once those past revisions are deleted from the current view of the file, I certainly won't remember that those notes exist for me to scrub back to in the first place.

- How do you manage this kind of stuff?

- What's your workflow for looking for and fetching deleted code?
There are two types of risks:

- epoxy sensitivity. Work with it too long (years) and you can become allergic. I can't tell if this system uses epoxy as a binder; it doesn't seem to because it would be messy.

- inhaling carbon fiber dust. This dust is made when you cut it, not when you lay it out. A 3d printer should put it in the right shape, so less cutting would be required. You'll want to avoid breathing it in, but it's not cancerous like asbestos: http://annhyg.oxfordjournals.org/content/38/inhaled_particle...
Open for everyone
You should read up on DMCA Safe Harbor. It's a very important concept that you should understand.

To answer your question, no.
in addition to our first blog post:

http://blog.auth0.com/2014/01/07/angularjs-authentication-wi...

Jose Paddilla is using it with django and he wrote a blog post:

http://jpadilla.com/post/73791304724/auth-with-json-web-toke...

and he wrote the backend for django:

https://github.com/GetBlimp/django-rest-framework-jwt

I hope this help you.
I don't get your point. Is it that people should not complain about Google removing a feature they like, because you have presented a guess as to why they removed it? (FWIW - I agree with you that it was not maliciously removed)

Personally I like it when users complain loudly about decisions that impact them. The idea of negative publicity might deter such actions in the future (in theory anyway).
Worse, $136 for more than 275 commits (= about $0.50 per commit), which is not that much. Plus most of Linus' commits are (iirc) merge commits, given how that's what he usually does.
Also you can think of it just the opposite:

Copyright incentivizes many authors to undertake works they normally might not due to the protections copyright provides. Many authors (who freely publish their books under copyright) probably wouldn't be able to spend 3 years researching and writing a book if they weren't able to get advance money from their publisher.

One is free to use a liberal license or a more restrictive license, both are out there and available to creators.
Cash for gold
If that we're true why don't they remove the AdBlock extension from he Chrome store? What good are targeted Ads if those Ads are blocked anyway?
People who lived and remember holodomor are no longer alive. The people who voted for Yanukovich grew up in the 70's and 80' - at the peak of communism civilization.
It's normally not too bad -- KeePassDroid creates notifications that copy the username or password when selected, so you find the entry then switch applications to where you want to use it and use those notifications.

More often, though, I'll be looking up credentials on my phone to enter into a different system. That's where having not-completely-random passwords becomes useful, as the output of `pwgen` is much easier to type.
I have to say that it's interesting that you so quickly found that a reference to your theme had made its way on to HN, and on this particular thread. Unless I am missing something obvious?
That's what would make intuitive sense, but it also makes intuitive sense that those would be one and the same, given the topic of the article we're commenting on, so I'm still not sure about it.
If the headgear is comfortable enough, it might help with RSI/fatigue issues -- body position is no longer narrowly constrained by practical display mounting.
It's not like your anonymity is one in a billion. In fact, your security habits make you stick out like a flashing red light.

Perfect anonymity: 1 in 7e9

Fluent English speaker: 1 in 7e8

Tor user: 1 in 3e6

Tor user today: 1 in 1e5

Fluent English speaker and Tor user today: 2 in 10,000

Fluent English speaker and Tor user today and accessed both Google Translate and Outlook.com outside Tor today (because Google and Microsoft block Tor exit nodes): 1 in 1,000

All of the above and purchased a Kingston Digital DataTraveler from Amazon in the last year: 1 in 10
Add to this the fact that Greenland is the suicide capital of the world (most suicides per capita).
In this day and age, why isn't there an automated way to keep file history? (like Dropbox does, but locally and with a decent interface) I am looking for something like that for Linux and my (admittedly short) research didn't turn up much.
This was after two hours of staring at a black screen

Only those still afflicted by eve-addiction can believe that not playing a game for 2 hours is playing a game.
The world is not burning. We are living in the most peaceful time in human history. A few people playing video games is neither here nor there.
I'm not sure I'd classify this as a web development "super power".

Companies like AKQA, RG/A, Huge and Code + Theory have hundreds of employees and engineers and work on multi-million dollar web projects. At 33 folks this is still a fairly small shop in the grand scheme of things.
Yeah, that's a good point. The things I've been building with both have been small and relatively simple.
At work, our approach is to simply not allow commented out code to get through code review. It allows individual developers to comment out blocks, and even commit those comments if they so desire, but they never make it into master.
All this does is show that human societies are big, complicated, and flawed, even the successful ones. And you can always cherry-pick statistics to point that out. I don't think anyone is under the illusion that Scandinavian countries are perfect, but it's quite true that they also have many statistics going in their favor and programs other countries can learn from.

Also, some of the statistics are questionable. Quoting ecological footprint and suicide rates without adjusting for climate? Not sound, but what do you expect from an article that just presents a random grab-bag of out of context statistics?
Fact! Tackling is my favorite part of fleet combat. I've pulled out battleships when necessary, but buzzing between the huge ships in a Vigil at 4.5km/s and fucking their warp drives is so much fun.
Gear doesn't matter
JSHint is helpful, especially (I think) for people who don't write a ton of JS. Unit tests are obviously important. I've been using Istanbul lately to check my test coverage, and that's made a big difference. It's awesome to be able to see, quickly, that "Oh. I'm not even testing half of this function."

Sticking to some kind of style guide also helps. Idiomatic.js is a good starting point.

Also, doing some basic checking on your own is often a good idea. Look at your arguments, make sure they're what you expect, and if now, throw an error. That'll make it a bit easier to see where your problems are, since you won't have to dig around stack traces as much.
Some people use type-checking compilers like the Google Closure Compiler or Microsoft's TypeScript to perform static analysis.
jshint is static checking. It would have caught your syntax errors. Even catches when you do something stupid like define a new function inside of a for loop. As far as type checking, typically it's not needed and can be confined in functions that care about types, you just defensively cast to the type you need. Closure's also an option if you really make heavy use of types of your application.
Oh, do we know who Satoshi is? Because I missed that.
Then don't use mysqld as it's obviously broken. Even SQLite doesn't have that problem.
Only on the latest Android if you buy it that way on very specific phones. For everyone else (read: MOST Android users) an upgrade happened, often from Google Talk, and wound up with a new app with full SMS control without the user knowing.
NFL to block mobile streaming video in Super Bowl stadium
I don't think identifying someone via textual analysis of a few hundred words is "almost trivial". In fact it seems really, really difficult...suppose your were the NSA and had obtained this sample from Google. Where would you start?
EVE: spreadsheet the game.
Porn industry is a better use case. Unlike regular movies you do not watch porn with friends and family.

Seems to me it is the future of regular movies for the Audiophile type guy that want to enjoy the very best experience even if alone.
It depends on the load, for a bullet poof vest you need to have woven threads, for a cable it's less of an issue but weaving still helps once the threads start breaking.
Tag commits which delete things you suspect you may want to restore later with a descriptive name and message. Occasionally go back and prune those tags when you have nothing better to do.
No, because a communication protocol has to handle all the types of problems HTTP and TCP solve. A transfer protocol is concerned with moving data and meta data, not the problems TCP solves.
No, you need the signed token for the link, that will only works for that particular url (protocol, host, path, query), for a breve period of time and only for GETs. As mentioned in the blog post, you can check hawk bewits:

https://github.com/hueniverse/hawk
Svbtle’s dashboard is designed to work the same way your brain works. It encourages you to dump ideas, links, and thoughts into a flow of draft posts, and then makes it easy to slowly sculpt those ideas into publishable articles. It just feels natural.

This isn't the type of marketing copy that makes me want to use the product, and in-fact drives me away from it. Contrast with Medium's more neutral, objective copy: https://medium.com/p/8d615d86ac04
Best of luck Zoli and thanks for sharing notes from your process.
Generally speaking, in dynamically typed languages, unit tests are the replacement for compile-time type checking. Type safety should not be a goal, duck typing is embraced and the correct behaviour is verified.
Yes, that was Jenny Price. Here's an article she wrote about this issue in 2003. The app was released last year. This is a long-term fight.

http://www.californiacoastaltrail.info/cms/pages/trail/price...
thanks, glad it helped!
I get the rather cynical impression that Monsanto may need to rethink the nature of the problem. Unless I'm mistaken this strategy is still going toe-to-toe with evolutionary biology and ends up causing individuals who are not succeptible to this target to flourish.

I also don't like the idea of spraying stuff around that is built to silence genes--I'd like to have some mention on how specific the targeting is i.e. are you knocking out specific codons, frame rewrite or transposons, and if it's that general how is it contained/delivered?

It's the vast crop monoculture that is the problem, not the "pest" who evolves and then takes advantage of it.
>>+++++++++++++++++[-<+++++++>]<>>+++++++++++++++++++[-<++++++>]<>>++++++++++++[-<++++++++>]<+>>+++++++++++[-<+++++++++++>]<>>+++++++++++++[-<+++++++++>]<>>+++++++++++++[-<++++++++>]<>>+++++++++++++++++[-<++++++>]<+>>+++++++++++++++[-<+++++++>]<>>+++++++++++++++++++++++++++++[-<++++>]<>>++++++++++[-<++++++++++>]<+>>+++++++++++[-<++++++++++>]<>>++++++++[-<++++>]<>>++++++++++++[-<+++++++++>]<+>>+++++[-<++>]<>>++++++++++++[-<+++++++++>]<>>++++++++++++++[-<++++++++>]<>>+++++++++++[-<+++++++++>]<>>+++++++++[-<++++++++>]<+>>+++++++++++++++++++++++++++++++++++++[-<+++>]<<.<<<<<<.>>>>>.>>.<<<<<<.>>>.<.<<<<<.<.>.>>>>>.<<<<<<<<<<<.>>>>>>>>.<<<<<<<<<.>>>>.<<<<<.>>>>>>>>..>>.<<<<<<<<<<<.>>>>>>>.>.<<<.>>>>>>.<<<<<<<<.>>>>>>>>>>>>>>>.<<<<<<<<<<<<<<.<<<.>>>>>>>>>>.>>>>>.>>.<<<<<<..<<<.>.<<.>>>>>.
Look to me like dear Michael has been forming his view largely by asking assorted grumpy people for their personal opinions about people in their out-groups.
I want my four minutes back.
Yep, compilers turn out to be a pretty cool idea :).

I don't think anyone's doing anything 'in place' of static type checking exactly. Oftentimes I'll check if a method exists on an object before calling it. Usually when I'm "type checking" I really just want to know if an object has a certain attribute. That gives a fair amount of flexibility because polymorphism is built in.

I think by and large the errors that would be compile-time errors in a statically typed language are caught with unit tests (I use mocha). For front-end work, end-to-end testing has also gotten quite good and easy. Take a look at karma if you're interested in a good front-end testing workflow.
I did not mean to give you a Kudo. I don't care for that button interface. Unless I can undo it, then I like it.
Haaa....I hate me, too.

Seriously, though, we do it all the time. Successfully. We even write skeleton code, and have other people finish it off, or take the half-baked idea and implement it properly. Sometimes in this sprint, sometimes in the next. We tend not to let these things stagnate though, so if the spec changes, the ideas are usually ripped out along with them. A lot of the cruft eventually comes out during code reviews...

It's definitely an anti-pattern, using one's code base to communicate....but the right team with the right processes, can work for the short-term. (short-term vs long-term is probably the key here)