skysight-inc/HackerNews huggingface dataset:
I evaluated React and Angular 2 several months ago and picked React. Some of the issues I found in Angular 2:

The HTML template in Angular 2 is stored in a string. This has several disadvantages:

1. Editors can't do syntax coloring.

2. Editors can't do auto-indenting.

3. Editors can't offer "intellisense" suggestions.

4. Editors can't match tags.

You embed variables in this template string like this: '<div>{{hero.name}}</div>'.

This means:

1. Compilers can't find typos or find syntax errors at compile time.

2. If you make a typo in the variable name you don't get a compile-time or run-time error, instead the value is simply not displayed!

3. Tools can't refactor (i.e., rename) variables embedded inside the template.

4. No intellisense for the embedded expressions.

You have to learn weird syntax such as ngFor whereas in React you just use a JavaScript for loop.

In React you embed HTML inside the TypeScript and VisualStudio treats both the HTML and the TypeScript as first-class citizens. You get compile-time checks and intellisense for both the HTML and the TypeScript code! You can even put breakpoint inside the template and step through loops whereas in Angular you can't step through an ngFor.

Note that some of the above may have changed since I last looked at Angular 2.
I'd be interested to hear people's experiences with running Angular 1 and 2 side by side in the same application for the purposes of incrementally migrating an Angular 1 codebase.
Angular's module syntax, while it makes sense, it's just easiest way to get version control merge conflicts. Even easier than import statements... since these can be put into oneliners.
Most other animals won't fight to the death. They might fight far enough to determine a victor, but usually the fight or conflict is over quickly or before the conflict actually takes place.

Humans on the other hand will pursue the illogical course of self-destruction for the slight chance of "moral victory."
It's still maintained and they have curator for AngularJS 1.x still.
From an european POV I'd guess it has to do with fire-at-will and litigation-happy culture combined with scant labor protections for white-collar positions & low union participation. Maybe people are reluctant to raise issues until it's blatant enough that they can win a court case if they are shrugged off and fired by the employer?

In many north european countries you could take these up as a workplace bullying issue and possibly escalate to your municipal workplace safety ombudsman and/or union rep. But in most cases you wouldn't have to, your grievances would be taken seriously internally because there's the threat of escalation that won't necessarily end with the victim leaving the company.
That's the easy part though. Australian sellers who ship from overseas would be committing tax fraud not to start collecting GST on these sales.
Keep in mind that Microsoft itself writes and/or maintains a lot of software for Linux - as you can imagine, WSL comes in very handy there.
Wada hacking scandal: debate turns to the use of powerful legal drugs
Let's add: clean, simple theme and layout that doesn't allow users to customize how other people see their page.

MySpace was a trainwreck. The default layout was horrendous, and each user had their own themes, many of which were unreadable (I remember having to select text just to read it).
Here's a Theano implementation: https://github.com/huyouare/WaveNet-Theano
We have been using Angular 2 seriously in the past month at my company.

There is a lot of roughness around currently when it came to upgrades during the RCs - Angular 2 was far from full-fledged even during the earlier ones, and has come a long way in the course of their development. Testing has a massive gap in documentation/articles on how to do it right. There are also some pains such as some (IMO somewhat poor) opinionation in the Angular router, especially when combining with server-side routing - had some battles integrating the Angular 2 app with the full server-side app for work, in large part due to hapi's major deficiencies when it comes to delegating routing to a frontend only application. Setting up can be daunting, although I got a large boost from using https://github.com/preboot/angular2-webpack, a great starter pack largely maintained by a member of the Angular docs team. Not all of the benefits are easy to tap into currently, such as the fairly recent AoT compilation, which lacks any plugin support for any build system such as Webpack currently. I intended to write one & open source it, but I was assured by a member of the Angular team that it was on the docket to complete. Documentation also needs a lot of work to be more developer friendly, I have found senior developers making easy mistakes with Angular 2 because they are not familiar with how to structure everything while having to produce on difficult story work. Testing is also a sore point, especially with the need for the karma shim to be produced for each app.

