> Once upon a time, I wanted to resize about forty screenshots. The first few search results either wanted an account before they would touch a file, or did three of them and then asked me to register for the rest.
> Resizing or converting an image can be accomplished by using browser APIs and a few bits of JavaScript, like <canvas> and toBlob.
This is an example of thinking in terms of "services" that do something big for you, end to end. An alternative approach is to think in terms of "small tools", each of which will do one thing and do it well, and then you combine them into something big – that's what we call the "UNIX way".
There is absolutely no need to implement a web page with JavaScript to resize a bunch of screenshots; it's just a trivial for loop in a shell, calling ImageMagick for each file.
Of the whole list of tools the author implemented for their own usage, there are some tools that indeed belong to the browser, but there are some other tools that just don't need to exist as a separate browser based app because doing it right in a shell is easier.
It's a sales funnel, and that data is worth a lot to them. You are the product.
With a bit of knowledge, persistence, documentation, you too can stop relying on dubious tools. This way you'll also learn how small the wizard behind the curtain is.
> Once upon a time, I wanted to resize about forty screenshots. The first few search results either wanted an account before they would touch a file, or did three of them and then asked me to register for the rest.
> Resizing or converting an image can be accomplished by using browser APIs and a few bits of JavaScript, like <canvas> and toBlob.
This is an example of thinking in terms of "services" that do something big for you, end to end. An alternative approach is to think in terms of "small tools", each of which will do one thing and do it well, and then you combine them into something big – that's what we call the "UNIX way".
There is absolutely no need to implement a web page with JavaScript to resize a bunch of screenshots; it's just a trivial for loop in a shell, calling ImageMagick for each file.
Of the whole list of tools the author implemented for their own usage, there are some tools that indeed belong to the browser, but there are some other tools that just don't need to exist as a separate browser based app because doing it right in a shell is easier.
Why do free online tools ask you to sign up?
It's a sales funnel, and that data is worth a lot to them. You are the product.
With a bit of knowledge, persistence, documentation, you too can stop relying on dubious tools. This way you'll also learn how small the wizard behind the curtain is.