Not going to lie, I read the title as the Art of Fishing... and spent the entire article waiting for the finale where some how this was an analogy with fishing...
came for the fish, stayed for the all-too-familiar feeling of incomplete projects.
I hate to say this, as I'm generally optimistic towards most developments like this, but over the last decade I've become so apathetic towards anything and everything from Google. They've lost so much mindshare and credibility. Their org structure leads to stagnation left, right and centre.
I'd rather tolerate the poor status quo in React land than take any sort of bet on Google getting something "newish" right.
its arcane syntax and tendency to behave in unexpected ways is a massive barrier to entry. you spend way too much time trying to figure out the edge cases to command outputs / errors / what-happens-if-the-output-isn't-as-expected (usually due to error conditions.) scripts need to be reliable and predictable (without fuss!) - especially if you're controlling things with them.
Who are all you crack-junkies, running SQL queries against live...? I've seen enough literature saying we don't do this anymore... ooooooooohhhhhh. right... yes, the people writing about that aren't the ones actually shipping and making the clock tick ;-)
the explosion of threads is because of twitter's algo...
to view a thread, you have to interact with a tweet. this interaction drives metrics that results in the tweet showing up more frequently in the algo-feed. the multi-post nature of a thread means there are more opportunities to "like/retweet" - which also drive the algo-feed.
all this increases follower count... and an audience (that's soon to be easily monetisable on twitter) is far more valuable than a blog... unfortunately
this is a MASSIVE selling point, BUT, when your users contact support trying to gain access to their account and can't describe what their email address might be... trust me, there is pain in your future.
interested to know your approach to long leases lasting more than 60 seconds (if you have this?). do you go for continual renewing (and bailing out if you get too close to the timeout without getting a renewal). or do you go for infinite with your own break logic?
Well Microsoft had their annual mail outage the other day... I guess they could have coordinated a bit better to get them done and out of the way at the same time.
Just because people are searching for it doesn't mean it's popular. It means people are trying to answer a question about it. I'd posit there is more of a correlation between searches and newusers/issues/problems with the tool/language than how much it's being used. Stack Overflow is a better source for these stats anyway.
- this is the first confirmation I've received from a company stating outright that they're not going to be GDPR compliant and you should stop using them if you need to be.
- they're explicitly saying it's too much effort to store data in a compliant manner and ensure their processors are complaint. this possibly raises some interesting questions about what exactly they're doing with the data they have today.
- this GDPR thing is like async code, once it gets into a system it has long tentacles. I don't think this company fully realises just how many companies need to be GDPR compliant to continue doing business online. if you're in the SAAS business, it's very likely you're dealing with EU customers - or at the very least a customer that deals with EU customers, or an customer of a customer that deals with EU customers. You get the point - this tentacle keeps reaching down. You may think you're not excluding many of your own customers by not being compliant because THEY aren't EU-based, but it's their customers/controllers etc that require them to be compliant and thus you.
hard to fathom there's an entire generation of developers out there for whom this is entirely new magic. there's an entire class of problem and suite of (bad) tooling that they're having to grapple with to deal with things that simply aren't issues in statically typed languages.
came for the fish, stayed for the all-too-familiar feeling of incomplete projects.