That said, Angular 2 is a phenomenal upgrade over Angular 1 in the ease of structuring apps. It also avoids incorrectly munging everything into components, avoids imperative logic to construct DOM/components, and imposes opinionation & more modern tooling such as the availability of observables to more correctly manage app state & app flow. It is fast, and much easier to tap into optimizations than Angular 1, where one had to be able to work close to the source code in order to understand everything one can and cannot do. It also offers the flexibility to do everything one can do with React, including server-side rendering (with the ability to do so on platforms such as PHP, Java, Node, and .Net in the pipeline), web workers, service workers, and multiplatform apps via React Native or NativeScript.
Maybe they can distillate the ensemble in a compact and efficient version for production.
YMMV, but I find sytse so hugely overbearing that I actively don't want to use GitLab because I don't want to encourage what I see as tacky, bad behavior. He and other GitLab staff can do as they like, but I'm not rewarding it.
It seems unlikely it'd actually get implemented.
Says who? You and a few others? Lots of people disagree so maybe you are in a tough shit scenario here.

Unless you actually have got someone fired for an innocuous comment. Then it's tough shit for them, I suppose.
Pretty cool. But I'll eat my hat if a regular webcam can pick up enough detail in regular lighting to do this. Plus 90% of the time the webcam will capture a users chest and the wall behind them, hardly useful for visual microphones.
What about the part where we stop buying products with integrated cameras?

What about the part where we stop buying devices that we have seeemingly no hope of control over?

What about that?

Is boycott a word too strong?

Gee, you're right.

We should all just give up, and accept that what we're sold, is that which we must buy.
I don't know how much of the last season you watched, but the show's writers certainly seem to be of the opinion that progressive ideas are preferable to Trumpism.
The template vs. JSX argument is highly subjective; a lot of people go the other way because language extensions break existing plugins, require extra build tooling, and add complexity.
FISA is all flavours of horrible. But what it doesn't do is provide a venue for convictions. Only (and I grit my teeth and clench my gut when I write that) approval of surveillance requests.

In a no-contest, no-appeal, rubber-stamp, kangaroo court, yes.

But only surveillance orders.

And, my error, it was whamlastxmas who went full tinfoilhattery on us, not you. The inability to see up/down thread when responding to an HN comment is a bit crippling. I apologise for my third point, that doesn't apply to you.

Your clarification that some other people might think Snowden's already been convicted (by a court which cannot convict, no less) might have legs, though I've seen no particular evidence of it. The strictures against in abstentia convictions make it little more than a myth, and it probably shouldn't be offered without noting that it violates numerous elements of US statutory and case law.
Correction: Australian government will attempt to restrict IP addresses of certain sellers when a large, party-supporting local retailer submits a complaint about them. (I.E. Gerry Harvey)
i knew what you were saying. no harm intended <3
It's not truly contained, though. There is no security boundary between the host and the guest there - WSL can access your entire filesystem, for example (subject to usual ACL checks, of course).

