jkeisling/hacker-news-corpus-2007-2022 huggingface dataset:
Well, in the case it's not from the OS, but purely from Azure.

And you're selling the information in order to get tech support from Canonical, otherwise you can get it without selling your info (but won't really receive tech support).
Well, I'm a jazz musician, so am used to listening very intently to music when there's music on, learning from it. When I put music on, it's to listen to it, to focus on it 100%. I understand other people might be more used to music as background music, and can have music on without listening to it. It's often a problem for me, as I usually don't like the background music in cafes and pubs, or the background music in youtube videos etc. And if I do like it, it's not less distracting!
If I recall there are something like 24 different main courses
I called this a Domain Agnostic Language:

http://code.extension.ws/post/169602795/dal-rb

I don't actually like the approach though. Ruby makes DSLs as easy as "normal" interfaces. Why not take advantage of that? Generating and parsing an AST is exactly the kind of extra complexity that Ruby lets you avoid.
This is a single data point. Its best not to draw conclusions from it.
This reminds me of the role of Ogham stones plays in Ireland and parts of Britain that were originally Celtic or partially Celtic[1] A primitive early alphabet survived an incredible amount of time, from the fifth and sixth centuries. For reference, this is around the time of the collapse of the Western Roman empire.

[1] https://en.wikipedia.org/wiki/Ogham_inscription
> Customisation over configuration.

Composition over Inheritance.
No, not even slightly.

FWIW, I grew up in Scotland, then moved to England, so I'm probably from a rather different cultural background than the poster.
I’d be delighted as it would give me an excuse to not use WhatsApp
I am very glad to see this. Having a “you can abuse copyright to have proprietary control over an API” precedent on the books had a chilling effect for programmers.

Let me give you one example as an electronic musician. Once upon a time, Steinberg created an API for connecting programs which simulate musical instruments and musical effects (think reverb, echo, flanger, etc.) called VST. This API was always proprietary but everyone ending up using it, including the open source Audacity program which uses an open source re-implementation of the VST API, allowing it to use professional effects when editing tracks.

Well, Steinberg decided that VST2 — the one everyone has been using — was out of date and removed all downloads to the VST2 API, since they wanted users to upgrade to VST3. While a lot of professional music making tools have updated to VST3, others have not, and a lot of tools will never be updated. Steinberg no longer has a copy of the VST2 SDK available for download; they’re really trying to get everyone to update to VST3.

Now, with this horrible “Google vs. Oracle” precedent looming over everyone’s head that a company was allowed to copyright an API, Steinberg could had, in theory, said “VST2 is copyrighted, and Audacity is not allowed to use their own independent implementation of that API” (they didn’t in practice because they know it’s bad business; indeed VST3 is dual licensed, where GPL3 is one of the license options).

