skysight-inc/HackerNews huggingface dataset:
It's not just photo. It's as simple as people just wanting to be able to do things intuitively and easily. Hey I took a great photo at the weekend, let me share it with you, here you go, done. Or you must hear this song, or read this etc. Sharing has to be very easy.

I have an Aunt with an iPad full of photos, that she's pretty clueless as to how to backup or share. She's given up trying and just takes her iPad to her friends.

I have another Aunt who can't for the life her, get photos from her camera to her laptop. It's a trial.

So if you have a phone with a camera, that lets you seamlessly share photos, even if it's through imgur, facebook, or whatever, it's probably going to be easier than connecting up cables, trying to traverse file systems etc.

My brother wanted to sell a motorbike, and wanted to send the buyer a couple of photos. He was absolutely dumbfounded by the process because his SLR took big photos that his email provider rejected. He's not that web savvy. In the end I said it might be easier for you to just install Dropbox, and it was. How arse about face is that?

Even copying files onto some people's computers doesn't help that much, if their file management skills don't exist.

OSs (desktop) haven't functionally changed that much in the last decade on the face of it. And even the simple problems haven't been solved, which is laughable when you have an insight into the complexity of some of the work arounds.
What is the DigiSpark for? Is the Pi's IO not enough? How are you networking them?
I see it rather the other way around. Copyleft licenses primarily defend individual liberty by guaranteeing the right of downstream users to modify software and distribute the modified versions, which is the natural state of things (absent state intervention, individuals can modify any software in their possession, and distribute it if they wish). The MIT/BSD licenses are freer in one sense: downstream users may sue other downstream users who use their modifications without a license. I can take a piece of MIT-licensed software, make changes to it, and then if someone uses my changes without a license from me, I can sue them for copyright infringement. The GPL takes away that freedom to restrict downstream users. Considering that the right the MIT/BSD license let you retain amounts to using the machinery of the state to restrict other people's freedom to use and modify software, I don't see how this is freer in the libertarian sense. At least, not unless you believe "intellectual property" is literally natural property, rather than a fiction created by the state.

Now, the anti-IP libertarian position would be in favor of neither the MIT/BSD nor the GPL approach, but simply in favor of abolishing copyright entirely. Then you would inherently have the right to modify and distribute any software in your possession, and wouldn't need a copyleft license to ensure you retain that right. However, so long as copyright exists, the GPL seems like a pragmatic approach to mitigate its damage.
I have two thermostats. The house has two heat pumps, one up, the other down.
You can burn most plastics too, it's not like polyethylene doesn't burn like frozen gasoline. Sure, some of them will offgas toxic byproducts but so, too, does wood smoke.
Ironically, my dad's advice to me was that college-level English is completely useless, maybe even counterproductive, and I'd be better off doing almost anything else with my time. He had a master's in English and made his living doing training (ie, public speaking) and writing books (over 40 of them).

His take is that communication absolutely critical. But what college English courses teach you is not so much how to communicate as how to bludgeon readers with how terribly erudite you are by using longwinded, stilted, and dense verbiage. ie, they teach you the exact wrong way to write.
Agreed, the community does seem pretty loose on project structure--which is interesting since the language takes such strong stances on code structure.

Since your folder structure is also your package structure, with rmux[1] I tried to separate the project into dependencies, and use a package for each one. I like to also limit files to one class--but if you read through the default package files, the creators seems to go both ways.

One interesting thing that isn't mentioned often is how to handle the equivalent of #ifdef, through +build flags. This isn't the best solution, since all functions and their arguments are evaluated (even empty functions), but it does allow for the use of constants to wrap around cpu-wasteful debug-only areas/

[1]: https://github.com/forcedotcom/rmux
Your parenthetical is a proper mystery. Clearly, "dumb" is not a single dimension, but it still amazes me to see, for example, people with both a steady job and a car covered in "UFOs are real" stickers.
Dg: Obviously the best alternative to Python that runs on the same VM.
Warrant requires probable cause.

How do you get probable cause without any information? How do you even get alerted to the idea that you should be opening an investigation into something, without any information?

I mean, how does that work in court? "Yes Your Honor, we would like to obtain a warrant to search Abdi Zullah's Internet-based communications for the next 3 months since we think that he maybe might be planning to blow something up. Maybe. And oh, this is all just a hunch, we've got no evidence at all for this yet."

You'd be laughed out of court, and rightfully so.
Yeah, this was the obvious prediction of what would occur en masse once the Internet of Things set in.

Comforting to see it's happening right from the beginning.
I'm not seeing that either, can you take a screenshot?
http://techcrunch.com/2012/05/24/betterworks-shuts-down/

===
BetterWorks, the employee perks startup led by Los Angeles entrepreneur and investor Paige Craig, has told its customers that it will be shutting down May 31.

