Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I still make websites this way because no-one told me to stop. They can be made responsive to things like smartphone browsers which incredibly minimal changes. No complaints so far.


What kind of sites do you make? I’d imagine that avoiding things like react is fine for a lot of sites that just need a bit of form input here and there and some nice styling, but that anything relatively big with interactive pieces would fairly quickly devolve into a difficult to maintain mess without components. I’ve sort of been trained to think that, though, as I was just starting development right before libraries like React started to get big. I remember reading cs books and learning about how important encapsulation and modularity was and then feeling like I wasn’t really able to apply those concepts adequately in my really early web projects. React came along and seemed like the best answer. Do you do something different to organize code related to more complex frontend user interaction than forms/animations, or do you find that you just don’t really need complex frontend user interaction for the websites you make?


Most of the things I've made are not public-facing. I just try to keep things simple. My sites generally require page loads more than the average single page application, but they have the advantage of loading faster and working in nearly any browser, even super old ones.


Link or not real.


Please stop

:P


No, please continue.


What is old is new again.

Brutalism for President 2020.


It's not necessarily brutalism, I own a maximalist site that doesn't have any Javascript on it, only CSS, HTML and images.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: