skysight-inc/HackerNews huggingface dataset:
I'm not sure having better predictors of what businesses are good is necessarily a good idea. Part of the attraction of silicon valley is that it takes some of the risk out of trying new things, even if they might be bad ideas. This culture of trying things leads us to find the occasional really good idea. If we sit around all day plugging our ideas into models to see if, statistically speaking, the will succeed, we won't find the really novel ideas that look bad but are actually good.
Yet, if you call a public key/private key a lock/key respectively, then a lot more people would immediately get the concept.

"You send him a copy of your lock which he uses to lock a package and return it to you. Then only your key can open it!"

You immediately fix the problem of people sending their key, because people know keys are important and shouldn't be handed out to just anyone.

The PKI people are brilliant. Their communication skills, not so much.
I'm surprised. I use Browserify (and Coffeeify), which spits out a source map inline at the end of the file, which has not once given me problems.
Yes, it may make sense to talk on the phone, but I don't find that's a good strategy for first contact. Especially if people don't answer their phone or like to small talk.
Benefits of Blogging
You are not wrong. What is newsworthy is that they are going to begin actually collecting that 20% which they have not been actually charging for in the past. This is more of a heads up for those that see an increase in their monthly bill/charge.
The technological singularity hypothesis
The author makes a very good case for why this approach won't threaten password-based authentication, including:

...hard for first-time users to get right:... The private key being unlocked and available via ssh-agent.

For this to be convenient for daily use, ssh-agent is essential, and that could expose naive users to compromise. I know enough to disable ForwardAgent in my personal config by default and generate site-specific keys for hosts I can't trust, but that's beyond most ordinary users and even many of the technical professionals I deal with.

It's a shame PGP was the target of so much persecution when it came out. Maybe by now we would have worked out the key exchange problem and would all be enjoying personally encrypted communication on the Internet. I sometimes feel that any attempt to move beyond passwords without realizing that ideal is doomed to failure.
> There are many ways to do things

Hopefully you realize that most Rubyists will strongly disagree and think that's not a "problem".
Has it been tested in court in relation to NSLs?
While I generally agree with you, the UK does make a fair amount of revenue from tourism (~9% GDP) so keeping a few iconic examples around might be a good idea. For much the same reason that castle's are interesting if largely useless structures.
FWIW, I pay dearly for 6Mb/s where I live, rarely get above 4Mb/s out of it, and can regularly consume that if some streaming video is running.
Suggesting a new story type: “Irritant”
How 3D-Printing Rocket Engines Could Win Back the Space Race
Completely agree - speeding up only really works with certain accents and presenting styles.
mobile.nytimes.com is written in CoffeeScript (frontend and backend) and is maintained by a team of around 8 people. AFAIK all of the developers are fine with it.
AOL To Lay Off 150 People, Mostly In Sales; Folding Joystiq, TUAW Into Engadget
Thank you!

Unfortunately, I'm not in Texas and just refinanced my house, so won't be moving anytime soon.
> and you see multiple languages

But they're not all included in the same image. We have 8 variants, 6 of which only contain a single language. There is 1 which contains everything, and there's 1 which contains nothing and is meant for customization.

> web server, app server

The web server and the app server are the same thing. Passenger is an Nginx module.

> aux services and tools.

Only the minimum possible to allow regular administration, inspection and debugging.

> First impressions are that this image is one-size-fits-all

But it is not. That's why we have 8 variants. Early in development we've explicitly made this a many-sizes-fit-all thing.

> and that they are disabled by default, but I still feel the balance of the README is wrong as it doesn't sound any kind of warning that you probably don't want to do that in most cases.

Fair enough, though I disagree. I'd rather assume the user knows what he's doing. If he chose to enable Redis then there's probably a good reason for that.
According to the encyclopedia:

It was established in 1952 by a presidential directive from Harry S. Truman in which he specified its mission as