The company offered tools to help businesses manage discounts and rewards programs for employees. In the past few months, BetterWorks still seemed to be rolling out a steady stream of new features like catering and groups and permissions. In fact, Director of Product Varun Krishna told me that BetterWorks was seeing growing interest from larger enterprises (though in retrospect that may have been a polite way of saying that it wasn’t making enough money from small- and medium-sized businesses) (...)
Obama's NSA 'reforms' are little more than a PR attempt to mollify the public
I think arch has it right with the rolling release approach containing binary packages that are built with a minimalist philosophy.

Need to tweak a package to include something else or be built a different way? ABS is fantastic because you most likely won't have to change much and the package can still be kept under package management.
"Second, even if petitioner did harbor some subjective expectation that the phone numbers he dialed would remain private, this expectation is not 'one that society is prepared to recognize as 'reasonable.'' Katz v. United States, 389 U. S., at 361. This Court consistently has held that a person has no legitimate expectation of privacy in information he voluntarily turns over to third parties. E. g., United States v. Miller, 425 U. S., at 442-444; Couch v. United States, 409 U. S., at 335-336; United States v. White, 401 U. S., at 752 (plurality opinion); Hoffa v. United States, 385 U. S. 293, 302 (1966); Lopez v. United States, 373 U. S. 427 (1963). In Miller, for example, the Court held that a bank depositor has no 'legitimate `expectation of privacy'' in financial information 'voluntarily conveyed to . . . banks and exposed to their employees in the ordinary course of business.' 425 U. S., at 442." Smith v. Maryland, 442 U.S. 735, 743-744 (1979).

Now, as a general principle, just because the Supreme Court has said something it doesn't mean they're not wrong, but the 4th amendment's use of the word "unreasonable" which is historically a signal indicating the need for judicial line drawing, puts this particular bit of line drawing peculiarly within their purview.
NTT DoCoMo backs away from early 2014 Tizen release
I think that's the unsaid part of the story, everyone secretly believes that some intelligent being placed that rock as a peace token (otherwise this kind of news won't make headlines)
why on HN top op the page comments are always not about the content but about meta / secondary stuff ?

ps.
please dont be mean, do not upvote this!
That's exactly what I was thinking - "Hmm, strange, somehow I manage to do all those things for myself without having my employer involved."

The advantages small companies have are about flexibility, not about doing chores. If I wanted to be coddled I'd work for google.
Don't want to argue, but yes it would. It would stop the user for a second, giving time to the brain to process for a while what's going on.
Stop fracking. Stop the crazy outdated fascination with having a lawn in suburbia.
You're only solving the example (painfully and incompletely as well, because now you can't sort your collection twice using different criteria, and I believe you can't sort objects you don't fully control since you can't add methods to somebody else's types — let alone a builtin, woe is you if you're attempting to sort maps). How do you handle a non-inplace sort? How do you handle implementing a treeset or a b-tree? A reference with compare-and-set semantics? Your interface won't save you from the devil of having to up- and down-cast all over the place and throw type safety into the trash.
Thermostats turn your heat/AC/fan on and off by connecting and disconnecting an electric circuit. Older analog thermostats did this mechanically; newer ones do it with electronic switches. That circuit has some small amount of current running through it to signal to the heating unit whether it's connected or not.

The control circuitry in the heating unit is sensitive to a range of voltage values. It has to be, because V=IR, and there's no way to know exactly how much wire (and thus R) will be strung through your house. The Nest can thus pull some current off the wire to charge its battery but keep the signal strong enough to flip the heater on and off.

My house has a new electronic "zone box", which, because it's all semiconductors, only needs to run a very small amount of current through the wires. That's not enough for the Nest to charge. Fortunately, the standard home heating wiring includes a "common" wire, with a low amount of constant voltage suitable for devices like the Nest.
Individual offices are far from free.
Worth pointing out (and you touch on this above) that this is not a function of electric heat but a function specifically of the type of electric heat (radiant in this case). I have electric heat by way of a ducted electric heat pump which is not zoned and thus centralized. Zoned ducted and non-ducted electric heat pumps both offer localized control over heating.
C# MCPD in web looking for some extra work here. Still looking for candidates?
Serious question: What is the benefit of having big pictures stack instead of scroll? The Aesop video has big images that dont move, but get covered up by text as you scroll. I've seen this in other websites. What is the advantage? I find it makes me lose my place on a page, but that's just me. Wondering if there's any usability research behind the stacked images effect.
Is your perfect, ideal, dream audience tech blogs? Are they literally the best source of new customers for your company?

If they're not, and that's almost 100% of the time, you should forget them and look for the best places to spend your time and energy pursuing.

1000s of pageviews from techcrunch/hn/etc may only be 10s of potential customers for your industry or niche, and then you apply your funnel and don't really have anything at all when the dust has settled.

So I would say it's worth hiring PR people to help you if:

