Like Gmail is emails but not IMAP. It's fine. We have seen that these kinds of wrappers work pretty well most of the time considering the performance and simplicity they bring in building and managing these systems.
Grown in popularity is not really a metric. A normal tuesday and the day half the company's staffers got fired aren't going to be the same in popularity. Doesn't mean one is better. Twitter is definitely more popular for all the mess they've made, yes.
The "narrative" was right. There are actual outages now unlike earlier. It's not like twitter engineers were holding up the servers to the light for there to be outages the moment they're gone. Systems run on their own just fine, until something does go wrong. And if there's nobody there to fix it, something usually small blows up. Enough of these and users start to notice degraded performance and outages.
My ideal 1:1 is about once a month. Especially in high-ownership teams, you could go days without actually talking to people aside from a 10-15 min check in call.
So, it's sometimes nice to have periodic validation that you're keeping true to the course / indication that you need to make a few minor adjustments, etc. That's on your side.
From your manager's side, if they find something isn't working, they don't need to wait 3/6 months to bring it up at which point there isn't much you can do to get back the lost productivity.
Everyone who is a manager actively makes independent contributions for a not-insignificant portion of their work-week.
So, when we have 1-on-1s with them, we can actually discuss improvement avenues from the same vantage point. Not some spreadsheet pushing manager who has no clue how to measure engineer-productivity or performance.
When they do code reviews, their comments serve as an important learning opportunity, pointing out good practices/conventions, etc.
And finally, when you disagree, it's backed by the validity of your points as 2 engineers, rather than their authority as a manager vs you, their direct report.
10 years across all 3 major cloud providers (and some others like Rackspace, etc), I can tell, Google support has been the absolute worst of all. I don't say that lightly. I take pride in how I can deal with customer service the most peacefully in my org. But that's all out of the window when their CS is nonexistent.
I can't remember the number of times they've shut down someone's production workload without notice or warning, gave them no way to resolve/rectify any supposed infraction, and gave no way to contact them to appeal the decision.
I once had to resort to numbering my points and just referring the boilerplate responses (few and far inbetween as they were) back to the numbers over and over until I finally gave up, moved away and never looked back.
If you can get away with hosting static html files, there's not much else that's more performant.
The comparison is only between server rendered HTML vs backend API + some frontend rendering locally (which is not as performant) and more importantly is a lot more complex to implement technically.
Getting turbo is trivial on any backend. Just include the js.
Stimulus is also not any different from any other javascript you'll write. There's no need for any kind of scaffolding from the backend stack except for some features - and those aren't particularly hard to implement either.
Source: Using Turbolinks & Stimulus js with Django.
>I don't think I've ever seen DHH or the Basecamp crew advertise any of this type of stuff as some groundbreaking new approach that nobody has ever tried before
Not disagreeing with the rest of the stuff. But they literally call it "NEW MAGIC" per DHH's tweet.