I'd wager that most agency devs have wanted to do this too. CMS's never work the way you want them to as an dev.
Thankfully, the work you have done (along with your competitors) in making headless CMS's viable not just for devs but also for content maintainers has made CMS work far more enjoyable.
It's awesome that you not only built out the dream most agency devs have, but made a successful business out of it at the same time.
In this case, it actually was due to unknown and unpredictable costs. They were about to start production on S2 when the strikes hit. They delays spiked the costs of an already expensive show (S1 cost an estimated $175M) which made it less tenable for Amazon. This happened to quite a few shows during the pandemic and during the strikes – renewed because it made financial sense, then pandemic/strike spiked the cost, and then they canceled the renewal.
Yeah, I agree. I have a Pixel Watch 3 and generally like the circular form factor. I wish they did more with it at times, but I feel like that's kinda what I'm seeing from the previews in the OP blog post
Personally, it's easy for me. If I get above 10 tabs, I just close them all. I don't see any value in having more than that and they just become a distraction for me. Tree style, sidebar tabs, tab groups, etc. are just overkill for me.
That's just not how some people browse. When I hit HN's frontpage, I open every thread with an interesting headline in a new tab (within the HN tree.) Then I visit them one by one, and at least each one gets another tab opened (for the article.) The article may get multiple tabs opened if it has references or links that are interesting. If there's something that I want to get back to later, or don't have time to read now but looks interesting, it stays open. If I won't get to it for a while (before the next time I return to HN) it gets pulled out of the HN tree into its own tree.
HN frontpage
|> Interesting thread
.|> Interesting article
..|> Interesting link from article 1
..|> Interesting link from article 2
.|> Link from interesting thread.
|> Interesting thread
|> Interesting thread
|> Interesting thread
|> Interesting thread
Things that get moved out of tree I might get back to in an hour or a year.
If I'm at Amazon trying to buy a spatula, I have 10 different Amazon spatula pages open, and also three articles about spatulas within the tab tree.
I dunno. When I go to a bookstore, I don't buy one book, go home, then come back and buy another book. I browse the bookstore, buy everything that I want, and I put most of them on a shelf while I read one. I do not find the shelf a distraction.
I'm in this boat as well. From my perspective, I'd only bother keeping a tab open for a long period of time if it meets the following criteria:
1) It's something I'd actually want to go and view later (most stuff fails this criteria)
2) It's not something I can easily find again
3) It's something that I only anticipate going back to a couple of times, and thus isn't worth making into a bookmark
And over all my years browsing the web, almost nothing satisfies all that criteria. I'm pretty aggressive with closing tabs, and I almost never regret closing a tab.
It's pretty common for people drive to the bar, get drunk, taxi/Uber/Lyft/DD home, and then return the following day to get their vehicle. I don't think it makes sense personally, but I also don't drink at all so I'm not a great judge here.
Yeah, this used to be me. I don't do it anymore but I used to spend a great deal of time playing with beta versions of Android, Windows, Firefox, and various iPod and Mac customization applications. I just enjoyed playing with the new features, figuring out how to break them, reporting those issues, and then helping get them fixed (even if I wasn't contributing code at the time). I don't have the time anymore, but it was one of my favorite activities when I was younger.
Same here. I remember playing with Beta versions of Windows Vista on my parents home PC. Ended up wrecking the system because I wasn't technical enough to fix it when it broke... but was still an important milestone in my journey today.
At the time, XP was 6-7 years old, and the screenshots of a shiny new Windows OS made me so itchy to try it out. Vista looked magical compared to XP just before release, it was the dawn of the frutiger aero aesthetic too. Very optimistic vibes back then.
Yeah, I was the same way with my iPod. I was contributing to iPod Wizard and one of the QA testers for iPod Linux, iPod Wiki, and Rockbox. I would install unstable firmwares on my iPod a few times a week and spend a few hours testing. I bricked my iPod more times than I could count. I had two iPod hard drives that I would swap between and I had a way of wiping the drive once it was out of the casing. To this day, I have no idea how my iPod 4G survived as long as it did.
I've tried numerous keyboards and the conclusion I've come to is that there's low profile and then there's low profile. The bulk of the low profiles I've tried (NuPhy, Keychron K8, the mechanical Logitech, a few others) are definitely low profile compared to the Logitech Pro X TKL I use for my gaming PC. However, they're still tall. Most of the gains are from a shorter switch and keycap, but the body is still quite high.
If you compare it to the Apple Magic Keyboard I'm typing on now – and that seems like a definite inspiration for the Bayleaf – it's a stark contrast. The K3, for example, is more than twice as tall (10.9mm vs 22mm backrow). The Magic Keyboard feels fine to type on without any sort of wrist support and I never feel any strain. But on the K3, even with a support (tried both their wooden support and a similarly sized foam one), I would feel strain after an hour or two.
Most low-profiles are really just a middle ground between the two sides. And, at least in my experience, you get the downsides of both without any of the positives of either.
Thankfully, the work you have done (along with your competitors) in making headless CMS's viable not just for devs but also for content maintainers has made CMS work far more enjoyable.
It's awesome that you not only built out the dream most agency devs have, but made a successful business out of it at the same time.
reply