to provide an effective, unified organization and control of the communications intelligence activities of the United States conducted against foreign governments, to provide for integrated operational policies and procedures pertaining thereto.
New string features in ECMAScript 6
AWS Lambda aka Node.js Meets IFTTT as a Service
This is correct. In the UK Mountune provides this for Ford and your car is still covered by the original manufacturer warranty

Edit: same for Mountune USA
Does Reddit allow anonymous users (e.g., via Tor)?
Docker is distributed as a part of Amazon Linux
>Brilliant, right? No, because user accounts are commonly shared

Gee, I guess only I can drive my car. If only there were some way to share my car with my spouse. Like having a second set of keys or something...
Tbh from watching streams for a few years now, I think the big guys make MUCH more off donations than any ads/subs. Most of the big guys don't even run ads and strictly push donations.

A single guy has donated ~50k to the streamer sodapoppin
There are multiple factors that make it unlikely for a third party to win, and "first past the post" is a lesser contributor.

Of far more concern are ballot access laws that make even the formation of a third party a colossal waste of time, and partisan redistricting that even makes it impossible for the second party to win. I won't even delve into ridiculously insecure electronic voting tabulators, because I'm too likely to devolve into paranoid conspiracy nonsense from there.

Eliding over all that, the spoiler effect is what forces the two major parties to make changes to their platform in your locale. If a party believes that your vote for another party caused them to lose an election, they will certainly make an effort to kiss your ass at least once in the next cycle, becoming more like the party you voted for. It is easy to argue that voting for either of the two major parties means that you don't want them to change their platform or policies.

Voting for the party in power means you are happy with the status quo. If you are not happy, and you find the second party to be more objectionable, voting for a third party that puts you between them and the party in power on the political spectrum is the correct move. If that party is scared enough by votes bleeding from them to that party, they will shift in that direction, perhaps enough that you will be happy voting for them again.
Not perhaps extremely expensive, but it may be more expensive than setting up pylons. But for instance when crossing waters, it is more practical to have an underwater cable than build pylons across sea.
I would be incredibly interested to know how the model was crossvalidated. It is utterly trivial to cherry pick features post-facto to correctly predict winners, however people who are unfamiliar with machine learning might not know this.
> Require US companies to follow US law and regulations, across global legal entities, even when the local law of locally incorporated entities is incompatible with US law, absolutely yes, that is required.

Then why the hell would anyone build a company in the US?
2 good network books in one day. Lucky me. I know what I'm doing this weekend.
> How do you easily fork to run a command in the background?

`turtle` provides `fork` for running a command in the background. Example usage:

example = do
using (fork commandToForkInAnotherThread)
theseCommandsStillRunInTheOriginalThread

> How does setting up pipes work?

See the `inproc` and `inshell` commands, which let you convert any shell command into a stream transformation embedded within Haskell.

> What's the idiom for chdir'ing to a subdirectory such that you pop back out again when you're done (I'd use a subshell with (ch xxx; ...) in bash)?

You can write a combinator for this using `turtle` pretty easily:

pushd newDir = do
oldDir <- pwd
cd newDir
return (cd oldDir)

... and you use it like this:

example = do
popDir <- pushDir "/tmp"
... do stuff ...
popDir

> what's the equivalent of <() in bash?

`inproc`/`inshell` which let you read in a command's standard output as a stream
> Again. Third party tools will have exactly the same benefits.

If that were true, the frictional problems I mentioned would not be the rule in every other language. Even something like Python, where PEP-8 has been recommended strongly by the community for many years and has widely available validators and automatic reformatters, still has perpetual low-level debates about this.

In languages like C, where there are multiple well-established conventions, you can still find bitter arguments going on over things like optional braces because there are still tons of bad programmers out there who think it's preferable to ship massive bugs every few years than type two extra characters.
I think there's a lot true in what you've written. However the root cause fix applied in a development environment is not always the fastest way to stop a user facing problem. Things get weird on live servers. I'm not suggesting altering code willy-nilly but a solid knowledge of production (logging, service status, etc) can lead to more effective debugging scenarios and faster time to resolution when things do go bad.
I find it hilarious when the girls have their camera covering up more screen than the game. Obviously they know what people have come for.
I don't know what you consider an extended period of time, but I've been writing CoffeeScript full time for 2 years now, and it's been like that at my day job (moviepilot.com) for at least 2 more before I came. Couldn't be happier!

