skysight-inc/HackerNews huggingface dataset:
You can use the web version for free at http://www.hemingwayapp.com/
Proof of Stake Velocity: Building the Social Currency of the Digital Age [pdf]
I am wholly in favor of writing tools that do one thing well and make it a priority to get out of your way. That said claims like "Git is that it's a whole subworld on[sic] to itself" seem absurd in this context.

Perhaps this is the authors problem in general: the trick to productivity is being able to quickly reach functional understanding of a tool/library you've decided to use. Enough to 1) evaluate the tool/library itself and 2) use it in a way that's at least somewhat conformant to how the authors intended. Obviously doing these two things requires good authors and good client programmers. However, if being a large body of work kept developers away from things you certainly wouldn't have a zillion apps on the iOS app store.
>Though for his part Shatner claims it was a one-sided feud he didn't even know about until 1993

Which, of course, humorously confirms all of the casts' characterizations of him as a selfish egomaniac in a wig and a girdle. I think that Shatner is aware of this (within the past 20 years, not at the time) and plays into it for the humor value and a media bump if he's currently selling something. He's always selling something.
Worked for me in beta 3, but they removed it in beta 4. Also, sending SMS from Mac doesn't work anymore.
This is awesome. Many times I have looked at an open source project and wanted to look around but didn't want to take the time to download, setup, etc. This looks awesome!
Do they require signed kexts now? How does virtualbox, vmware, osxfuse work?
I've been using this for around 10 minutes now and it seems fairly buggy, the main ones I've hit are:

* Messages appear in the wrong conversation, then move back to the correct one on close/open.
* I get notified about new chats that then don't appear in the list
> But if a potential contributor wants to fork your code, you'd better understand pull requests, branching and merging, and a whole series of other operations that might or might not have counterparts in the SCMs you've used.

I don't think these tools are all the same, at least as traditionally used. And you don't have to (ab)use all their features. Also, you don't have to use these tools at all.

But the original author more or less claims that you have to use git to get any community involvement.
I just want to paint said Michelangelo.. but now I spend all my time mixing paint and building scaffolding and such..

SCM,Frameworks and such are part of the price we pay to be able to build larger and larger projects.
It seems like no one here shares my opinion on this: I really like comments, even if they just restate, in English, what the code does. I don't think that's pointless. There is big value in it. I can scan and mentally process English sentences much faster than code. With a heavily commented file you can just skim through the comments until you locate the part you need to work on (then slow down and read the code around it and edit it).

Look at the Backbone.js annotated source [1] (the stuff on the left is just the comments pulled out from the original source JS). The comments make it much, much quicker to grasp what's going on, even though many of them just state exactly what the corresponding code does, which according to the Haskell docs' advice is pointless and to be avoided.

[1] http://backbonejs.org/docs/backbone.html
Seriously? You submitted your reddit submission of the article?
I still use Firebug for Cookie management. I have to try if FF tools support that
Oh the irony of an analogy... The point of these complications is that you are able to travel farther and faster on a jumbo jet than on a bicycle and these journeys will take you to many more interesting places (once you are set up, that is).

Version control, build systems, compilated makefiles, testing frameworks, profiler sessions, deployment scripts - all that takes time to set up, but pays handsomely on all projects of non-trivial size and length.

The right thing to do is not to get rid of this "overhead" but make this setup as easy as possible.
This isn't meant to be a comprehensive list, but it does have some holes I'd point to primarily in (1) Consulting / services, (2) Enterprise, (3) Hardware / manufacturing. On the first you have time and materials, fixed fee, etc. On the second you have on-premise solutions, enterprise licenses, etc (Think Oracle, tons of security companies), and the third is, well, I'm not sure anyone needs examples: you make physical stuff that does something and you sell it.
> I mean the deeper you go the more freezes on it and the thicker it gets?

As the article makes a point of mentioning, unlike nearly all materials, added pressure is more likely to melt ice than cause it to freeze, at least at the pressures and temperatures we're considering.

The pressure of water at 10000m (basically the deepest the oceans go) is ~100 MPa. Look at the liquid part of the phase diagram between 100 kPa and 100 MPa. See how it abnormally extends left as pressure increases to ~200 MPa?
Secrets of New York's real estate agents
When I read that I immediately thought of BJ Penn. He has a rather wide face for his size. He's never been knocked out, although he was TKO'd by Hughes when held down in the crucifix position in their second fight, but I consider that different than being completely knocked out.
Note that this is exactly what is wrong with how the experiment is discussed in text books and pop culture!
Clojure (and ClojureScript) have stand alone compilers and ship very nice APIs to compile code (if you want to write your own compiler). People use lein (and its plugins) because mucking around with a compiler and then managing dependencies, setting up your classpath manually, and writing a test runner is a waste of time.

