skysight-inc/HackerNews huggingface dataset:
The value the scalper provides can still be analogous to transporting some goods across a distance. They act as a middleman that changes the availability of the thing they sell.

I'm not arguing in favor of scalping, I'm just saying that the good arguments against are about fairness, they aren't economic.

For instance, there is always the option of not attending a concert. This is not the same things as "no other options".
>I'm sure in Asia all little 1-2 people phone and laptop stores do?

Can't speak for all of them, but one that I visited in Hong Kong to do a screen replacement definitely had a guy sitting at a counter breaking down a stack of used iPhones for parts.
Is violent sport an inherent part of a country's psychic makeup? Mexico has wrestling? What about Bermuda?
That is to tie your wifi access point to a specific location. They can then use this information to deduce the location of users who are not using GPS too. They can use it to deduce relationships between people who are connected to same wifi at the same time. They can deduce what time you are at what location and predict where you will be next. The possibilities are endless.
They need to fix their ui on mobile, there's no way to listen to the podcast and most people listen to podcasts on the go I would imagine.
"It is with appreciation and gratefulness that I accept from you this scroll for the Los Alamos Laboratory, and for the men and women whose work and whose hearts have made it. It is our hope that in years to come we may look at the scroll and all that it signifies, with pride. Today that pride must be tempered by a profound concern. If atomic bombs are to be added as new weapons to the arsenals of a warring world, or to the arsenals of the nations preparing for war, then the time will come when mankind will curse the names of Los Alamos and Hiroshima. The people of this world must unite or they will perish. This war that has ravaged so much of the earth, has written these words. The atomic bomb has spelled them out for all men to understand. Other men have spoken them in other times, and of other wars, of other weapons. They have not prevailed. There are some misled by a false sense of human history, who hold that they will not prevail today. It is not for us to believe that. By our minds we are committed, committed to a world united, before the common peril, in law and in humanity."

J. Robert Oppenheimer, Acceptance Speech, Army-Navy "Excellence" Award (16 November 1945)
Most browsers at least show a spinner somewhere, do they not?
Personally, I'm not eagerly waiting for updates on Facebook all the time. They might as well appear after a reload.

