> "Ohhh, an OO pattern with a couple of one-liner lifecycle methods is just WAY too much code! Higher likelihood for errors and worse developer experience."
...
> "So instead, I'm going to replace this with a functional pattern, that crams a couple of lifecycle functions into a closure, and is riddled with edge cases and common developer mistakes."
This article perfectly crystalizes why my career has tracked toward the backend over the past decade. All of the virtual ink in this article, and honestly most of the complexity in the field overall... and it seems to really all just boil down to, "I think this looks cooler."
IMO there's significant complexity in building a feature-rich frontend client. The "thicker" the client, the worse it gets. There's definitely a lot of 'I think this looks cooler' going around, but also we shouldn't forget that the need to come up with something better is partially a response to very real, very-not-imagined, frontend complexity.
I've been using Lit.js for about a year now and something about it just clicks. I just wish it were more mainstream.
Plus I can't even see how this simplifies anything, if you're posting to instagram it's surely simpler to skip the extra step and just use instagram's built in editor, even if you have to place the emojis yourself?
Or you could just not post those photos. What's even the point of posting a photo of your child, with the face hidden? Seems very niche. Just post another photo.
Casey Liss is a very anxious person, there is nothing wrong with that but if you make apps for people like yourself, it's an advantage to be more mainstream!
Might be a cultural US thing, but this is something my wife does a lot and I see a lot of people doing. It's one of those things that might not make sense if you don't have kids.