skysight-inc/HackerNews huggingface dataset:
I've updated the tutorial to include AWS a few days. Based on your feedback I've added a note regarding AWS support toward the top of the project README and in the project description field.

In some cases you'll find side-by-side labs that focus solely on AWS like this one for bootstrapping the underlying compute: https://github.com/kelseyhightower/kubernetes-the-hard-way/b...

In other parts of the tutorial you'll find sections for both GCE and AWS that highlight the different commands required for each platform - only a small fraction of the tutorial requires something different between GCE and AWS. Both cloud providers are now treated equally in the updated tutorial.
Twitter has also recently started going to greater lengths to lock up images, videos and other media. It used to be easy to download them, now it's next to impossible on mobile and a hassle on desktop.
> The only mail client that does real HTML is Thunderbird (because under the hood it uses the fully featured Firefox engine).

And this is widely considered to be a bug and a source of insecurities, not a feature. The few remaining people I know who use Thunderbird use it in text-only mode in order to control its HTML-rendering tendencies.

Most people don't want a full-fledged browser in their email; it opens up too much attack surface, opportunities for "read receipts" and tracking cookies, etc.

That said, I think email is a good and underutilized tool, and it's unfortunate that more MUAs don't support features like digest handling properly. I think there's a pendulum that's going to swing away from public services like Facebook and back to direct-communication services (Snapchat might already be arguably a part of that) and email is already well-positioned there.

But forklifting the web and HTML into email clients is probably never going to happen.
When you build a better language, server platform, viewer application, development tools and ecosystem that can create, render, transmit and load dynamic user interfaces over the wire - even rapidly on limited bandwidth connections - please let me know ;)

I'm not saying it's the best thing ever, but we're not doing too badly all things considered.

The web is still young. Let's work together to make it what we want it to be - what it should be - instead of moaning about what it isn't.
I tried with http://њњњ.срб , which Firefox copies correctly, but Chromium copies as http://xn--g2aaa.xn--90a3ac/ — not very useful.

This is a different mechanism to the path part, where both Firefox and Chromium give https://ru.wikipedia.org/wiki/%D0%A0%D0%BE%D1%81%D1%81%D0%B8... rather than the readable https://ru.wikipedia.org/wiki/Россия
Ok, fair enough, but the term is still bad :)
No. That's for us to do. Not to buy.

Aspirationally speaking: I agree. Practically speaking: everyone is already buying it.

It might even be a paradox of Apple's success that the author is writing what he is. Apple's popularity is, in no small part, due to selling people a statement to make.

The appetite for buying the branding of individuality has existed for ages. Apple was the first to master using that style of marketing for their tech. But Apple is a default choice now, everyone uses it and everyone copies their style (or even when Apple is following a trend, everyone else follows it because Apple does).

Apple sold people the high of a luxury product everyone could have and show off. Now everyone has it, and we're all coming down. Apple is bland now, GIVE ME SOMETHING NEW!
"Stepped up to challenge" is a reactionary response.

Something challenges you, your reaction is to ignore/quit or step up and respond.
I disagree. In the example, account 4402278 is a resource represented at /accounts/4402278; actions on that resource should be performed … on that resource, not on some other resource (e.g. all accounts, at /accounts).

