skysight-inc/HackerNews huggingface dataset:
"The problem is not the problem, the problem is your attitude towards the problem." - Jack Sparrow

So many times I've seen someone struggle to implement a poorly written spec rather than just say 'hey can we just do X instead?' If X solves the REAL problem then sure you can.
Happy New Month to All Our Dearly Beloved Reader and Followers
Scroll down to "The end of the level playing field" on 2/06/17.
2 party consent is the case when you're in a private space with someone else and have a "reasonable expectation of privacy."

This is not an absolute thing. For example, a shoe cam to look up skirts doesn't fly just because you're in a public space.
grep's good for sure but the comment you are replying to is a reply in turn to someone speaking specifically about powershell piping capabilities. personally i am a unix person, not a windows person, but i believe that for a tool to be most effective it should adhere to the workflow of the platform it is written for. since wtrace is written for windows it makes sense to expect that it should integrate well with the windows way of doing things.
Except that we don't really have time to implement it because we're too busy posting to the resulting Rust vs. Golang foodfight.
I know, all these European migrants are running around out here scared because Lord Merkel tells them to be when they have nothing to worry about

Its a hard point to convey without really spelling out the underbelly of American society
It's my understanding that border guards are trained to ask random questions and assess your body language while answering. The important thing isn't the question or the answer, but how you answer.
Physical activity is not associated with two-year weight change
I suggest talking to most recent grads of a program as things change all the time. For example, schools which previously had good placement may hugely expand number of cohorts - and not scale out job-finding resources or company partnerships.
That would seriously be an AI milestone that makes AlphaGo look like 'Hello world'.
definitively: https://github.com/gchaincl/httplab/issues/4
can u elaborate on the predefined request-response case?
> As the article points out, there are all too many HTTP libraries that only support GET and POST, not the more "esoteric" verbs like PUT and DELETE.

GET and POST are all you need: "Return representation of available operations" and "apply this operation". It's the lambda calculus applied to the web (see Waterken's web-calculus for a more formal treatment).

You might say that this is too anemic a foundation and you want more built into the protocol level to handle some common tasks, but I'm not convinced it's necessary or even desirable. At some point requirements will change and some of those tasks will be supplanted, but we'll have to live with them forever if we bake it into the protocol.
Not much of one. The amount of time it takes to allocate the memory and free it is the dominant factor.
You can sprinkle links/rel and use custom/vnd mime types (and include links to the correct json or xml schema) and then a developer can figure out how an API works just from an endpoint, yes ..

but that's not what this person is saying. The thing about SOAP is that it is very concrete and a standard. Yes you get implementation glitches/bugs here and there, but for the most part, you have a standard definition for an object and a standard way to describe it.

It's so standard you can point a debugging tool like SoapUI at it and it will construct a nice little form for filling out all the objects you want to pass with the correct types.

There are other terrible things about SOAP and it's difficult to version/add functions/update/blah blah, but it was concrete.

You could create tools to auto-discover all the paths in HATEOAS implementations, but it's still not quite as concrete as SOAP. Most people don't and rely on documentation to build clients with the right schema/requests/types. REST/HATEOAS are concepts and you document your formats, marshallers, etc. SOAP/WSDLs describes the entire data-interchange in a much more concrete format.

As much as I hate SOAP, I wish we had a more concrete interchange standard that wasn't as terribly complex.
Stanford Engineering Hero Lecture: Kenneth Arrow (In Memoriam) [video]
They would have to strip advertising for this to be worth it
Is this necessarily a bad thing? Arguably, the NSA as an institution does unconstitutional things. Breaking it up and sending the resources out into private industry might free a lot of value that nobody would otherwise see, and keep the US government from surveilling its own citizenry and then using the information against citizens.
I'm so excited an anonymous and angry member of the tech community is having such success at acting like everyone else is dumb and they are smart. This novel format is not at all tedious chest-beating that is then retroactively "satire" because snark verging on feral rage is fantastic. To whomever started the rumor that it's yet another didn't-and-never-will member of the community here should be ashamed of themselves. This is art.

I especiky like how they meticulously avoid the majority of social issues to really drill down on the arbitrary tech decisions. That's how you know it's true satire and time we'll spent.
Growing problem: Pot lights give ham radio operators a buzz – KRDO
If your algorithm is such that everything can be placed on the stack then GC gets you nothing.
In what ways do people see twitter as a cesspool? Im just genuinely curious because I get a lot of value out of twitter. It's a great way for me to be exposed to new work from artists, finding circles of people with overlapping niche interests, reading political dialogue and analysis, funny stuff...etc
How accurate are those curated lists?
> Although PUT is not necessary using it for idempotent calls like it was designed to do actually helps developers using the API understand the intent of the call better. They don't have to worry about undesired consequences/side effects.