Team size varies between 8 to 15 people, roughly.
Yes, but they slowed down...

The LS2 issues are from years ago and nothing is happening.
<keygen> can generate client side keys. It's not very good, but it exists.
Everything you know about passwords is wrong
Btw the main developer, Kenton Varda, is also the author of Cap-n-Proto -- a pretty neat serialization & RPC format.

https://capnproto.org/

I was playing with that and stumbled on Sandstorm a while back.
This looks incredibly useful for things we're currently trying to make Docker do. Huge potential here.
Technically it is because you've gotten a DUI recently. But yes, it is there to prevent (another) DUI.
I used that. These days, I use Atom + Go-Plus.
Ask yourself honestly, are you using your wife as a convenient excuse? Or would you be wearing a helmet now anyway? :-) I'd go with civilized over emasculated.

I think the awareness campaigns of the 80's, as well as generally "growing up", in addition to quite a few near-deadly accidents, have changed my (in hindsight, ridiculously stupid) viewpoint on helmets.

In the last 12 months two friends have broken helmets, but survived. If they weren't wearing them, who knows...
Yeah! I am pleased that Noritake may have found a way to keep their company/plants going. I hope it works out for them.
Folks, this was always part of the plan ;)

CoffeeScript is a fun little experiment in what's possible when you take JavaScript semantics and try to boil down the user interface to a minimalist surface. But JavaScript will always keep on rolling onwards — and to the extent that future versions of JavaScript take any minor inspiration or reference or overlap with things that CoffeeScript already does, the more the better.

For example, see this talk from four (!) years ago: https://www.youtube.com/watch?v=QTj6Q_zV1yg

There's more than one way to skin the JavaScript cat.

In other news, CoffeeScript 1.9.0 came out yesterday — with support for ES6 generator functions. A-la Python, in CoffeeScript, a generator is simply a function that "yield"s.
The scope of content in that book is pretty large for an audience needing an introduction to computer networks.
Utility is having something work efficiently and effectively.

Beauty is the art of making something pleasing and desirable to humanity.

Engineering and architecture should aim to do both. When utilities are ugly they can depress the price of properties around them, making people less willing enable future needed projects. I mean, is your home a (subjectively) ugly gray box with no decoration. I mean the purpose of a house is to shelter you from the elements.
Also if it works good, you can give them the same color as whitespace, which I always show, but with almost the same color as the background. This reduces the cognitive overhead a bit.
Looking at the TOC, I think the one by Loyola University's associate professor, seems like a better introduction.
As a designer, the website gave me an 'aha- moment, nicely done! :)
As a motor control guy I'd really like to have a look inside Teslas control algorithm. Most people - even experts - leave something on the table. This improvement is no surprise to me.
In theory Swift's arrays are little more that a c array + length, and this is how we have been encouraged to use them.

The issue here is nothing about "managed code", but about how the Swift compiler behaves without any optimization passes. Currently (and it should be noted that this is a recognized issue), the unoptimized builds are orders of magnitude slower than ObjC because Swift will auto refcount code that in ObjC is either not ref counted at all, or uses manual RC. After optimization, Swift can eliminate many uses and put things on the stack etc, but we are at the mercy of the optimizer for that.

Compare this to the (compararively) predictable behaviour you have in C.

Yes we can in theory use UnsafeMutablePointer everywhere, but in that case it's much more efficient to write the function in C instead.
Sorry Thomas, I only referenced you because I thought the post in question was worth sharing in this context.
That's a retarded retort. In the SSH case you have ONE password to remember. Not one per website. Furthermore, the password never leaves your machine. Log in to a hundred websites with SSL and a password and the NSA comes along, collects all your passwords server side, knows which ones you reuse, knows your password generation patterns, everything. You are completely nuts if you think these two things are the same.
Coolest thing is that it uses only 2% the power of comparable tubes.

