ts330

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.

How Twitter (nascent at the time) has changed… let alone the technology landscape and the wider world!

Exciting? Possibly for those involved.

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.

It wasn't always like this.

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.

sorry, the UK sarcasm mark-down doesn't always render correctly...

Surely this will become a non-problem as we migrate to NOSQL... no...? oh? we're migrating back? great.

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

basic manipulation in CF is an absolute pita - so much overhead for simple things like clobbering a header value.

but by allowing JS/whatever, it gives you an infinite landscape to work with the values in a language that a wide range of people grok.

it's just a matter of getting a decent deployment setup so you can rinse and repeat easily.

but i agree, it's a freaking jack hammer where most people need a small tack hammer.

Happy customer of RevenueCat. Integrated and never looked back.

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.

Question: had Microsoft chosen a less ridiculous sounding name to begin with, would it have been more popular?

... and will be shutdown in about 18 months when our attention wanders elsewhere ...