←back to thread

434 points pykello | 1 comments | | HN request time: 0s | source
Show context
esperent ◴[] No.44994941[source]
It seems like the community fork would be the better link for most people.

https://github.com/ManimCommunity/manim/

replies(2): >>44995220 #>>44996923 #
Waterluvian ◴[] No.44995220[source]
For good reasons or for drama reasons? I read the blurb about the fork and can’t tell why exactly if Grant is continuing to maintain the original.
replies(3): >>44995263 #>>44995281 #>>44995457 #
Jorge1o1 ◴[] No.44995263[source]
Well, to me it seems like he just shared the original so that others could benefit from the work he had already done, but that since his main priority is to continue making new videos, he may not have the time resources to:

- Avoid breaking changes

- Keep APIs stable

- Test and document everything, etc.

I personally think there's nothing wrong with that. We wouldn't say that a musician is *obligated* to put out a second album or a remaster. We wouldn't say that an author *must* make a sequel to their popular book. But when it comes to code sometimes we feel like the original author has an obligation to keep working on it just because it would convenience us.

(edited for formatting)

replies(2): >>44995283 #>>44995297 #
dleeftink ◴[] No.44995297[source]
I agree, but want to add that while we may perceive other creative works as 'finished' (to an extent), code often is not. It unfortunately, needs perpetual work.
replies(3): >>44995360 #>>44995363 #>>44995570 #
0_____0 ◴[] No.44995360[source]
It's pretty wild to me (I do hardware) that data goods like code can rot the way they do. If my electronics designs sit for a couple years, they'll need changes to deal with parts obsolescence etc. if you want to make new units.

If you did want your software project to run the same as today when compiled/interpreted 10 years from now, what would you have to reach for to make it 'rot-resistant'?

replies(9): >>44995467 #>>44995475 #>>44995548 #>>44995551 #>>44995594 #>>44996206 #>>44997847 #>>44997879 #>>44999676 #
vntok ◴[] No.44995467{5}[source]
> If you did want your software project to run the same as today when compiled/interpreted 10 years from now, what would you have to reach for to make it 'rot-resistant'?

Target Windows, avoid Linux.

replies(1): >>44995737 #
1. the__alchemist ◴[] No.44995737{6}[source]
ABI compatibility is one of several components involved. The OS the software runs out plays a small role in this problem.

There is a relevant point about OSes though, and it has a different conclusion from yours: Write our software (And OSes) in a way that doesn't create barriers and friction between systems.