skysight-inc/HackerNews huggingface dataset:
>In which case I must wonder by what logic it is important for a government to stop me being killed by another person but not at all important to stop me being killed by a market failure?

Many forms of libertianism are deontological (based on principles, e.g. "natural rights"[1]) rather than utilitarian (based on ends). A libertarian might believe that if they obtain something either by finding/making it or accepting it from someone else, potentially in exchange for providing some good/service to that other person, then they have a natural right to that property. This means they'd view it immoral for anyone else to take it off them without their consent, and hence oppose taxation. Some Christians are also libertarian for this reason: they take "Thou Shalt Not Steal" as an absolute, not making exception for people acting on behalf of others.

Such Libertarians generally support only "negative rights", not "positive rights". A negative right means the right to have other people not interfere with you (e.g. hurt you or take your property), while a positive right is a right to have other people do something for you (e.g. feed you when you're hungry or pull you out of a river when you're drowning). Many concepts of "market failure" only make sense when assuming the existence of positive rights: that the other people/the market owes you something or should work towards some specific end. Libertarians would hence not necessarily consider these a failure: from that perspective, the immoral thing is someone killing you, not necessarily you dying per se, if no-one is actively trying to harm you. There are also some forms of market failure, however, "negative externalities", that many libertarians do believe in, and the proposed solution is to strengthen property rights (so e.g. class action lawsuits are allowed against any kind of polluters, and unlike the BP lawsuit the government cannot cap the payout).

1. https://en.wikipedia.org/wiki/Natural_and_legal_rights
Mate

At no point did I say it was a good idea, you're projecting your fears of a technical dystopia upon my pseudo-scientific hypothesising. In fact, if you re read my thread you'll see that I say I AGREE with your ecological point - i.e. I want garden earth. Don't be careless at comprehension.
I just said it appears practically possible to improve significantly on the energy conversion of sunlight into not just dextrose but the full biological stack - fats, amino acids and subsequently proteins.

