skysight-inc/HackerNews huggingface dataset:
I would feel sorry for Uber here if their drivers had commercial drivers licenses (CDLs) and paid commercial taxes for the commerce they engaging in on public roads.
I agree that you shouldn't assume any information will necessarily improve performance, but I feel that, naively, inter-car communication would have tons of useful applications.

If anything else, during the transition to fully-automated, it would be wonderful if human drivers were able to visualize the intent of the automated vehicles around them. To know that a car is going to merge into my lane in 50m, or is attempting a U-turn, is so much more useful than simply seeing a turn signal.
This is such a minor nitpick, but I'm bothered by it because I see so much performance-shaming coming from some Googlers:

The site loads large pictures for all viewport widths (ideally they'd load downscaled images for smaller viewports — it's wasteful to load a large image for small devices) and the image files are PNGs when they should be jpeg or webp (example: http://waymo.com/static/images/journey/streets.png)
I think it's overly paranoid, personally, but there's no reason not to have more backups if possible. Just adding up the few rows in the spreadsheet that have size estimates, it's going to be at least 0.2 PB. I hope they can find enough donor to supply the storage.
We tried this. Fast commits for small features gave us an unmaintainable code base that eventually didn't work anymore.
Those two ideas are contradictory. It's not fully autonomous if it only works in ideal conditions. There's already a bunch of prototypes that work perfectly in ideal conditions.
However, in gacha, cards do have weighted probabilities. Some cards are much rarer than others... probabilities of 0.001% or less for top items is not unheard.
Investors Get Ready for the Coming Electric Car Revolution
In a non-Euclidian geometry perhaps.
Fascinating. Neither of my Edge 7s have blown up yet. Should I request a refund?
That's a misrepresentation of what the OpenBSD people were getting at. They had a dispute with Richard Stallman over his deciding to not endorse OpenBSD. That does not mean that they don't like free software. Tellingly, the ports tree has an abundance of free softwares. The idea that they don't like free softwares is disproven by the very thing that they and Stallman had the dispute over.
Thanks, we've updated the title to what the article says.
Apt security update
Preface says:

One way we work to earn that trust is through our commitment to transparency about government requests for user information.

I think explanations for these kinds of things would work significantly better for making users trust Dropbox more.

No need to include those in report, but I'd rather see a page about reasons behind weird behaviors than a bunch of numbers (which might as well be random from my layman's POV).
It's a bit of a mess and incomplete but I start out running this script. https://github.com/charlieegan3/dotfiles/blob/master/bootstr...
Thanks. There could be a description on how to set the default search engine as it is a different process on each browser.
We tried this. It gave us an unmaintainable code base that our platform could no longer add features unless we threw so many people at it.
I've actually never heard of Kakoune. And I'm not too familiar with verb based text editors in general. I've been using Visual Studio Code recently and like it functionality wise.

http://jsdiaries.com/2016/11/27/visual-studio-code-features-...

I may move on to a verb based editor like this as my projects getting more complex and navigating through verb commands is a must. But can someone tell me what languages would benefit most from an editor like Kakoune? I'm assuming creating macros would be a big part of using it ?
> I'm just trying to get a picture of what was the setup before.

The setup before was Skyping with a spare laptop or smart TV, and often having to call each other on cell phones because the service isn't working.

There's huge value to good integration. It doesn't matter if the specs don't compete to building your own with a projector, computer, custom webcam. Because no one else has actually built it, and if you do assemble it yourself, do you want your org coming to you for troubleshooting constantly? Are you going to build it for every company you want to chat with remotely?

In the old HN thread where Dropbox was announced, you see a lot of the same sentiment. "For a Linux user, you can already build such a system yourself quite trivially by..."

But the benefit isn't just having your own smart whiteboard. It's having a smart whiteboard that plays well with people who aren't able to build one themselves, and plays well with other services.
This repels me for a few reasons:

