skysight-inc/HackerNews huggingface dataset:
I understand your points, and there have been many appropriate checks and balances introduced to avoid past abuses (which were very real).

That said, I have a hard time feeling that allowing a person to go untreated and end up in jail or prison is in their best interest.

Here's a quick link about "transinstitionalization":
http://www.namisacramento.org/advocacy/docs/Mental%20Health%...
Link without paywall > http://www.theaustralian.com.au/business/wall-street-journal...
No, the reason he suggests the government move assets into private hands is because his main thesis for how China can get out of the jam is to improve household consumption vis-a-vis growth in household wealth.

Not covered in the article I linked in particular, but his main idea is that China has had investment-fueled growth that's no longer sustainable; the foundation for all advanced, post-industrial economies is a robust consumer sector. China's is stunted at best. That's the motivation for transfers, not a productivity argument.
I live in Toronto. I've been to the ER here. We were seen promptly, given the right care, and paid no bill.

The efficiencies gained by not wasting time on unneeded treatments, not having a billing department and not paying million dollar CEO compensations, these outweigh, in my opinion and experience, any gains we might have via privatization.
The reading experience is really rough on mobile: huge font with weird spacing to keep it justified.
Tracklib – Discover, Sample and License from thousands of original recordings
The words of yours which resonated with me were how your support network was rounded up and I had similar experience from a completely left field, but the same origin in as much LEO was desperate to have me charged with anything. Bit of explanation is in my recent comment history just the other day I realised that my personal privacy had been traded long ago unknown to me and the results I can only hope will be as recreative in my life.

I'm tempted to joke that the TL;Dr for all such encounters is Authority Cannot Afford Being Wrong But Isolated From Social Function Unable To Evaluate Reputation Risk.
The words of yours which resonated with me were how your support network was rounded up and I had similar experience from a completely left field, but the same origin in as much LEO was desperate to have me charged with anything. But of explanation is in my recent comment history just the other day I realised that my personal privacy had been traded long ago unknown to me and the results I can only hope will be as recreative in my life.

