this post was submitted on 02 Jun 2024
488 points (97.7% liked)
Technology
59674 readers
3817 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
On another forum, I was complaining about how Microsoft was planning to remove WordPad from Win11. I was advised that installing OpenOffice or LibreOffice was an appropriate replacement. I replied that WordPad was only 3 megs large, as opposed to the recommended replacements, which are decidedly larger.
I guess not everybody appreciates tight code, but I surely do. Things like this are amazingly impressive.
Size doesn't matter much when you have SSDs that read upwards of 5000mb/s. It's why we're seeing an advent of web-based apps despite them being woefully inefficient, and why games regularly go above 100gb. The reason file size gets so large is that assets can take up a lot of space and they come with plenty of libraries that they just have to bundle. These "small size" software optimize for size at other costs, like speed, asset quality, development time... Reducing file size is just not relevant anymore and if anything you should be wary of software that do it.
yeah, you know what?... no. This is the kind of attitude that got us here to begin with. Yes, processers get faster, and yes size gets more available. But that shouldn't be an excuse for poorly-written code.
An empty Microsoft Word document is larger than the first word processing program I ever used. That is just crazy when you think about it. but "oh people have lots of resources they're not even using so it doesn't matter", right? When companies have this attitude of "oh the resources are there I may as well use all of them for myself" then their code runs like garbage and you need a faster computer just to make it work halfways decently. And because of this we all end up on this goddamned technology treadmill where we have to keep buying bigger and faster and more expensive computers to do the same thing the old computers did just because the programs written for it are too bloated and the people writing the code couldn't be arsed to make it work well. It wastes our time and our money. I reject that. I think others should too.
If you're old enough, then the first word processing program you ever used was probably on a screen 640x480 pixels or smaller, didn't support internationalization, couldn't provide true WYSIWYG to match output between the screen and a printer, and couldn't render fonts with anti-aliasing. Which of these features would you like to drop to reduce the size?
Everyone loves "tight" programs until they realize what they have to give up to make it work.
Fonts can be handled by Windows itself.
I don't care about internationalization, just EN-US is good enough.
Having more pixels doesn't change asset sizes when the pixels used per asset are the same. Just show me the smaller button or use vector graphics.