This can also be solved by futures. Any POST that you'd like to retry, which will be any of them given the unpredictability of network partitions, can be bound to a future so the operation is applied only once and all future attempts simply return the bound value.
Yeah, I understood that. The ones in the middle are generated using their voices. You don't find that amazing?
No but seriously... so much this. Pardon my casualness.

Whenever we strive for both 'quality' (of information, talk/debate, etc.) and 'brevity', we end up with the exact opposite of books: traits d'esprit as they say in french, #randomWordPlays of the empty kind that made Levi Strauss hypothesize that humans didn't really form sentences but rather patched together chunks of expressions they had memorized (he was proven wrong by linguistics later on, but damn was his assumption so impeccably fitting much of the anthropological data). See any bland instance of "cheesy jpeg + logically flawed pensum" boasting thousands of likes/reshares circa 2017 to prove this point.

It's nothing new either, for as long as documented human societies existed, mind-numbing memes apparently were part of the landscape. For about as long, some (always much fewer) people prefered reading books. Or even writing them.

I don't think Twitter can ever be anywhere but at the far opposite side of books and quality discourse. Or it would become something else. Twitter is meant for remarks, quick-shot killer moves, and plugs. It's basically an ad board for opinion, and you've made a sale when someone likes/shares your tweet. Some people might defigure the sacred columns with a Shakespeare quote here and there, but vandalizing its culture is the only way to make a smart tweet.

I think it's OK that Twitter is 'dumb', as in non-filtering. Neutral towards speech, unpurposed. We need that too, just like we need curated libraries. It's fine that people have a place to vent and unwind. So long as they don't mistake that for an actual forum of opinion, let alone representative of anything but the few 'influencers' and their circles.
I'll work on it here: https://github.com/gchaincl/httplab/issues/4
Still no RCA? I'd love to hear what the issue was for this. A couple of coworkers and I are betting that it was a networking issue of some sort.
It's not about recognising a terrorist, it's about recognising a liar and uncovering information.
I'm still breathing a sigh of relief that it's no longer the Haskell Evangelism Strikeforce. People can preach Rust all they like, but Haskell scared me.
Does GCS support events yet?
I'd subscribe to this if it was a newsletter! OP where do I sign up?
Most big store parking lots tend to be legally mandated vast wastes of asphalt. New Urbanists celebrate Black Friday as "Parking Day": taking photos of nearly empty parking lots on supposedly the busiest shopping day of the year.
In Rust
New mobile-first products should consider GraphQL over REST. There's a lot of benefits that you will probably end up doing yourself in a bastardized version of REST anyways, like field restrictions and multiplexing multiple unrelated data requests over the same network call.

GraphQL handles these cases elegantly.
Yes. By "supporters", I meant funders, allies, etc. Not voters. Maybe they just got trolled.

Or maybe not. But let's see how the next few years go.

I'm not arguing, by the way, that any other politicians would have represented them better.
What are your problems with Google Analytics?
"Why is exactly 140 still the right length?"

That's common knowledge. They were asking, why is it STILL the right length?

If Twitter want to encourage short form content, there are other ways to do it. Either hide 141 onwards behind a [+more] link or style the long ones differently so they have less impact.

Better yet, create multi-panel tweets so content is still presented bite-sized, but in a way that people can delve as deeply as they like.
In accordance with federal law, I must dutifully inform the author that there are at least five Mozilla employees working on Rust, thank-you-very-much.
hey I don't see deep learning anywhere, that's not the hackernews I know
Thanks. I can certainly see how time-series & planning actions are currently a tough fit for existing approaches. (I always chuckle a bit when I see things like having to turn time-series into stationary distributions, effectively attempting to remove the time information from the data completely)
Because the way the bill apparently reads, anyone in a protest could end up with their property seized. Great way to bankrupt the Quakers, I suppose. Ensure that a few goons get into the next anti-war protest. Have the goons hype up a few unstable protestors into smashing a 7-11's window. Arrest everyone, and confiscate all their property. After that happens twice, all the Quakers are going to never organize again. Chilling effect. Luckily, Arizona didn't pass this, someone must have come to their senses.
If only we had basic income so everybody could be paid to produce content like this.
Fantastic!

Humour is generally downvoted on HN, because us programmers (mostly) take things too literally. But, seriously, tech really is the biggest laugh because we take each generation of software, language, platforms so seriously, completely ignoring the fact that we are just glorified typists trying to find patterns where none might exist even without having the necessary background to do so.
The problem with that theory is that it's wrong on the facts. The federal government has consistently been about 19% of GDP since the 1950s. Your wages are no more eaten up by bureaucracy than was your grandfather's.

See epi.org. Wage income has been flat for the median earner since 1979, despite 128% productivity growth. Nearly all benefits to increased productivity went to the top 10%; 80% of that went to the top 0.1%. Return on capital is doing nicely. Return on labor, not so much.