I'm tempted to joke that the TL;Dr for all such encounters is Authority Cannot Afford Being Wrong But Isolated From Social Function Unable To Evaluate Reputation Risk.
Well, no. Because you can do it per-process. I don't see the reason of doing it per threads here.
One obvious thing is that multiple processes means no sharing of any kind of state or in-memory cache, so you immediately have to go to an external cache like Redis or whatever, with the additional maintenance and minor performance hit.
Scanning the article one more time, it seems pretty limited in focus to "like" buttons and social validation. You could probably write a whole book on the other types of products and devices :)
I would pretty mad if I was one of those interns!`
Yes, but this also doesn't mean that one person trained in one tool can't learn the other in fairly short order, provided they understand the core principles behind it and haven't been 'brainwashed' into thinking 'this is how things work'
That's an interesting experiment, but what was the expected outcome? The deliberately feigned illness to get in and then reverted to completely normal. That's not a class of patient that is ever expected to show up. How would someone expect those cases to be handled and why?
I'm not a big fan - once you start encoding type information in names, you have to be extremely attentive when refactoring. It doesn't scale too well in a larger team.

I prefer clojure.spec to guard significant (ns, api) boundaries.
Okay, so not everyone is a sweeper, fullback, goalie, wingback, midfielder, striker, or forward.
There's a fundamental difference between holding engineers accountable for the downstream impact of their technical decisions and making engineers take on the added responsibilities of an additional position without compensating them accordingly for the added responsibility. In an organization that prioritizes stability there is an appropriate balance between engineering and system administration as well as potential overlap given the right boundaries and understanding of job responsibilities. The engineering team will be held accountable by the system administration team and changes will happen because of it.

The inherent failing in this structure is when one of two things happens; one, the system administration team does not have the appropriate channels (and clout) to provide push back against the engineering team; two, the technical teams (both engineering and system administration) don't have the ability to get technical debt payed off properly due to an improperly structured project management process.

Anecdotally, I've been witness to the second issue a number of times. If there isn't an immediate understanding of ROI for a proposed change then it isn't prioritized to be worked on. The thought process is generally along the lines of, "Engineers are an expensive resource, having them working on something that won't make the company money is obviously not the priority."

While some of this is on the engineering leadership as their job is to provide insight into ROI for technical matters there also needs to be a balance where the non-technical leadership trusts the technical leadership to know when to prioritize projects with non-obvious ROI.
Knowing that today we still see bandwidth issues in VLC, even without IPC, I kind of doubt it.
Duh, yes, of course

What a weirdly trite response given that you're essentially repeating what I said. And without specifics the linked piece, and its claims about benchmarks, is utterly meaningless.

"Rewrote inefficient code. Now it's faster. Story at 11!"

The AgeOfAscent story is not a PR piece

Humorously it was likely a "copy a L1 cached static response" type benchmark.

Okay, so it wasn't PR, it was self-aggrandizement (which is effectively PR). Got it. Though in this article it was linked as a performance improvement of "switching" to .NET Core, when really it was a story of terribly inefficient .NET Core code becoming better, though again in a nutshell it is meaningless. Cool.
You're coming to hacker news to argue that vaccines are actually a conspiracy?

Best of luck with that.
Let me guess, just as Ruby on Rails, is Ghost in the Shell a new framework for web development using Bash?

(just kidding...)
Ask HN: I don't want to be a founder anymore
Hi HN,

Using a throwaway account because there's a lot to lose from speaking about how I feel.

I founded a company several years ago. Fast forward to today and we're profitable, growing steadily, debt free and are about to be acquired (there are LOIs on the table). You may ask what the problem is? Well, the problem is that I'm supremely unhappy.

Each morning for the past couple months, my first thought has been "What could today be like if I didn't work here?". I drift off into exploring what it would be like to work at Wal Mart, or the construction site outside, or as a bagger at a grocery store. It seems so stress free. Then, my phone starts ringing for the day and I'm snapped back to reality. This morning, I locked myself in the bathroom with the shower running (don't want wife to know) and cried my eyes out. I haven't cried in many years. It felt great, but only for an hour.

So, from my (possibly skewed) point of view, I have 2 options:

- Quit, which effectively kills any acquisition and likely the company as well

- Suck it up and work on the same thing for 2-5 more years

I'd been mulling over a third option (hire someone to do my day-to-day), but don't know how to make it work. The product is just too complicated (tons of domain knowledge required) for someone to come in and take over. Additionally, the product just isn't that interesting (glorified CRUD app) and it's been hard to retain developers.

Please tell me I'm missing something! Maybe I'm just being ridiculous- it's getting hard to tell. Is it common for a Founder to go through this train of thought before an acquisition? Is there a trick to convince yourself you want to keep doing this? Maybe I'm suffering from some kind of depression and need drugs.

Any advice appreciated.

- A founder in pain
Ha, then I should read more carefully before I comment :-)

Excellent work! Do you think it may make more sense to market Ory as a Page Editor or Page Maker? Content in my mind can mean anything from a block to an entire page, though I recognize that CMS's have popularized the idea of content being equivalent to a page.

Right now, I see "Layout Editor" and "Content Editor" being used to describe it, so maybe it would make sense to standardize that.

Just a thought!
I'm not a web dev by choice, I get dragged into it with work.

That's very much true of me as well, and is a key reason for using Vue. It's a very pragmatic choice for getting things done in a modern JS/SPA way without making a career of front-end development.

As far as the differences, others have already answered better than I can. :-)
Is this CodeFlow you're talking about?
I don't agree with this at all!

More or less every mainstream language has adopted first-class functions to the extent that they can. JS has always had them. C++, C#, Java have all added them; Python and Ruby have had them for a while now. Standard functional programming constructs like map, filter, and reduce are now extremely familiar, whereas not too long ago they would have required a tutorial and explanation.

And just as imperative languages have adopted functional features, functional languages are growing more popular. Even if you just limit yourself to Lisps, Clojure is used widely. There are probably many more Lisp programmers now than there were 5 or 10 years ago, thanks to Clojure's adoption. Branching out a bit, Scala is also very popular.

That's not even to consider hipper, trendier things like Elm, or the increased popularity and visibility of Haskell.
Looks and works great, but there are 2 limitations I think would prevent it from using it in our stack:

1) It cannot be easily embedded, ie. as a field in a form. Apparently it's meant (UI-wise at least) as a full-screen editor and has lots of dependencies of its own, including React.

2) AGPLv3 license is a killer. Means that any work that links to the library should be opensourced. Despite some people interpreting it differently, it would be risky for a consumer product to ship making use of this library.
Please see https://kin.kik.com for more info, https://reddit.com/r/KinFoundation, and http://slack.kinfoundation.com for discussion.
That is why there is a "Talk" section for each Wikipedia entry.

https://en.wikipedia.org/wiki/Talk:Ghost_in_the_Shell
They recently replaced Qt's v8 engine with a smaller self built one called v4, no?
Well, the full term is Development Operations, meaning the branch of Operations concerned with supporting Development. I recoiled from the definition you offered because I've actually witnessed an organization use that as a justification for not hiring any Operations staff, which is a terrible idea.
What a great write up and novel approach to the subject. I really enjoyed this. Thanks for sharing!
I'm curious what the cross-over between GvFlt may be and the return of virtual files for OneDrive in the Fall Creators Update? Is the work being coordinated between the efforts?

From your description it sounds like there could be usefulness in coordinating such efforts.
App Samurai launches to help startups take a stab at user acquisition
Cable TV Industry Among Most Hated by Consumers Again
Nick Dearden is the director of UK campaigning organisation Global Justice Now. He was previously the director of Jubilee Debt Campaign.

Maybe he can explain where the anonymous 200K came from?[0]

[0]http://www.globaljustice.org.uk/sites/default/files/files/pa...
There are several aspects of what I described that do not align with the way I would like the world to work and would prefer if alternative methods were practical. In the world of politics and diplomacy, I don't think they are because politics and diplomacy require engagement with actors who are not driven by scientific methods, generally praised moral theories, or a strong sense empathy or who simply cannot do positive things without first caring for their political survival.

The WHO has the political ability to operate at the ministerial and executive level above regular bureaucracy. A technocrat may not care if a senior WHO official arrives on a bicycle, but the WHO does not always deal with technocrats and a meeting planned with a technocrat may turn out to be a meeting with a politician as well or instead.

That's part of why protocols matter for the WHO more than for Médecins Sans Frontières. Protocols also matter more for the WHO because its primary role is at the diplomatic level even during an emergency. During the same emergency, Médecins Sans Frontières primary mission is on the ground delivering services at the endpoint.
For a story that has decades? IMO it'd be akin to a [spoiler] alert when talking about LOTR or similar.
History and Philosophy of science is definitely a field of study: http://www.hps.cam.ac.uk/ - it definitely doesn't come through from learning the subject in the normal manner, because that tends to present a "finalised" view of science that doesn't include any of the dead ends or lengthy mysteries.

HPS for CS wouldn't be a whole graduate course, but would be a worthwhile module in a larger course.
> From the questions we received around the specifics of our performance improvements, there seems to be two schools of thought:

> 1. Of course it’s faster, Node is slow

> 2. You must be doing Node wrong, it can be fast

Allow me to offer a third :)

When you rewrite something, it had better be faster! You know a lot more about how it works and how it's used than you knew at the outset. There was a recent post, about going back to Ruby after creating the first version in Clojure, that touches on this point.
> I haven't found a way around this other than careful communication, which works with most but not all clients.

My wife does this kind of interface mockup presentation as part of her job, whenever she does a client presentation she starts with "so this is a screenshot of the inside of my head..."
I haven't seen it. I don't find myself using atoms very much and when I am using atoms, it's almost always because I'm trying to use doseq when a more functional version of my code exists if I would think about it.
There are many reasons why a single currency may be preferable to many in a single market. The biggest is company scrip[0] but there are others, like the fact that this just creates more market speculation and that vendors have the option to not accept any currency they aren't required to by law.

[0]https://en.wikipedia.org/wiki/Company_scrip
That's awesome, wish my city would do something like this - you're lucky to get updates once per 2 or 3 minutes on their service.
SEARCH ENGINE OPTIMIZATION – WEB DESIGN|SEO|PARAMARKETING.GR
I think you've nailed it. The suitability to small projects particularly tickles me, since most of my web development projects are small — I'm not a web developer by trade, it's rather a side effect of the actual work I do.

I think another big selling point of Vue is that the core functionality you fundamentally need is all _in_ Vue. There are third-party components out there, but they are really ancillary, much like third-party Angular 1 components. Fundamentally, the core Vue library is all you need to know. React, in contrast, is really a many-headed beast with tons of separate libraries that go into what could be reasonably deemed "core" functionality.
This sounds so useful in theory (I tried it) but I think it just doesn't work with my flow of operations. I'm mostly anti-mouse and pro-keyboard but somehow this combination of xmonad window layouting and using terminator (where I exclusively rearrange my split shells with the mouse) has been useful for years and while I'm a thankful and frequent user of tmux on servers I never could be productive on my desktop... :(
Optimize Sales Ops by Integrating Data-Driven Tools
What it’s really like to be twenty-four, single and on your way to success
lower barrier to entry maybe?
>> Node is a productive environment, and has a huge ecosystem around it, but frankly it hasn’t been designed for performance.

Isn't/wasn't part of the hype behind node that it's fast? Compared to what?
Nearly everything you have written is incorrect.

It's rare to find a psychiatric hospital, public or private, that's not accredited by JCHO. This group has the same standards for general and psychiatric hospitals about patient rights, and due process for any hands-on or involuntary interventions.

Psychiatric patients can, and do, complain. The assumption is that they are making a genuine report until proven otherwise.
We've always felt strongly about Facebook's views on real names: they're intrusive and unfair.

So we made Lyra, a better conversation service which lets you have whatever name you like (among other things). https://hellolyra.com/c/343

We're a nonprofit and don't take investment, so excuse the plug :)
I've thought about this issue, but it seems like any type of advertising or program that refuses to respect boundaries and pushes psychological buttons is bound to win over a product that does not.

Is this a concern internally?
Advanced REST Client
We're on it :)
We are working on (1), and make it possible to include it in non-react environments. However, there are still some dependencies required (such as react). So yes, this is not perfect at the moment.

We're actually not confident with AGPLv3. We might change it to a more permissive license if it prevents people from adopting the technology. Feel free to create an issue on GitHub and we'll discuss it!
But this is built with React so its not really reusable outside of its ecosystem.
Is there a version that would run on preact instead?
Maybe QuillJS would be a better option for general purpose editor.
Zelda BOTW's cartridge teardown
Damn, I remember another Marauder's Map that was just genius!

Long story short, Facebook's Messenger automatically geotagged users by default. People reported it to their security program, Facebook said it was intended. Then someone made a browser extension that looked up location of active Messenger friends and showed their location on a map. It got increasingly popular. Facebook decided to switch the location from opt-out to opt-in.

Some sources:

https://www.theguardian.com/technology/2015/may/28/marauders...

https://www.quora.com/Can-I-still-download-the-Marauders-Map...

https://github.com/arank/marauders-map
Did nobody notice that "human" is just an adjective in "human resources"? The operative noun is "resources".
If that's what you want there's always Bash on Balls! [0]

[0] https://github.com/jneen/balls
To me the original makes more sense. A cons cell is a 2-tuple. CAR retrieves the first element; CDR retrieves the "other" one. The fact that CARs are usually atoms and CDRs are usually lists is a convention, not a rule. You can easily put an atom in the CDR of a cons (this is called a dotted pair) and you can easily put a list in the CAR.
At this stage ICOs which have a sufficient hype factor have an upward ramp in trading after launch, which attracts a lot of unsophisticated libertarian investors ("suckers"). Kik seem to have decided to get in on this action, as it's sufficiently distinct from plain Ponzi to appear legal.
Yes, we've been banging our heads to finde the right terminology to describe it. We'll put page editor / maker to our list of keywords :)
It's hard because in a small example you can always say "well why not just restructure the team some other way?", because there's no collection of real forces to balance against. But a simple example would be, let's say you're offering several services to the public. You want all of them to have a single sign on. Then you'd better create an "authentication" team, because if you leave authentication up to each of your 5 services, you'll end up with 5 authentication schemes. (Usually to make the "authentication" task large enough that team will also be responsible for the central record about billing info, contact info, etc.)

It's tempting if you don't believe in Conway's Law to say "What's so hard about having everyone share authentication services? We'll just mandate that they have to use one service without having to create a separate structural team to do it." But it will not generally work.

One element that contributes to this is that the teams are not just technical, they are embedded in a company in a larger context. If you create product teams A, B, and C, the larger company will be grading the management of A, B, and C on the revenue they generate, or other appropriate metric. Thus, the management for those projects will tend to be very focused on that metric. If you tell each of them that they are responsible for authentication, they will each want to spend as little as possible on it because it is not a revenue generator. (Who has ever signed up for a service because its authentication was just so awesome?) They will each correctly come to the conclusion that the cheapest thing is just to bash something that vaguely resembles authentication into their own system, because the costs of coordinating between the three teams will be too large. So you really have to carve out this interest into a team that will be measured on the goals relevant to authentication, such as scalability and security rather than revenue.

Engineers are also constitutionally inclined to say "Well, the solution is just to stop measuring teams A, B, and C by revenue and instead measure them by..." but then it's somewhat hard to figure out what the next words are. "Code quality" is something engineers would love to say, but even engineers on some level tend to recognize that does not actually put food on the table, so to speak. (It is an important element of considerations of how to spend resources, and I would agree that it is often underestimated. But it makes no sense for it to be the prime measurement of a team's output, even before we get into the issues involved in objective measurement of code quality.) It's really hard to avoid having at least some of your development teams being measured directly in dollars in one form or another, and from there the rest of these forces tend to flow.
The Ultimate Guide to Web Data Extraction – Product Hunt
I previously did Angular 1, and I agree that an Angular 1 background is highly complementary to grasping Vue quickly.

However, Angular is very highly opinionated about how to structure your application and demands exacting tribute to its mandatory "design patterns" of "services", "factories", "providers" and all this other nonsense. Consequently, the minimally viable boilerplate for even a small Angular 1 app goes up considerably.

My favourite thing about Vue is that it's not opinionated in that manner. You are free to write your own JS as you please and structure your application however you like, using as little or as much of Vue as you like. While it scales well to large projects, for small projects, which are the vast majority of my projects, you don't have to do all this _crap_ just to get started.

Angular 2 is criminal insanity from a practical perspective. It's the worst of J2EE-style monstrosity-building. When you need tools just to generate untold amounts of boilerplate just to get to Hello World, you've crossed the boondoggle event horizon.
I use sublime text as my main editor, but I still need to use vi from time-to-time - e.g. when ssh'ing to a remote server. That's definitely an objective need, unless you can offer an alternative that is just as widely available.