57
all 34 comments
sorted by: hot top controversial new old
[-] Bye@lemmy.world 21 points 6 months ago

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.

[-] lysdexic@programming.dev 31 points 6 months ago

But in my humble opinion, those projects shouldn’t really exist.

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.

[-] SpaceNoodle@lemmy.world 16 points 6 months ago

"I reject your reality and substitute my own."

[-] corsicanguppy@lemmy.ca 3 points 6 months ago

It's a way of saying "these are wrong and should be deprecated."

[-] lysdexic@programming.dev 15 points 6 months ago

It’s a way of saying “these are wrong and should be deprecated.”

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.

[-] douglasg14b@programming.dev 4 points 6 months ago

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.

[-] Bye@lemmy.world 2 points 6 months ago

Did you just stop reading there? I was saying those projects should have atomic architectures so that “rewrite small parts when needed” can happen

[-] abhibeckert@lemmy.world 9 points 6 months ago* (last edited 6 months ago)

those projects shouldn’t really exist

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.

[-] lysdexic@programming.dev 3 points 6 months ago

If Google were to start over, all of that would be thrown out. It just can’t be done.

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.

[-] deluxeparrot@thelemmy.club 2 points 6 months ago

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.

[-] douglasg14b@programming.dev 7 points 6 months ago

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...?

[-] corsicanguppy@lemmy.ca 6 points 6 months ago* (last edited 6 months ago)

I've found that big projects need refactoring without replacement, as Joel says. Bind and sudo and even sendmail have value in this world (the latter for versatility) that cannot be easily replicated without massive cost and decades of maintenance amid real attacks.

But yeah, trivial stuff can be rewritten and exhaustively tested at occasionally a cheaper cost where it can provide value to the enterprise that will one day out-balance its rebuild cost.

[-] magic_lobster_party@kbin.run 5 points 6 months ago

But in my humble opinion, those projects shouldn’t really exist.

In my humble opinion, everybody should just write perfect software first try.

[-] Reptorian@programming.dev 2 points 6 months ago

For small projects, rewriting is often superb. It allows us to reorganize a mess, apply new knowledge, add neat features and doodads, etc.

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.

[-] marcos@lemmy.world 19 points 6 months ago

Yet the world is full of code that was replaced with less work than it would take to fix a single bug on the broken original.

It's almost like if universal rules for software engineering doesn't exist... but no, that's crazy.

[-] abhibeckert@lemmy.world 9 points 6 months ago

Replacing code is fine. Replacing an entire product is the mistake.

[-] lysdexic@programming.dev 7 points 6 months ago

Yet the world is full of code that was replaced with less work than it would take to fix a single bug on the broken original.

Can you point out a concrete example? Because you're commenting on a discussion on an essay that documents several notorious examples that demonstrate the opposite point.

[-] QuaternionsRock@lemmy.world 2 points 6 months ago

I’m not extremely familiar with it, but I think X11 qualifies. I think it was determined that HDR support would be basically impossible to implement.

[-] KeenFlame@feddit.nu 2 points 6 months ago

Ah yes those projects exist, that just are perfect and.. Or wait was that a dream maybe. Anyway, I'm sure they exist. After all, there's no universial rules, society and science doesn't constantly evolve and improve by searching for and defining such rules since the dawn of time.. Or was that a dream maybe. Anyway, I am certain this is wrong because my code is perfect

[-] GissaMittJobb@lemmy.ml 11 points 6 months ago

It's mostly stopping the world to re-write everything from scratch that is a mistake.

Good practice is to refactor the codebase until it's modular (if it's not already sufficiently modular), and then proceed to replace modules gradually until you reach your desired state of re-writtenness.

This has the benefits of actually getting you up to speed with maintenance over time without having to halt new feature development, giving you the best of both worlds.

[-] Faresh@lemmy.ml 9 points 6 months ago* (last edited 6 months ago)

For anyone who was confused as I was about hearing of a new release of Netscape, this article is from 2000.

[-] Daxtron2@startrek.website 1 points 6 months ago

The 2000 in the title didn't give it away?

[-] dyc3@lemmy.world 1 points 6 months ago

No, I was totally flabbergasted and bamboozled until I read the parent comment.

[-] Daxtron2@startrek.website 1 points 6 months ago

honorably flamboozled

[-] JackbyDev@programming.dev 4 points 6 months ago
[-] corsicanguppy@lemmy.ca 4 points 6 months ago

You may know it as Mozilla, the namesake project that Mozilla (the company) felt was too hard a raison-d'etre to maintain and, yet, still exists. If you ever hear of Mozilla the org refered to as MINO, it's because they couldn't even continue their you-have-one-purpose task.

Unleash the downvotes, ye dissonants.

[-] JackbyDev@programming.dev 2 points 6 months ago

I only left the comment because of my pfp being the old Netscape logo haha

[-] eveninghere@beehaw.org 3 points 6 months ago

Shipping JavaScript in one week

[-] johnefrancis@lemmy.ca 3 points 6 months ago

never put salt in your eyes

[-] Fades@lemmy.world 3 points 6 months ago

Where was this post when Elon decided to rewrite Twitter lmao

[-] Masterkraft0r@discuss.tchncs.de 2 points 6 months ago

laughs/cries in embedded we are currently changing from mbed to zephyr rtos. at the beginning it was decided we will never replace mbed, the thing i am currently replacing, so all the code is using parts of mbed everywhere. there's not enough space on the chip to have both mbed and zephyr in parallel. yay. you desktop/server/web/whatever people don't how good you have it.

[-] Cwilliams@beehaw.org 1 points 6 months ago

Except when your rewriting it in rust, ofc 😎

this post was submitted on 25 Mar 2024
57 points (100.0% liked)

Programming

17225 readers
66 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 !webdev@programming.dev



founded 1 year ago
MODERATORS