Re the numbers, as I said that was my fermi equation method of getting to it. I know ballpark figures for most of the numbers so in true fermi fashion it's within an order of magnitude of the true figure. I don't care if you're skeptical of the figure, that's not the point of a fermi equation (unless you're the great man himself and get within 5kt of the yield of the trinity nuclear test by dropping a piece of paper)
I'm a .NET fan, but it sounds strongly like these guys knew what they were doing on .NET and not so much on node. It's amazing how many of these rewrite stories actually boil down to "and the new version didn't do some incredibly dumb things the old one did".

If you really wanted throughput and large numbers of simultaneous connections, you'd be looking at Erlang, anyway.
Formal verification is an really interesting and challenging field but it's worth commenting that it is very expensive and time consuming. It generally only makes sense right now when bugs can cause serious damage.
The is already happening en masse. Look up "initial coin offerings" (ICO's)[0]

[0] http://www.investopedia.com/terms/i/initial-coin-offering-ic...
> most family members of a person with a severe illness will tell you that they struggle to get their loved ones admitted even when the situation gets dire

In South-Africa you have to beg private hospitals to admit patients with certain psychiatric conditions. The default is to send patients to public hospitals, and that will likely involve much more restraint and much less care.

My respect goes out to people that keep on trying to deal with these situations with limited resources.
I would be surprised if this doesn't get a nod.
Demo here: http://editor.ory.am/

Looks similar to Draft (https://draftjs.org) at least in how they think about maintaining editable content outside of the DOM. Glad to see some editors finally put this theory to practice.
It's an MS 'Customer Story' so it is a press release.
Almost broken on mobile, and my iphone gets really hot...
I made a compiler for IBM's Quantum Computer:https://github.com/vtomole/aubree. It's​ my most impressive hackathon project because it's the only one that I still work on post-hackathon.
Looking at my Prometheus stats right now, I've got a Node TCP server doing 12k concurrent connections with 3-5% CPU and 130 MB memory. At least 4 DB queries are done per request, sometimes 10 queries. Raygun either has some nonobvious stuff going on, or Microsoft paid them to write PR fluff. After 6 years with Node it seems odd for their performance to be so bad. They should dive into more technical details to explain what specifically was made faster.
> However, in the original context it makes even more sense to use cond as the number of variables is clearly limited (and they probably have meaningful names).

But the construct with remove and first can be applied to a limited number of variables with meaningful names just as easily as the cond construct.

Plus it has these advantages:

- It's shorter.

- It avoids jarring repetition.

- It's more readable, I'd argue, than the cond version: in the threading-macro version you offered, it translates directly into English as "take a sequence, strip out the nil values, and return the first item of what's left".

- It can be applied equally in situations where the number of items is known at compile time, and those where it isn't.

- It can be applied to an arbitrarily large number of items.
Changing the way we talk and think about Africa
Declarative APIs: tell Twilio what to do
On the topic of "few moments to load updates" while I also could not find anyone claiming to have solid evidence on this practice, FB having a history of being intentionally being anti user with it's android app is pretty well accepted. I wouldn't put it past them, though I suspect it is obfuscated in the form of javascript bloat. Anticipation plays a big role in addiction.
> Notice that each paragraph is relatively short and approximately the same length

This technique is also called "good writing" in some fields. You see it in newspapers a lot.
No, any organization that stores personal data has to allow you to recover that data though.
> Promising libraries potentially solving the above where abandoned by their maintainers, because it started as a special use case, or a free-time project.

> It is built by a company, reducing the likelihood of abandonment.

Even projects "built by a company" suffer the same fate. The only way to reduce the likelihood of abandonment is to tie a revenue stream directly to it, like customers paying for support or a pro version with additional features
There is a reason why you shouldn't adopt the e-mail address or phone number your cable company _could_provide to you: it ties you closer to their network and increases your dependence on it. I doubt that Kik's "core competencies" are anywhere near what it would take to launch and maintain a digital currency.

So, don't call it a digital currency and call it for what it really is, a "customer loyalty" program where hard money and attention is traded for scrip that never... ever... leaves the "company store."
It would be quite interesting to compare Ke Jie or other experts feeling about the game with those data :)
The 8 Worst UX Mistakes Coming from Experts
A Report on Digital Marketing and Ai in 2017
Is there perhaps a resource where there are "stories" of failed attempts? I'm planning for 2021 and very humbly want to walk in the footsteps of others.
I drank beers and chilled for a week while people were burning out coding for free. That's the most impressive thing I've done at an hackaton. I code 24/7 from Monday to Friday for the same company, sometimes on the weekends too. They said hackatons are optional so I took a break and was fresh the next Monday at the office ;)
Or as I like to quote at work "only a Sith deals in absolutes"
Why Choose Cheap Football Jerseys
"Unfortunately, as the Atea-1 had no telemetry downlink, was not tracked by ground-based assets, and was not recovered, its maximum altitude during its only flight is unknown and it is not possible to verify the claim that it reached space."

Edit: I'd delete if I could as this is older launch
"Unfortunately, as the Atea-1 had no telemetry downlink, was not tracked by ground-based assets, and was not recovered, its maximum altitude during its only flight is unknown and it is not possible to verify the claim that it reached space."
We had a local politician who was caught using money to fly first class instead of economy. They defended themselves by saying "You can't step off economy to meet with the leaders of the world."

But it doesn't matter. If you are part of WHO and arrive at your destination, you aren't going to be greeted on the plane. You're likely going to get off the plane, get in a car, and head to your hotel.

In other words, other people rarely have anything to do with it. Most meetings take place inside a meeting room, not a plane or limo.
> Well, yeah, perhaps the craziest thing about XML is that it has namespaces built into its syntax with no realistic model of how or why you would be mashing up different sources of XML tags.

The thing that gets me is that they were added to XML, so the downstream APIs then got mirrored interfaces like createElementNS and setAttributeNS that cause all sorts of subtle problems. With SVG, for example, this generates at least two possible (and common) silent errors-- 1) the author creates the SVG in the wrong namespace, and/or 2) more likely, the author mistakenly sets the attribute in the SVG namespace when it should be created in the default namespace. These errors are made worse by the fact that there is no way to fetch that long SVG namespace string from the DOM window (aside from injecting HTML and querying the result)-- judging from Stackexchange users are manually typing it (often with typos) into their program and generating errors that way, too.

Worse, as someone on this site pointed out, multiple inline SVGs can still have attributes that easily suffer from namespace clashes in the <defs> section. It's almost comical-- the underlying format has a way to prevent nameclashes with multiple attributes inside a single tag that share the same name-- setAttributeNS-- but is no help at all in this area.

edit: typo and clarification
It absolutely does -- Hacker News is popular, so it serves as a counterexample to the implication that a "safe space" website is doomed to being unpopular.
You don't need to decide which is expert is right. You need to know -- if it concerns you-- that there is a chance there will be a contraction in the Chinese economy. Economists predict this sometimes, and it gets news because when it is presented as a certainty it seems like news. The truth is it is always a risk, and probably more of a risk than it was ten years ago. As an average HNer it probably doesn't matter much either way, unless you are planning on investing in China or counting on no recessions in the US in the next ten years.
At what point does a premium virtual asset become a "currency"

For example, if Clash of Clans has gems that you purchase to purchase items and such inside the application, is that a currency?

'...sells tokens that can be used to buy services on its platform. The idea is that as more and more people use Kik, the value of those tokens, called “Kin”, will rise in value.'