For the 2/3 of the workforce with no college degree, real wages since 1979 fell 28%. Before you start feeling smug about getting on the right side of that divide, remember they vote, too. Ergo: President Trump, the man who promised to restore their jobs (and wages).

How to let everyone participate in a prosperity so unevenly distributed is the central problem of our time. The solution will not be found in flexible work hours. It will require a lot of work, starting with understanding that the capitalists will not give up their winnings easily.
Ignoring the dissertation is OK. It was designed for people to understand how the web was designed, not as an implementation guide.

Ignoring REST is impossible, the web is built on it.

- The uniform interface is in every URI (if you use them, you use REST).

- The code-on-demand constraint is everywhere (if you use JavaScript, you're using REST).

- Hypermedia is everywhere (if you have links on your web page, you're using REST).

- The client-server constraint I don't even have to bother explaining (although WebRTC might bring P2P back in the game).

- The layering is everywhere (if you do haproxy, varnish, squid or similar, your using REST).

The _RESTful API_ thing is just a myth. People needed a name to discourage tunneling RPCs over HTTP, so they invented these loosely defined terms to push the idea. It should be called HTTPful, because it tells more about avoiding re-implementing HTTP features than it tells about the REST style.
Did I missed something on the article, whereas, I was hoping that it would expound on why REST should not be trusted. A title more apt would be:

"REST is totally flawed" or something similar.

Saying REST is a big lie is somewhat misleading, when the overall context of what it is and what it should be is still up for debate.

Does it matter when you can't completely and fully define what REST should be, but you are out there building awesome products while the rest of the web world is still up in arms on what it has to be?
So in my actual production website, I'm using a ssl certificate that's valid for quite a while that I bought off namecheap.

You could still get around having to take your website offline if you're using letsencrypt by using a docker volume and having it read the certificate from your host machine. I wanted to keep the post short & didn't want to get into volumes. There are several ways to automatically renew a letsencrypt certificate. The last part in https://www.digitalocean.com/community/tutorials/how-to-secu... explains how you can automatically renew using a cron job.

The advantage of using Docker for my setup is being able to plop the whole thing on a different service and having it run exactly the same way (as long as it's provided an ssl certificate).
Out of curiosity, are you also using the cloud CDN?

https://cloud.google.com/compute/docs/load-balancing/http/us...
Raising kids is a metric of nothing other than having had sex.

Every parent I know is a "great mom or dad" simply because you're not allowed to say people aren't great parents unless they are truly bad.
No need to port WordPress to Rust. Didn't you hear that WordPress runs on C# now? Just port the CLR to Rust and you'll get WordPress-on-Rust for free!
Maybe in the non-atomic case. Atomic refcounts force synchronization between CPUs when different threads access the same data, even if they only read it; that can have a quite significant cost.
$750 of that is an employee.
Java does PGO on every server running Java in the world.

Even some swing apps benefit once you get it started up..

That said, I'm not sure the full JVM is coming to browsers anytime soon.
What do you think the doctor is doing when he walks out of the room after seeing you. That's right, they are looking things up in a book or on their computer.

Your argument is invalid.
Personally it wasn't the font for me but the way it wraps. I have some annoying vision issues that pop up from time to time. My solution is to use Safari reading mode on iOS, but that made it worse in this case.
What we really need is a set of verbs that allow to reliably distinguish between these three types of operations:

1. Pure read.

2. Impure (stateful) read.

3. Idempotent write.

4. Any other write.

There's no particular reason to separate inserts, updates, deletes etc as part of the protocol - they're all just different kinds of writes, and middleware doesn't derive any benefit from being able to distinguish them. Thus, this can be a part of the payload.

On the other hand, the difference between reads and writes, and the two subdivisions within each, do matter for purposes such as caching and automated error recovery (e.g. a proxy can repeat an idempotent write a few times before returning the error to the originator of the request).

In REST, we have GET for #1 and #2, PUT and DELETE for #3, and POST for #4. In practice, this is often simplified to just POST used for both #3 and #4, but that loses a valuable distinction (but is unfortunately often necessary because of the lack of support for other methods). On the other hand, the PUT/DELETE distinction is largely pointless.
Sure, eventually, and I assume some day there will be decent debuggers. But if your toolchain outputs JavaScript, you already have these things today.
It's very easy to spot when someone is nervous, there's nothing subtle about it.

If you're twitchy, talking fast, sweating and can't answer questions accurately about your job or a place you've just visited, then yes I think that is absolutely suspicious and worth investigating.
It may sound egotistic, but it's also a solid way to build something akin to a 'book' albeit in a discrete blogged form: you tend to quote yourself not to make the same point over and over again in so many different phrasings. It makes the arguments consistent, and rewards thoroughness, paying attention to each post (coherency, wording, etc.) Eventually it builds up a coherent, cohesive corpus of ideas that hopefully, should the theme be well-defined, is a book.

Usually when going for publication, you'd replace these quotes with references to previous chapters, typically in footnotes.
I don't really understand your point. WordPress is ubiquitous. Until today I've never heard of MODX Revolution.

Commented out in php.ini does mean disabled - as in not enabled. PDO isn't enabled by default in FreeBSD you still need to install a separate package for PDO.
Seeing Theory: A visual introduction to probability and statistics
Isn't the de-facto answer to this 'Unity' or 'Unreal Engine' ?
I just think it's wonderful that this launched within hours of someone recommending twitter be turned around by being the go-to solution for interacting with and watching live tv.
Cloud is still competing with on premises solutions, right? One year is nothing, try ten or twenty.
I think REST is a perfectly acceptable and well-adopted pattern. There's no lie to it. I think GraphQL could displace it but adoption will be key.

What I am sick of with REST APIs is having to code them from scratch in dynamic languages each time and hook up all that laborious plumbing!

I read in an O'Reilly book on the subject that good REST APIs are declared. To that end I've been looking to tools like PostgREST, PostGraphQL, Swagger, and the ill-named Servant. Define the data, declare the resource routes, and you're good to go; generate the server stubs, the client code, and the documentation from the specification.

You don't get that from adopting a new standard every few years.
Related: "A visual intro to machine learning": http://www.r2d3.us/visual-intro-to-machine-learning-part-1/
Price of Renting a Room in SF Has Dropped 12% from Peak
They still swoop in and perform random tests and interviews on people, even happens when you're a Australian citizen LEAVING the country. Last time I flew to LA, I had a customs guy give me a really limp-wristed frisking.
I found Google Cloud CDN a little overly complicated to get setup since you need to use load balancers.

I use CloudFlare. They handle generating a SSL certificate, can have a CNAME at the APEX, full-site static caching, 301 http => https redirects, etc.
The Housing Crisis Is a Building Crisis
Julius[1] can do this. But the accuracy depends on the language model you are using, and unfortunately the free English language model (VoxForge) is not the best.

[1] http://julius.osdn.jp/en_index.php
Reinforcement learning is fully general. NNs on their own can only do prediction. You can predict what object is in an image, or what word a person will say next, etc. And that is quite powerful, and there are a lot of useful things you can do with that ability.

But there are also a lot of things you can't do. Really any task that requires performing a series of actions to reach some kind of goal. Which covers most of the things we want AI to do. Like controlling a robot, playing a game, talking to a human, proving a theorem, etc.

Of course with regular ML, you could do mimicry, and predict what actions a human would do at every time step. But then you are severly limited by the time and quality of your training data. RL requires no training data and can potentially learn to be much better than humans.
I'm not saying they must be opposed to every government function. I'm just saying that there is no logical "small government" reason to be opposed to growing the legal definition of marriage but in favor of having a legal definition of marriage.

Your argument is basically that people tend to be more skeptical of change than of the status quo. Which is absolutely true, but it's not reason, it's just inertia.

"Small government" people are as prone to this mental shortcut as anyone, but that doesn't make it consistent or reasonable, it just makes it human.
Anyone care to disrupt the construction industry?
Drive-by browser exploit steganography toolkit
And what's wrong with that?
Is TypeScript as annoying a language to code in as Javascript? Or is it comparable to other modern languages like Swift and Go? If it is, I'd say that pain of dealing with Javascript (for developer productivity and happiness) is already taken care of.
Right, there's a great many blog posts that can be TL;DRed as "We implemented REST wrong, and it didn't work. I guess REST is overrated."

There's two major components that makes an API truly REST, as opposed to the XML-RPC and SOAP-style APIs that were popular in the early 2000s: Proper use of the HTTP verbs, and the use of Hypermedia.

Most so-called RESTful APIs have adopted the verbs part of it successfully and correctly, but the vast majority have completely whiffed on hypermedia.

Your HTTP API is a state machine whether you like it or not. Hypermedia gives you a means to describe the state transitions as a part of your API. Without it, you are essentially requiring each of your API consumers to re-implement the state transitions for themselves. (The aggravating part of that, however, is that there's not too many good hypermedia-based client libraries, because it seems that most of the proponents would prefer to navel-gaze in their ivory towers, thinking about RFCs and getting the standards perfect. But I digress.)

I wrote a blog post a few months back that goes into more detail about the advantages conferred by a true Hypermedia API: http://blog.theamazingrando.com/in-band-vs-out-of-band.html
Where do you see four nines for S3 SLA?

https://aws.amazon.com/s3/sla/ shows 99.9%
This is the same situation we're already in with minification. The debugger can reformat or decompile it, and if you have source maps you'll see the original source, even if the original source wasn't even javascript.