water42

The example on using emojis is very strange:

> It'd be nice to get that report by this afternoon.

This phrasing is inherently passive aggressive since it's not a direct ask, regardless of how many emojis are included.

Why not:

> Hi <name>, will you be able to have the report on X ready by <time>?

Don't filter input. Instead, prevent certain characters from being input in text elements. This is a user experience problem, not a software problem. The software can validate that a "name" is rejected if it does not follow the front end validations, but it doesn't need to do any more than that.

Of course, this argument does not extend beyond a "name" field to more complex fields. But more complex fields are less susceptible to introducing UX problems if certain characters are sanitized.

There's nothing wrong with having a prescription for marijuana, even if the "prescription" is really just a state medical license provided by a sketchy doctor that you slip 200 USD once a year.

But please stay off the roads while you're under "psychoactive" effects (read: high) . There are LEGAL drugs that are illegal to use while operating a motor vehicle.

There's valid points here, but the impact is lost in the disjoint laundry list communication style.

> used by hipster startups to Facebook

Well, yeah, it's developed by and for Facebook...that was a weird line.

I think you're overcomplicating how transferrable framework knowledge is. An expert React developer could switch to Vue no problem if there was demand for it. Similarly an expert Vue developer could switch to React no problem.

Clickbait. The author switched from Angular 2 beta 9 (not even a release candidate) because he was unable to migrate to Angular 2.0.0 since 'too many things broke to make the upgrade non trivial'. Yet somehow rewriting the entire app in Vue is easier?

Drug lords

Not as long as ads/tracking make companies money

I'm assuming it's the Reddit effect. People read headlines, upvote, and move along without ever clicking the link.

Every framework is going to have flaws, but if you perform a comparison I think there's a responsibility to accurately represent the frameworks being compared.

yet another web framework medium article with a misleading angular vs react comparison.

it isn't angular 2 anymore. it's just angular. it's been out for over a year and if people were having problems running it in production, we would hear about it. there are many sites running angular 2-4 in production, google it and see for yourself. just because google didn't rewrite gmail in angular doesn't mean you shouldn't use it.

I wonder if there is some highly ranked google search result that spreads this misinformation, months after some of these points were valid.