But how is this different than buying premium currency in a free to play game? The "Kin" can only be used inside Kik, how does the value increase?
Educated guesses when regulators will comment on ICOs, and the impact of that on the crypto market?
Which iphone do you use? Also is it safari? It's currently absolutely not optimized for mobile, as most content creation happens on the desktop. We might though at some point.
Salespeople Need to Tell Stories, Not Sell Products
It's like an in-game currency for a MMORPG.

...at least that is how I read it.
I never trust any benchmark stories from Microsoft ever.
Immutable configuration (puppet) is a godsend. No more digging into backups of etc and wondering who wrote something there, when (was it before or after the emergency?) and why. Now you place everything into a repository with commit logs like any piece of code.

That said, immutable configuration is static, so the need for grumpy admin style scripts did not go away. It just reduced.
"How can mirrors be real if eyes aren't real?" - Jaden Smith

I made a Chrome Extension that blocks eyes: https://vimeo.com/90351144

If someone runs a dumb ideas hackathon in London, my next plans are either:

- Song lyrics to nineties powerpoint presentation converter, with lots of bullets and stock photos, and timed transitions

- A computer vision and Mortal Kombat-style announcer for pissing the shit off toilet seats
Microsoft has about 50k developers. When you're dealing with an engineering organization of this size, you're looking at a run rate of $5B a year, or about $20M a day. It's a no-brainer to spend tens or even hundreds of millions of dollars on projects like this if you're going to get even a few percentage points of productivity.

It can be hard to understand this as an individual engineer, but large tech companies are incredible engineering machines with vast, nearly infinite, capacity at their disposal. At this scale, all that matters is that the organization is moving towards the right goals. It doesn't matter what's in the way; all the implementation details that engineers worry about day-to-day are meaningless at this scale. The organization just paves over over any obstacles in pursuit of its goal.

In this case Microsoft decided that Git was the way to go for source control, that it's fundamentally a good fit for their needs. There was just implementation details in the way. So they just... did it. At their scale, this was not an incredible amount of work. It's just the cost of doing business.
Reminds me of my Lisp professor's terrible joke, "Today we're going to learn about defining functions because that's where de fun's at"...
That's what we're doing: http://www.ory.am/sites/ - although there's obviously never the guarantee that a project is maintained. However, all of our other projects have been maintained for over two years.

Anyways, you're now one library richer, that solves a hard problem and we're committed to making it awesome.
> and having that option not be Perl

Oh, Python is quite old already :)
My Macbook gets really hot as well. It seems to be quite cpu intensive, and the editing is not very smooth. Otherwise, the product looks interesting
> I would say it's often hardly about just "operating" the machine. You need to know how the machine works how it can affect other machines and what can you do if parts of the machine break.

So, in terms from programming analogy, you need how your runtime operates, how
it can affect neighbour processes/services, and what can you do when the
runtime breaks down. This still does not affect how you structure your code
(at least usually, when you don't work closely with the OS, which I bet is
majority of code in the wild).

> Not only that but also how many operators you can find, how many additional modules (libs) are there and how often you need to oil the wheels.

How does workforce availability affect the way you work with your system?

How does availability of libraries affect the way you work with your system,
apart from amount of code for you to write (libraries have to come from
somewhere)?

The architecture and strategies stay exactly the same. With this regard,
there's very little difference between CFEngine, Puppet, and Chef.

> Sure the implementation of the known algorithms will be similar in Java and C++ but the overall usage and how it connects with everything (aka the workflow) will be very different.

It will hardly affect how you think about the system and how you approach it.
It will only affect where you get your code from. Unless you think about
yourself as a guy who only puts together different libraries/modules and never
ever writes own code, then of course it's a new paradigm, but I don't think
you had this scenario in mind.
Here I was thinking it was some kind of joke about you wouldn't download a car.. never learnt Lisp!
As a full-stack dev this is my exact experience as well. As Martin Fowler says in his book Refactoring -- don't go ahead of yourself, code your way out of the business problems, stay on top of your code, refactor periodically (even if it's only to remind yourself what does a module do!) and the best patterns for your project will emerge by themselves.
There is too much. It's specialization out of necessity. I know enough "DevOps" to be dangerous, but in addition to having a deep knowledge of our product's codebase, the multiple features of our product, configurations, etc. there are not enough hours in the day to master (not simply be familiar with) Jenkins pipeline, Docker, AWS, Ansible, Zookeeper, etc, etc.

99% of the people who could claim to have knowledge of all the above in their organization either have a very shallow (read: not useful) knowledge, OR their product itself is simply the gluing together of various DevOps technologies listed, so there is little more to know outside that.
The relevant bit of the article was explicitly concerned with situations where false values needed to be returned if present, and ruled out the use of or for precisely that reason.

But I agree: if you were ever in a position where you needed to do this, you might want to reconsider how you were representing your data.
To me this is like telling "Government will be right for everyone this time, if we tweak the parameters right". Applying rules of Empiricism to large scale governing will just make things worse as long as people have very different world views.