As far as text editors go, you're not forced into using an nrepl-enhanced client. I got by fine on tmux+vim with no editor support for clojure other than syntax highlighting and rainbow parens for a long time. That said, having paredit, nrepl (for code completion, dynamic eval in the correct context, documentation lookup, misc other plugins), and a test runner with easy macros in my "ide" makes my experience better. There's absolutely no reason why one couldn't just use a notepad and the clojure compiler plus whatever random build system strikes their fancy.
Some initial feedback:

1 - My first CC was rejected

2 - The spelling hint (the red line) is bad. Just type "Hollowness" and, for me at least, it underlines "Hollownes" and doesn't pick up the last "s" until I move on to the next word (and then some)

3 - Themes / font / spacing and fullscreen would be nice

4 - Tried to save a file:
Uncaught node.js Error

Error: EACCES, open '/x.txt'
(and now I can't go back, and I lost what I was writing)

5 - On startup, it now flashes the intro text, but then goes into write mode. Feels unpolished.

6 - Personally, I'd like something that helps me organize my writing a little bit. For now, I just use a folder with project view in sublime, which works great. Not sure I'm willing to give that up.
are you sure it's actually gcc and not clang, because "gcc" on OS X is clang
I use the free basic SSL certificate from StartSSL for my crowdlending analytics site PeerCube. I haven't had any issues or need to look somewhere else. I am actually thinking of getting another one for a new site I am building.
Get Started With Jekyll/Octopress on a VPS in 3 Hours
I'd like to be able to change the font size in the edit window.
Transasia Airways plane crashes on landing in Taiwan, killing at least 51
Why Do I Study Physics? [video]
Sierra: A SIMD Extension for C++
not when the 'templates' are just cut and pasted form elements from the docs.

if you're doing any kind of course work in web design, you need to be able to compose the majority of this stuff yourself from just the docs.
It's not mentioned in the article, but Composite A is rotated in a chin-up direction compared to Composite B. The difference is subtle yet distinct. Composite A's head angle appears to project a winning attitude, while Composite B's head angle appears comparatively submissive.
Some stats two hours after submission if someone is interested:

- 92 new users

- 88 chatrooms were opened

- 14 users from London, 10 Amsterdam, 8 Berlin, 8 New York, 8 Chicago, 6 Toronto. It seems like because it's so early, mostly Europe has seen it so far.
REPL-driven development is wonderful. I'm not a Clojure user (yet), but I write a lot of Scheme. My programs are living creatures that adapt and evolve as they are running. It's refreshing to see that Clojure is seeing real use in the industry. Gives me hope that I can get paid to work with a language I really enjoy some day.
This is amazing technology - but I'm curious as to how unusual it is? The article says "It feeds (fed) power from the Scattergood Steam Plant in El Segundo to a distribution center near Bundy and S.M. Blvd."

Are most power stations and distribution centres connected in a similar way? Or are they typically co-located?

i.e. are there loads of cables like this, and if not why did they do it in this case?
I occasionally have to work on (fairly complex) Android apps and I only use emacs and make for edition, compilation and deployment - the makefile calls the SDK CLI toolchain to compile and deploy (ant & ndk-build for the native side).
There's really no reason to use Eclipse IMHO - it's just an horrible mess of an IDE that hinders more than it helps.

For iOS, however, it seems you're indeed kinda screwed - you have to go through Xcode and the atrocious storyboards stuff.
Would be happy to pay the $5 to be able to use this as an addon in Sublime Text (or Atom/vim/emacs/whatever you like) instead of having to use your editor app. I don't like having to switch to a new editor for writing. Any plans for this?
Well, the "dead fish"fMRI experiment showed how fMRI data is strikingly similar to reading tea leaves .
I read it as github being the most popular example of that type of tool. If not github, then SourceForge, or code.google.com, or launchpad, or... the list goes on.

And whatever community you ascribe to, you'll have to learn how to operate within it to get community contributions.
This is a fantastic list, and it is extremely helpful to have everything in one place. The next step, IMO, is for folks like us in the HN community to put a little more meat on the bone. Annotate or link to this list with specifics for each model.

I might quibble, on a very minor level, with calling these "business models." More accurately, they are revenue sources. One could argue that this is a small distinction, but there is a real difference. A revenue source is necessary, but not sufficient, for the operation of a healthy business. Plenty of other things go into the mix, even leaving aside the obvious (product): COGS, logistics, competitive differentiators, etc. There is so much more to the success of Uber, for example, than just the "excess-capacity market" revenue model. All of what Uber does with its drivers on the back end, for instance, is quite sophisticated -- and equally responsible for the company's success as its top-line, nominal model.

Further annotation -- and I'm happy to get my hands dirty and contribute -- will also help us flesh out the pros and cons of some of these models. "Pay-what-you-want," for instance, lists Radiohead as the example. That's fine. But what a lot of folks don't realize is that Radiohead made approximately 80% of its money from the "In Rainbows" album release by selling collector's edition box sets for $81 a pop. In that case, pay-what-you-want served as a loss leader and demand driver, and the collector's sets earned the real money. Either of these tactics, without the other, would not have worked as well. The combination of the two was a stroke of genius -- allowing the band's customers to segment themselves, and in effect, adding an ultra-premium tier to the top of the "pay what you want" curve. The operative lesson of Radiohead's experiment was that pay-what-you-want can be effective, but you need to structure the pay scale to account for your customer segments' different willingness to pay for different versions of the same product. Give them suggestions, at both the low end and the high end of the product/price spectrum. If you don't, you're anchoring everyone towards the low end. And that leaves a lot of money on the table. This lesson has carried over to sites like Kickstarter, to great effect. (I have no idea if Kickstarter took any inspiration from Radiohead's experiment; this is just a thematic observation.)
Apple Confirms “Back Doors”, Downplays Their Severity
Tracking down a kernel bug with git bisect
I would suggest that the most obvious reason for putting this contest up is because you do have a whole bunch of ideas for solving the problem, are pretty convinced that the problem can be solved, and would like somebody to go and spend the few years of engineering work needed to turn one of those ideas into a working product.

I don't think this is the next X prize. I think this is closer to an open contract for somebody to build the damn thing, when that is a somewhat risky venture that none of the people offering the prize feel they have the ability to execute.
I like this metaphor because, if you get any two bike enthusiasts together, they will likely be able to argue endlessly about the details of their respective machines. And if either of them was to try to ride the other's bike, they would have lots of small annoyances and pain points.

Try watching someone who is an expert at Cocoa/XCode and you will see that they also have extremely tight, natural interaction with their toolset. They know where the rough corners are and avoid them. Their environment is already configured so that builds just work. etc.

Those of us who work in the browser have similar tools and workflows so that, once we have them working well and meld with the tools, we work very productively. Yet any time I have to show someone new how I do my work, it involves many layers of learning over the course of months before they can get to that point.

Similarly, though your workflow seems quite natural to you, I doubt it would make any sense to me. Yes, I know git and vim, and I can probably read the python code just fine. But knowing how to build the project, how to test incremental changes, how to debug and do performance profiling, and how to have a basic feeling for when I'm done? It would take me quite a while pairing with you before I felt comfortable.

What's the lesson? While there certainly are better and worse development environments, if you judge the one you know well against the one you know poorly, you will always think that what you know is best. I appreciate the sentiment that says learn one thing and learn it well, rather than chasing every fad. But I also think that, if you're going to be well-rounded or wise, you need to have the perspective and take the time to go deep in other environments before judging them.
Could you tell us more about what you ended up missing from Python ? is it syntax ? concepts ? libraries ?
core.typed is super cool, but I don't think it's liable to impress anybody who is used to Haskell or OCaml. Java, perhaps.
It's not about density. In fact, the opposite. It's about making each piece of the code dead-simple in terms of readability and functionality. When every class does exactly what you would expect it to, you can build complex structures reliably (which themselves act as dead-simple abstractions on top of the building blocks, and so on).
What kind of digitizer is there in Samsung Note Pro?

If you are so flexible as to consider Android, iOS and Windows, you should consider Microsoft Surface Pro 3, too. I am really interested to know your opinion; my email is in the profile if you will actually look into it and decide to share. For me, Microsoft tablets are an overseas shipping order away, so I hesitate a lot before buying a completely new piece of hardware.
That’s still so obstructive as to be useless for any normal adult. For example I was banned from seeing the opening times for a local brewery tour by default on my mobile connection; had to phone them up to unblock it.
Mods, please fix title.
You can't wrap it with your own scripting because compiling is too slow. That's the essential problem, Leiningen has to be the center of your workflow. There's no other (meaningfully productive) way.

What I dislike is the need to run a background task per-project, every time I work on the project. What I would like is either:

1) Faster (sub 500ms) compile times so that I can flexibly use a workflow I prefer.

2) A "Leiningen daemon" that runs when I start my computer and automatically compiles any project.clj files that exist.