The reverse is also true, by the way - WSL portion of filesystem can be observed directly from Win32 (cd %USERPROFILE%\AppData\Local\lxss and look around, but don't touch - there's some magical pixie dust there that's easy to disturb and break things from the Linux side of things).
Yeah I would agree it's a move against osx. I run debian on a raspberry pi3 don't even deal with Windows but this is clearly aimed at the corporate web developers where you have a macosx near monopoly.
Yes, my SF apartment gets moldy and musty smelling if I don't run my dehumidifier all the time. I think I have some kind of allergy. Does wonders for my PG&E bill.
What a shame a philosophy education confers no ability to address such a question meaningfully.

The counterpoint, of course, is that over the course of human history, philosophy has a better track record than anything else at producing fruitful inquiry and results. It's just that the results always end up branded as entirely new fields of study, meaning that what's left in the "philosophy" bucket is the stuff which hasn't yet been productive enough to spawn an entire separate field.
This is the return of Multiple Master fonts that I always wished would happen but gave up hope on.

Color me very, very impressed.
Can't wait for Angular 3!
For me, it's easiest to pretend that GraphQL is a DSL (a domain-specific language) that offers special syntax to make it easier to implement certain things.

- You can pretend that each GraphQL query is a JSON object (which, it actually is)

- You can pretend that each GraphQL schema that you declare is actually a JSON-Schema document, which some people use to specify in a machine-readable way your API's inputs and outputs will look

- You can pretend that each GraphQL resolver, which the piece of code you have to write (on the server) to actually dig up the result of a query, is a function that parses your incoming JSON, validates it against your JSON-Schema, and then reaches out to your datastore to produce a result. You'd then have to construct another JSON document which matches your response schema, stuff the data in it, and return that to the user. Except that in GraphQL, you only have to supply the resolver, the rest is handled by the framework.

You can of course do this by hand and many people do (most obviously when you see APIs that include arguments like "operator=eq" or "limit=100" or "page=25"), but GraphQL gives you the tools to do this with less effort, and end up with a cleaner API by passing everything in the query body. And the GraphQL server saves you from having to manually build up the JSON text of every single response.

Reading through your docs, I've seen this style of API in enterprise settings where there was a backing relational database and the designers were basically trying to expose the underlying database through HTTP. It can get the job done, but GraphQL gives you nicer abstractions, a cleaner way of passing parameters, and conveniences like a real type system (known both on the client and server side) and you only have to supply your resolver function implementations.
Others, such as Google, do the same. They develop some system in their labs, but put in production a worse system because it has lower resource usage.
What a bullshit article. The author clearly has no idea what the hell they're talking about.

Pepe the frog belongs to the cancer that is /pol/ no more so than pictures with captions using Impact font superimposed over them. The only reason pepe is associated with /pol/ and Trump is because they both originated on 4chan as memes. The Trump versions of pepe comics are only a minority fraction of the many different permutations of the meme, ranging from "smug pepe" to "rare pepes."
Which editors? JetBrains Webstorm has the same things for both Angular2 and React.

https://www.jetbrains.com/webstorm/whatsnew/#v2016-2-angular...

I do agree that I really really was a fan of the backticks for ES6 / react for templating. Avoiding the whole " vs ' escaping nightmare is something i've always looked forward to.

That seems like a very simple fix for them though, potentially.

edit: tone
Seems like you discovered it already, but shin splints, knee problems, back problems, etc. are usually based in either bad shoes or bad form. There are also strengthening exercises you can do for each to make you less susceptible to them.

Often times the body's limitations are caused by problems that can be fixed or worked around, allowing you to push yourself farther and harder without hurting your health.
You don't choose between those two routers, they are not replacements for each other.

At the risk of stating the obvious, the Angular router handles routing for the Angular frontend, the Go router handles routing for the Go backend (the initial page load, the AJAX calls made from Angular to get data...).
IMO:

A lot of people seems to think they are smart because they belong to a powerful or politically correct group.

Also a lot of people seems to think they are smart because they are rooting for the underdog or just plain contrarian. ; )
Getting to use Scheme was almost an accident.

We had a dual Python/C stack, where we basically had a prototype in Python, running for small clients, and then a better C one for embedded devices.

We decided that was a bad idea, and went to rewrite the C for both consumer and embedded devices.

However, the lack of progress had the manager investigating all kinds of things, like MicroPython.

I had been playing around with Scheme in my spare time, and pointed out that Scheme was almost as fast as C, and almost as fast as Python for prototyping.

They handed me a test to see if Scheme was suitable -> Rewrite our Python prototype in Scheme, within three weeks.

Because of how consistent Scheme is, and how close Python's syntax is to it, it only took me three days.

With the decent C output of Gambit's compiler, I wrote a script that modified it to work on our embedded devices as well, in another three days.