Besides, locality has inherent advantages such as familiarity, cultural similarity and accountability. So at least some local governments will be probably suitable for your liking.
Not to be too contrarian, but I'm a 45 year old developer whose (basically) only code that is currently in production is what I've made in the last year. Code is generally eventually thrown away, whether it's garbage or not.
Yeah, I've gotten this response for my framework vs. a competing one from Mozilla. I usually reply "Mine came out a year before theirs and I still work on it all the time, and how 'bout that Shumway?"
The official tournament page says it was only the second game. Why does the article suggest it was the third?

https://events.google.com/alphago2017/
http://www.yiddishwit.com/gallery/hen.html
How Drivers Are Finally Outfoxing Uber
Oh, and I almost forgot to say that. The editor is also used at serlo ( http://en.serlo.org/serlo ) which is the largest educational platform for germany with 1 million MAUs. So there's really little chance of this being discontinued over the next 4 years.
SpaceVim release v0.3.0
Thanks for the response, but I wouldn't call that empirical support for prototypes. They took JIT technology developed for Self and applied it to a class-based language, Java. That doesn't mean that prototypes are good for writing programs. It actually indicates the opposite, because the technology in Self that ended up actually being deployed turned out to be something else.

(I also worked at Google and am somewhat familiar with the Self to HotSpot to v8 heritage.)

Your second paragraph is exactly what I think is wrong with prototypes. There's not enough structure, and not enough constraint. Constraints are useful for reasoning about programs. You might as well just have a bunch of structs and function pointers (and certainly many successful programs are written that way).

Having every application roll its own class system is a terrible idea, in theory and in practice. In practice JavaScript programs end up with multiple class systems because of this. The Lua ecosystem also has this problem.

It's analogous to every library in C rolling their own event loop or thread pool, leading to a fragmenetation of concurrency approaches. Go and node.js both unify the approach to concurrency so every application doesn't end up with 3 different concurrency abstractions.

I don't buy your 3rd paragraph. Python is class-based; it has the characteristic you're talking about with respect to a small team of hackers; and that has been empirically supported by hundreds or thousands of startups being acquired (Instagram, etc.) and even huge companies created (Dropbox).

I honestly think prototypes have failed in the marketplace of ideas and there's a good reason for that. I use metaclasses all the time but not for dynamically changing sets of methods. That seems like a horrible idea. The way I use them is for generating types from external sources like CSV/SQL/protobuf schemas.
But if you make a modeling mistake in a monolith it's a little painful, but if you make a modeling mistake with microservices it's excruciating.
Yes, that is why I used the word "want" not "do".
Kik to decentralise using a cryptocurrency
IMHO ease of development isn't guaranteed with microservices. It's usually a bit more complicated to manage multiple services all coordinating the completion of a single task. Where it does help is to define responsibility, and allow different teams to work without stepping on each others toes.

Also, there are cases where microservices would make sense even with one person on the tech team. For instance if you want to scale services independently of each other. For example, your web app isn't used that much, but you get heavy traffic on the mobile API. In that case, maybe having the mobile API as a separate service helps.
The Great London Property Squeeze
> When money shouldn't be an object in the equation it should be removed from the equation.

Money is just a proxy for goods and services; in this case a proxy for having a bunch of highly skilled scientists and doctors work for years to treat a disease only a small group of people have. Having a public benefit corporation rather than a private company doesn't fundamentally change that dynamic.

As to regulations: at bottom, all they really require you to prove is safety and efficacy. If there was a cheap way to prove safety and efficacy, drug companies would just do that on the front end, and send only working drugs through the clinical process. But most drugs don't actually work; most actually fail clinical testing, many after they've made it pretty far along. If you get rid of that testing, and the safety and efficacy data that comes from it, what exactly do you disclose to the public?
Books new graduates should read
TL;DR: I didn't set it up but it's worked well for physical products my clients sell.

I haven't gotten my hands dirty with it but I freelance all types of web stuff so I have (and work closely with) a few people that handle the SEO/Ad stuff. Usually we are promoting physical products (think event tickets, used computers, ect..) with FB and have had a pretty good success rate. FB lets you target with a level of specificity that is kind of creepy IMO but useful.

I'd say it's worth a shot. It's not too expensive and you can run a short campaign to see if it makes a dent. Maybe start with a wider scope and narrow that as you see what's hitting.

I guess the tricky part would be having users on it to talk to when the first timers click through. Also a lot of FB traffic is mobile so that's something to consider. Maybe you can exclude them from your target? Idk.

Hope this helps!
Just to be clear, they spend $200MM on travel for 7000 people a year, that's ~$75/day/person.
Alien Covenant: By Land and Air
The Botmakers Who Rule the Obsessive World of Streetware
And most of the things social media do to increase engagement are called "user friendliness" and so on.