- Instead of talking about their car's capabilities on the front page, they include a pathos about drunk driving. I feel embarrassed how Google doesn't have more things to say about the car.

- It looks really unattractive, I could hardly call it cute.

- It's not in production, it's in testing.

These companies are sitting on mountains of cash! And they still fail to do things effectively! Apple and Google are just sitting on their fat cashflows while the world is getting very scary very fast. I'm tired of these "technology" companies doing complete fails of R&D projects, too damn shy to leave their advertising revenues. We need leaders with real courage.
Watch Handmade Hero from Casey Muratori.
Looks more like an ancient and unmaintained API. This is AV security-firm-hype at its best.
> But some drugs could help increase one's creativity, or to "loosen up", shed inhibitions, see the world in a different light, or appreciate things you otherwise wouldn't.

They can also act as temporary solutions to permanent problems - many people self-medicate with alcohol or other drugs.
That is some nice revenue. I would assume you have pretty high margins on that as well. How long has your app been released?

I'm going down this route and making dev tools that help replace the sucky entrenched big players. I haven't officially launched a proper version (early access is going on now) but I'm hoping that I'll be able to be as successful as you are.
concepts missing from the article: 'staging' and 'commit size'.

People who have worked in code review shops tend to stage their commits, i.e. do a bunch of work but commit it with git commit -p.

Article also doesn't look at deployment frequency, and 'merge' appears only once. We don't know if these 'high impact' devs are in their own branch for 6 weeks cooking up the PR from hell. That's one way to have a high impact.
See that Senior Engineer over there with the white hair, dorky glasses and a shirt begging for a pocket protector? Attach yourself to him and listen. You'll learn more from him in ten minutes than you will in ten hours of conversation with your classmates-cum-coworkers.

That knowledge will build up with time, and someday, a younger developer will come to you with questions. Take the time and answer them; it's worth it.
Type Safety and Statistical Computing
You can read Google's initial rationale for "no steering wheel" here: http://www.npr.org/sections/alltechconsidered/2016/02/24/467...

They seem pretty clearly, however, to have changed their minds on the topic. It's enlightening to compare the information on this new site with information on the old site (https://www.google.com/selfdrivingcar/). You can see what language they've either removed, or toned down.
Show HN: Immotionar full body virtual reality suite
'backdoor' comes with the implication that it was included intentionally to allow for future (secret) access.

Where it could instead be a bug or mistake that was not intentionally included.
Developer here. While people are discussing PostGraphQL I figured it would be neat to show off a GraphQL project I've been working on for a couple weeks: the MusicBrainz schema, available via GraphQL.

MusicBrainz actually does use Postgres as its database, but this doesn't use PostGraphQL or even talk directly to the database – it simply translates the GraphQL query into calls to their REST API, orchestrating multiple queries for you as necessary. It would be possible (and more optimal) to talk directly to the database, but it'd require setting up your own server. This way, it can be pointed at the public MusicBrainz API (or any private deployment).

GraphQL is awesome and this was actually surprisingly easy to develop. Most of the work was simply around making optimal REST API calls (taking advantage of their API's subquery features, etc.) instead of doing it naïvely. Also, making sure every field and type in the schema had a useful description.

The documentation part is huge. Reading the official REST API docs [1], it's nearly impossible to get an accurate overview of which parameters each endpoint accepts (in fact, some aren't even listed in the docs), what fields to expect, or even find a description of what every field means. Compare that to the "Docs" sidebar you get in GraphiQL (click the demo link), or the Types document [2] that I was able to automatically generate from the schema. Sure, you can work hard to document a REST API and keep those docs up-to-date, but GraphQL encourages it and makes it easy.

No idea if the Heroku-hosted demo server will survive HN, but have fun playing with it.

[1]: https://musicbrainz.org/doc/Development/XML_Web_Service/Vers...

[2]: https://github.com/exogen/graphbrainz/blob/master/docs/types...
a big red emergency switch telling it to pull over and shut down may be useful.