With this precedent, the Audacity team can more easily retain their independent implementation of VST2 knowing the legal precedent saying re-implementing an API is fair use.
It's better with ElectrifyAmerica in the US, not perfect yet. Give it one or two more years.
The artist Beardyman (https://www.youtube.com/user/beardyman) used to create entire albums within an HOUR - and many tracks were incredible. He has an incredibly custom audio editing setup I'd highly recommend checking out some of his work.

Been following his journey for 15+ years and now I'm one of his patrons.
I recommend getting an es100 to pair with wired headphones
The diffing/merging stuff that you see when you use the git tool is really just some sugar on top of the underlying data which is being stored. If you look at what a commit actually contains, it's just a hash of the tree root, one or more parent commits identified by their hash, and some other metadata (author, date, etc). There's nothing about the commit that cares about the contents of its tree or its parents' trees. It's the git tooling on top of those structures which does.

In git world this distinction is referred to as the "porcelain" vs "plumbing", the plumbing being the underlying structures and porcelain being the stuff most people actually use (diffs, merges, rebases, etc...)
At least you could actually read the answers, unlike, say, expertsexchange.com
Are you saying that your initial reaction to the headline ("For 2 million years, humans ate meat and little else") and first line ("...hyper-carnivorous “apex predators” that ate mostly the meat of large animals") was to note the obvious corollary that "There is little argument that Paleolithic diets were higher in plants than recent Polar diets..."?

Since the whole point of science communications is communicating nuanced ideas without perpetuating misunderstandings, the fact that discussions here are reflecting the former rather than the latter is what I mean.
Wow super cool, you could probably fetch a pretty penny if you made the pilgrimage to Omaha, Nebraska for the yearly Berkshire conference. The acolytes there might even make you a priest or something!
Would someone comment on this idea in context of JWTs? Not trolling, just curious as I use JWTs and embed this kind of metadata as a custom claim, which accomplishes some but far from all of what GitHub accomplishes here, but then I have no need for the easy scanning. So seeking wisdom from anyone who has thought carefully about whether or not to prefix their JWTs in this way.
I wonder if Snowden and co. were that stupid to keep all their files with Miranda. The fact is the gov can never be sure if whatever he was carrying is in fact the complete set.
I disagree with you regarding avoiding using the command line. I enjoy working in terminal and to the extent possible do as much as I can in there. I also try to understand what is happening "behind the scenes" when working in a GUI.

The way I look at a GUI is that it is built entirely on terminal functions. I see you disagree, but I don't know how a GUI could be created without being built on something at a lower level. Something has to cause it to work, somewhere between bits and hardware, and the screen. Double click to open file? Same as `open file`. Find and replace in a text editor? Same as sed or `s//`.

A GUI can make it easier to do those things, but not always. For example I find using git in a GUI to be a worse experience than it's command line counterpart. I'm more at home with `git diff` than whatever built in attempt at improvement is available. I'd rather edit and resolve conflicts in vim than a visual editor (even XCode which is a pretty nice diff tool).

In short I just don't see myself ever moving off of terminal, and I would never see knowledge of it as a handicap. On the contrary, I'm always looking to learn how to do something new and powerful in it.
> It's quite possible that knowledge of vim and emacs and package management won't be the world's most valuable skills in ten years. Whaddya think?

Replace your hyperbole of "world's most valuable skills" with just "valuable skills", and I think knowing how to use a text editor and a package manager will still be valuable skills in 10 years. The last 20 years of inertia serve as evidence for me.

> Only if that's the way the system is architected. Maybe thinking that way is actually a handicap.

That is the way all (afaik) computer systems are currently architected. Having a correct model of the world isn't a handicap.
This is a worthy idea and a lovely example of programming (particularly web development) tackling interesting problems outside of your domain...I think there's huge potential for programmers who, arrogantly or not, attempt to tackle industries and fields as outsiders.

However, I don't understand why the OP believes asteroids too small to be seen through computer-vision algorithms would be noticed by human eyes? I'd think computer processing would be much better (and configurable) at detecting the smallest cases and, at the same time, be better (with some additional tweaking) at reducing false positives. I'd be interested in seeing whatever data/edge cases the OP found that led him to go this crowd-sourcing route.

(OTOH, bringing people in to help find asteroids is a great way to bring attention to the project...but hopefully he's doing a lot of pre-filtering/processing of the images to serve up just the most likely candidate sequences for humans to go over...and if so, what's the threshhold he's set for the pre-processing)
For those following along at home, this issue is now tracked at:

https://github.com/yeoman/yo/issues/69
The truth is that one should be concerned with how much memory is taken in our world of big-RAM consumer computers, too. To do otherwise is purely egocentric, being a bad citizen: he assumes that his software is the only thing running on that system that needs memory. Of course, this concern needs to be weighed against all the other usual concerns of optimization, but frankly, one should not flagrantly waste memory where it is unnecessary. This is a shared resource, not a limitless supply.

We heard this argument a decade ago with CPU. "The hardware will get faster. Moore's Law, lol." Oops?
Hi Zach, yes, that's true. I definitely think it's a good feature to let people know their voting power though. It might be solvable by only letting them know in segments: 1-5, 6-10, and so on, or something like that.
1-Click is a trademark too, not just a patent.
Is Amazon suing anyone for saying something like "I did it in one click" ?
Two weather apps exist on my phone for different purposes. Weather Underground's i.wund.com (webapp) strikes a perfect chord with forecasts such as "today is scheduled to be colder than yesterday". MyCast (native app) is the other one, which provides excellent radar imagery. It was worth buying.
Mistakes in non trivial languages are not fixed, they are worked around. (cl-containers does offer a clos based sequence protocol)
My comments as posted last month when Apple first filed this suit are here: http://news.ycombinator.com/item?id=2352076 (analyzing the pertinent trademark issues in some detail).
Ink/toner subscription with free printer?
For a slightly different perspective, I could see this making certain forms of loans we do in the U.S. possibly easier and/or allowing for more involvement from lenders (at Kiva). Our legal counsel is very conservative though so I wouldn't imagine that being the case any time soon even if it does allow for that.
If the app crashes is the mem freed?
I am far from a tax expert, but my impression was that excess sales tax paid in another state can be claimed on your California state income tax return?

It sounds like the customer can talk to the repair place, it's just that the repair place can't contact the customer, or even advertise themselves as a Tesla repair place.
This is called the Dunning-Kruger effect: http://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect

The Dunning–Kruger effect is a cognitive bias in which "people reach erroneous conclusions and make unfortunate choices but their incompetence robs them of the metacognitive ability to realize it." The unskilled therefore suffer from illusory superiority, rating their own ability as above average, much higher than it actually is, while the highly skilled underrate their abilities, suffering from illusory inferiority. This leads to the perverse situation in which less competent people rate their own ability higher than more competent people. It also explains why actual competence may weaken self-confidence: because competent individuals falsely assume that others have an equivalent understanding. "Thus, the miscalibration of the incompetent stems from an error about the self, whereas the miscalibration of the highly competent stems from an error about others."

“In the modern world the stupid are cocksure while the intelligent are full of doubt.”

— Bertrand Russell
Benjamin Zander on classical music and shining eyes :) http://www.ted.com/index.php/talks/benjamin_zander_on_music_...

And a rather controversial but spectacular idea by Wubbo Ockels on time as a creation of human mind as a response to gravity http://www.tedxamsterdam.com/2009/video-wubbo-ockels-on-time...
1. Use fax. Practically, it is more secure. Given a motivated intruder, it is no less secure than email.

2. Use password protected PDFs. Tell your lawyer friend to use the person's last name and/or DOB (or some equivalently easy to remember token) as the password. Pre-arrange the password over the phone--since it is based on their name it is easy to tell them what it is. The key here is to stop the vast majority of folks who might stumble across the email. Again, given a sufficiently motivated intruder, this is pointless, but still more secure than plain old email.

3. Use encrypted archives of the documents. The files can be encrypted with AES256 or an equivalently difficult cypher. Test the type of archive/encryption to ensure that Windows XP and above will be able to decrypt the file easily w/ the build in archive folders. This can avoid any potential compatibility problems with #2 from above. It might introduce new ones.

Using a web drop service doesn't eliminate the need to protect the file. If you password protect the file then you need to share the password. If you password protect access to the file, you need to share the password. The link in an email is nearly equivalent to an attachment, so it doesn't really solve anything unless you have an easy way to share a secret with the receiver.
Fascinating! Through sheer chance I noticed that this comment was at 5 points before lunch, then on returning it was at 4 points (about 13:30 Zulu) Clearly someone thought 5 points was too many and down-voted it.

I must admit I'm intrigued. Is it the term" dog-fooding" to which they objected? Is it the explanation of why I think this will get very tedious? Is it the links to explain the term "dog-fooding" which, I would've thought, some people here wouldn't recognise (although most certainly would.)

I try to ensure that my comments and thoughts are generally useful (well, perhaps except for this one. I pray indulgence) and hence add to the value of HN, but clearly someone thought one wasn't. Oh how I wish it were possible to see into the mind of the down-voter.

<sighs, shrugs, wanders off, wondering.>
> Anyone who wants to can get started on any computer with some simple HTML.

"Lots of people wrote in to say that HTML and JavaScript are the new BASIC. NO!!! You can’t be serious!!! So people have to write two languages now, which are intertwined in an almost inexplicable and unfathomable way? This doesn’t do it.

Hello world should be one line." - _why, "The Hackety Manifesto" http://wiki.github.com/steveklabnik/hacketyhack/the-hackety-...

I'm inclined to agree with him. (Surprise!) Don't get me wrong, I love HTML/CSS, but I think it's far too much to get started with.
I'd like to know if the RescueTime guys can confirm or dispute this info. It would make a nice counterpoint.
It's not about whether they're smart or not - it's that a multimillionaire can lose a bunch of money on a private company and not be out their retirement savings. That's not nearly as true for the typical middle class person.
> The login screen is pretty self-contained and we don’t have to worry about application compatibility or support for exotic devices. And we will get Wayland to run on (almost) all systems this way, which should give a lot more exposure and help shake out lingering bugs and hardware issues.

Let's test the exciting new technology by making it a dependency of ... being able to log in.

I. Um. This seems ... unwise.
Read about him a year or 2 ago in National Geographic ... bothered me then as now that he was referred to as "Batman". He's clearly Daredevil.
One thing to note if you've never used an Amiga is that you can pick up the white bar at the top and drag it up and down to reveal a screen behind it. This was what passed for entertainment in those days.
So has putting it all on black in Vegas, alcohol, and any other number of statistically proven vices. At least investment has some measure of upside. But yeah, I'd like the $n trillion in debt government tell me how to manage my money.
I see I should be clearer on that formula, you are absolutely right. What I meant was a range of $x to $x + $y(thousand) more. Such that I would take $100,000 to $110,000 depending on other factors such as benefits.

I also should have been clearer in stating that I generally will pick the initial "$x" value of the range by deciding what I want. However, if asked, I will often state this is where I am at my current position, even if it is not my actual salary. I do not often share what my actual salary is.
To answer the usual complaint whenever the release announcement gets linked here, the NEWS file is intended to give current users of Julia an overview of all the things that changed that they may want to adjust to. It is however, not designed to give people who are only casually following the project an overview of all the work that's going on and why it's happening. We've been talking about writing a more casual document like that for the releases, since they do tend to get a fair bit of attention, but that's just one more thing on an already-extensive list of things that need to be done for each release.
Oh, also: try to fit a bell curve on the AIDS epidemic and see how “Farr” you get.
Enabling overcommit machine-wide is a puerile, broken approach that not only converts your server to an unreliable toy, but encourages other idiots to rely on the same broken behavior in their libraries, language implementations, and so forth, basically leading the current plethora of collection libraries that don't even bother to monitor their own memory use or check malloc's return. It is software engineering plague, a rot on the underbelly of allegedly-solid code. oomkiller's unpredictability causes any number of problems in actual production environments, usually by killing the wrong process, and secretly ripping the stability out of programs whose code does check malloc's return. The answer is:

{ echo 'vm.overcommit_memory = 2' ; echo 'vm.overcommit_ratio = 100' ; } >/etc/sysctl.d/10-no-overcommit.conf

Which restores classical semantics and allow processes to identify memory allocation failures and respond to them responsibly in a number of ways (garbage collect being an obvious one, clean, safe exits after logging being another).

Now, if we could say that a specific process was allowed to overcommit because we could guarantee it would use the bogus memory allocation, then we'd have something vaguely useful.
They should do like the tech community. Make "Pinterest Boys Meetup" and "PiGuys" making free lunch paid by all the major clothing companies where girls are not allowed to participate. Also, they should host conferences and encourage guys to participate and make discounts for them. They should tell everyone how much they appreciate guys joining them.
It would be nice to get some more info on the VCs behind this. Who are you, and what have you made?
Comparison of historical age distributions in the U.S. suggest this problem.
http://www.wolframalpha.com/input/?i=u.s.+age+distribution+i...
http://www.wolframalpha.com/input/?i=u.s.+age+distribution+i...

This problem is much worse in China.
i disagree with both of you. my non-nerd friends have taught me how to use my android device way better than i was able to teach myself.

i never thought to look for a text pop-up app, i just figured that functionality was on my old phone and not my new one.

i didn't consider the advanced task killer widget would put a button on one of my home screens and take care of the work i put into the manage applications menu force killing things i don't want anymore.

i have two girlfriends that use android way smarter than me, the one who is reading an android development book.
gnosis makes a good point, and to be honest, I'm not sure the AIs coming out of the AI research sector are the ones we'll need to be worried about anyway.

Basically, I'm thinking something along the lines of Hanlon's Razor: "Never attribute to malice that which is adequately explained by stupidity."

We'll see serious damage caused by "weak" AIs long before we have a "strong" AI capable of causing similar damage. For example, 2010's "Flash Crash" seems to have high frequency trading at its core.

My hope is that through the growing pains we experience from "weak" AI systems doing something stupid, we'll be better prepared for a "strong" AI system that may try to do something malicious.
Test being difficult is not a problem, we want our lawyers to be competent, after all. The more important part is if it is fair. In Poland bar exam had been famous for near impossible questions, which were only answered correctly by applicants that knew them in advance, which typically were family members of already practicing attorneys/judges.
The root is this: is your job maintaining LAMP servers, or is your job running your business?

I know how to maintain a server, reasonably well. But I don't want to actually do that. I'd rather just 'git push heroku' and be done with it.
Norwegian news site digi.no picked up this story and have a statement from Tandberg. Tandberg claims that their invention is different from what's in x264 and that they invented it before x264 the referred code.

Google translated link: http://translate.google.com/translate?js=n&prev=_t&h...
Ha, I like that, I'm not the funniest, guy in the world but some of the guys I work with are pretty funny. I suspect my biggest problem with this is that a ridiculous name won’t get past some of the more serious old school members of upper mgmt.
I find it tremendously frustrating that so many people are creating this problem for themselves.

Anything that needs to be data should be data, not images. Except for some very specific cases, you're not doing anybody any favors by outputting PDF. That format is a data black hole. It allows you to transmit very well-formatted output, but it absolutely stops you from reliably using anything in that content.

I beg you all: if it's anything that contains data, or really, if it's anything for which layout and formatting is not absolutely critical, please don't use PDF. Send data as data.
It's a little bit out of place, but, does anyone know how well do the 11 and 13 inches AIR handle Xcode for iOS development?
“In two years, this type of piracy will be over. After a ruling like this and all the pioneers start to get older and have children and families, piracy won’t occur to this extent.”

The only way I can see this type of piracy being over in two years is if the media industries up and die so there's nothing left to steal.

I wonder how much this case actually cost the media industries to litigate. The actual fines involved are relatively small, so it would be interesting to know whether the record companies will be able to use the fines to cover their legal fees.
Some people seem to have a hard time with deeply nesting languages. Anecdotally, they seem to prefer "chaining" constructs, like "someObj.method(arg).otherMethod(arg2).om3(a4).om4(a5)". I'm fine with heavily nested Lisp-y code, but chaining code feels very awkward to me.

Self and Prolog both have well-designed, completely unambiguous grammars. People interested in syntax design (or "fixing" Lisp) would do well to look at those, rather than trying to force a pseudo-Python syntax on Lisp. Python's grammar has too many edge cases. (Lua's syntax is also quite simple, though not as much as Self's.)

In the end, clear semantics are at least as important as a good syntax. Lisp has very clear semantics. So do ML and Erlang, another language which has a bit of a quirky syntax.
On the iPhone 4 iOs 4.1 it raises the keyboArd each time you press a button