thehardsphere

Okay, so, maybe he's a nut or a troll, but nothing really about gaming?

I'm not so sure. The problem when the only "wall between genders" that's "erected" is consent, you often find out too late that it's not strong enough of a wall. It seems like at Atari in the 1970's it was fine, but there are easily identifiable places it was not, like most of Hollywood in the current decade.

I'm guessing something else about Atari's culture prevented the kind of problems that can crop up when you have a relaxed sexual attitude, but it isn't as easy to identify.

Right, but the women at Atari weren't disenfranchised. Even in the 1970s, their alternatives to working at Atari were numerous. The secretary there who was "stacked" wasn't facing an alternative of no employment or living in Bangladesh if she didn’t like hot tub meetings; she could go work at any company in America that didn't have hot tub meetings, which was all of them.

I've never heard of Notch having strong biases regarding social issues and the game industry. I quickly googled but all I could find were references to some tweets he deleted about some "heterosexual pride" or something that he later apologized for.

Do you have a link or can you sumarize what those biases are?

I'm guessing that Filipinos aren't obviously "white" or "black", and thus get to dodge all of the baggage that Americans have about the topic of race.

Just another guess: "Filipino" is also associated with a single geographic place, unlike most of the other races that Americans typically think about.

See, "we're not Google" should actually mean that you care about performance more. Google can throw millions of dollars worth of infrastructure into making an app go marginally faster. Whereas, all you have is brainpower before you deploy or ship. And it doesn't take that much more brainpower to get big increases in client performance when you're starting from not-optimized-at-all. The marginal payoff is larger and the marginal costs are much smaller.

Just a guess: You were alive when progress marched on before your eyes. Animations are "new" to you, and like many people you have some sort of implicit association somewhere in the back of your mind that "new == better"

Do you ever find some animations to be lower quality than others? E.g. a pop up with a progress bar being lower quality than a spinning wheel? That might be another sign.

> TBH most of the cons stated in this article are just because of bad programming, not because it's a SPA

The worst programming is the result of choosing the wrong tools for the job. There is a class of jobs for which an SPA is entirely unnecessary.

That's a good starting point. I'd drill down even further and ask "what does the user do with the application?"

If the user needs to look at multiple screens at a time (e.g. like a mail client or something of similar complexity), then they're a candidate for an SPA. If the user does not need to do that, the app is probably simple enough to not be an SPA.

The problem with SPAs in the sort of cases that the author is talking about is that people don't think clearly about what requirements they are satisfying when writing a new one. If your app actually needs to switch between various screens without a refresh so your users can most efficiently get their work done, then yes, by all means, make an SPA. That requires knowing clearly who your users are, what they want to do, and what constraints they are under (e.g. if they all work on desktops with good internet access, maybe it doesn't matter that your app is bloated and slow on mobile). I think most people don't do that thinking step first. They want to play with the new shiny, either as a sort of fun or so they can add it to their resume.

This I think is made worse by the unparalleled decadence in which the modern, first-world developer now lives. It is absolutely excessive to have to download 2.6 MB just to show a blog or some simple textual information, but thanks to broadband everywhere and terabyte hard drives, nobody under the age of 30 who isn't working in embedded systems thinks about this anymore.

People always say things like this about despotic regimes while they're in power. Yet, every time they fall, we almost invariably learn that things were actually much worse.

Well, sure. I get that sort of argument for something like tax policy.

But is this actually an experiment that should be run at the state level? I mean, having 50 different net neutrality laws that all actually mean and require different things doesn't strike me as being efficient.

Serious question: Is having state-level net neutrality laws actually good policy?

The current administration says they want less immigration occurring, but also seems confusingly willing to cut deals that completely flying in the face of the President's public statements. There's presumably room for a deal if partisanship doesn't get in the way, because it seems as if there's no will to revoke DACA for real on anybody's (even Trump's) part.

But, it's an election year, so...

This plan would fail, because someone sophisticated enough to find the naming and shaming list of awfulness would probably already be sophisticated enough to realize that old, bad advice is bad and why it is, and where to find new, good information. The problem is not merely that bad old content exists, but there is a class of PHP developer who is insufficiently sophisticated to distinguish between good and bad information independently.

Whether that's a feature or a bug of PHP is an exercise I leave for the reader.