I think Tachyons struck the balance to be honest. Tailwind's "functions" and combinations seem to allow a higher level of complexity where it becomes difficult to quickly inspect a class block after some time has passed.
This is a cool project! One small suggestion: the native blue links for the author name, "thread", and "reply" make the content hard to focus on as the UI is quite intrusive. HN solves this quite well with a colour scheme that has the comment content as the most prominent element in a thread.
> We shouldn't limit ourselves because of climate change. We should instead improve the technology and make it better so it doesn't impact the climate in such a way it becomes unsustainable.
I think we totally should limit ourselves from the idea that it's totally normal to expect to be able to fly anywhere in the world in ~24 hours and to do this regularly.
Really enjoyed reading this article as a Sunday afternoon long-read. Well structured and covers a lot of things I have experienced but haven't formed into such a clear description. Also really appreciate the realistic examples!
Your line of thinking here really resonates with me. I'm building services on top of two bots right now that fit into this transactional "I want to do X in as little time as possible" category and I think Messenger bots are a fantastic way to achieve that.
> I think this is down to the sad truth that most developer roles offer very little challenge outside of learning a new stack.
This is a gem observation from this thread. In my own tech sphere the first thing developers are talking about with each other is the new x,y,z lib or framework they're using to accomplish something relatively banal. There's still a lot of work out there that really boils down to basic CRUD and reporting at the end of the day, and developers naturally begin to invent complexities on top of that CRUD to make the work interesting and challenging. I'm absolutely guilty of this first hand.
I've found personally it also doesn't help that past work on projects e.g. large Rails apps that were never architected well turn out to be such nightmares to work on. The memory of the end state of these projects lingers with developers as they move onto the next piece of work, and they're inclined to say "no that doesn't work" and pick up shiny new-tech to do the old job instead.
As a side analogy: most small business construction jobs, e.g. building a timber frame house, don't involve the builders arriving on site and are stumped by the challenge of how to put up the framing for the bedroom walls - there's also very little challenge in these projects, yet the reward is in the completion.
Can you please elaborate on how a CRM is likely to be in a category where it would benefit from state heavy client-side?
A CRM is typically a form based app doing CRUD - to be this makes it a solid candidate for being a stateless client.
I feel like there's a whole class of applications out there now (including my own) that have gone down the stateful client route where it wasn't necessary and introduce a whole new set of problems and solution libraries / frameworks that can be forgotten about with a return to a stateless arch.
I was trying to place emphasis on the regularity not the cost of an upgrade. Packaging up what seems like relatively trivial features into a major OS release isn't really progress.
Feeling pretty disillusioned by another iPhone and
iOS update. The 3.5mm coupled with lightning instead of USB-C just look like obvious traps for lock in with no real gain (5hr of playback time?!)
iOS still continues its march of adding minor features that should be in regular OTA updates and packing them up with some serious marketing hype. There's barely any improvement here and most of the features are already well implemented in Android / Google Apps or Facebook Messenger.
This is a good description of the difference between available architectures, but more detail is probably required to backup some of the discussion points, beyond the fact that reducing presentation is beneficial for response times. An API server is still required to render JSON responses?