1) the audience is your ideal audience

2) it will land you 100s of new users because of 1)

3) those 100s of new users can absorb the cost of reaching them
GNU's stance on man pages is entirely correct! For real documentation, read the info page, but you rarely want real documentation, you just want a quick example or the command-line invocation syntax, or what a particular argument does. And 99% of the time, that will be in a man page.

The problem lies when you want to find something 1% of the time, and it's here that man pages become sprawling unindexed messes. For example, take a look at the man pages for perl or zsh: you'll have no chance finding anything, as those programs are so large that they need a wealth of documentation to go into them. At the same time, the info page for ls contains the things you rarely need to see such as exactly how things are sorted or the minute details of timestamp formatting. If this were all in the man page, you'd complain that you couldn't find anything in it.
You're not wrong, but the situation is complicated by "reins" often being used to talk metaphorically about being in control. Alexander is "at the reins" of the NSA. Obama "took the reins" during his first inauguration.
Unfortunately there are several cases where users have entered an OTP code for another user. The recent high profile case was with World of Warcraft's OTP.
Yeah this is one of the best examples of people proving a point by trying to disprove it I've ever seen.

"The ecosystem isn't (that) confusing, just use X Y and Z"

- "No, use X Y and A"

-- "Who uses Y? Use C"

Myth: confirmed!
You clearly don't understand the Blub paradox. Blub is whatever language you are using.
How to Salvage your Business from a Deep Freeze
That's probably what happened.
And the data normalized per county is overrun by noise from counties with 10 people and 1 player.
> There's a lesson in there somewhere

The website that lets technologists hang out with people who might give them large sums of money to see their ideas succeed doesn't have to be good, or pretty.

If the website were better, or prettier, that would not add any additional value to the previously mentioned large sums of money.

(Oh, and advice, and being able to chat with industry leaders and experts on diverse arrays of topics, etc.)
"My question is, in 2016, will the bar be even higher? Maybe angel investors will expect a working product, reasonable traction, and product/market fit all before they put in the first $1M? How much can market-risk be proved out before any professional money is raised?"

At some point, the start-up founders have done all the work and bootstrapped themselves into a thriving business. If the VCs (or Angels) delay the funding too long, there's no value for them to add between those rounds and an acquisition.
Withings has a wireless blood pressure cuff, and makes the data available through a Web API for services like exist.io.

BodyMedia's FIT detects when you lie down and get up (so no need to push any buttons), and you don't need to transfer the device into an awkward wrist strap (since you're wearing it on your upper arm).
One of Clojure's fundamental opinions, asserted by the language eagerly, is that vector quantities should be treated as values the way scalar quantities are in most languages. Specifically, this means that when you operate with a list and append to it, instead of modifying the value of the next (cdr) pointer in the last node, you create a new list and return the new list as the result of the append operation. These immutable collections afford certain classes of algorithm that destructively modified ones do not. Rich reviews this concept pretty well here: http://www.infoq.com/presentations/Value-Values

This story doesn't spend much time discussing this particular opinion of Clojure's or why you would choose to circumvent it by making a mutable linked list. Additionally by virtue of skipping the immutability discussion, it fails to discuss how append to the head of a list is crucially different from append to the tail when working with data structurally sharing underlying data.

Additionally it prefers to define an interface over a protocol (using definterface instead of defprotocol), and it uses camelCase naming instead of Clojure's culturally embraced hyphen-cased naming.

In short this describes a way to build a data structure in Clojure, but is not a particularly good as an example to be followed of how you should build data structures in Clojure. johnwalker cited a couple more idiomatic examples, e.g. data.finger-trees: https://github.com/clojure/data.finger-tree/blob/master/src/...
Pretty often. Yes you can use mb_* functions everywhere but not all string functions have an mb_* counterpart, and forget just once and you risk blowing up the entire rest of the request. Not to mention times when you have to use a 3rd party library that doesn't bother with mb_*.

Native UTF is such an important thing... I know it's tough to implement, but come on guys!
None of those perks are free. Some of them are extremely expensive.
I always thought the main technical challenge would be the machine learning, which I imagine was made more accurate by relying on data from groups of people rather than just the one household. Although for thermostats, I really would rather it just learn from me alone anyway.
I've had this idea of minimum language version as well. In PHP it should probably done at the namespace level. It doesn't even need new language syntax, just a function to declare the minimum PHP version for a namespace and child namespaces:

set_minimum_version('My/New/Component', '5.7.8');

This could be called in the component itself or maybe by a composer autoloader. Then PHP components that expect different version could live together.

The big problem, as you mentioned, is that the interpreter would have to maintain all the deprecated features and behavior for older versions and that would make development and maintenance of PHP much more complicated.
The point is to get the reader ahead of the curve! It's not really Java they're suggesting you learn: it's concurrency. Once you learn concurrency in one language, much of your understanding carries forward to other languages.

Intel has told us multicore is the future. They're trying to get you ready for it. Less certain is whether Java or Clojure will be the new cool thing.
That's what have been found, or what was let out, no? How much does the internal watchdog wants to keep this numbers reaaaally low.. is it really adversarial?

1 employee, 9 women, after 6 years... Not a pretty picture in my mind, honestly. They employ a looot of people, and they're growing more each day... no way that's all that happened imo..

I imagine what would happen if it was a private company employee snooping on women for 6 years...
This conversation is dead, but I've expanded on this at http://www.jerf.org/iri/post/2928 .
Copyright is a property right though, and I was under the real impression that if there was any right libertarians did protect, it was property. Which would again make MIT/BSD-style licenses as a libertarian license.

But either way, keep in mind that the lawsuit you posit can only happen if the changes you speak of are not themselves licensed under a FOSS license. With GPL this is effectively impossible; you can't link GPL code with proprietary code except with certain limited restrictions (or maybe it was can't distribute, but either way no downstream should be affected by your proprietary changes). In this case GPL restricts your individual freedom even to write proprietary modifications and use them for the good of the whole commons.