Anything more than that would mean your system is not fully autonomous, because the driver would have to pay attention all the time. What good is manual override if there's nobody paying attention? It would also mean you need a qualified driver, you couldn't use it to ferry around children, disabled people or simply people without a license.
AntergOS Linux on Retina Macbook Pro – Late 2016 Update
Seems like an issue with skillsmatter/vimeo :(

If you're interested, we also went to CoreOS Fest Berlin this year, where I presented how we dynamically reconfigure our SpatialOS simulations and our Platform microservices:
https://youtu.be/zo_Hv0WyNTo?list=PLlh6TqkU8kg_3FpXLlHMnoVqK...
Wow, the clipboard is really a thought-provoking comparison. I'm not sure if many people are quite aware of what you said, unless they've done desktop programming: when an application puts something on the clipboard, it can put multiple formats, so that when something else wants to retrieve it, it can use whichever format it prefers. This is how you get such good copy/paste interoperability between programs.

What if pipes worked the same way? What if we added stdout++, stderr++, and stdin++, and when you write to stdout/err++, you can say which format you're writing to, and you can write as many formats as you like. And then you can query stdin++ for which formats are available, and read whichever you like. And if stdin++ is empty, you could even automatically offer it with a single "text" format, that is just stdin(legacy).

The appeal of the Unix text-based approach is a kind of "worse is better". It is so simple and easy, compared to Powershell. The clipboard idea seems like it has a similarly low barrier to entry, and is even kind of backwards-compatible. It seems like something you could add gradually to existing tools, which would solve the marketplace-like chicken-and-egg problem.

You could even start to add new bash syntax, e.g. `structify my.log || filter ip_addr || sort response_size`. (Too bad that `||` already means something else....) Someone should write a thesis about this! :-)
Well at least understand it's not the be all and end all.
1) They should have done this long ago anyway.

2) I don't really understand this. If Trump thinks it is a "hoax", why would he try to delete the evidence of their crime?

3) "One Trump adviser suggested that NASA no longer should conduct climate research and instead should focus on space exploration." Good, mission creep is the main tool used to destroy government agencies.

4) This seems like chicken little behavior. I really doubt anyone is going to "delete" any data, instead they will stop getting funding to store it, run the servers, etc. But once again, if he thinks it is a "hoax" he would want more people to access the data.
For those that did not notice: if you click the second comment by the margin, you get a comment with a step-by-step decomposition of the proof.
> This argument I'll buy, but there is a lot of really good work going into orchestration like kubernetes which makes a lot of these concerns much lower.

Can you explain more how kubernetes help with distributed transactions? I was aware they are more of a management system for microservices, not something that handles db transactions.

I've found splitting a monolith into microservices very painful because it prevents you from easily having all-or-nothing db commit semantics. It's a lot easier to wrap your entire RPC/API endpoint in a single db transaction than it is to issue multiple commits (e.g. an RPC to a microservice that writes) and worry about the large number of states that can result if your endpoint crashes mid-way.
I'm not sure if you're being serious, but it seems that the teacher was asking you to interpret why the author had the characters hide in a church (i.e. symbolism). A similarly reductionist (to your) answer would be 'because that's what the author wrote'.

I must also say that your answer was more agnostic than atheistic; the atheistic answer should be 'because they were fools'.
Why so small number of stations from Africa?
Yes, that's what I did (10 years, not 2). But it was always temporary since china doesn't have immigration.
I'm really just going by basic idea that once an attacker can run arbitrary code on your desktop, it's game over. That attacker doesn't gain anything by engineering and organizing some 'backdoor' into Skype, they've already owned you.
You would be impressed of how many people in the transportation industry plays these games.

Truck drivers are some of the highest revenue players.
Article is from nine months ago, actually. You have something negative to say on literally every Google-related article that appears on HN, but every one I've seen commits some factual or logical error. Why don't you give it a rest for a while?
Is not there a ban on political subjects this week?