Of course, chat/messenger is something else, but I consider that an exception. (It's easy to build a chat service on top of a static website).
I think you're basing this off of old technology. With webpack 2 and HTTP/2, this is less of an issue. But, the top comment's statement I think is the most valid: if you're loading static text, then simple html pages are the best. Notice the rise in popularity of static site generators for this purpose. A SPA will win out when you have lots of interactions and you only experience the initial loading of the first page once - and then the majority of your user experience is around interacting with the app.
React-Move 2.0 – Resonance joins React-Move to make your animations even better
> But, sadly, part of the saga of nodejs could have been avoided by people looking at the history of computing. If you look at Go's concurrency model it was entirely mapped out in the 1970s in CSP. There wasn't really any need for go the 'single thread, non-blocking' route that nodejs took and evangelize it as nirvana. There was a ton of distributed systems work done in the 1970s. Just look at Lamport's clocks paper.

Non-Blocking IO is still the best we have because its a limitation in syscall interfaces. Node.js, nginx, go, etc all use epoll and their ilk under the hood. In fact, in go goroutines only ran by default on a single OS thread until go 1.5. The ergonomics of call-back based non-blocking io is the issue here, not non-blocking io itself. Because of javascript's history on the browser where callback based events are the only apis it made sense to copy this style of api for IO so stuff like `setTimeout` worked in both cases. Node's selling point with regard to non-blocking io was never about ergonomics, it was the fact that you had a dynamic scripting language where the entire ecosystem was using non-blocking io using the same standardized event loop. Contrast to the other popular "web" languages of the day, Ruby and Python which have had some non-blocking io for years but usage is isolated because most of the ecosystem doesn't support it at all, and when they do they completely different and incompatible low-level io stacks.
Oh man so cool, there are great footages on YoyTube under Nasa Dryden I think. Like old research videos on flat spins, aeroelasticity, one these was in there the Vertol 76 that's a cool video that bubble canopy and those twin rotors.
We've banned this account for continuing to violate the guidelines after we've asked you to stop.

https://news.ycombinator.com/newsguidelines.html
I think so, if only because the discussion should be surrounding best practices and following standards, as opposed to a sensationalist notion that single page apps should be abandoned in general.
I don't think that's a fair comparison. I love motorcycling, and the Isle of Man TT is probably the craziest spectacle I watch every year. And every year, at least one person dies in the race.

A lot of the mechanics and race shops that build bikes for that race talk about whether or not they're doing a good thing.

And as dangerous and awful as the above is, I wouldn't change the TT for anything. But I also wouldn't watch it, if it was a commercialized race with large corporate backing.

I guess what I'm trying to get at, is there's a difference between letting people take dangerous risks in pursuit of something they love and giving them the means to do so, and exploiting people and pushing them to continue taking dangerous risks for spectacle and profit.

Its a fine line to tread, but while typing this, I think I'm realizing that its easily discernible. In the first category, if there is a safer way of doing something, without neutering the fundamental nature of the activity, the community will embrace it. Just look at the armor improvements of motorcycling over the years. Or the quality of wingsuits and rescue equipment.

In the second category though, other considerations start to take effect, like overall viewership numbers and team profits.
Of course. eg it can be used to measure how people are influenced by a clothing display, what brands/seasons they're looking for, the effectiveness of different "Sale!" signs, which products are dead inventory wasting floorspace, etc

On the other hand, personally I would immediately stop shopping at stores that spied on customers like that.
TL;DR OP chose Ember for a small project, found himself [1] "fighting with Ember a lot", and felt that it would have been easier/quicker to build just a Rails CRUD app in the first place.

This is a standard challenge with any framework, but the issue is especially acute in Javascript-land.

Many JS libraries and frameworks exist to cover missing libraries and functions that would be "batteries included" in other languages. As core JS has evolved (along with CSS), the value of those frameworks decreases, but their legacy is deeply present in Github, StackOverflow discussions, and other libraries.

JQuery is one example: a minuscule wrapper around document.querySelectorAll() plus ES6 arrow functions gets you 75% of the way there, without having to understand how/where JQuery is being "clever" in various event handling corner cases.

Bootstrap is another: flexbox is not perfect, but it replaces a lot of CSS cruft and JS hackery.

Moral: above and beyond the usual tradeoffs for framework decisions, make sure the framework/library is still as relevant today as it was N years ago. Don't just go with inertia.

[1] The author's name is "Matt".
While Red Bull sponsors the extremes, and with that comes extreme disaster, I think those participants very well know the risk. Football, on the other hand, is sold to youth and the American public as safe with light risk, even though it's likely that we'll find a significant % (at least at the pro level) will suffer from long-term brain damage. Plus, for every $1 Red Bull sponsors, there's likely $1M sponsored in pro football.
I feel like I answered most of these questions on the post, but anyway:

1 - I've tried a number of frameworks, although ember is the only one I've used extensively. As I said, the issue was mostly with the thick client / thin backend api set up rather than specific ember stuff, with the exception of ember being overly opinionated.

2 - not interactive enough to require a js framework

3 - BugMuncher is just me, so I'm also the UX guy and I think server side rendering is awesome

4 - no (in my own humble opinion)
Most likely will get bashed for it, but.. I absolutely love Angular 1. Productivity is through the roof for me. (caveat, I build small dashboards/automation/tooling frontends). And no fancy build process, sometimes I just work off 2 files (1 HTML, 1 JS)
Do you have an email I can reach you at? I have a quick question.

(HN hides the email field in your profile, so if you want to make it publicly visible you'll have to put it in your profile's "about" field.)
I think the headline is much stronger than the story. Cunningham's professional life is still deeply intertwined with football:

> At first, Cunningham told ESPN executives that he was leaving to spend more time with his sons, ages 3 and 5, and because of his workload as a film and television producer. He was a producer for “Undefeated,” a documentary about an urban high school football team, and has a string of projects lined up.

I'd guess the truth is closer to "he decided to leave ESPN for several reasons, and his concerns over the brain damage was one of those reasons -- but not the biggest reason."
Train, Score, Repeat, Watch Out! Modeling Pitfalls in a Dynamic World
It was known long before 19 days, actually within a week of publication:

https://cstheory.stackexchange.com/questions/38803/is-norber...
> However, I think that in a strongly typed languages like Java, it's more than a few keystrokes.

Type inference solves the extra typing issue and Java isn't a great example of a strongly typed language. For JavaScript, you can use TypeScript which has type inference and non-null checking. There's also BuckleScript or Reason if you want to code in OCaml so there's practical ways to get this safety in JavaScript.

> At the end of the day, I think simplicity is the best hedge against errors.

You can have static types + simplicity though which is better than just simplicity. Types and immutability constrain the behaviour of your program to make it simpler to reason about.
Could you please comment more substantively so that an informative discussion is likelier to follow?

https://news.ycombinator.com/newsguidelines.html
Is rugby safer? I'd actually be interested in watching rugby on tv. Never been a fan of football due to all the stopping and setting up plays, makes the game move too slowly to be interesting.
Yeah nice thing about gas gets lighter doesn't get weaker unlike batteries, gets weaker, stays the same weight. Guess it depends how far down you run the batteries.
> Lower barrier to entry than other platforms

I think this is the main reason Node caught up.

SSR and code sharing are only useful in full stack projects, not in APIs. I don't know the numbers, but my conjecture is that there are more RESTful APIs written in Node than any other type of server project.
I don't think the post is depressing and masochistic. I think football fans are depressed masochists, and they get their temporary fix with vicarious participation in a gladiator sport. The more fans pay for tickets, the more contracts go up in price, the more justification for violence they feel entitled to receive. OH, these guys are getting paid a million bucks at least, I would do that!
New project I'm working on got a 97.
http://imgur.com/a/fVqCB

Cool.
But, but what were the colorization projects? What was the domain?
I had a few realizations of 2D brownian motion that I had generated on Processing laying around. Three of them are illegible, unmemorizable gibberish but get 90+ scores.
You got downvoted, likely becayse americians all know a pedantic asshole who repeats this ad nasuem. However, it should serve to point out how US centric a lot of our assumptions are conversing on HN.
The flaw is shown here:

https://cstheory.stackexchange.com/questions/38803/is-norber...
Thanks for the tl;dr :) this post did run a bit longer than I planned
I did something similar off of CoreOS's tutorial. So while I'm missing a lot of understanding of the newer functionality, going through this was worth it.
German court rejects case seeking compensation for Volkswagen owners
> I used quite an early beta of Ember to build BugMuncehr’s new feedback interface.

