Earlier quoted context omitted.
One off few hundred or few thousands is nothing in comparison to 30% tax. That said, I don't know about Mac, but you can build apps using free tools - maybe in not as convenient way, but certainly you can. I remember, because I was someone who couldn't afford Visual Studio licence and had to make do with GNU tools. The greed of these companies put me off from developing anything.
In the early 90s, you could expect to pay anywhere from $200–1000 for a good C/C++ compiler. Now it’s free. The 30% tax, as many people have already pointed out, is only if you want to sell through the store. Back in the 90s, if you were selling software, downloading off the net wasn’t really a thing yet and you could easily expect to end up giving up 40–60% of the retail sales price and out of what was left you were…
Did we lose our way in making efficient software?
381–390 of 515 posts
Re: Did we lose our way in making efficient software?
#382I want to make native apps but Apple and Microsoft seem to be trying really hard to stop me. I have to buy developer accounts, buy certificates for signing binaries, share 30% of my revenue with them for barely any reason and so on. Not to mention the mess they've introduced in their APIs - especially Microsoft. So of course we choose the much simpler, much cheaper way of the web.
Considering the whole point to have Windows is to use apps I'd expect they made the process super smooth.
Re: Did we lose our way in making efficient software?
#383Again and again people complain about this. But it remains a fact that essentially nobody actually wants this. Developers certainly like to have their completely integrated, connected and universal computing platform (the web). And users do not seem to particularly care about performance as long as it is good enough . And that is exactly the standard that is set, software is allowed to be so bad that it doesn't reall…
It is always fun to put up the task managed on these to see them using 20-30MB of RAM with a large part of that being the current data base loaded in.
VLC & Blender are other examples of this.
Re: Did we lose our way in making efficient software?
#384Earlier quoted context omitted.
Counter offer: the tooling is ultimately for their benefit. They need the apps to make their platform what it is.
They ultimately need money, not apps or platforms, so this is exactly how they achieve that ultimate benefit, no top-level logic will just justify free here
Not true. The technical term for "ultimately need money" is discounted future cash flow. It is impossible to know for sure what price you have to charge for any particular item at any given time in order to optimise for this metric.
Realistically, the answer depends on the state of competition between platforms. We all know what that state is.
Re: Did we lose our way in making efficient software?
#385Earlier quoted context omitted.
[flagged]
The alternative that exists today that I can buy and all the apps I need for work will actually exist and function correctly is called…
If your work mandates something you can't solve with Linux the issue is with your work and you should push to change that.
Re: Did we lose our way in making efficient software?
#386My opinion about this is that yes, we lost our way, and the reason is very simple, it is because we could. It was the path of least resistance, so we took it. Software has been freeriding on hardware improvements for a few decades, especially on web and desktop apps. Moore's law has been a blessing and a curse. The software you use today was written by people who learned their craft while this free-ride was still ful…
> path of least resistance Great take. It feels like the path of least resistance peppered with obscene amounts of resume driven development. Complexity in all the wrong places.
It wasn't supposed to be like this but it looks like most people never have found the way by now.
So, misguided efforts, wasted resources, and technical debt piles up like never before, and at an even faster rate than efficiency of the software itself declines on the surface.
Re: Did we lose our way in making efficient software?
#387Earlier quoted context omitted.
Not discounting your lament about memory use, this caught my eye: > I would throw my computer out of the window if it takes more than a minute to boot up, even Windows 98 was faster! Sure, Windows has grown a lot in size (as have other OSes). But startup is typically bounded by disk random access, not compute power or memory (granted, I don't use Windows, if 8GB is not enough to boot the OS then things are much worse…
But that is true. My laptop with windows, i7, nvme, 32gb ram now feels the same as my old laptop with i7, SSD and 16gb ram did 7 years ago. Bloat ware everywhere, especially browsers.
Others in the thread talking about the heyday of older spreadsheet and document programs that were just as fast. So? I bet you could write a book on the new features and more advanced tools that MS Excel offers today compared to 1995.
We went from things taking minutes to taking seconds. So you could improve things by 50% and that could be VERY noticeable. (1min to 30s, for example.) If your app already launches in 500ms, 250ms is not going to make your laptop feel 2x faster even if it is. On top of that, since speed has been good enough for general computing for several years now, new laptops focus more on energy efficiency. I bet that new laptop has meaningfully better battery and thermal performance!
Re: Did we lose our way in making efficient software?
#388Earlier quoted context omitted.
To quote Wolfgang Pauli, this is not just not right, it's not even wrong ... The "C ABI" and libc are a rather stable part of Linux. Changing the behaviour of system calls ? Linus himself will be after you. And libc interfaces, to the largest part, "are" UNIX - it's what IEEE1003.1 defines. While Linux' glibc extends that, it doesn't break it. That's not the least what symbol revisions are for, and glibc is a huge us…
glibc is not stable on Linux. Syscalls are.
It's providing backwards compatibility (by symbol versioning). And that way allows for behaviour to evolve while retaining it for those who need that.
I would agree it's possibly messy. Especially if you're not willing or able to change your code providing builds for newer distros. That said though... ship the old builds. If they need it only libc, they'll be fine.
(the "dumpster fire" is really higher up the chain)
Re: Did we lose our way in making efficient software?
#389Earlier quoted context omitted.
In several countries you can't file your taxes or access your bank without a google/apple smartphone. People need to live too.
What country only lets you file your taxes and do banking via a smartphone. It's always been an app in addition to a website.
Re: Did we lose our way in making efficient software?
#390It is just a different kind of efficient, there is economic incentive in making software development process more efficient and not that much incentive for making software itself efficient .
Software development is more accessible to millions and millions of new developers due to the work on higher level languages, frameworks , IDEs , libraries , low code , copilots and so on .
Each of these innovations made software development more efficient (not necessarily faster ) .
Nobody buys or uses software because it is faster , only cheaper .