But it's confusing: There is already a model of tube called 6P1 (1).

Anyway, who is this for? Engineers/instrument designers? Korg to use internally?

(1) http://en.wikipedia.org/wiki/6P1P
I think it's somewhat rare to have generic relations (content type + model id) popping up this way in serializers. I tend to use generic FKs for things like "tags" or or "comments" that can apply to multiple objects. As a result, I'm almost always requesting the parent object ("post") and want the model with the generic FK serialized in that response ("post.comments"), not the other way around.

Just looking through largish DRF codebase, I'm not sure there are many places I could use this, thought it seems like a good idea if your code has a lot of these scenarios.
Reading the RFCs for popular protocols is also a good start. Several of the RFCs also document many years of learning from operating networks. A good place to start is the RFC index - http://www.rfc-editor.org/rfc-index2.html

(eg HTTP/1.1 is RFC 2616)
There are lots of reasons! I'd encourage people to try something new (Go, Rust, Scala, whatever), it's easy to ignore Node's shortcomings sometimes. Community was a big one for me, the "unixy" nature of node+npm is no good when the module quality is pretty poor and the names are completely nonsensical, your app just becomes an abstract blob of code that makes no sense. Go's stdlib is pretty rock solid, nothing in Node comes close IMO.
Have you tried them at all recently? If a source map is off by a line, that's a bug that should be reported and fixed pronto.
Interestingly in the UK upgrading your brakes will get your premium bumped up because now the vehicle is 'modified', even though it now stops better
> The left seems to view the opposition as backwards and deserving of contempt,
> as a group of bumpkins and idiots and sometimes subhuman.

This.

John Oliver, Jon Stewart and Stephen Colbert each have an amazing ability to use humor/satire as a way to make a point. But I can't hardly watch This Week Tonight without feeling like he's portraying "the other side" in exactly this light. And it's a gimmick. A cheap way to put your viewpoint on display without actually lending any credence to anything your opponent would say (would it be fair to call this tactic an Ad Hominem?).

The sad part is, I get the impression that the generation who are now in their 20's and 30's have grown up knowing only this kind of "political discourse". They don't recognize that by sheltering their ideas from opposition in this way their viewpoints remain intellectually weak and stunted.
I came in expecting something like an Amazon shopping history. I don't find it too surprising that in-person purchases can be tracked so readily - geographic information is a huge dimension to add to these data. It would be interesting to see how many data points are necessary to achieve similar accuracy just with a purchase history. Particularly interesting would be matching users across websites.
I believe its just a matter of time until churches will lose their 501c3 tax exempt statuses for one or more reasons. Once donations to churches are no longer tax deductible I foresee the big church building owned by the org going away and "churches" just gathering in public spaces or people's homes. It makes the most sense from all sides.

Why are church donations paying for a building that often remains mostly empty most of the time (I know, not all and not always as some churches try to keep their doors open and share the building with others) to heat it, upkeep it, take away land/property taxes from the local government/community? Those saved upkeep expenses could go directly into helping the poor and those in need.

Scrap ten buildings and get one, keep it open 24/7 and make it a shelter and soup kitchen. (But too many church goers/members treat "their church" like a country club or Malibu beach side home owners... "I don't want to mix let alone see those 'dirty poor rascals'".)
If anybody has been able to connect, could you summarize what this is?
7 Tips to Save a Struggling Business
Are Magnetometers Used in Space?
Hmm, I can predict that 90% of the time, so I don't follow.
How much do indie PC devs make, anyways?
Has someone copied your app idea + design? (Like totally copied)
I didn't look at that link because you presented it as "investigations still continue" which is meaningless, considering that investigations still continue into things like general relativity and electromagnetism.

