agentPrefect

This is precisely what fragmentation causes.

Which is what a lot of people have been saying for a very long time.

IntelliSense. Definitely my reason for not going back.

in exchange for paying this cost, you gain maintainability, developer efficiency, and (hopefully) better performance during runtime.

You also gain responsiveness to user interactions, a programmatic way to reason about your application/website & and some animation-sugar if you want. Don't throw the baby out with the bath water simply because people follow trends instead of good design practices.

The amount of colossal horror stories I've heard about that company has made sure I don't go near it with a 9 foot pole. Their platform is designed to obscure process in lieu of exploiting workers - all whilst advocating to "serve the client". Utterly toxic.

But this is exactly what the article talks about - and what I agree with - let them ask for help. To each his own, I agree that some people need that intervention, but for the rest of us, don't assume it.

Co-workers who have a tendency to "shepherd" newbies are downright annoying. Other than the initial on-boarding, there is no reason to be involved in solving someone's "new comer experience".

Is the "extend" portion of the new Microsoft strategy commencing...

This reminded me a lot of how DHH described their thinking (paraphrasing A LOT): other people don't have to have a bad product for yours to be successful. Good article!

Me too.

To be honest; I'm a little surprised it's lasted this long.

The way Redux works is that it essentially stores all the dynamic information of an app in a single JavaScript object.

This is the temptation when starting with Redux/Mobx/GraphQL/etc. You can't simply relegate reasoning through your application architecture to a single library or because some big company solved a problem with it.

Redux is a fantastic way to organise some of your app state & GraphQL is also great at a lot of stuff! Absolute no need to play the all-your-eggs-in-one-basket game.

Because the battery drainage with Firefox is unacceptable.

I don't know why, but some people assume these services are being used as a utility rather than a community. So they make their case based on stats and data, and completely ignore the relational aspect of being part of it.

You can spit facts & figures all day long, but unless you make it clear why your own community is intentionally betraying you, it's all noise.

4. Reddit is lame.

Thanks mom. Carry on.

That is sad! My condolences. That was a very well written letter from Slack and I completely agree with them, but unfortunate for BetterSlack nonetheless. Always room to pivot!

Yea me neither. Generalizations like this aren't helpful, or least bit fair.

As a non-user of Facebook, I completely take their side with all of this.

1) If people don't want to read the fine print, whose fault is that? 2) How have we gotten to a point where we are abdicating our choice voluntary, and then acting begrudgingly toward the new owners when they misuse it?

I must apologize for my cynicism here, but we've been going around this mountain for a very long time now (circa 2013 IINM?). I'm getting tired of hearing how people are feeling violated due to their own actions.

Absolutely agree.

Everybody favours the underdog.

Mr. Robot was stupid because - why do I want marketing in a product I use as an eveyday utility? Chrome is the standard because of the majority market share and also because they do a great job of delivering a good developer AND user experience.

Updated with no problem at all.

100% spot on.

Nothing to disagree on. :)

So I've used Vue for personal projects before, it's really nice. I lead the dev on a small team within a large corporate company, we focus on React & Angular(io).

The primary reason why I would not adopt Vue is because Vue is still driven by Evan You - which is great, but if something had to happen to the guy (and I hope nothing does), I'm unsure Vue would have the long term support & drive it does right now.

So I reckon Docker & PHP7/HHVM have contributed for sure. So much easier deploying Nginx - not to mention just plain nicer.

This is quite interesting though. On the web, search engines were built to fulfil a very specific need... finding content. The more open the web became the better search engines could find what you were looking for. Now with apps, they're being built at an extremely rapid pace, I wonder if we could expect to see some content-finding framework popping up to solve the saturation/discoverability issue.

Ya, it's the usual HN comment section crap. Everybody's an expert.

Just a quick note; but "sugar in general" contains fructose. Given that you're talking about simple sugars.

I must admit - this is kind of why I started moving AWAY from Google. You just don't have any guarantee that the product you're using won't be shelved in leu of a "better" (newer) solution.

Actually really agree with this. As someone who develops for Android I can't tell you much potential "mental damage control" you have to be prepared for with implementing stuff. Accommodating the different support packages, APIs, device & hardware specifications - it's a headache sometimes. But I think that's part of why I love it too, the freedom and "openness" relative to iOS eco system.

That being said - Apple might be closed and all the rest, but make no mistake: they know their customer and they are willing to defend them. Even if it means pissing people off. Which is kinda nice.

I also should say, that I do agree with you. If it is more that losing weight you want, then the caloric deficiency is not the best way go - like if you're doing resistance training. But somebody who is obese? Eat cleanly yes ... but most certainly eat less.