Germany's Sovereign Tech Fund Now Supporting FFmpeg • Hacker News Board

Re: Germany's Sovereign Tech Fund Now Supporting FFmpeg

#51

Post by IshKebab » Fri, May 17, 2024, 4:04 PM UTC

xnyan wrote: post #50

IshKebab wrote: post #48

Earlier quoted context omitted.

> If it doesn’t support the formats, it’s not a replacement for ffmpeg. That's dumb. Like saying a car isn't a replacement for a horse because it can't jump over hedges. Most people do not care about the obscure formats at all. > I’m sure people will flock to that just for the excuse of saying they are using a rust library. Well, for not having to worry about trivial security bugs, yes I suspect they would flock to i…

> That's dumb. Like saying a car isn't a replacement for a horse because it can't jump over hedges. A car is not a replacement for a horse, it's a replacement for what was the most common use case of the horse, getting from A->B in a developed environment. There are still (limited) applications where a horse is the best or only transportation option. A pocket knife is not a replacement for a multitool, even if the mu…

You can't win by inventing your own overly narrow definition of what "replacement" means. Under your definition nothing is a replacement for anything, which is clearly idiotic.

Re: Germany's Sovereign Tech Fund Now Supporting FFmpeg

#52

Post by martinsnow » Fri, May 17, 2024, 5:13 PM UTC

IshKebab wrote: post #51

xnyan wrote: post #50

Earlier quoted context omitted.

> That's dumb. Like saying a car isn't a replacement for a horse because it can't jump over hedges. A car is not a replacement for a horse, it's a replacement for what was the most common use case of the horse, getting from A->B in a developed environment. There are still (limited) applications where a horse is the best or only transportation option. A pocket knife is not a replacement for a multitool, even if the mu…

You can't win by inventing your own overly narrow definition of what "replacement" means. Under your definition nothing is a replacement for anything, which is clearly idiotic.

He didn't invent his own definition. A drop-in replacement does the exact same thing, as what it would replace in the exact same way.

You however don't seem to understand _why_ backwards compatibility is important, and i would absolutely hate to interface with whatever mess of a software you write.

Re: Germany's Sovereign Tech Fund Now Supporting FFmpeg

#53

Post by IshKebab » Fri, May 17, 2024, 6:54 PM UTC

martinsnow wrote: post #52

IshKebab wrote: post #51

Earlier quoted context omitted.

You can't win by inventing your own overly narrow definition of what "replacement" means. Under your definition nothing is a replacement for anything, which is clearly idiotic.

He didn't invent his own definition. A drop-in replacement does the exact same thing, as what it would replace in the exact same way. You however don't seem to understand _why_ backwards compatibility is important, and i would absolutely hate to interface with whatever mess of a software you write.

> A drop-in replacement does the exact same thing, as what it would replace in the exact same way.

I agree, but do you see "drop-in" anywhere in my comments?

> You however don't seem to understand _why_ backwards compatibility is important

I completely understand why backwards compatibility is important. But something doesn't have to be backwards compatible to be a "replacement".

I have replaced C++ with Rust in my hobby projects.

Re: Germany's Sovereign Tech Fund Now Supporting FFmpeg

#54

Post by martinsnow » Fri, May 17, 2024, 7:43 PM UTC

IshKebab wrote: post #53

martinsnow wrote: post #52

Earlier quoted context omitted.

He didn't invent his own definition. A drop-in replacement does the exact same thing, as what it would replace in the exact same way. You however don't seem to understand _why_ backwards compatibility is important, and i would absolutely hate to interface with whatever mess of a software you write.

> A drop-in replacement does the exact same thing, as what it would replace in the exact same way. I agree, but do you see "drop-in" anywhere in my comments? > You however don't seem to understand _why_ backwards compatibility is important I completely understand why backwards compatibility is important. But something doesn't have to be backwards compatible to be a "replacement". I have replaced C++ with Rust in my h…

> But something doesn't have to be backwards compatible to be a "replacement".

Yes it does. Especially when it's the size of projects like ffmpeg. Just because you replaced c++ with rust in your tiny hobby projects doesn't mean you have the experience, nor the qualifications to say what it entails what it takes to do it at this scale.

You come across as extremely unexperienced.

Re: Germany's Sovereign Tech Fund Now Supporting FFmpeg

#55

Post by IshKebab » Fri, May 17, 2024, 9:09 PM UTC

martinsnow wrote: post #54

IshKebab wrote: post #53

Earlier quoted context omitted.

> A drop-in replacement does the exact same thing, as what it would replace in the exact same way. I agree, but do you see "drop-in" anywhere in my comments? > You however don't seem to understand _why_ backwards compatibility is important I completely understand why backwards compatibility is important. But something doesn't have to be backwards compatible to be a "replacement". I have replaced C++ with Rust in my h…

> But something doesn't have to be backwards compatible to be a "replacement". Yes it does. Especially when it's the size of projects like ffmpeg. Just because you replaced c++ with rust in your tiny hobby projects doesn't mean you have the experience, nor the qualifications to say what it entails what it takes to do it at this scale. You come across as extremely unexperienced.

You are getting very very confused. Let me simplify it for you.

1. It is desirable for replacements to be drop-in replacements. But it isn't a strict requirement. It is possible to replace something with something else even if it requires some work to do that replacement.

Cars did replace horses for transport. That is fact. They were not a drop-in replacement. Roads had to be built. People had to learn to drive.

The fact that they were not a drop-in replacement for horses does not mean that they were not a replacement. That's simply not what the word "replacement" means in English.

2. You seem to be confusing the size of ffmpeg itself, with the difficulty of replacing it. That's not how programs work. The thing that matters is the size of the interface of the program, which isn't the same as the size of the program itself.

For example if you are using ffmpeg on a web server to compress or convert videos to a standard format, you might be running a single ffmpeg command, and replacing it with some other system would literally be a matter of changing the command. It doesn't matter that ffmpeg itself is a huge program.

I hope that helps you understand a bit better. Good luck learning about computers - keep at it and you will get there eventually!