Anyway it is quite a funny situation. Some climate scientists had to fight tooth and nail, to get raw climate data available.

And mirroring online data and media content, has been a best practice in some communities for several years.
This proof's use of "clear" is sorta reasonable, since they are probably assuming the reader is familiar with alternating series with decreasing terms.

I would agree that it is sometimes fairly annoying. "Proof by intimidation"

A: "it is clear that X"

B: "Sorry, why is it clear?"

A: "No, it is CLEAR that X!"
Why?

A) It is problematic to accept help of that sort from someone in your social circle. It makes you "a charity case" and that term is quite insulting. Once you are marked as "a charity case," good luck getting any actual respect ever again. So, many people resist that because they don't want to be your bitch and would rather go hungry.

B) Women face special safety challenges above and beyond that. The vast majority of men offering a woman a few bucks in charity will, sooner or later, conclude she "owes" them and want her to pay them back on her back, so to speak. So perhaps she had already been badly burned by that once, learned her lesson and was unwilling to risk it again.
Thread on the HN front page right now: https://news.ycombinator.com/item?id=13168888.
The argument is that if you aren't paying attention 99% of the time, that you wouldn't be capable of dropping whatever you are doing in order to take control. Also, these are meant to enable transportation for people incapable of driving.
The Saga of Go Dependency Management
So basically in response to reports of lackluster battery life on the smaller battery equipped 2016 MacBook Pro, they remove the time remaining indicator? LOL!

It wasn't an issue for 16 years, but now it's a problem? Does anyone buy that?
No. A backdoor is considered to be deliberate and obfuscated from easy discovery, with the intent to be secret access.

If every system flaw or coding bug is a backdoor, then defects like OpenSSL's Heartbleed would be deemed backdoors, and they're not.

Unless you're wearing a heavy tin foil hat and think the coding mistake for Heartbleed was intentional. I guess I can't dissuade you from that train of thought.
They've told you exactly what matters to them: not sexy cars, not the kinds of technology used, but the goal they have in mind. Tesla, by comparison, is building sexy fast cars that happen to be self-driving.
That is certainly ideal. Unfortunately, many (maybe even most) of the machines here are laptops which are taken home each night. I could probably overlook the Windows updates if it weren't for the noon full-disk virus scan every day, but that's a topic for another day :)
Thanks for replying, yeah I suppose I didn't think about the ramifications of having to deal with reified generics and higher kinded types. I still think they're an amazing productivity boost, and the initial 'weirdness' of learning that particular abstraction pays off a tremendous amount in code readability.

As for the 'cool paper' comment, I wasn't aware of this new jargon, thanks for informing heh. I'm not sure how well it will play outside of haskell, I've done a Scala encoding of them and it's a bit more awkward than other representations.
Beyond Seq2Seq with Augmented RNNs
This is really exciting! I see these cars all over the place in the Bay Area, so it's nice to see that they're at least one step closer in making it into a product and thus bringing it to reality.

I wonder about the internationalization of this product, especially if (or when?) it's brought to other countries and regions, such as the Middle East. In some of those countries, women aren't allowed to drive and men drive with extreme speed (and park in the most horrible of ways). While this will cut down on things like speeding / drinking / etc, it may also potentially impact social norms as well.

I'm hoping to keep a level-head about this project, but any step forward in this endeavor is worth being excited about.
As we age, we will learn it anyway.
Europe's own satnav, Galileo, due to go live
* If you look around and your the best person on the team, start looking for another job -- it will be a lot harder to get better if you dont.

* Switch employers every 2 years. Do not have loyalty unless you have stock options.

* Contribute to open source for the learning experience

* Use what works, dont focus on the hot new trends (redis, mysql, django, ror vs express, mongodb, etc.).

* learn at least one functional language really well

* learn one statically typed language really well

* learn one dynamically typed language really well

* multiply all time estimates by some coefficient C, where C is always larger than 1.

