skysight-inc/HackerNews huggingface dataset:
"for all the deficiencies Go has, it is somehow highly compatible with the way my brain works."

I have been tempted to write a blog post about "Why People Actually Can Write Real Programs In Go." To listen to HN complain about the language you'd think that it must be clearly impossible to ever write a program of any kind without massively copying and pasting everywhere, when in reality I find it's actually quite pleasant for a non-trivial subset of programs.

The short answer is that it has a lot of features that people, generally not being used to them, work better than people may realize from the bullet points and often work together better than people realize. Favoring composition over inheritance is a legitimately good choice. Being able to declare interfaces that other objects I don't control conform to has a lot of little effects that you wouldn't anticipate in advance, to the point that while I understand the bondage&discipline impulse to require code to declare what interfaces it supports, I would consider that a legitimate mistake in most of the languages that do that. (In practice, it turns out the problem of "accidental satisfaction" basically doesn't exist. We learned that from the duck typing languages like Python and how they never really had a problem with that.) And while the grand concurrency stuff may seem neat, the little stuff can be nice too; just yesterday I wrote some code that takes a list of servers to query for some particular thing, and it was easy to write it to do them all simultaneously; that wasn't a Grand Architecture thing, it was just a function that casually did something that is a royal pain in many languages. (There are also languages that can do it better; I actually know many of them. Erlang would be roughly a tie here and Haskell could look really awesome if you put a bit of work into it. Elixir might beat Go, not sure, but I know Erlang itself doesn't.) And there's some other things like that.

The other thing about Go is that I like it for work, but not necessarily for my hobby. The thing about all those restrictions in Go that apply to me is that they symmetrically apply to my coworkers. As much fun as a more powerful language can be, it becomes a lot less fun when you've got dozens of developers trying to work in one code base in those languages; what is power for you is power for them, too, and, well, let's just say they are not always going to be the most expert developers in the world. I've seen... things. And at times, I've even been the one who did the "... things". So even though I know how to use Haskell productively and generally correctly, I'm generally very uninterested in introducing it into the team environment that I have. This is, IMHO, a very important point that I don't hear discussed often enough.

Basically, if you take HN's opinion of "Go is useless and should be wiped from the face of the Earth" as a scientific theory that predicts how useful it would be, the theory is falsified. It is useful and some of us even enjoy it for certain tasks. But I for one would never suggest it is useful for everything and actually frequently warn people off from certain tasks.
Go has functions with multiple return values. That's not at all the same.
> This is probably an ill thought through rant but...

Everything after the "but" and all.

The whole point of Redux is to separate actions and state manipulation. An argument that, "well I want to manipulate variables feely," is not an argument. Just don't use Redux. End of story.

The pattern doesn't come from React. There are many patterns in React that are just Monads by a different name. Redux isn't much different.
> She didn't flinch and just went on about her business like nothing had happened, and he was thinking what a fuss/embarrassment etc that would have caused if it happened in a hotel in the US -- when it's just an adult being naked with another adult present. It's not like everybody hasn't seen genitals before or it's a big deal.

I'd caution against using a single situational anecdote and drawing conclusions about an entire culture. For one, it's highly likely that many maids in the U.S. (especially at a dedicated guesthouse or bathhouse) would also have a more minimized reaction to guest nudity and privacy. The experienced ones have seen some shit.
You are just choosing a precise meaning for "wishes" and hammering on that.

Look at the context and consider a scenario where a will has a statement that Facebook should be deleted (or frozen or whatever). The comment I replied to implies the statement shouldn't matter if someone living wants something else.

My meaning was something like the whole concept of a will is about respecting and recognizing the priorities expressed by the dead.

I don't disagree with what you say about what people do with things they inherit, but you are imputing an awful lot of meaning to make that a contradiction of my sentence that I posted above.
Try https://github.com/hplgit/doconce .
Controlled doesn't mean "I am writing as Grandpa" but rather "I am writing on behalf of Grandpa."

Part of what needs to be addressed is "is what I write and what I control online part of my _identity_ or part of my _intellectual property_?"

No, a person inheriting the estate doesn't have the right to pretend to be Grandpa and collect social security checks or defraud people based on that identity.

Yes, a person inheriting the estate does have the right to take the collected poetry and essays that Grandpa wrote and publishing it. ... even if they are published on Facebook.

Are Facebook, Twitter, Github etc... in the first category or the second category?

Microsoft outlook has a neat feature to "send on behalf of" (account settings, delegate access). Such an approach would be something to consider for an online presence to distinguish who is doing the sending - the deceased or the estate.
I don't know if that is really morally objectionable either.
I totally agree, but based on the reaction to this guys christmas cards after he died [1] this idea is not received well (which i dont understand). You are thinking about loved ones in the future by your request. I doube FB would go for it.

[1] http://www.nbcnews.com/id/22394223/ns/us_news-weird_news/t/d...
Designing a "checkedInt" class is not trivial
Humans aren't black boxes. You can press them on their reasoning, and they often experience public criticism if they refuse to provide it.
This culture sounds like, "at first they wouldn't hire me, because I looked different. But I kept coming around, and they let me start sweeping the floor."
Learning to Map Vehicles into Bird’s Eye View [pdf]
If you use something like Kea (https://kea.js.org), the amount of boilerplate for Redux goes down dramatically. The syntax is actually pretty simiar to Vuex, perhaps with even less boilerplate.
The smaller thread should also be big enough to be found on the first 10 pages, but I couldn't find it there.
> Clearly you don't, because you've intentionally designed a license to allow you carte blanche to violate other companies' patents if they're dependent enough upon React to not be able to easily stop using it.

I think it's pretty clear how disingenuous this is since they don't even constrain the patent revocation to IP lawsuits.

If they were doing this in good faith they would want to scope this as tightly as they could, but this is clearly Facebook just trying to extract additional benefit from their OSS contributions.
> If you want a full blown huge application to last years, then go Angular.

After what they did with Angular 1 -> 2 not a chance.

At least with Vue you can swap it out a lot more easily if it does go away in 3 years.
https://burners.me/2017/08/09/how-to-deal-with-cops-at-burni...
Social media have a tremendous number of factors contributing to success or failure. It's hard to pin it to single factors.

Technology is almost never the initial driver, though it's also quite frequently a determining factor at scale.

The most critical key factor is probably in achieving a coherent and compelling founding cohort. Both Usenet and Facebook effectively started at selective-admissions academic institutions -- Usenet at UNC and Duke, then spreading through the early Arpanet. Facebook, of course, at Harvard.

Usenet failed for numerous reasons, including superior alternatives (largely blogs and mailing lists), but also because for various reasons (cultural and technical), hostng Usenet feeds was both not profitable and an increasing liability. Spam, warez, pr0n, and various other activities created risks, and there was no real option for advertising or other means of revenue generation.

(Universities hosted Usenet as long as they did in part because it addressed an institutional need: communications and collaboration across distances. There was no effective alternative at the time.)

Facebook has managed to do what Usenet couldn't, which is to survive, so far, the Eternal September. At 2.2 billion users, it's the largest single integrated social networking system ever. Something I note with appreciation despite pretty much despising the company and what it's doing.

As to Mastodon: I'm on it, I'm asctive. It's faded a bit since April as initial interest is giving way, but it remains active. And GNU Social of course rocks on (and rags on the New Upstart to Get Off Its Lawn....)
Thanks, that looks pretty reasonable.
You have it backwards.

If you have a patent, and use React, you can't sue Facebook if they use your patent.
No it is NOT identical. In situation A/C (React is licensed under BSD + PATENTS), you have explicitly agreed to have what is essentially your lawful use of React immediately revoked if you sue Facebook for patent infringement. So you sue Facebook, and whether or not your suit is of merit: You have to immediately stop using React. This actually prevents people who are dependent on React from suing Facebook for patent infringement, since they'd basically have to remove any dependency on React before suing. And this emboldens Facebook to infringe on the patents of entities who have a dependency on React, where it would be a major undertaking for the React-dependent organization to cease the use of react. Remember, Facebook is saying they have this in place to prevent merit-less legal battles. But the way they've set it up, it's not a question of whether your suit has merit or not. Facebook is saying "Sue us for patent infringement, and you immediately give up your use of React. Period." So the court rules in your favor over an unrelated patent infringement case? Congrats you won that case, but you've still given up your use of React, because you sued Facebook.

In situation B (React is licensed under just BSD), the patent rights necessary to use React are not written in explicit terms. You have made no explicit agreement to have your patent grant to use React revoked when you sue Facebook for patent infringement. In addition, without an explicit patent grant, a patent grant is implied with the license. You can at least continue to use React until the results of the court case.
Sounds like a sport for assholes
React has multiple alternatives to JSX too.
Well, I guess I just can't see any reason why a mod of HN would prefer the older thread over the more active one, and thereby removing its position from the front page and stop any further HN discussion altogether on the topic. Even the older thread is not present at all on the front page, or any subsequent pages.

Anecdotal, but it certainly _feels_ like an attempt to censor the topic at hand. Now that I think about it, I agree that my choice of title wasn't the best to be quite confrontational, but it is what spurred my creation of this thread.
"Flamewar" has become a weasel word for interesting discussion.

It's a shame HN actively combats debate, the only discussion allowed here is about benign stuff where mostly everyone here agrees.
> Some company that has failed as a startup, but which holds 1-2 patents might decide to turn into patent-trolling to make a quick back while it dies.

If the startup is dead it should be trivial to transfer the patents to a separate entity and then sue from that entity, making counter-suits irrelevant.

This only has an affect on companies which are a going concern.

Companies who plan to make litigation part of their strategy can pretty easily just not use React.

This does the most harm to companies who were not planning to come into conflict with Facebook, and then do.
Two weeks is a tiny investment to properly evaluate a language. Haskell is tripping you up because you're likely new to proper FP and very strongly typed languages. Pushing past two weeks, even if you don't use it, will make you a better developer, and the next FP or strongly typed language will come more easily.
They revoke the React patent grant, which effectively downgrades "the React license" to just a stock BSD 3-clause license. At that point they will likely counter-sue you for patent infringement.

In my mind that situation is effectively identical to losing "the right to use" license on grounds of patent suit (like Apache). Interestingly, in Apache you'd still be sued for patent infringement (not copyright infringement) because "right to use" is provided as a patent license.
n00b. off mah lawn.

https://en.wikipedia.org/wiki/Eternal_September

:)
>Is it a symbol of puritanical values?

It fills the void of moral panic previously occupied by transvestites, homosexuals, adulterers, divorcees and witches (in that order). Give it enough time and the society will find the next deviant behavior to raise their collective pitchfork.
> So pictures of KKK members killing little black girls would be fine as long as the images were "drawn"?

Much worse things are displayed in comics and described in books. What's confusing here?

It's fiction, and there's no reason I can see, except in the light of very special evidence that such drawings have an effect on the incidence of such events taking place (which is similar to when people say that violent video games cause children to become murderers later in life), to make it illegal.

Unless you have evidence or an argument, that is. It seems to contradict the notion of liberal democracy to engage in such censorship of artwork and fiction.
Socialism has failed 100% of the time. You can't get worse than that. Even if capitalist systems failed to improve the lives of the poor 95% of the time, it would still have a better track record. In reality, the most successful countries are all capitalist and free markets have lifted more people out of poverty than anything else.

The fact that some autocratic countries also employ capitalism doesn't change that. Capitalism doesn't magically cure corruption, it's merely a superior economic system. Poverty isn't a function of wealth inequality, it's function of economic development. In a socialist system, the poor may be less poor in relative terms, but they're more poor in absolute terms, because socialist economics eventually fail.
This.

How much simpler than functions as components, that get their props as parameters could it get?

Every example of Vue components I have seen was more complicated...
Google cache does not transform the content.
>"I love the principle, but I can't use it with AWS, ..."

You can use Google Authenticator with TOTP with you AWS console. Or am I misunderstanding your comment?

It's not a hardware device obviously but its the same principle, just implemented in software.
The active discussion was closed, the "correct" discussion is nowhere to be found without searching explicitly for the discussion.

Whether censorship was the intent or not, it's the effective result.
I've read ISL and ESL. ISL is a practical introduction to concepts, and ESL goes deeper into the algorithms.

This books seems like a historical survey of how things came to be, rather than a practical guide. I believe this is not a book for practitioners, but for someone who is looking to advance the field (researchers, Ph.D. students).

As someone who was in academia in 12 years, I think it is immensely valuable to have a survey like this because too often new researchers don't have a clear idea what has been tried before and why they failed or succeeded.
Understanding the Facebook vs. Apache Software Foundation License Kerfuffle
Elm is also promising: http://www.oreilly.com/web-platform/free/files/why-elm.pdf
Models of emotion
How is sexuality repressed in Japan?

Hentai etc are descendants of shunga pics; you've probably seen Hokusai's "The Great Wave Off Kanagawa". You may have seen "The Dream of
The Fishermans Wife" (NSFW)
No application lasts "years" nowadays, so I'd suggest not go "go Angular" simply because it's Angular. The modularity and speed-to-productivity of Vue is the reason I choose it. Plus, the community is quite supportive; always nice.
Congratulations on losing 40 pounds!

To your first point, it's great to see you say that: I see this repeated so often, yet I observe very few people actually internalizing it even when they hear it from others. The most effective and efficient method for consistently losing weight is diet control.

Exercise (specifically the type and intensity) changes body composition, but diet alone impacts overall mass. You can't expect to lose much weight just because you're running - it might push you into a caloric deficit if you're not already, but it will take focused effort not to unconsciously eat more to compensate if you're not used to controlling your diet already.

Gaining mass at a caloric deficit will be impossible no matter how much weight training you do (but again: composition will alter), and losing mass will be impossible at a caloric surplus no matter how much running you do! Someone with specific fitness goals needs to strategically optimize both their exercise regimen and diet.
It is very much illegal, as is stories depicting it. Here's an Australian supreme court of the Northern Territory case describing such a ruling: http://www.supremecourt.nt.gov.au/documents/judgements/2014/...

It is also illegal in Canada (similarly with stories), some US states, some European countries, and England, Wales and Northern Ireland (though only drawings rather than stories as far as I know).

I think such laws are hideous.
Ranking history for the two stories: one story decayed over many hours, one story was at the top of the front page for hours. Guess which one was marked as a [dupe]?

http://hnrankings.info/15050841,15050705/

Is there a way for users to "vouch" that a story is not a dupe?

Edit: Ranking of this Ask HN:

http://hnrankings.info/15053297/

Edit2 (1440 UTC): the [dupe] tag has been removed and the story is back on the front page, rank #11.
It is possible it was flagged by too many users. Censoring can happen from the users themselves and I think the "flag" button should be replaced or deactivated for users with weak Karma.
That's the mechanism by which HN does censorship.

For another example see: https://news.ycombinator.com/item?id=12285545

This was marked as a duplicate of a PDF version of this essay that was submitted over 270 days prior to that being submitted.

It was high up on the front page and then gone out of nowhere.

I fully expect dang to come and remove this comment but we'll see.
Yes, my impression is that Go was created partly to be used in corporate environments to replace Java with a less verbose language that scaled well, and it seems to be doing well in that regard.
Apache revokes your rights under the patent section of the license if you sue anyone for patents granted under said license:

> If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.

Note that the "Grant of Copyright License" of Apache doesn't grant you the right to use the work, so revoking the patent license is effectively revoking the whole license (though you can still redistribute the work).
Probably penalized by user flags. Unfortunate that user flags can have such an outsized impact on the discoverability of important topics.
Child porn and Nazi stuff have long been really bright lines in user content. Recent events have revealed more acceptance of Nazis and adjacent groups in our society than previously thought, so I guess I could see the taboo against child-porn easing up too. Very sad and scary.
He is alleging that HN purposefully uses questionable dupe marking decisions to make the react discussion undiscoverable, effectively censoring it.
What Should You Do with Your Crappy Little Services Business? (2011)
Cake and dont forget Wikipedia.
TheVirtualBrain
> One of the downsides of Webview based apps is that it's harder to align with the native OS look and feel.

Is this really a problem though? It doesn't seem crazy to want your app to just look the same on all platforms.
I'm perplexed as to how the author managed to find the Pixiv sign-up page offensive - if he hadn't mentioned it I would never have made the connection myself.
I've heard the same "it pays the bills" argument quite often for PHP. ;)
I was a huge Ember evangelist until I started trying to onboard other devs into my project. It took months for people to figure out which way was up. In comparison, other devs picked up Vue in a week or so.
Your link [2] came 1 hour before your link [1]. Don't think there's anything malicious going on there, they just marked the one that came later as a dupe.
Today I sold Ether token for Augur reputation token just to give it a try via the OTC Dapp. No middleman, cost me almost nothing, it was a great!
There's a lot of potential in this technology IMO
The big thing with Docker containers is that you don't patch or update them.

You include patches in the build process that produces a patched image. You then tear down your containers and deploy the new image.

One of the main benefits is once you have a proper pipeline setup you just modify your Dockerfile commit it to git, the build happens automatically and then it's automatically deployed once the new image is checked in to the repo.

Now the all your containers are "magically" patched. Imagine having to patch a CVE in each of your VMs. Quite different.

VMs are pets. Containers are cattle.
Define "massive Western intervention" first. Socialist policy at one point in history ruled half the world's economy. You'd think at that size, if those policies made any sense, it should be able to do fine even without the West.
An Examination of the risks of building your enterprise stack
The Total Solar Eclipse We Deserve
It surprises me how this "vue vs react" gets to the first line for the 10th time in one or another form
I find it very concerning. I'm a member of a group that has been accused of hate (mainstream religion). It's completely false, and things have to really be twisted to even pretend it, but get the right mob fired up and I'll be thrown under the bus too. And if you think you're safe, I'll bet I can find somewhere in the world where at least one of your beliefs could be attacked too. That's why due process is important, rather than mob justice.
> Flutter is not based on webviews, but is also not using the native widgets but instead rendering custom widgets.

Yeah, I only just realised this after further looking into it today (when I last checked their site, they only had one page introducing the project). They try to spin this from a negative to a positive[1], by saying that they think they can guarantee the Flutter widgets quality and performance compared to native widgets, and it's on them (the Flutter devs) to make sure those widgets are up to date to the look and feel of the platform.

Which to me just seems like trying to solve a non-issue in the first place, not to mention depending on the Flutter developers to ensure their supported widgets remain up-to-date to the platforms standards and not deviate in any way.

[1] https://flutter.io/faq/#does-flutter-use-my-systems-oem-widg...