> I wanted to add a full REST API to BugMuncher, even though no-one had asked for it.

> I committed to using Ember before I knew enough about it.

> I didn’t keep it simple, I was stupid.

> Web apps often look complicated from the outsite, but underneath most of what they do is simply Create Read Update Delete, and you really don’t need a fancy JavaScript framework to do that.

So, to summarize, you failed at your first usage of a JavaScript framework due to your own bad decisions. Therefore, all the benefits SPA structure can offer the multitude of other projects is meaningless as, "...most of what they do is simply Create Read Update Delete." Honestly, you've just swapped the bandwagon effect for confirmation bias as you fell back to Rails.
Apple release Augment Reality guidelines (beta)
It's easy to pick out 1 or 2 studies that show no result on this topic, but that'd be cherry-picking. Google scholar gives 1,750 results on "breast milk iq" in just 2017.

See my other response.
The robot theme on its own is too reminiscent of Android, and the name is too low-contrast on a thin font.
The risk profile is entirely different. When you go jump off a cliff you're saying "there's an x% chance I will die right now" but there's no chance that you die slowly 20 years later after surviving the jump. So it's much more fair to ask the jumper to evaluate the risk.

Playing football is a slow killer. After years and years of hits you may get serious brain damage. But there was no one particular moment, no single play, that you should have avoided. It's the sport as a whole.
TJ moved to Go too, and he doesn't work at Google.
I was confused with this initially as well.

