skysight-inc/HackerNews huggingface dataset:
It sounds like France and the UK both played a part in early nuclear weapons development in Israel as well.
Intel to supply up to half of iPhone 7 baseband chips, breaking Qualcomm's hold
"Natural talent"? I'd chalk it to hard work.
Modular phone project abandoned a few days ago. I really hoped it would bring to the end stupid era of endless consumption where you have to replace your whole phone just to get better camera or remove micro-jack.
woah woah woah!! relax buddy, take it easy, breathe in, breathe out.

Sales will tell how bad some decisions are.
How I got a CS degree without learning what a system call is
Even with perfect information and highly experienced experts, I've found that accurate estimating is so unlikely that it it's basically a waste of time to try for accuracy. Just go with a high level vague guess and keep updating that as you go. (For project/phase estimates not individual small tasks).
Then use one of the nowadays many alternatives - there is Apparmor, Tomoyo, and GRSec's RBAC all performing the same MAC job.
The action is "close". The status may or may not be "closed", but that's not what he's doing. Read a little farther. In the brief example JSON for the accounts, there is no "status" property. In fact, there are four actions available on the account:

{"rel": "deposit", href: "/account/4502278/deposit"},
{"rel": "withdraw", href: "/account/4502278/withdraw"},
{"rel": "transfer", href: "/account/4502278/transfer"},
{"rel": "close", href: "/account/4502278/close"}
Surely a job for machine learning? There's enough metadata to spin a short narrative:

- We went to Legoland when you turned 4, here's the pics of the day...

vs

- Here's a toad we came across on the way home from school one day...
I always wanted to be known as two integers separated by a comma, but I was too late.
Nice, did they finally get a new UI?
Disclosing it publicly before it's been fixed only increases the number.
I agree with your point, but I'm not sure about your example! Can't self-driving cars "see" around the blind corner much earlier than a human could due to the fact that they have sensors on the very front of the car, as opposed to our "sensors" (eyes) back behind the windshield? They might do better!
What? It's really simple. First figure out what version of SMB/CIFS you're using and if that's compatible. Then figure out if you have packet encryption enabled and if that's compatible. Then figure out if the compatibility issue you're still experiencing is due to the volume being served by a non-Windows appliance or server. If it's Windows dig through group policy settings applied and start toggling them on and off desperately until you're ready to explode. Then after days or weeks of packet captures and support calls find out it was a known issue and get a firmware patch from the MFP manufacturer.

Easy.
As an Austin driver I can agree with the dangers of our roads but I think those zero visibility turns are solvable in exactly the manner you propose. Slowly edge out until a front corner sensor can look down the road. I'm sure there are an unlimited other factors I can't imagine so I understand it isn't as simple as that.
Send donation to your favourite open source project.
i think Apple is doing find because it still is known as a friendly and otherwise great UI; it also creates a lock-in effect because you can't just get a phone from a different vendor with the same UI;
LinkedIn Profinder
LinkedIn ProFinder is the new Craigslist.

I've been asked to participate in this "ProFinder" and am getting lots of project proposals from dip shits wanting ios and android projects in two weeks for cheap ass bucks.

This is no better than CraigsList. What a joke.