In any case, you might recall that I said I'd never seen any data for these arguments except for the supposed autism link, which is based on fake data. Considering the tone of the paper I think it might be in that category. Maybe not. I'll hold off on spending time investigating until some anti-vaxxer actually mentions one as support for their ideas, because "X argues Y" and "there's data to support Y" does not imply "X argues Y because of data supporting it."
same as you can have, just stand up and walk away from treadmill... oh wait, cash, security, not dying from appendicitis and whatnot is so comfortable, right? :)
I really wanted to like this as it looked promising and I'm already using (or have used) other OVH-backed products like Kimsifi and So You Start, with great results. I set up an account to test it out and ended up cancelling and deleting the account after less than an hour of use.

What went wrong, in chronological order:-

1. 30 character password limit. Not the worst thing ever but it indicates they may not be properly salting & hashing passwords.

2. UK Postcodes fail if you type them normally, you must remove all spaces which you must learn through trial and error - the only feedback you get is 'Invalid zip code'.

3. Credit card details must be entered before you can use anything, and a 'Memorize this card' is checked but disabled, which seems odd.

4. No guaranteed minimum bandwidth for like on other OVH products. In my testing I saw about 19MB/s up and 26MB/s down, so not great but okay for the price.

5. The worst thing for me was really slow disk speed on their VPS's. My plan was to move one from DigitalOcean to RunAbove (very happy w/ DO, but want to mitigate risk by using multiple providers). Running 'dd if=/dev/zero of=iotest bs=64k count=16k conv=fdatasync' several times produced results showing disk speeds of barely 50MB/s. I can do this all day long on the cheapest DO VPS and see 5x those speeds. No comparison.

Still, like I said the other OVH projects I've used kick ass and I will probably try this again in six months or so. But for now, there is absolutely no comparison between RunAbove and DigitalOcean if you are looking for a VPS. For object storage only, you should test read and write speeds and make sure you are happy with the results after considering the slightly lower prices. Not quite there yet for me.
Sounds cool but I think the WordPress implementation is TERRIBLE: it depends on a WordPress fork that is completely outdated, instead of downloading an up-to-date fresh archive.
90's for me :)
The target audience is non-Haskell programmers, and if you don't think the tutorial is good enough to onboard such a programmer then I consider that a bug against the library. I would actually appreciate if people submitted Github issues highlighting any pedagogical problem with the tutorial.

I think the use of `liftIO` is a reasonable objection. When I wrote the library I had the choice of utomatically pre-wrapping all `IO` commands with `liftIO` for the user (making them all `Shell` commands) by default. However, I decided not to do that for two reasons:

* If you do that you can't use them outside of a `Shell` any longer
* The user has to learn `liftIO` anyway if they want to use `IO` actions not provided by the `turtle` library. I didn't want to teach the user a leaky abstraction

I don't see any issue with `do` notation is bad. Same thing with parser combinators, which are just strings in the simple case, and the "Patterns" section of tutorial has a table showing you how to convert regular expression idioms to `Pattern`s:

http://hackage.haskell.org/package/turtle-1.0.0/docs/Turtle-...

The language pragma is sort of a grey area. I decided to keep it because it doesn't take a long time to explain and it significantly increases the usability of the library.
Stuff like this is why I never buy or take any medicine until I know what's in it and do some brief research to see how it works and what effects it might have.
>Someone claimed that Marriott's net income was irrelevant to Marriott's internal decision-making process in this particular case.

Can you point out who claimed that and where? I don't think the person I originally responded to made that specific claim, only the more general claim that net income was not relevant (and they made that claim indirectly).

It's likely an absurd notion that net income is irrelevant to Marriott's internal decision-making processes. Of course, none of us were there when decisions were made, but if you claim that marginal gains are what drive Marriott's decisions then you must accept that net income is relevant. Margins are (and can only be) built on top of net.

Examining margins to the exclusion of net is madness, although based on some comments I read on HN it wouldn't be surprising to find some (or many) on here that have already gone deep down that hole.