What I came to understand, was that "server-side rendering" refers to whole application lifecycle steps:
- The server generates initial HTML markup, based on the request.
- The browser can parse & render the already generated HTML (instead of waiting for the client-side JS to load first, then have it create / modify the DOM).
- From that point onward, all changes in UI happen through client-side rendering.

You could do this with Django template / JSP pages / Jade templates as well. Just write your templates, and some jQuery sprinkled here and there, to dictate how user interaction should change the page.

But that's not all there is to it.

We slowly took away SSR, with client side JS frameworks, like Backbone, Angular 1, Ember etc. Applications started to have client side routes, even with ugly hashbangs in the URLs.

It was easier to write entire application logic of your UI in a client-side framework with two-way data bindings; than writing the server side in a template language, and put in some JS here & there to handle interactions. Especially, if your application was big enough.

But this started having problems with SEO, and initial load times.

Say, your app has a homepage URL, of the form https://company.tld/, and a products URL, of the form https://company.tld/products.

If a user goes to homepage, and clicks on the "products" link in the navbar, the page content of /products route would load in the client side, via the framework.

But, if a user directly hits the /products URL from their browser (can be from history and omnibox prompt), the browser would first load the home page with assets, then the client side JS would take over, and route the user to the /products URI endpoint.

New server-side rendering paradigm gives you best of both worlds - get to maintain a single codebase to render your page (be it server or client), while give the initial fast loading, so that your page is interactive quite fast.

This is not easy to do. One big challenge for most server side rendering solution is that, after initial render, the JS in the page would try to re-render the page; thereby creating an impression of a "flash".

Yes, if you're using a framework like React or Vue, which uses VDOM, this won't happen in most cases, because of how a virtual DOM based renderer works. But there are still cases, where you might need to explicitly do something to prevent the re-render.

There are other challenges too. For instance, having the page server-rendered, and hydrating the state.

In the search of maintaining a single unifying codebase for both server and client (isomorphic rendering), we often do things that cannot work on server. For instance, chunk splitting your front-end bundle based on routes. Or CSS media queries.

To sum it all up, "server-side rendering" isn't just about initially rendering the page on server. It's so much more than that. It's mostly about how we can maintain a single codebase (now that we have JS on server too), and run on two different platforms.
You should try skimming to the end, where there are two pages of references. Not to mention the fact that Cardelli is a prominent figure in the study of programming languages.

And I think you'll find that Gilad Bracha is a more informed critic of reliance on static type checking.
Do cyclorotors count or no

Also the jet engine stand that they tilt forward and they cruise around on single man. It looks like a flying podium haha.

What about jet-tip helicopters or fall under helicopters too yeah
So "normal users" doesn't automatically mean "privacy-conscious users" to you? You also are missing (or trivializing) the problem.
Speaking as someone from a rugby-playing nation, where mostly players wear no protection except mouthguards and shin pads, American Football is spectacular but insane.

Wearing protective helmets just ups the ante as players launch into each other with full force. In rugby, you don't tackle someone like that as you'll hurt yourself, and fail to stop the opponent.

Rugby is a plenty violent sport, and has its own health issues, but the lack of protective helmets and body armour (and rules preventing tackling without using your arms) means that attacking players think about their own safety before launching ridiculously high impact hits on each other.

https://www.youtube.com/watch?v=-F6POhAbAhE
It's not so much Michigan as a whole that's failing as it is Detroit.

And wealth transfers from richer states to poorer ones are the inevitable (indeed intended) consequence of federal income redistribution. They're a problem if they're disproportionate, i.e. two states are equally poor but one gets more money because it somehow has undue political power. Obvious example is Florida. Other than that it's no different than redistribution from richer people in California to poorer people in California, except that they happen to be in different states.

Another problem is the state-level consequences of some of the income cliffs the feds have in place, i.e. six independent subsidies phase out at the same time with higher income.

The states need the incentive to improve. Increasing average income by $4 shouldn't cause the feds to take away $5 from the state.

But if that happens, the cause is flawed federal policy, not state-level diversity.
Kelsey Hightower has a repo experimenting with using HashiCorp Vault as a Secrets backend.
Recently I heard that a guy owned 100 trucks is selling his house for quite a low price. Probably lost a chunk of stashed black money. Well, this seems like the effect of demonetization. This is great. The thieves do deserve this.
"Both exclusivity and duration are important, because dose response is well established for breast milk benefits.3–5" [1]

So the author cites findings that how-long you breastfeed for or amount of breastfeeding you do has an effect (e.g. once a day vs twice a day) that's a big unexplained phenomenon (which could NOT be explained by maternal IQ, SES, etc).

To quote this author's interpretation of the literature "Although the topic is controversial, and a recent systematic review identified heterogeneity between studies, among the 4 studies with the least bias (each >500 subjects, controlled for maternal IQ, breastfeeding recall duration <3 years) breastfeeding improved performance on IQ testing by 1.76 points (95% confidence interval, 0.25–3.26), suggesting a small but durable impact of breastfeeding on intelligence.10"

(Again 2017, fully aware of the difficulty of controlling [1])

Now does this case-closed prove breastmilk bumps IQ? No, it proves my original claim that this is hotly contested.

1. Breastfeeding: What Do We Know, and Where Do We Go From Here?
“Those are two of the issues,” Cunningham said. He waited weeks before he revealed the third. “The big one was my ethical concerns.”
ELI5: Why would constructive math be more typed than non-constructive math?
Why is torque expensive in an electric motor? They tend to produce high amounts of torque at lower RPMs than ICEs. Even a Nissan Leaf gets 187 ft-lbs, and a Tesla motor has a flat torque curve to to 10,000 RPM.
> Exactly! And by their very nature, free-markets are susceptible to races-to-the-bottom.

I was actually thinking that this was an example of a Nash Equilibrium. It's basically like the prisoner's dilemma. If all the states cooperated and refused to offer tax breaks, that would be good for all states. But if a single state "defects" and offers tax breaks, that state reaps the rewards of its defection. Unfortunately this leads to all states "defecting" and offering tax breaks, which leaves the states in a worse position than if none of them offered tax breaks.

> So, yes, here they are at work doing one of the examples of free-market behavior that work against the public interest.

Yep, that's true, but there's not really any way around it in this case.

> Here's another variant of my comment above: If all the workers refused to work in abusive conditions for low pay, the companies would still need to hire workers. And you could reply "Why would workers refuse that? Accepting abuse and low pay is a pretty obvious means to convince a company to hire you over others — the free market at work."

And that's why unions exist. But that won't work when we're talking about states.

> Are you one of those people who blindly thinks that the algorithm of "free market" necessarily (tautologically) results in the best situation for everyone?

Haha no (but thanks for asking instead of silently assuming!). But the "free market" is what we have (even if it's not always, or even often, really "free"), and it results in consequences like states offering tax breaks, and there's no real way around it beyond tearing up our government and starting over because I seriously doubt you could ever convince all 50 states to outlaw tax breaks for companies.
Love dual monitor, display on the right code on left and i3-wm, but would like to get used to just using a single monitor/laptop.
I would like to see studies of specific industries. In government affairs, have multiple monitors is a lifesaver. Research on one screen, writing on the middle, email and other time sensitive resources on the right. I tried it with just one monitor and my quality and time dramatically improved with three.