skysight-inc/HackerNews huggingface dataset:
Steve? What? We've had totally opposite experiences with him, I guess. Actually, Steve Klabnik makes me want to use Rust (and I'm generally quite happy with C++ and Ada). Very helpful, knowledgeable guy in my experience.
Uber on track to lose 2.6B dollars this year
Consider reading relevant parts of 'Creativity, Inc.' by Ed Catmull if you want another side of the Jobs & Pixar events.
7 reasons why local SEO should be more important for your business
That assumes that you have enough spare cash to buy in bulk.
Sometimes I think every issue submission form should be a multi-page wizard that starts with a few questions, like “Do you understand that this software is being maintained by people in their spare time, free of charge, and will you promise to be civil in your requests? Agree/Cancel”, before they can even reach an insta-complaint text field.
Weekend: $155.1M Cross Rogue One a Star Wars Story
IMHO:

1) Just ask whatever you want, no limits, but without expecting it to be done. There is just the possibility that it will be done.

2) Provide as many details as possible so that the maintainer does not have to context-switch to understand what's going on.

Point "2" is very important. Example: pull request subject is "fix hash table crash". Only change is a one liner like:

- if (next) {
+ if (next && ht->used != 0) {

No mention about what are the states causing the crash. Now, as a maintainer you HAVE to understand what's going on, you can't blindly merge a commit otherwise you'll likely merge many things that are harmful instead of fixes.

So now good luck with stopping with what you were doing and understanding what happens if ht->used is not 0 in that case, and the corner case that triggered it.

Instead in the original PR description, the contributor shold have written: when the hash table is reset, if there is a running iterator, next will be NULL because bla bla bla. Testing for empty hash table instead bla bla bla.

Now your effort is 30 seconds... Understad, merge, say thank you.
> DVCS is fundamentally a simple concept

It is, if you're going to simplify it so far as to avoid the problemspace by nomenclature. It's just transforming nonlinear events into a linear sequence! I guess multithreading is also a fundamentally simple concept, in that vein.
> If two branches have parent commits in common, it technically belongs to both branches.

It belongs to both branches as well in Mercurial, it just hides that information from you. An astoundingly bad idea, no? I'm not sure how mercurial hiding information from you is a "feature" in any sense of the word.
I don't follow this line of thinking. If automation implodes labor markets, no one has money to buy goods/services produced by robots. What exactly is there to be concentrated at the top? I feel you're underestimating the potential for radical change. Remember, we've only been a predominantly "capitalist" system for ~150 years (when the term began referring to a framework for economic management. Prior it was a noun referring to individual capital owners, for the most part.) It's not set in stone it'll survive.

I can see autonomous vehicles imploding things like Taco Bell too. We have fast-food burrito making machines. Why can't we have a rover delivering food, avoiding going on the road? Or why go to Walgreens for Preparation H at 1AM when a rolling pharmacy can drop them off? They can roll up, I'll walk out and swipe a phone or card and get the stuff I requested. Bookmobile's for every thing are a possibility. Wouldn't necessarily need to go to Amazon Go.

Once this technology becomes mainstream, what's to stop people rolling their own local autonomous services for their communities (after another 10-20 years of smoothing out kinks)? Only accepting deliveries from bulk producers?

What's to stop an autonomous Car2Go like network of cars moving about to pick up passengers as needed? Thus imploding automobile sales, but reducing load on infrastructure, saving communities a shit ton of time and money?

Above all, what's to stop the world from skinning capitalists in the streets if they insist they own everything we invented, and oops, no more money to buy things. Excuse us while we take advantage of your outputs. Millennials are already feeling pushed to the periphery, with gloomy prospects around wages, and debt. Populist anger is in the open right now. As things continue to go autonomous, I have a hard time thinking we'll just adapt it all to our current way of life.
Depends on what you're developing.

A few months ago I bought and modified a Chromebook[1] to run Linux natively and it works great for non-compiled language development.

Here's what you get for $350:

- 1.7 GHz Celeron 3215U (or an i3 for $45 more)

- 4GB of RAM

- 13.3" 1920x1080 IPS display (165 PPI)

- 128GB SSD (or a 256GB model for $50 more with room to grow)

- Full size SD card

- 2.9 pounds

Full review and write up can be found below:

[1]: https://nickjanetakis.com/blog/transform-a-toshiba-chromeboo...
The only comment I'll make in this thread is to link to https://news.ycombinator.com/item?id=13098744
Simple Cross-Platform File Change Monitoring
That last ditch effort is called an extinction burst [0]

https://en.m.wikipedia.org/wiki/Extinction_(psychology)#Exti...
I think you're getting hammered on this because you have a very money-centric way of looking at OSS. For some people, sharing code/knowledge is for fun, not money.

>If he tells me he can't do it at any price, then that means I can't rely on OSS as a pillar of my business.

No one is asking you to make anything a "pillar of your business"! If you choose to, great - you should also think about arranging for some sort of support (either in-house devs, a company with expertise in the area, or some kind of arrangement with the author). You don't get to come along later and basically demand support in return for some cash. I think it's the "demand" part of your ethics code people have a problem with - "offer cash" or "ask nicely", folks will perhaps agree with.

I love dogs and give away free puppies, and you take one no-strings-attached (express or implied). A year later your dog throws up in the backyard and you want me to drive over and clean it up for $100. No thanks. If you up the offer to $100K, I might do it. Heck, I'll clean out the cat litter box too. But that's nothing to do with the free puppy - if you offer $100K to anyone capable, they'll come by and clean it up too.
Ask HN: Why aren't there 3rd party laptop power adapters?
Aside from mag-safe adapters for the likes of Apple laptops, I'm just wondering why there aren't 3rd party power adapters available. Clearly, Apple put some time into designing the form factor of theirs but other companies don't seem to invest nearly the same effort. Since it's just a power supply, this seems like an area where a 3rd party could provide "one power supply to rule them all" with form factor, built in surge protection and adapters to fit various laptops.

Just wondering how, in 2016, power supplies are so bad?
Ireland had no transfer pricing rules until 2010, which was well after the 1991 and 2007 tax rulings.

http://www.pwc.com/gx/en/international-transfer-pricing/asse...
The "example" I had in my head when writing that one where I found a pretty nasty bug in a relatively small library I was using.

I opened an issue, but struggled on how to get across the feeling of "If this isn't fixed i'll need to do it myself", but without the demanding feel.

I'm completely okay with a "can't get to it now" and i'll take over and fix the problem in the library myself for myself (making a PR if it makes sense to), or completely replace it with my own code or another library. And I would never fault the maintainer for not having time, or just flat out not wanting to fix it for me.

But having written that out, I see what you are trying to say. There's no need to point out my timelines, or ask for an ETA or anything like that. At the end of the day I'm responsable for my code, so I'd be better off just making the issue about the actual issue, and set a deadline (internally in my team or to myself, not publicly) that if it's not fixed by that time I do it myself.
This piece seems to have its own agenda than just critiquing the film.
The beauty of OSS is that there are plenty of people willing to play ball, and they all can. So, in your hypothetical, one project maintainer is unwilling to quote you a price. Big whoop. Approach a company that professionally offers support for this project. Send a general RFQ to the appropriate mailing list and see who bites. There is an entire market worth of solutions.

Your hypothetical seems to be stuck in a vendor-client mode of thinking, with the maintainers just vendors-by-another-name, the implication being that they wholly control the ability to modify the software in question. If that were the case, 'no' would admittedly be a deeply unprofessional answer, and your conclusion would make sense. However, maintainers are not vendors. They're arbiters of what the public project is, but they have no control over what you do with the project in the confines of your domain. Acceptance of a patch into the public project is not a precondition for using it.
To be fair, the reason gpus can be fast on gpu workloads is that the hardware makes totally different assumptions about typical control flow across processed pixel tiles.
You can't run Call of Duty or Tensorflow at the speeds we see today on x86 style control flow. (Knights Landing proved that!)

Bugs are annoying, but so are mismatched programmer expectations.
I can't even imagine the amount of fear I'd feel if someone asked me to make some modifications to an antique violin worth millions of dollars. It'd be like deploying an update on a Friday afternoon.
Vanilla JavaScript in 2016 – Maybe the future is closer than we thought
I'm not going to invest money into my employer's company unless I get a return on that investment.

Edit: That's a slippery slope. What next? Buying a new microwave, new window blinds, a modern thermostat, softer toilet paper ...
I recently redesigned my website using Metalsmith, a static site generator. This post outlines the pros/cons of transitioning from the original Octopress static site, to a single page app (Chaplinjs), and finally back to a static site.
Show them John Oliver's segment on government surveillance, privacy and dick pics? [1]

[1]: https://www.youtube.com/watch?v=XEVlyP4_11M
My grandfather made violins as a hobby.

He would wear 20 year old pants, never ever eat out, grew most of his veggies in a garden.

He would think nothing of spending $100's on a tiny piece of wood from god knows where.
Can you implement analytics on top of those flags, plus a nice UI for nontechnical employees to toggle them faster? If you don't need those, then you probably aren't in their target audience.

Disclaimer: no relation, just playing devil's advocate.
Percentage of Young Americans Living with Parents Rises to 75-Year High
Don't get me wrong. I agree that the new syntactic conveniences have improved the overall developer experience of using C++. I know how difficult it is to improve things in C++ while still maintaining backward compatibility with the huge history it has. C++11/14 was a step in the right direction and i'm looking forward to what will come with the new, more rapid release cycles they are trying to adopt.
There is also the possibility that a Rust 2.0 could fragment the community much like with Python2.7 <-> Python3.x, which would be "undesirable" at best.
This is just a general front line support problem. A poor problem description or incomplete problem description is irritating and gets to people. The other one is the people that only show you step #4 of a procedure they are using and keep trying to point to that as the root cause while it was really step #2. An issue report should show from damn near install to the observed problem, or thorough enough logs/config/stacktrace to give people on the receiving side enough information on how you got here. I call this the A-B-C-D problem, where they only keep telling you about something breaking in C but nothing about A, B or D that feeds in.

The assume you may be wrong attitude to take in problem description is definitely something I have seen well received as a reporter and a recipient. Issues that are submitted with a tone of finality and then it turns into a problem resolved by configuration/FAQ/documentation can be frustrating, because in the triage you have to ignore such language and verify anyway.

The unassertive language also clues the reader of potential knowledge gaps in the reporter. Inevitably just by construction of the report

Also this was something that was mentioned in postgres response after I believe Uber transitioned from the technology to MySQL recently- if you are doing something massive/slightly insane it helps build a strategy. A communication issue from VPS host to VPS host for MySQL will require a different diagnostic strategy than microcontroller to microcontroller MySQL connection over an TCP/IP on I2C bus duct taped to the bottom of a Honda Civic.
There was another motto like this one. It went in the lines if "If you are not with us you are against us".
To be clear, Rust has no garbage collector, and unless you type "unsafe", it's safe. RefCell will panic when something goes wrong.

I should take this opportunity to mention that the book has been stagnating because I (along with Carol Nichols || Goulding) have been re-writing it out of tree: https://doc.rust-lang.org/stable/book/ The ownership/borrow checker stuff has been completely re-done. The existing book chapters explain it in the abstract; in the new book, we use String/&str as a motivating example, since that's an area that often trips up new Rust programmers.
I see a lot of speculation about how this is going to play out when the robots take our jobs so hey, why not join in right? Holiday week and all.

We know what people have done in the past when this sort of thing has happened - https://en.wikipedia.org/wiki/Luddite

> The Luddites were a group of English textile workers and self-employed weavers in the 19th century that used the destruction of machinery as a form of protest.

I think that once the robots take enough jobs such that the anti-automation movement reaches a critical mass (and it won't take 100% of the jobs to do that, prob not even 50%) then we'll start seeing these sorts of things happen.

Sabotage of driverless cars will be trivial to carry out and very expensive to deal with... some forms may not have adequate protection under criminal law yet, which will require cooperation with legislators and law enforcement to address (good luck with that Uber).

I'm thinking things like finding and intentionally exploiting environmental cues that driverless cars use to make decisions (releasing plastic bags into intersections?) or else using directed radio interference to prevent them from communicating with homebase to know where to go next.

Some of these may be protected already by FCC or EPA or state-level equivalents, but will enforcement be up to the task? Is the FCC prepared to monitor and enforce local signal interference for corporations? Is a $500 littering fine enough to dissuade individuals and groups from continuing in "civil disobedience"?

My core point is that if anyone thinks people are going to take this lying down then they don't know human beings. Everyone is only 3 missed meals away from doing "whatever it takes" and that's even less if it's your kid(s) that are missing the meals.

If nothing is in place when the layoffs come then it'll take no time for former workers to organize and take matters into their own hands... within that election cycle the organization will be co-opted by some other ideology which conflates their anger at losing their job to automation with race, class, political affiliation, etc.

/speculation
IMO humans are just bad at communicating in a precise / efficient way. Most people I meet / work with who are not in a technical field are usually very bad at explaining their business needs in face-to-face let alone by email or over the phone, etc... And ironically isn't it usually the case that these are the people who are (a) the stakeholders, or (b) the ones writing the paychecks.

Until technical folks start taking over the world (maybe we're in the infancy stages of that?) I think most people who want to work remotely will need to expect to be in the office regularly if not every work day.
As I read it, he was offered money to fix it. But he said he didn't had the time.
BTW, the gcaptain website is an ongoing source of interesting ship related news.
Since it's a Wall Street Journal article, to get around the paywall, hit the "web" link above and access the story through Google's search results.
yea you are right. I confused synths with 'new generation of music synthesizers capable of accurately duplicating the sounds of real instruments. ' [1]

1. https://en.wikipedia.org/wiki/Ray_Kurzweil
Perfection is a pretty high bar! Most researchers who argue that practice isn't sufficient for being the best at something still view meaningful practice as extremely useful in a broad range of circumstances.

(see an article on Brooke Macnamara's work here: http://www.psychologicalscience.org/news/releases/becoming-a...).
One place we use them effectively at the healthcare company where I work is as an abstraction over the vastly complex and varied data we have on file. Put a little more simply than the reality, we "tag" patients with various statuses, conditions, and other things. All the tags are stored in a single table. The metadata for those tags, which can be, for instance, an array of hospitalization dates, a dictionary/map of various lab values, etc., is stored in a JSONB column.

There is a "population explorer" in our web application that allows users to search for patients based on the existence (or lack) of any combination of tags, and additionally to filter each tag by the values contained. The JSONB metadata is generated in SQL, the filtering is done on the frontend, and the searching is done by a query generated in the Python backend. It is surprisingly easy to maintain and extend, and even after a year and a half, we haven't run into any insurmountable issues, or even any difficulties of note.

For instance, if a user searched for all patients tagged with a hospitalization since November 1, the following steps would happen (this is vastly different from the actual code, just trying to give a sense of how it functions):

1. the backend generates an SQL query:

select ...
from patient p
where exists (
select 1
from tag t
where t.tag_type_id = :type_id
and t.deleted is false
and t.patient_id = p.id
)

2. the backend iterates through the results, filtering as necessary

exclude_list = []
if filters:
for key, patient in results:
for filter in filters:
# each filter is a lambda generated by the
# user-defined parameters (in this case,
# since November 1)
if not filter(patient):
exclude_list.append(key)

for key in set(exclude_list):
del results[key]

3. on the frontend, if the filters for any of the desired tags are changed, a process very similar to the above is run to recompute the display set

However, on the whole, I tend to agree with you. Really the only other places we use JSON at present are in storing API requests, where the data sent with each HTTP POST are in widely differing formats, and in various intermediate abstraction layers, where data from different sources contains different columns, and we can carry forward the "outlier" columns as a JSON object for later reference.
I'm not sure I agree that is a successful way. In most cases, the person either remains abusive, or doesn't post anything else.

I think the best thing to do is to just delete all abuse.
I wonder if anyone has done any machine learning on recipe ingredients. Type in what you have available and it could come back with combinations that work. There are tons of recipe sites out there that training data could be taken from.
Haha, well, it didn't seem like that long... I ended up binge-reading the latest one over the course of two days after it came out
awesome guy ! thanks for posting.
This article does a nice job of setting up a straw man and summarily knocking it down. The original article on The Register states that the issue arises with people using Java SE Advanced features without realizing they are licensed separately from Java SE itself, particularly on Windows which (according to that article) has one installer which installs both (thus making it easy to inadvertently use JSE Advanced features).
Show HN: Anytranslate – Quickly translate words from and to your main language
What kind of application s would Rust be an appropriate for? What languages is it largely meant to replace/improve on.
Ask HN: Looking for clean frontend code to learn from
I mostly use bourbon/neat/bitter from thoughtbot as my frontend libs. I want to improve my coding style by reading clean code. Can you link me to any projects on github?
>Am I a burden on those around me? Yes? Well maybe that's okay, because being a "burden" doesn't have to be inherently bad.

Then all you have to do as a reader is personally define "burden" as "burden-that's-not-inherently-bad-which-is-okay" and therefore you mentally answer "no I'm not a burden" and the plea from the essay no longer applies.

Also, I don't assume the passion-chaser coerced the parent to pay unfairly. (That was your assumption of my answer.) What's unfair is up to the reader to decide.
> So why not have a joint EU tax code to simplify life?

Subsidiarity.

http://www.europarl.europa.eu/ftu/pdf/en/FTU_1.2.2.pdf

It's really bizarre: if the EU creates the rules directly, it is "overreach" that interferes with "sovereignty" (despite the fact that these powers were ceded willingly, never mind...), if, on the other hand, the EU leaves things to member states and just imposes principles for those rules, it's "too complicated".
It happens to me, and there are two consequences: 1) your email becomes kinda of a Twitter timeline, you from time to time cherry-pick emails to reply to, because they are too many that require a personal direct reply, and it is impossible to cope. 2) You have to make a decision, if you want to prioritize for money, you are likely not going to do the best for the user base: it is perfectly reasonable but not my pick since I'm already sponsored to do my work. However it is very likely that you get a money offer to put into the project something you don't like, and this is going to be actively bloating the project. Not an easy one.
Interesting proposal.

You still need a lot of delta vee to get a harpoon+cable from orbit to the surface. You can't just fire it straight down, you have to cancel most of your orbital velocity (which would have to be way out at geostationary). Dunno what the strength requirements of the cable would be either, but I imagine the answer is "not small".

Doing the same trick to Earth probably wouldn't be that much harder than Mars. So maybe, once you've solved the hard problems, you wouldn't have to worry so much about mass-to-orbit anyway.
You're half right, but coming from the wrong place. The fact that git is hard to make a GUI for is an intentional design choice in git. It was built to be CLI first and shoehorning a GUI onto it is the wrong way to use git. The correct way is to learn how to be comfortable in a CLI. Git's design with that web of shell and perl and C is totally fine and suited to a CLI-first application.
Auto-Scaling Kubernetes on DigitalOcean with Supergiant
I'm coming in with very little knowledge of Hawaii, but having lived in Taiwan, beef was very expensive compared to back home in Texas because there isn't really any cattle industry on the mountainous island - it's all imported. Wondering if it's the same for Hawaii and thus they stand to make quite a bit of money selling locally? Or shipping to the relatively close Asian/Pacific Islands that also don't have cattle?