The manager was sold, and our whole team moved to Scheme.

I was very unpopular for a few months.

As to the actual project? The little I can say, as it isn't launched yet, is that it's a kit designed for schools.
Opening that link in a new tab beach-balled Firefox for a few seconds. Woof.
Person 4's fascist solipsism is astounding. She has transferred the "toxicity" and "unacceptability"in her own mind onto the whole team.

A song was referred to but there was no actual mention of sexual assault. The song is not "completely unacceptable" as it is obviously commonly known and legally sold. It is therefore acceptable in the workplace, referred to as it actually was.
There seems to be a lot of advocacy for tossing everything into the component tree in the React ecosystem - recently I got linked to a snide remark by Ryan Florence on Twitter implicitly arguing for putting everything in the component tree, including constructs that should have a better separation such as routing (which the tweet appeared to be a reference to).

Some services don't belong in JSX though - this is why you have the idea of stores in Flux/Redux/etc. Some data doesn't make sense to couple to the component hierarchy - doing so makes it very easy to create dependencies on the component tree, which decreases modularity, as well as has perf ramifications by increasing the DOM elements that get rendered unnecessarily by React. Some examples are data models, routing, and interactions with non-element DOM api (window.location, XHR, etc.). This also has a side-effect of increasing difficulty of testing what generally should be vanilla constructs not tied to various frameworks/libraries unnecessarily.
Auto-GCAS started pulling out at 8,760 feet ASL and bottomed out at a hair under 3,000ft AGL (Judging by the Radar altimeter).

It looks like the pilot start pulling back on the stick at about 6,690ft ASL (Based on the G-Meter going above 5Gs). If the pilot had woken up at that point and immediately pulled back then the AGL clearance drops to about 1,100ft AGL.

Then we have to consider the fact that the plane was already pulling up when the pilot yanked back on the stick. Had the Auto-GCAS not already been pulling the plane up then the pilot would have been lower when he started the recovery.

The "At this point" in the article is not well worded because "At this point" actually looks to be a second or so after Auto-GCAS activated which, when plummeting towards the ground at 650 knots in a 55 degree dive. is basically another 500'ish feet lost

All in all this implies HEAVILY that even if the pilot recovered without Auto-GCAS the margin between survival and lawn-darting would have been a LOT less than 1000ft which is far too close for comfort.
Can someone who knows about tax law explain what the scope of the GST is with regards to imports? I.e. how big of a deal is this?

Does everyone who sells items to Australian purchasers have to pay GST? Or is the GST only applied for some corner cases where, (for example) Australians sell stuff to each other, but involve an oversees leg in the deal?

(Edit: this is of course a seperate issue from how blocking capabilities can be abused in future...)
Conda seems to deal with binary packages only. Solves a different problem.
We're all going to get a couple of nights sleep, but that project is in progress and should be out soon. We're making sure it shows off the best of ng2.
I was really frightened with it. But webstorm from jetbrains has an EAP version which basically shows your compiled JS file "nested" under your typescript file. It's a small seamingly meaningless change that was the difference with me being comfortable with TS vs. not -- screenshot here:

http://imgur.com/CLTk3wB
Compare for yourself:

https://react-bootstrap.github.io/components.html#btn-dropdo...
(click on show code)

vs

https://ng-bootstrap.github.io/#/components/dropdown
(click on <>)
Cool... Is there anyway to combine this with a seam carving approach?
For reference (this post is clearly mimicking the format):
https://www.hillaryclinton.com/feed/donald-trump-pepe-the-fr...

and:
http://i.imgur.com/Pe27DXI.jpg

My best explanation for Pepe is sort of a collective Baader Meinhof where 10,000 trolls spending a million hours posting Pepe memes eventually piece together a semi-coherent mythology via a vast trawl through frog symbological history.

It is sort of painfully funny that serious organizations like SPLC and the Clinton campaign have seemingly fallen for an intentional trolling effort. [1]

