Comment by eterm | Hacker News Reader

Comment by eterm | Hacker News Reader

Parent Full thread

You've enjoyed it, but those hours cost your business, and is that really worth it?

Some beliefs which are frequently displayed in these parts:

> Money on chairs / desks / PCs are no object because developers cost money, not those things

> Ship quickly and iterate

> Make it, make it work, make it fast

> Write code your successor can maintain

And then HN goes ahead and upvotes a boast about spending their (expensive) time unpicking libraries from code.

The point of "you might not need X" is to encourage package maintainers to keep their sub-package footprint small, not that end-users shouldn't use X.

I'm sure you'll be back to suggest that you've delivered "500% speed-up" or some other nonsense metric and I look forward to that.

Ultimately, custom business owned code which attempts to deliver the value of angular is just a future maintenance nightmare, and I say that as someone who really doesn't like angular.

If you really replaced angular with a "javascript one-liner" I'd like to see that line!

I'm going to take a guess and say he won big in maintainability and performance on low-end devices.

If it will operate with no js at all, then it is also more compatible with some security requirements I have. Don't get me wrong, I've always been a big fan of JavaScript, warts and all. However, in this particular instance, what should have been a simple server rendered login page was written with a full SPA application development mindset.

I see where you are coming from, there rarely is any reason to reinvent the wheel, but at some point reducing libraries is beneficial for the long run when and if you can afford it.

I think the "enjoyed" part was definitely meant facetiously.

Ultimately, custom business owned code which attempts to deliver the value of angular is just a future maintenance nightmare, and I say that as someone who really doesn't like angular.

I suspect the problem the commenter is hinting at concerns situations where people think they need the "value of {angular,react,bootstrap,whatever}" when really they don't.

Just because you can't give a $ amount for the costs saved by reducing complexity, doesn't mean it doesn't have value. Simple is good.

We all do things that aren't objectively "worth it". Was the time you took to type this post really worth it?

I wouldn't think someone's livelihood depends on worthiness of this post. In businesses, however, that often is a case.

Depends if they are on HN at work...

What about the money lost because people don't wanna use your app because it's bloated and slow?

Who said anything about it being bloated and slow?

JS is the bloat here.

Reply on news.ycombinator.com