This also gives increased future-proofing, since someday one might have uncloseable accounts; those accounts could still live under /accounts, but would simply have no /close endpoint (as opposed to having /accounts/close, which sometimes works and sometimes doesn't).
Other commenters are correct that POST /accounts/4402278/close is not right (and also fairly hilariously contradicted in the next section).

Account status (open, closed, suspended, whatever else) is a property of the account, in the same way that the account owner's name is a property of the account. If you went to all the trouble to represent each account as its own resource, which I assume responds correctly otherwise to GET, POST and PUT requests, why is this one property special enough to get its own endpoint? Why would you not just PUT or PATCH the account to change the "status" property to "closed"?

In my experience, programmers typically break best practices in this way when there is special logic that needs to happen when the property changes. In other words, PUT is fine as long as it's only overlaying new data and not triggering other processes, but closing an account kicks off a whole host of internal processes at the business, so it seemed reasonable to someone to make it a separate endpoint.

This either represents a friction between good API design and what programmers find reasonable ("I have to make a bunch of special things happen, so I'll bundle them into their own function and expose them"), or the API framework isn't flexible enough to supply hooks to insert logic at field-level changes, or both.
Closing it may not delete it, but simply mark it as closed.
No, RDS does not give users the SUPER or FILE privileges, which are required for this exploit.

The whole thing is a bit overblown, given that application users at any security-minded company won't have either of these two privileges either.
Agreed.

My suspicion is that they are way ahead of competitors in terms of data from testing self driving cars and realize there are still so many unsolved problems that true autonomous vehicles aren't going to happen nearly as soon as competitors claim.

For instance, I see self-driving Google cars on a daily basis here in central Austin. There are a ton of zero visibility turns where you have to slowly edge out and hope no one is coming because visibility is blocked by a hedge.

How can self-driving cars handle that scenario without delegating to manual intervention?
Fidget Cube
So what exactly are the front-end stack haters proposing as an alternative to hack-on-hack? Should we just dev/maintain N code bases of native apps to run on every OS and then somehow connect them?

Haters are missing the big picture...
> is this really true?

Not in my experience.

As an undergrad MechE, I spent a lot of quality time with Fourier transforms in control theory, vibrations, solving pde's, and math classes. As a graduate CS student, the FFT got a lot of attention in algorithms (for the DFT), computer vision, and robotics (signals filtering) classes.
I can't speculate on the economics part of it all, but I have a different take. I think it will lead to another renaissance of sorts. Assuming that AI and automation are well done, it will give people a lot of free time to indulge in activities like art and philosophy more than what is possible currently (if one doesn't do it, then at least appreciate others' efforts). Liberal arts will come to fore again. There will be more intellectual activity that isn't tied to technology. Wars will become rare (after the last war to end all wars, of course). Fewer people will die (at least in non poor countries) due to advanced medicine. I am not sure what all this critical thinking etc and over population will bring about though. Probably a combination of natural phenomenon like super bugs and massive solar flare will take us back to early 1900s.
You may be operating under the misapprehension that "POST" means "CREATE".

It WOULD make a nice set with CRUD operations:

POST - Create

GET - Read

PUT - Update

DELETE - Delete

But that's not actually how the HTTP verbs are defined[1]. Instead, my own mental mapping looks something like this:

GET - read information. Must be idempotent and side-effect free so this one really IS just for reading.

DELETE- delete. Usually pretty obvious except for arguments about whether a "soft delete" (mark as deleted but don't remove from the underlying DB -- like a bank account which can be closed but continues to exist (its account number, for instance, is never freed up).

PUT - update things. Must be idempotent. If you're a stickler for doing things right, this should NOT be use for a "partial update" (where you supply a few fields and everything else is left "as is") but only for a "total update" (where the new thing you sent in replaces whatever was there).

POST - "do it". Means to do the obvious thing (whatever that is for this URL).

PATCH - great idea. Maybe in a few years support for it will be ubiquitous enough that we can actually start using it. If we DID us it, this would be the partial update variant of PUT.

OPTIONS and HEAD - occasionally used at a framework level. You won't ever use it.

everything else - don't use it.

[1] - https://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html
Just my two cents, but you asked for it. I give all young engineers the same basic advice "Follow your gut". If you are religious, pray about it. If not, meditate about it. Either way, the answer will probably be screaming at you in the first minute. Now having said that, I have two more pieces of advice.

First, is to see the value in every job along the way. I started out as a hardware engineer, but had this nagging voice telling me I wasn't in the right job. It took a while to realize that my heart was in software. At first I felt like I had wasted career time as a hardware engineer, but then I realized I was much better at certain software problems because of my hardware background than others. If I take inventory of all of my jobs, even from high school, I realize that I have skills to this day that can be traced back to them. Even the ones I absolutely hated.

Second, while finding your niche is important, also find the right boss. Bosses have almost as much to do with liking your job than the work itself. I actually think it is harder to find a boss worth working for than finding work I want to do.
I was talking specifically about layout (because the comment I was replying to mentioned layout specifically). I don't think any of the things you listed promised to improve layout, except flexbox and grid. And flexbox does improve one-dimensional layouts -- vastly so. I suppose the jury is still out on the grid spec, but it is in the process of being implemented by all the browsers and you can actually play around with it (behind feature flags).
And here I am, upvoting both the post and ... mostly the critical comments.

Guess I really enjoy you folks discussing :-]

Edit: seems I didn't make myself clear, I actually enjoy reading it and feel I learn a lot from it.
My Secret Eight-Dollar Guaranteed Flight Upgrade Trick
I don't know how much Google is perfecting the technology, but I agree with the sentiment about the other car makers. There should be the equivalent of a "do no harm" first approach when AI technology crosses some threshold and goes into life-or-death territory. People who talk about how computers are safer drivers than humans in the aggregate still don't seem to ask questions about the split second decisions humans can take when they are about to crash (and in general, all the pattern matching instincts humans have in potential crash situations)

http://bogbit.com/vancouver-man-sacrifices-self-to-save-wife...
http://www.ebooktrove.com/Asimov,%20Isaac/Asimov,%20Isaac%20...

The Dead Past by Asimov.

I also recommend this story for a very refreshing view on government agencies.

--

(Spoiler alert)

The issue with such a device is not being able to see people's lives unedited, but that "the past" also means "a microsecond ago" - which turns that device into an ultimate spying/voyeur tool.
...and? There are plenty of things that were "designed" for one thing and used for something totally different.
Isn't it a subset of PDF? I thought the rasterisation happens on the host.
Had it been any other company, the same article authors would have ripped the producer a new one.
>the mere mortals around him

I think I can empathize with your view, now.

Your mileage may vary, but as a mere mortal I personally find it much more reassuring when the role of luck is recognized.

Too many narratives are akin to:

"Well, I worked very hard every day without stop and tho I struggled at first - with how hard I was working - eventually the fruits of my labour yielded this unbroken string of successes thereby reaping my just deserts"
I had (bah, still have) one of those, and I ended up replacing it with an earlier Samsung (and mothballing the 2165).

It was awful, and it didn't let me use generic toner. I had to flash it's firmware. Way too much hassle for a printer.
Back in college I worked as a iOS and Mac technician at a Apple Store Genius Bar. First couple of months working there I noticed we had a yellow safe under our bench. My supervisors informed me the safe was for swollen batteries, hot iPhones or anything that could explode or catch fire.

Needless to say I only ever experienced one dangerously swollen battery on a MacBook. Food for thought.
Back in college I worked as a iOS and Mac technician at the Apple Store Genius Bar. First couple of months working there I noticed we had a yellow safe under our bench. My supervisors informed me the safe was for swollen batteries, hit iPhones or anything that could explode or catch fire.

Needless to say I only ever experienced one dangerously swollen battery on a MacBook. Food for thought.
Why bats ‘waggle’ their heads like adorable little puppies
man, its not updated in real time, it just queries another API, the way you put looks like it has some database, or it stores something internally.
Also, you should really consider to add support for non-promise, not everybody like promises, and native promises in node world are not that good yet.
I should've included a "I have no idea what I'm talking about" disclaimer. Thanks for the info, just read a bit more about it.
A computer screen connected to the Internet already has ridiculous distraction potential, seeing multiple windows simultaneously makes it even worse.
You could PUT the entire value of the resource representing account 4402278 (to include owner's name, contact information, history, &c. &c. &c., or you could PUT a custom range to just update the account status, or you could POST just the update. Honestly, if custom ranges worked a bit better, that'd probably be the best option.

Given that they don't, really, I think POST isn't terrible. At least it's not GET!
Those "UNIX BASICS + ASSEMBLY" courses are where I'd expect it in that list... Not sure how you could cover those without at least mentioning them.
There isn't much of a difference between web and application development in my eyes. Both should be build on a service backend, with a common architecture making different systems work together through APIs or MOX-agents.

In that world the "view" part of your system might as well be web based. Making front end look and feel good, is terrible in everything anyway.
Exactly what people said about those first yellow Sony Walkman headphones.
In CRUD, delete is rarely a hard delete that removes the data entirely. Best practice in most situations is setting a flag to mark it deleted. Closing an account is the same behavior - you are not purging the data, rather setting it to a closed/deleted/archived state.
I think it's more differentiated than that. There were big efforts to have convoys of trucks drive themselves on freeways many years ago. Freeway driving seems pretty solved and save at this point and probably more reliable than human drives. So not realising that does no good. Driving on icy country roads with pedestrians walking on the side is a totally different story. So I think we need to look at this by functionality. We will only learn sooner by releasing mature functionality sooner and can fund research toward more automation. I don't think this is fundamentally different than releasing a web site with all the features you could want on day one. Granted it's like a website handling incredibly important operations that you don't want to go wrong. But that's similar to banking websites, health care applications etc. We didn't insist surgery robots to be a full surgery replacement day one.
Congratulations on the release but I can just discourage people to use URL shorteners. They obfuscate key information, are potentially a security risk as a result, require extra http requests and what happens in the future when you turn the service off? A trend I've never fancied.
It seems to have gone in both directions, the class drivers on Windows are pretty much all configuration and little or no real software. However most printer manufacturers can't seem to resist bundling extra software to manage the printer, sell you consumables, etc.
> Lots of lower tier CS programs like mine seem to really just focus on popping out Java programmers that can work on enterprise systems.

Even in higher-quality ones, OS (and thus syscalls) may not be covered if the curriculum focuses mostly on, say, computational science, or PLT, or formal methods.
This is gold and I am stealing it. Thank you.
https://blog.documentfoundation.org/blog/2016/09/07/4420/

This has the list of fixes in each RC:

* https://wiki.documentfoundation.org/Releases/5.2.1/RC1

* https://wiki.documentfoundation.org/Releases/5.2.1/RC2
I can't give you 'realistic' drum sounds, but I was working on an approximate recreation of a Roland analog drum machine using only Javascript. I got the sound engine down more or less, but kind of fell off the rails when I moved away from my earlier, crappier sequencer and started using a framework.

The sounds should work across browsers when you're manually playing (use the bottom row of your keyboard) but when sequenced playback happens, things get weird. Chrome more accurately reproduces the sounds as I'm imagining them.

Grab the whole thing at https://github.com/leviathant/BossDR110/tree/feature/synthes... or just play around with it yourself at http://bitrotten.com/dr110/webaudio/
Falcon – a Chrome extension for full text browsing history search
He did drop some platforms, although nowhere near as many as NeoVim did:

Omitted in this version are:

The 16-bit DOS, OS/2 and Amiga versions, these are obsolete.

The 32-bit console version for MS-DOS/Windows 95/98

The 16 bit MS-Windows version
Old Style and New Style Dates
9 security tips to prevent Express from getting pwned
Y'see, I don't think the writer "really" cares what the devices look like. I think the article attempts to hide a very serious, terrified, heart-felt objection to the f*ing horror of the Western military-industrial complex' relentless pseudo-enslavement of those it claims to protect from those it funds/equips to attack them, in some drivel about 80s futurism and design aesthetic. For that, I find it rather clever. That you (and several others commenting here) missed its point suggests it did its intended job quite well (as I see it).
This is pure gibberish. Mutations don't have any effect other than their consequence in expressed form - a mutation that alters protein folding is just a mutation like any other. And biologists generally hate the concept of "evolvability", which usually (as in this case) has no mechanistic basis.
I mean, we're running up against one of the problems which metadata systems have to deal with, which is that metadata about an object really "lives" in parallel with that object, and not really "contained within it". But usually you just think of an object as containing all of the metadata we know about it so far, and under that model this makes perfect sense.

To do this in 100% RESTful style you would therefore probably store details about how an account was closed in the /accounts/440278/closed reference, so a PUT is correct, with GET /accounts/440278/closed returning either a 404 for accounts which are not closed or else the metadata about how the account was closed. This could live in parallel with a cache that's on the resource itself describing whether it was closed or not.

So, POST or PUT, with the PUT exposing more of the metadata interface to REST and POST putting more of it in the request bodies themselves.
In tech, some people (not you, other people) might need an article titled

What Could I Possibly Learn From a Mentor Twice My Age?
yeah, my next phone will be an Android again. I've tried both ecosystems, and the iPhone world is just too locked-down and anal for me. Others will undoubtedly disagree, and that's a good thing.

I'd be interested in how the costs work out for designing and manufacturing a phone. Are we near the point yet where we can get them built cheaply to spec? Are the parts commodity enough now that putting one together in the shed is do-able?
Facebook fails to halt legal bid over nude teenager photo
Couldn't Yelp just leave the comment up but add a message to note that it has ruled as defamation by the court? Maybe the court should structure its order like that, so that no content has to be removed but the plaintiff can get some relief.
If it's included in the box, they're still selling the adapter: it's just that they're selling it as part of the purchase price of the phone+adapter combination.
Facebook is imposing American censorship on the rest of the world
In emacs, helm-buffer ("<SPC> b b" in spacemacs) has basically replaced tabs for me, and I haven't really missed them.
David Cameron to Quit as Tory MP for Witney
How to Incrementally Switch to webpack
Show HN: New Photography Website Powered by Node.js, Bootstrap and Cosmic JS
Evolution in action – video of bacteria gaining antibiotic resistance mutations
Happy to improve the tutorial to incorporate the production approach that should be taken for each task. The main goal is allow people to run through a cluster bootstrap step by step so they learn how things work.

If you don't mind filing a few issues on the project I'll be happy to rework each lab to start addressing these concerns. Until then I've added a note to the README regarding production readiness, but that should not prevent people from learning.
It seems like both Google and Apple are having big troubles with their car programs. For either of them, why not attempt to acquire Tesla?

Wouldn't that launch point give them a huge leg up against the other?
I personally find the subject-changing 'what-aboutism'of Chomsky-ists tiring and repitive, but I'll bite.

Iran is currently the largest exporter of religiously inspired extremism, bar none. They are not engaged in short-term realpolitik that installs favorable governments in previously unfavorable countries. The IRG and Quds forces are true believers who see it as their duty to cultivate religious extremism across the world, and have been practicing their trade for the past several _decades_. There is no other country in the world that has been as deeply committed at all levels of government to fomenting sectarian violence throughout the world for nearly as long, and this is why Iran has such a powerful sphere of influence. These groups see the success of clients like Hamas and Hezbollah as their crowning achievements, and have been actively cultivating similar groups for the past several decades.

Again, the indisputable fact that I keep harping on is that Iran is the largest exporter of religiously inspired violence, bar none.

If the same was true of Saudi Arabia there is no doubt western liberals would have no problem publicly flagellating themselves, but since America is currently hostile towards Iran there are inevitably 'what-abouters' who will pop up and defend the propagation of violent interpretations of Shia ideology.

If you would like to contradict this fact, you could probably start by naming the US forces that Christian theology using torture, bombings, and creation of fundamentalist Christian terror groups. Until then, Iran is the largest exporter of religiously inspired violence, bar none.