[1] http://dailycaller.com/2016/09/14/heres-how-two-twitter-pran...
> Surprised they are not focusing on LOCAL Aussie ecommerce sites that don't collect and remit GST for local sales.

Like?
I don't know about that. From a pure physical health perspective (i.e. discounting convenience, cost and supposed mental health benefits), there are a bunch of exercises that are strictly superior to running. They provide all of the cardio benefits of running, but without the prevalence of joint injury when you crank up the time investment. Some good examples are swimming, biking, or using a rowing machine.

I'm a big believer in the idea that motivation trumps all other considerations when it comes to exercise though, so you should run if you like running.
As see I on github there are lot of issues - https://github.com/angular/angular/milestone/58 for final release., however they released it. These issues are not important? Who can clarify?
Tips and tricks on how Docker can be useful when working with Go code
Just look around on the internet, you'll find the same thing. I researched this a few weeks ago and was amazed.

You basically have to disable the audio driver in OSX to disable it, and doing that, means you can't play audio at all. And even that isn't enough, it technically can be hijacked at an even lower level.
Really interesting findings on clickbait. I worry about the viability of the second half, using machine learning to detect bias (which seemed admittedly inconclusive).

> finding bias in headlines is a more subjective exercise than finding it in Wikipedia articles...

Probably because bias from new Wikipedia users is less careful. And absent smoking guns, once you get into the gray areas, several studies have shown bias is often in the eye of the beholder:

https://en.wikipedia.org/wiki/Hostile_media_effect
I think your second sentence is wrong or at least very misleading. The bolt is not the only long distance practical ev. The tesla model s and x are exactly that. The bolt is cheaper, and has great range (less than existing teslas), but the bolt is much less practical because it charges much more slowly and has a drastically less comprehensive and less reliable network. The tesla covers the country and has been shown to be reliable.

The bolt is a great car, but its recharging network makes it far less reliable as a long distance car. It's shorter range is part of that, but its not as important as the fast recharger network availability.
I think you're being a bit quick to judge people here…

Having an integrated camera is obviously a lot easier to deal with, logistically, than lugging along an external USB camera.

I think a lot of the people here would love to have hardware-level kill switches for their video camera. And mic. And WiFi. (I would; I used to own a Thinkpad with a hardware kill switch for WiFi. It was useful, even aside from the privacy benefits.)
I'm not sure if that's really true about mathematicians lacking rigour.

I do recall a logic professor of mine jokingly say that mathematicians were afraid of logicians, and (more seriously) that the former thought the latter were unnecessarily precise. (I hope I'm remembering this right and not misrepresenting what he said)

I'm not sure about the superiority in rigour in the rest of philosophy (even if we narrow the meaning of that term to just analytic philosophy, some of whom sure are fond of their logic, symbols and attempting to sound "scientific" or rigorous). If anything, I'd say those analytic philosophers have math (or hard science) envy.

You're right about mathematicians not being very interested in the foundations of math. That's a consequence of the failure of the great foundational project in the early 20th century. From what I understand, most mathematicians have decided that such a foundation is not possible, and view themselves as moving on to doing the very practical business of math anyway. After all, the lack of a foundation has not prevented them from achieving many interesting (and often useful) results.

That said, there has continued to be interest in foundations for math from some logicians, and (at least according to my logic professor) it still might be possible to found math on logic yet. That's quite a bit out of my league, however, so I'm afraid I can't elaborate much. But if you're interested in that, I do recommend taking some courses in symbolic logic and in the philosophy of math.
There are three grocery stores within a 15-minute walk of my house. Two of them are next to the nearest subway stop; they add no more to my commute than walking through a parking lot would add to yours. The subway gets me to many useful places in 30 minutes.

My time is valuable, and I spend none of it stuck in traffic or looking for parking.

Advocating for density means that more people have the option of living this way.

You've been served badly by public transit, but you seem to be saying that public transit should be as bad for everyone as it is for you.