Hacker News new | ask | show | jobs
by laputan_machine 1017 days ago
> When you're writing a specific program, e.g. it's never going to be anything more than "Hello, world!", why would you use the fattest framework when you can write it in plain HTML?

Emphasised the parts I think you should re-read
2 comments
uxp8u61q 1017 days ago
Sorry, I guess I disregarded it because I figured we were talking about serious programming, not literally "Hello world".

And if you're writing a single "Hello world", HTML is overkill. Make a free website on a random platform and literally just write "Hello world" in their WYSIWIG editor. Or hell, just serve plain text with "Hello world" inside, browsers will render it just fine.

link
satvikpendem 1017 days ago
> why would you use the fattest framework when you can write it in plain HTML?

I mean, don't use "the fattest framework" then, who is forcing you to use it for writing hello world?

link
laputan_machine 1016 days ago
As you get more experienced in programming you'll inevitably inherit projects that you didn't have any say over, when that time comes come back to this comment, I'd be interested to hear if you still feel the same way.
link
satvikpendem 1016 days ago
I have inherited such projects. But it seems like you're talking about code that is no more complex than hello world, as you've quoted, so it wouldn't be too complex to do in any language or framework. Now if you do inherit a larger project that you don't like, well, you either work on it or you switch jobs.
link
laputan_machine 1016 days ago
> Now if you do inherit a larger project that you don't like, well, you either work on it or you switch jobs.

Which you wouldn't have to contemplate if your predescessor had simply used the right tool for the right job, right? Such as not using an over-engineered framework for a problem that didn't need to use one. :)

Cheers!

link
satvikpendem 1016 days ago
I mean sure, but I wouldn't work at such places anyway. One cannot escape complexity, it's either in your code or in other people's code that you use. Don't overengineer, but not everything you'd think is overengineering is actually the case. Otherwise, just work in assembly.

It is also interesting that you haven't responded to the other comments that call out flaws in your argument, just mine, perhaps because you don't have an answer for them either, as your original comment is now dead.

link