disbelief

Interesting. So it seems that enjoying baseball is a form of mild insanity that is distributed evenly across all races ;)

I think you're misunderstanding him. What he meant was the cultural norm (or more accurately imo: "the stereotype") in America around black people is that they can't swim, don't like baseball, don't listen to rock/country or play golf.

Wow I had no idea this canal was such a disaster in the making, and the article didn't even mention the canal the Chinese are building in Nicaragua which would significantly shorten shipping routes compared to Panama.

The author repeatedly conflates conservatism with Christianity. While there's probably a higher percentage of Christians who identify as conservative, it's not their conservatism that would trouble me in a University setting. I wouldn't want a University science professor to be a creationist for example, but I couldn't care less if they're fiscal conservative who believes in small government.

Pretty sure these numbers are international, not limited to the US? Though I'm sure there is a sizeable percentage in the US.

Also doesn't really mention what sorts of roles are getting cut, just that they're skewing towards older employees. My guess is that there will be a lot of non-technical people under the knife here.

Ah yes of course, thanks. I took too brief a glance at the S3 pricing page.

Anyone know if the quoted cost of $0.04/GB for Transfer Acceleration is instead of the $0.03/GB for standard S3 ingress, or in addition to it? Ie. is the final cost per GB $0.07 or $0.04 when using Transfer Acceleration?

Edit: as pointed out to me below, there actually is no ingress cost for standard S3 uploading. The $0.03/GB is monthly storage. So the cost of this service is $0.04/GB instead of $0.00.

Density isn't really the problem in San Francisco. The problem is available housing. Relatively speaking San Francisco is far less dense than many other cities. But these other cities don't have housing shortages.

A couple questions:

(1) I notice that your pricing chart mentions storage. I'm wondering what that typically would consist of? Only thing I can think of are static assets as I imagine a codebase — even with a million npm module dependencies — wouldn't come close to 1GB let alone 100.

(2) Is it possible to back your apps with a database/datastore? Say I want to use MongoDB with my app. Would I need to purchase a third party service and set the MONGO_URL in the env? Are there any plans to offer database services as add-ons?

That's one hell of a clickbait title. In order for any browser to be "the new IE", developers would have to hate it and dread developing for it/supporting it. Ask any web developer today which browser is their favourite, go-to browser for development. This statement holds absolutely no water.

Secondly, the author cherry picks a couple things that haven't been implemented in Chrome, glossing over the fact that Chrome tends to support way more features than any other browser on the market, and is more often than not the first and the best implementor of web standards. A quick perusal of caniuse.com or the support matrices on MDN will drive this point home (honourable mention to Firefox).

Agreed, the title was link bait done to death.

I'm not in the situation of ramping up a team unfamiliar as the author was. But it sounds like he was experienced with JS and React himself. Or are you suggesting he should replace his team with people more familiar with JS+React?

You're an A because you know you're a C and have employed this workaround to compensate ;)

This sounds like a great idea! One caveat being that the it probably caters more to web/mobile devs. Eg. you probably wouldn't use this challenge for a database engineer, or machine learning role. You could, but it wouldn't tell you much about their skills in the domains you're interested in. Still definitely worth trying for roles where it makes sense. I might try this.

Whether or not React's goal is to cater to beginners doesn't make the argument any less valid. Also React doesn't equal JSX. The React docs also mention how to do things without JSX.

Maybe it's the article's title that has understandably rankled some people by seemingly maligning JSX. However, I think it's a very valid concern to have when ramping up a team that's unfamiliar with JS and React.

I think his points about new developers having to learn JS, React, and JSX all at the same time and then context switch between them in ways that aren't entirely clear was pretty spot on. I don't know how you draw that comparison without mentioning the shortcomings of JSX. Also with Hyperscript you're still building your markup directly in your Javascript, just using JS for it instead of JSX, not templates. Not sure if that's what you meant with your "separate template pages" statement.