Because of the "individual freedom" nature of MIT/BSD licenses, you can legally link BSD and proprietary code. If that ends up being a problem for someone else, well, so be it.
Everyone has different reasons for their choices, but speaking only for myself, none of those things matter much to me. Here's why I'm currently at a big company instead of a startup (and I've done the startup thing in the past, so I have some idea of what I'm missing out on):

1. Research-y projects. Big companies have the resources to place long-term high-risk bets on research projects that will probably fail. Some startups have a single such high-risk bet, but you can't just decide to work on whatever crazy idea you come up with because the company can't really absorb your salary for years if the bet doesn't pay off.

2. Really broad scope. One cool thing about working at a startup was that I could do whatever I wanted as long it was relevant to the startup. In fact, that was the biggest reason I went with a startup just out of school; I would have been some tiny cog on a giant team at a big company (that's not inevitable, but that's what the offers I personally had entailed). But I now have enough credibility that I can go off and do whatever I want at a big company. Since the big company has a much larger scope than a startup, there are many more things I can work on.

3. Resources. At the startup, I could take 100 machines to run an experiment and it wasn't a big deal. If I wanted to use 1000 machines I'd have to get people to ok it because I'd be eat into resources that were necessary for the company's operation. Now, if there's something I'm curious about, I can run a map reduce across the entire internet.

4. Relaxed environment. The vast majority of my team is married with kids, so the office is deserted by 5pm. There are a couple of folks I've seen stay late for a week or two to hit some deadline, but that's like one or two weeks out of the year. The startup was one of the most relaxed startups I've ever seen, but there were still month long crunches of 50+ hours/wk as some emergency came up. In principle, a startup could be as relaxed as a big company, but that's extraordinarily rare. At the big company, one of the most respected people in the office casually remarked to me that he's been at negative available vacation for all but his first two weeks at the company (and he's been here for seven years). At the startup, the most respected people all lost vacation every year because pushed up against the vacation cap.

5. This should really be like 25 or something, since it's not in the same league as the others, but I'm making a lot more money than I was at the startup.

Don't get me wrong -- there are a lot of advantages to being at a startup, and I'm glad I spent a good chunk of my career at one. I'm just saying that there's a lot I'd have to give up to go back to a startup, and the things on that list don't even make the top 30.
I'll have to defer to this paper. It mentions that the core persistent vectors are cache-friendly, but I would suspect that the llvm will always be an upper-bound for the jvm.

infoscience.epfl.ch/record/169879/files/RMTrees.pdf‎

I'm very interested in better answers to this question, though.
What about the interpretation that something that is illegal for them to do isn't illegal when a machine does it, but only becomes illegal when a human gets involved?

E.g. they can collect every detail about a person's life in ways that are normally illegal, but it's ok because no person has looked at the data yet.
Another fun fact: from the Canadian tax perspective, a U.S. LLC is taxed as a corporation. If you had your LLC while you were living in Canada you'll need to see what Canadian exposure you have for that.
Click "Per Capita" on the map. They have that accounted for.
Just give us the data and let us decide which application presents it in a form we can consume efficiently.
How bout just treat employees well, pay them fairly, and give them autonomy. That's all anyone really wants. Nobody takes a job for the free dog walking.
Popular Chrome extension bought by malware maker
The top story right now is "Decide which init system to default to in Debian". This doesn't matter much to an awful lot of people, but matters a lot to folks around here. I'd say we're not so bad off yet...

HN used to be more full of things that mattered to us. I agree that I used to go to reddit to look for stories like this. But the us here has changed some over the years.

Just upvote the stories you like and flag the worst of it and take it in stride. The whole thing is just a great big Ouija board of geek culture.