(concerning the comments... this was taken completely out of context if you actually read what was written and the subject matter. If you have no ability to interpret things that way, then by all means show them how silly you are.
Small Business Technology Transfer Program Phase I Funding for Startups (STTR)
Ok, and when would be for Cygwin ?
Mercedes is working on that and it is partly available as a driving assistant called: Cross-Traffic Assist. But I assume there is still a lot of additional work to do.

Second, it will come when cars finally talk to each other, which will become mandatory in a few years.
My question would be how can a human handle that scenario without computer assistance? You can always add a visual sensor near the front bumper of a self-driving car to safely let it peak around the corner without having to pull forward far enough to get hit.
Some alternative cryptocurrencies were created using memory-hard hash functions. Litecoin uses scrypt, for example.
OpenText Acquires Dell EMC’s Enterprise Content Division, Including Documentum
Top 5 DevOps Practices to Improve Security in Engineering
Get a human (or some other sensor) to look around the hedge? At some point, humans are going to become "just another sensor platform" for the car's autonomy to utilize. And then we can just work to replace human sensors with cheaper sensors.
The Biggest Mistakes Pokemon Go Made Startups Make Everyday
5 ways artificial intelligence will change enterprise IT
A Glorified Sidewalk, and the Path to Transform Atlanta
There are a ton of specialist printer manufacturers out there including point of sale, barcoding, wide format printing, etc. My guess is if the printer manufacturers thought there was a market for it they would do it.
Samsung may remotely kill all unreturned Galaxy Note 7's
Application development on a web platform meant for documents is inherently a hack, but the evolution of the ecosystem is reaching a point where many of the hacks are quite good. There's just a lot of inertia from existing codebases and developers used to the previous ways of doing things, and FUD from places like Google with Angular and Polymer.

Web development seems to be particularly suited to the model of building a hack, then pouring concrete over it, then building the next layer of hacks on top.
From a strategy perspective it always seems like you develop better with a clear incremental goal, even when the increments are huge. In that sense, Tesla has a clear goal to incrementally improve its cars. Uber has a clear goal to augment its service. Next steps for Google? Apple? I'm not surprised they are drifting.
> Node allows you to run isomorphic JavaScript that runs on both your server side and client side

But then you're writing JavaScript on the server side, and I think I'd rather shove live weasels down my trousers than write one line more of JavaScript than I absolutely must.
I as well received a CS degree without ever hearing about syscalls. It's not especially surprising either, considering that computer science is essentially mathematics with some programming sprinkled in. Only one of my classes used C and assembly at all, and we used it to write an assembler, not to interface with an OS. The entire rest of the degree was in Java (with a single notable digression into Scheme).
I use Spacemacs for Elixir programming and honestly, Emacs is slow, I would often type commands and then wait for it to complete. I think some reboot like Neovim did for Vim, could be beneficial as it is awesome editor, but it is just too slow to start and slow to use.

It might be that Spacemacs layer is adding additional complexity, and maybe going through Helm is the issue, I don't know, just it does take quite a bit for it to catch up. In Vim, you really are plowing through at the speed of thought.
This misses the elephant in the room.

The REST-inspired API that requires 10,000 API calls to do something that could be done in 1. This is a disaster from a simple performance perspective.

There is no simple way to build transactions on top of REST so if you need to do something that involves updating more than one data record you really are best off updating them all in one API call.

When you are writing a web front end this is all the more acute because choreographing a complex interaction with a server is a PITA with asynchronous communications.

If Fielding's thesis went in the trash and got replaced with "one click, one API call, update the UI" we'd hear a lot less carping about how awful the web platform is.

Careful reading of the http spec is a road to hell anyway because 80% of it is dark corners that aren't really used or implemented.
This depends on your data model.

If "status" is just a property on the accounts resource and doesn't have further meaning, I would tend to agree with you.

If "close" is an action or activity that acts upon an accounts resource, then his approach makes sense.

Since the context is an account that we "need to close," I would assume the author is talking about something more complex than a database field. It's probably a workflow that initiates other actions and workflows, maybe even requiring additional review. I'd want to see/understand the requirements more fully before I started down either path.
I was the original programmer at my startup. 7 years later I'm the chief architect. I've had very little time to contribute to open source projects. Any kind of creativity itch I have I can funnel into our product somehow. It would be very upsetting to me if someone got a bad vibe from my low activity on github.
I can't speak for jvns, but for my degree, "UNIX BASICS" was essentially "Command-line basics" (an intro class), and Assembly was pretty much just the actual language syntax, registers, pointers, and interrupts. The word "syscall" might have been mentioned once or twice, but only in a hand-wavy, "don't worry about this right now" kind of way.
If you are returning multiple errors of different types, (403 for the forbidden change and 422 for the incorrectly set field) then you are supposed to role it up into a generic 400. Google JSON API for more information about the right way to represent multiple errors at a time.
I agree with your sentiment. Wouldn't the scenario you posed be solved by not turning in red lights though?
You forgot something for the mobile strategy, something for web stats, something for monitoring, something for source control, something for issue management, something which shall remain nameless for team communication that breaks store and forward and interrupts you constantly, something for 'social', etc. Oh wait, and your infrastructure automation solution. And your third party DDoS protection/web cache integration... and all of this is TRULY NORMAL. We are underpaid.
Such a shame. Samsung printers were among the best in the industry.
I feel that HP were pretty mediocre in the last few years and they're just riding the hype train.

What we need are printers which are more "open". Cheaper to run, easier to service. Just like the ones Brother makes. Their toners are refillable and the drum is a separate unit. And they have Linux drivers out of the box.
This same argument could be extended to say that auto makers are ahead of Google. Correct me if I'm wrong, but my impression of the Google car was that it relied more on accurate maps, while the auto makers had better sensing hardware.
Why did you replace RHEL? You scoff at it without any explanation whatsoever. (BTW they invented RPM, not yum, and they don't position yum as a virtualization platform to my knowledge. Citation, please?)

For many of us, RHEL (or CentOS) is the only distribution we would consider running at scale because we feel they make better choices and have better policies and documentation than the competition.
The absolute volume of Lego is pretty small, and it's far more likely to be resold than discarded because it has high resale value.

Lego that rotted would destroy the brand.
Isomorphic Javascript. A shitty idea with a fancy hipster name. Ohh but it minimizes the context switching and congnitive overhead of blah blah fucking blah shut the fuck up.
Javascript was a language miraculously invented in 10 days by the great Brendan Eich and 20+ years later it's still basically the same hack of a language.

ORM. an even worse idea. Let's make data access slow except for the most brain dead example code while removing the important aspect of understanding the basics of a database. Awesome.

Webpack. Only seems like a good idea because every thing else before it is so much shittier. It's still an over-complicated hack.

Forcing JS on the server so that front end people can write crappy backend end code with a shitty SQL abstraction layer! It still doesn't solve the problem that the web is a system of hacks. It only adds to it! The backend was the one fucking place that was doing just fine without javascript.

Christ, if that's the best choice then we're all fucked. /rant

Who knows, maybe WebAssembly will turn out to be something.
JavaScript, unlike C#, is intended to be easily implementable. The team that built Mono had a mountain of work to do before that was a useful product.

Meanwhile a college-level student can probably write a JavaScript interpreter that passes all the specification tests in six months. It won't be fast, but it will work.

Yes, there are better languages, but stop freaking out. If you're such a fan of C# then work on getting C# to transpile down to JavaScript, asm.js, or WebAssembly and ignore the ugly parts of the JavaScript language entirely.

JavaScript is both amazing and ridiculous all at once. Deal with it.
Being a Product Manager: How to Get Your Products Built
I agree with your main point. Google certainly has enough data to have encountered issues beyond the progress of the automakers advancing incrementally. However, I would not be surprised if Tesla's approach is also yielding advances unavailable to Google. I would love to see their results combined at some point.

Discussing your specific example, I wonder if autonomous vehicles might learn to avoid blinds given enough crash data.
I'm fine with the Patreon bit. What better précis of his efforts' market value?
How do you run all these languages in a browser?
Develop a Winning Edge
And now you have to trust the service provider that the container runs on etc etc etc.
Run Several WordPress Sites on a Cloud Server for Less Than $5 a Month
Google has no interest in actually building cars. Google has an interest to collect the data and for such sell (or even may giving it for free) the software collecting the data.

Google is a data driven company and not a hardware manufacturer. Even that Google is building their own hardware in regards of server, server racks, and such think. But all that is only to support their data driven model.

The problem here is, that car makers have no interest to buying this software from Google and as such selling the data to Google. They want to keep the data to them-self.
12 Ways to Complain to Google HQ (About Anything)
The average lifespan of a car in California is 19 years.

Let X = # of years before true class 4 self driving cars are available to buy
Let Y = # of years after introduction before class 4 self driving cars are the majority sold
Let Z = # of years after Y where self driving cars provide the majority of trips.

Z could be 19/2, but we can probably assume that newer cars are used for more miles than the older ones, so Z is probably somewhere between 5 and 10.

That could mean that X+Y is as little as ten years away. X=5 and Y=5 both seem fairly optimistic to me.
Google and Tesla beg to differ.
Yes. Just make sure everyone is on the same page for PATCH. Multiple ways to handle it, and two very different RFCs.

On an old project our backend team agreed to support PATCH, but they wanted it based on this RFC:
https://tools.ietf.org/html/rfc6902

The front end team wanted something more like this (before it was ensconced in an RFC):
https://tools.ietf.org/html/rfc7386

To me, RFC7386 more accurately represents the idea of just sending the updated content.
That's kinda the problem, though: Unix really is worse than VMS or Lisp Machines, when measured on certain axes (and I love Unix!); rather than fix it, or replace it with something even better (e.g. Plan 9), the computing industry has instead decided that POSIX is the end-all, be-all of OS evolution, and collectively ignored all the ways that life could be better.

It's very difficult, as I get older, not to survey the computing landscape and be profoundly bitter about our absolute and utter refusal to use better tools in order to achieve greatness. It's like people choosing to eat McDonald's when they could have an affordable home-cooked meal prepared for them, for essentially the same cost.
There are some interesting ideas in here, but the argument could be stronger and more clear. A writer has to be at the top of their game if they're going after something as many people have a soft spot for as Apple.
I like to think of DELETE as "if the response to the DELETE is 200-level then further GETs to the resource should be at the 400-level." Call those responses to GET requests "2XXing" and "4XXing" respectively.

Similarly a PUT should make sense whether the underlying resource 4XXes or 2XXes, and should in either case make it 2XX with the same response.

Then POST is just a verb which does not share these semantics at all; POST <url> can be done on a URL which either 4XXes or 2XXes, and even if the post succeeds that's no guarantee that the underlying URL will now exist. POST /update-caches for example might not change the HTTP statuses of anything.
Is there any (non-PR) advantage of driving around with a passenger as well as a backup-driver?
Go Carl!

One way to support his work is by donating here:

https://public.resource.org/

And to better understand his passion for this space, see his memorial speech at Aaron Swartz's memorial at the Internet Archive:

https://youtu.be/VllJDnMcTzM
Because you should never, never, never create your own verbs.

The main reason APIs have become ubiquitous is that we have a shared understanding that follows us from API to API. That includes the concept of verbs, response codes, and how to interact with the nouns/resources. If you add verbs, you're breaking that agreement.

Also, from a technical perspective, some of the internet infrastructure - servers, routers, etc - drop things they don't recognize. Heroku for years was dropping the PATCH verb despite recommending its use for customers' APIs.. and PATCH is in one of the specifications! Imagine what would happen to your custom verb.

Don't create your own. Stick to the standards.
You should participate in sig-cluster-lifecycle. The conclusion of that sig (or my interpretation of it) was that having a production suitable cluster is - today - essentially orthogonal to having a discoverable build-your own cluster. So we are all best served by having this document for those that want to learn about how kubernetes works, but a separate approach for installing a production cluster that prioritizes correctness over obviousness. I think what you are doing is great, but I worry that using words like "support" imply that you will be offering some support for people that try to run this in production.

However, the long term goal of sig-cluster-lifecycle is to bridge the gap here, to make a production configuration easy and obvious. So I'd love to see you start using the new kubeadm work, for example, so that we can meet in the middle!
Blue Origin unveils New Glenn, a monster rocket to fly by decade’s end
This has finally been happening, world wide paper volumes are decreasing, from http://www.mypurchasingcenter.com/commodities/commodities-ar...

"overall printing and writing paper demand in the U.S. has declined by about 4% in 2014 and there will be a similar contraction in 2015"
or update

$ brew update && brew upgrade vim --HEAD
Given Vim powers our industry, it'd be neat if pg or any of the other big members of our community donated a non-trivial amount.

There is very few pieces of software I could never imagine replacing in my toolkit. Linux? I use Windows, too. GCC? Clang gets some love sometimes. Languages themselves? I'm fluent in several. Shell? I used Bash for years, now I switched to ZSH, but could go back to Bash if I needed. Tmux? I could also go back to screen if I needed to.

But vim? There's no replacement for vim. vim changes how you think about programming, how you think about software development. It is this frictionless editor (I mean, yes, huge fucking learning curve, but so is programming in general) that, even 20 years later, I will never abandon (unless I'm doing Java, because... fuck Java outside of Eclipse or IntelliJ; and yes, I've tried using that one vim<->eclipse bridge, hell no).
> It was explicitly mentioned in the keynote that you can also use only one

Oh, good! Thank you for mentioning this - I haven't found time to watch the full keynote and probably will not do so, and I did wonder how annoying it would be to use just one AirPod at a time, so's not to block both ears and severely hamper my situational awareness. It sounds from what you say like this is a use case they've put some thought into, and that's good to know.
Really really useful extension, whoa. Searching the content of pages you've browsed. I need it legitimately multiple times a day lol.

Two caveats though: 1) obviously it can't index the pages you browsed before installing the extension and 2) it's a bit unclear how to use it (in searchbar press f tab).

I'm also interested to see info on storage usage after a long time using it.
Never underestimate the power of chance. The naturally talented, hardworking individuals who don't succeed tend to not write blog posts about it.
The issue is not that they got rid of the headphone jack. The issue is they went with a solution that is not industry standard. In the past, when they got rid of something it was either in decline (e.g. floppy) or something industry standard was taking off (e.g. SSD).

The wired headphones are not industry standard. That leaves you buying expensive bluetooth headphones. For me it s a big problem, because sometimes I unplug my headphones from my phone then plug it into my laptop or into another device. Now we have no solid industry accepted wired headphone connection socket. That is a shame.

The real truth here is Apple makes solid revenue of dongles, wires, docks, and now headphones. By creating their own walled ecosystem for headphones, they gain more revenue. If this wasn't the case, they would have a regular old USB jack at the bottom of the phone. They don't.
I think they mean Sandstorm.io

Sandstorm pretty much meets those requirements:

* Your data is exportable

* They focus on security and have a non-privacy-invading business plan

* You can decide exactly who to share data with, and revoke it.

It's like a private hosted cloud - you have to pay for it yourself (once it's out of beta), but you could host it yourself, and it's open source.

https://sandstorm.io
Indeed. Calling a car that requires constant human supervision with the ability to retake control in a few hundred miliseconds "autonomous" is misleading and practically fraudulent.

If it can't get from A to B without a human behind the wheel, it's not autonomous.
Our devices should be making a statement about who we are and what we do

Should be? They already do! The author clearly understands very little about marketing.
I agree that there is a range of goals. But mostly just treating things as separate silos. They all have different focuses and cover different bases. Where a 6'6" guy who takes boxing may feel it meets his minimal needs for fighting in the modern world, a 5'2" female may enjoy the sport but reasonably feel the need for something more effective on the side for self defense.

There is also things like learning to fall which have utility in a wider context or some like archery also cover hunting etc. There is also a range of risks, as boxing is far more likely to result in head trauma than tai chi. Judo risks joint injury etc.

Basically, rather than silos I feel a list of outcomes and a 0 - 5 scale much better maps to reality.

PS: Further, people tend to use whatever they have in whatever context they are put in. Fall off a horse and know judo?