* become familiar design patterns described in Gang of Four

* learn the UNIX commands and piping really well, they will save you a lot of time.

* have side projects and dont be scared to show them off!
Sharing National Security Letters with the Public
I have friends that live in one of the neighborhoods they're testing in, here in Austin (Mueller, if you're curious). And they've said the vehicles have been performing well, with no issues at intersections or dealing with pedestrians or cyclists. It's a new-urbanism style neighborhood, with the houses positioned close to the streets, with lots of on-street parking. I imagine it's a challenging environment for the car.
Don't optimize too early, no matter how bad the itch (or clever your solution). Chances are that part could change and your optimization could have implications elsewhere or on features not yet added
Tracking down rogue bandwidth – a story of Comcast data caps and offsite backup
Most software sold as a license via a microISV has very little overhead/fixed costs. Whatever you sell you keep.

It's been a bit over a decade.
Whenever the discussion comes up about man pages and how documentation should be organized, I like to quote this section from the GNU coding standards about how Info documentation is structured:

----

Programmers tend to carry over the structure of the program as the structure for its documentation. But this structure is not necessarily good for explaining how to use the program; it may be irrelevant and confusing for a user.

Instead, the right way to structure documentation is according to the concepts and questions that a user will have in mind when reading it. This principle applies at every level, from the lowest (ordering sentences in a paragraph) to the highest (ordering of chapter topics within the manual). Sometimes this structure of ideas matches the structure of the implementation of the software being documented--but often they are different. An important part of learning to write good documentation is to learn to notice when you have unthinkingly structured the documentation like the implementation, stop yourself, and look for better alternatives.

[…]

In general, a GNU manual should serve both as tutorial and reference. It should be set up for convenient access to each topic through Info, and for reading straight through (appendixes aside). A GNU manual should give a good introduction to a beginner reading through from the start, and should also provide all the details that hackers want. […]

That is not as hard as it first sounds. Arrange each chapter as a logical breakdown of its topic, but order the sections, and write their text, so that reading the chapter straight through makes sense. Do likewise when structuring the book into chapters, and when structuring a section into paragraphs. The watchword is, at each point, address the most fundamental and important issue raised by the preceding text.

https://www.gnu.org/prep/standards/standards.html#GNU-Manual...
The Cronologics team is joining Google
Hi, original author here!

Quickly, on the "elementary" nature of the post, this was adapted from a lightning talk I gave, and so it was sort of designed to be a very quick introduction into the problem space.

Also this was meant to be (and this is my own fault for maybe not more carefully spelling this out) aimed at people just starting out with a new project or endeavor, as a warning that "just sprinkling some microservices on it" is not a magical panacea for scalability or good software design.

Thanks for taking the time to read and comment!
Virtual internet communities and commercial success [pdf]
Now we can have car trolling!
Seriously, I always thought honking was a crude way to send a message. Also people resort to flicking of headlights.
It's a general fact that any series satisfying the list of conditions in http://calculus.subwiki.org/wiki/Alternating_series_theorem is bounded by any two consecutive partial sums; the author probably expects everyone to have seen the proof of this before
The people who left from Google's self-driving car division walked in the door as the world's leading experts on the subject. I'm not sure you can say that they learned everything from Google.
Thoughts on the new Gucci song -- Selling Heroin? https://www.youtube.com/watch?v=FcXDMXuUPB4
1. Negotiate for your salary. Once got an offer I accepted which turned out to be (at least) 20% below what company was willing to pay me if only I'd asked.

2. Always test your code, and if you're writing in language you're new with get someone else to code review it. Especially if you're bugs are likely to break your company's main customer.

3. Technology is worthless if it doesn't help you achieve your goals. Software is worthless if it doesn't help you achieve your goals. Figure out your goals first.

4. Put another way, ask "why", don't just code.

(These are all based on actual mistakes I've made. You can get the full story of these and other mistakes I've made at https://softwareclown.com).