3) ClojureScript to build in the browser, so that my workflow can be any text editor + refresh the browser.

Leiningen plugins cannot give me any of those things, correct?
On a literal basis it is racist because you invoke race. On a logical basis it is racist because you ignore context and treat the use of a word based on the color of the skin of the person using it. On a moral basis it is racist because one group getting offended is not any more or less valid than some other group getting offended.

Most importantly, the fact that the word is offensive to someone does not invalidate the racist double-standard. That's what context means: that the use of a word or phrase has multiple properties. On the one hand, use of the word by a white person is offensive. On the other hand, saying a white person can not use that word is racist. Both of these things are true at the same time.

You can attempt to gloss over these facts by saying "oh, historical use" or "oh, it's offensive" and many other reasons, but that does not remove the racism inherent to the double standard which is based on the color of the skin of the speaker. If the word was not offensive, it would still be a racist double standard.
Interested in collabing with you on this. I had the same idea and vision.

any way to contact you
I was curious as to what URLs are blocked by some ISPs in the UK. Here's a (maybe NSFW) list: http://uk-blocked-sites.herokuapp.com/
IEEE to Create Health Tech Product Standards
If you want the community to be involved with your code you should use what the community use. For a lot of languages today this is git and GitHub.
And the more expressive your type system is, the more that becomes true. It will be interesting to see what is done for Idris tooling if it gets some popularity.

