51–60 of 275 posts
No point in learning "the ideal" stack, if you can use something you know that is as good as any other stack.
Let's be honest. You can develop and deploy static site anyway you want.
Surely this is meant as satire, the title is clearly tongue-in-cheek. I’d worry that some less experienced folks might take it at face value, rather than as a salient warning about the dangers of grossly over-engineering for no discernible benefit.
I’m sorry, but this is ridiculous for a static site. React and Typescript with embedded markdown? This problem has been solved a thousand times over with much simpler tooling. > I literally have zero memory of how we used to build forms in the pre-React times. :(
Surely this is meant as satire, the title is clearly tongue-in-cheek. I’d worry that some less experienced folks might take it at face value, rather than as a salient warning about the dangers of grossly over-engineering for no discernible benefit.
(It’s not the tech stack I’d choose, but I see exactly why it’s being chosen.)
This is front end only so not really a complete stack.
There's nothing simple about this crapton of dependencies. Sure, it may be easy to build things this way, but let's not conflate the two terms.
As a non-React developer: forms, before React, were actually super simple. The author mentions they forgot how to do forms the normal way, but like, can you imagine how excited they'll be by the simplicity?
i think (but i'm not sure) that this blog post is a joke?
Earlier quoted context omitted.
Because writing your own blog engine is a good way to learn various web technologies that you haven't had a chance to use.
I agree, but then really you're not interested in creating blog content per-se, but in exercising your engineering skills. I think it's important to be honest about that intention both with your audience and yourself when writing articles like this.
A lot of devs get excited by the idea of building a blog and not of actually writing the content. You've got to actually have ideas to share and be prepared to put in the time to write posts.
I wouldn't even think about tech before you've got a backlog of at least 2 or 3 posts.
Ugh.
It's a personal blog. A small amount of mostly static text and images served on demand in a couple different formats. Maybe some search/tag capabilities and maybe a comment section.
This problem is essentially the foundational problem that the web was initially trying to solve twenty-five years ago. And to be honest, twenty-five year old server-side solutions still do a pretty good job of it. (Although admittedly, the format of the resources served by those solutions are now far richer than they used to be.)