←back to thread

139 points obscurette | 1 comments | | HN request time: 0.276s | source
Show context
thinkingtoilet ◴[] No.44465473[source]
> Software has followed the same trajectory, piling abstraction upon abstraction until we’ve created a tower of dependencies so precarious that updating a single package can break an entire application.

This is like saying old software is so simple that updating a line of code can break an entire application. It's a silly thing to say. No matter how complex or how simple a piece of software is, you can easily break it. If you have a program that prints out "hello world", guess what? Updating a single character can break the entire application!

The world is more complex now. We've stood on the shoulders of giants who stood on the shoulders of giants. A few centuries ago a renaissance man could make advances in multiple fields. Now people are specialized. It's the same thing with software. Of course, people take it to an extreme. However, you go ahead and write your own crypto library, I'll use a vetted one created by experts.

replies(5): >>44465615 #>>44465616 #>>44465638 #>>44465793 #>>44466466 #
softfalcon ◴[] No.44465638[source]
This is exactly my take on folks bemoaning the evolution of complexity in software (and hardware) worldwide.

To lend some credence to other folks points of view, there are arguments I can agree with that are adjacent:

- "We don't need that complex framework for our needs, we stick to a simpler, older library."

- "We decided to not use <shiniest_new_toolkit> it had performance issues that the maintainers are still sorting out."

- "Working with the new framework showed a lot of promise, but there is still a lot of instability in the API since it's so new. We couldn't commit to using a toolkit that hasn't been nailed down yet."

These are actual concerns and shows caution towards adopting new things until they match your use-case, dev-timelines, and performance requirements.

replies(1): >>44465838 #
1. shermantanktop ◴[] No.44465838[source]
I’d add “The DOM api probably already has everything you need and has zero dependencies.” That applies to many lower-level APIs which have gotten smarter and better over the years—often in response to the needs of fancy frameworks, but now they are pretty rich by themselves.

“I don’t have time to learn a new framework, I have things to do.” Everybody’s cool new abstraction is a cognitive burden for someone else.