There's also lamdu[0] being made for Haskell which is pretty interesting.

0: https://peaker.github.io/lamdu/
Have you tried a 15 minute power nap?
An exploratory data analysis of the 2014 World Cup Final
I see some different layouts you can make with boostrap but no actual themes?
You may want to check out Everquest Next. I think it would be fair to say that EQN is very close to a completely voxelized environment and at least mostly procedural. There is a great deal of curated content as well, but it seems like they are working on sourcing lots of that from players. The voxelized environment in EQN is based on Miguel Cepero's work. I believe they in fact hired him. I have been reading his blog for a long time and you can get a pretty good idea of the techniques that are being used.

http://procworld.blogspot.com/

A couple of quick hints to get you going in the right direction is that there are ( I believe ) a couple of generalized tricks involved to pull this off well. The first is using the 'correct' method to tesselate your voxel geometry. Minecraft literally uses cubes and you are familiar with the result. Another 'classic' method is the application of marching cubes/tetrahedra. This gives you fairly good organic-ish shapes but suffers from the inability to render sharp edges. Everything looks blobby. I believe the method used by EQN makes use dual-contouring, or a variant, which allows you to create organic shapes and also preserve sharp edges. A second factor is the ability to use different levels of resolution or scale for your voxels situationally. This allows you to craft human-scale things like cups and swords and whatnot, with human-scale details, and still craft houses and mountains and trees, without the need for storing extreme resolution in those items as well. It can be very tricky to patch together various bits of geometry tessellated from different voxel resolutions like this, and not end up with ugly visual artifacts. There is also the thorny issue of applying textures or materials to everything I have mentioned previously, which I have never investigated :)
You don't want them to fall on people, or brittle devices. But otherwise, they could fall onto a lot of places and things without further consequences.

If you consider a city like Los Angeles, with 3792621 inhabitants, and a surface of 1215e6 m², assuming each person takes 1 m² (ie. the person-drone cross section), that gives for fall points equidistributed over the surface a probability of hitting a person of 3792621/1215e6 = 0.0031; only 0.31% per fall! To hit a person with 1/2 probability, you'd need a rainfall of 160 drones!

Will your drone fly over crowded areas? Most people are inside houses most of the time anyways, and there's no reason to fly over the sideways.

Now, you must also consider other areas to avoid landing (or falling) on. Cars, (streets), random machinery (eg. air conditioners), power lines, etc. But all in all, that still leaves a lot of places where to crash with no consequence, if you need to crash.

IMO, there's a lot of unreasonned fears about the subject (as there is about anything else; and people wonder in other threads, why the belief that humans use only 10% of their brains persists...).
I can't wait to copy-paste one of Hemingway's novels into here and see how many issues it has with his writing.
Seems like they didn't account for weight cutting? Sadly, a lot of efficacy in the ufc today comes down to who can cut more weight and be the bigger fighter. Maybe wide faced people are better at cutting.
This is just stupid. Here are some sigils they could have easily used without much issue: #, *, +. They could have also used something like [var-name] or <var-name>.

I am convinced that at this point CSS is a clusterfuck that should be killed with fire.
This is a wonderful piece of computer science history, and is of interest less for its nominal topic (recursion) than for the insight it gives into an early slice of languages research. Well worth a full read.
in some poorly-understood conditions

This factoid gets trotted about without ever noting the (tiny) magnitude of the effect, it just plants a (false) idea in the readers mind that you can get ice faster by microwaving water first.
I guess such communities exist, but it looks weird to me. It shouldn't be like that. I mean, your project's community should consist of people who use or are interested in using your code. Whether it be hosted on github, launchpad, your own yourproject.com or another server capable of hosting the project. Hosting it is technical details; people should come to the project for what it is, not for where it is hosted at. Therefore the community shouldn't be "github community" or "sourceforge community" or whatever. Or did you mean communities such as "git users", "cvs users" and so on? I think that's still the wrong way to think of it. It sounds like a religious cult formed around specific tools.

They're just tools. I shouldn't need to ascribe to "vim community" hosted on "vimhub" even if I wrote my software using vim (I don't).