this post was submitted on 25 Mar 2024
54 points (95.0% liked)
Programming
17661 readers
242 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities [email protected]
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Boy do I ever disagree with this.
For big projects, with multiple people and man-years of work, sure. Don’t start from scratch. But in my humble opinion, those projects shouldn’t really exist. Instead they should be atomic, made up of small page-length units which individually can be scraped and rebuilt.
For small projects, rewriting is often superb. It allows us to reorganize a mess, apply new knowledge, add neat features and doodads, etc.
What's the point of your opinion if not only do these projects exist but they are also pervasive?
You cannot wish things away and pretend reality is something different.
"I reject your reality and substitute my own."
Did you just stop reading there? I was saying those projects should have atomic architectures so that “rewrite small parts when needed” can happen
They aren't wrong. No one in their right mind just throws away years of work delivering a stable production project just because a random clueless person in the internet said something. It's lunacy.
This thread is a great example to why despite sharing knowledge we continually fail to write software effectively.
The person you're arguing with just doesn't get it. They have their own reality.
You think web browsers should not exist? How do you write Google Chrome, and all of it's dependencies, in one page of code?
I think you're miss-understanding the article. Joel didn't say you should never rewrite an individual component in your code, he was saying you should never throw out an entire project (all of the components) and start from scratch.
He also wasn't talking about "multiple people and man-years of work". He was talking much larger projects. How many people have contributed Chrome? Not just direct contributions writing lines of code, but indirect contributions such as reporting bugs or writing documentation on how it works?
If Google were to start over, all of that would be thrown out. It just can't be done.
All you can really do is what Microsoft did with IE / Edge. Edge was a fork of Chromium which was a fork of WebKit which was a fork of KTHML which was a fork of the KDE HTML Widget. Which dates back to 1996. Internet Explorer started in 1995. Microsoft didn't start Edge from scratch, they basically shifted their team of developers over to another project that was the same age.
The smaller the project, the easier it is to do a full rewrite but realistically it's almost never a good idea unless your product is very young.
To stress the importance of this very basic fact, people need to understand that even Google, a company with virtually limitless resources to rearchitect and rewrite any and all type of software project, made the call to avoid using major features offered by some programming languages, such as C++'s exceptions, because it could have unintended consequences on the company's legacy code base which they could not rewrite.
And here we are, reading fantastic claims over how complete rewrites are reasonable things while flipping compiler flags to harden legacy projects is unheard of.
They actually did somewhat start Edge from scratch originally. They made EdgeHTML as a rewrite of the IE 11 trident engine.
In the end they abandoned it and moved over to chromium. One of the reasons being Google intentionally breaking their sites for EdgeHTML.
Yes. Multiple historical layers, each giving the creators way too much power over presentation, while they are still supposed to handle stuff like accessibility themselves, making a company webpage a thousand manhours project. Browsers being monoliths is only one page of the book.
So we agree that browsers are way too complex?
This is reaching a level of idiocy that's completely unheard of.
Just say you know nothing about what you're saying and you're completely oblivious, and sit out the rest of the discussion.
Please refrain from using personal insults in this community. You're free to express your opinion, but personal insults does nothing but make the community more toxic. c/programming is a gathering ground for both inexperienced and experienced programmers, so this level of lashing out is uncalled for.
This is a weird take given that the majority of projects relevant to this article are massive projects with hundreds or thousands of developers working on them, over time periods that can measure in decades.
Pretending those don't exist and imagining fantasy scenarios where all large projects are made up of small modular pieces (while conveniently making no mention to all of the new problems this raises in practice).
Replace functions replace files and rewrite modules, that's expected and healthy for any project. This article is referring to the tendency for programmers to believe that an entire project should be scrapped and rewritten from scratch. Which seems to have nothing to do with your comment...?
In my humble opinion, everybody should just write perfect software first try.
In my humble opinion, you shouldn't be allowed to participate in big projects if you don't fulfill some minimal requirements.
Reminds me of the crack i had to explain the concept of technical debt. He was the main maintainer of a years old Xamarin project, he took over from his precursor.
Most software is built under non-ideal circumstances. Especially in the beginning there’s often tight deadlines involved.
“Good news! We finally got a new customer! Looks like we will survive this month! Bad news. We sold a feature we don’t have yet and oh, we also promised to have it delivered by tomorrow morning, so hurry up!”
Exactly this.
I think a bunch of people commenting in this thread on the virtues of rewriting things from scratch using the flavour of the month are instead showing the world they have zero professional experience working on commercial software projects. They are clearly oblivious to very basic and pervasive constraints that anyone working on software for a living is very well aware.
Things like prioritizing how a button is laid out over fixing a rarely occurring race condition is the norm in professional settings. You are paid to deliver value to your employer, and small things like paying technical debt are very hard sells for project managers running tight schedules.
Yet, here we are, seeing people advocating complete rewrites and adding piles of complexity while throwing out major features, and doing so with a straight face.
Unbelievable.
This. I'm coding to contribute to a open-source software with very small amount of coders, and with a non-mainstream Domain-Specific Language. A lot of the code I did before has been proven to work from times to time, but they all could benefit from better outputs and better GUI. So, I end up reengineering the entire and that'll take a really long time, however, I do a lot of tests to ensure it works.