Resource hungry operating system

[the_leander]

If Windows is a GUI based OS

Plainly it is.

why do you need to use the 'run program x' to get at some of the options.

To stop the headstickers from touching things they have no understanding of.

Back to the original question. The only realistic answer is "other" because it depends on what the OS is doing... Windows, Linux and OSX for instance offer more services out of the box than AmigaOS can offer period.

[the_leander]

On the subject of bloatware I don't agree. There are apps that take up 100 times the space, perform slower and only add eye candy over a much leaner app with the same or better functions. It is clearly just shoddy programming.

I do agree that you should be able to push the resources if appropriate.

Using large amounts of ram does not necessitate the software running poorly. He clearly posted specifically that he would trade "efficiency" for features.

Elive 2.0 linux, it's an ultra slim distribution which pays particular attention to older hardware. On this system it ran for several months and at startup used around 150Mb of ram. After struggling to get it to play nice on this laptop I looked for a successor.

Kubuntu 10.04LTS was selected as it's replacement, at boot it uses around 400Mb or ram. Yet it boots quicker than Elive and is every bit as responsive.

Using less ram doesn't necessarily make your program efficient, it just means it uses less ram. Dismissing anything that uses more ram without bothering to learn why as "bloatware" is shallow, lazy thinking.

[the_leander]

However, poster #10 could still learn a thing or two from reading post #11.

You are making the assumption that I don't understand the underlying technical reasons as described by Karlos.

You would be in error in this.

[the_leander]

I actually thought both posts 10 and 11 were good. But maybe  understanding a concept and explaining it are 2 different things.  Especially when it is about something complicated like computers.

I just wanted to show a real life example of why looking solely at how much resource a given system uses isn't the only variable - how it uses those resources is at least as important.

It wasn't my intent to get into the technical side of the discussion, especially when there are people (like Karlos) who are better suited to that side of things.

I am curious as to why the pair of you brought this up as an issue.

[the_leander]

I'm afraid it is your assumption that is wrong.

Perhaps my post was too subtle.  Karlos comes across as a nice guy.

That help?

Ah, so it's tone trolling.

Suck it up.

[the_leander]

Did someone say tone trolling?!

WINDOWS ROOLZ!

That's just regular brand... Needz moar exclamation marks though

[the_leander]

Did someone say tone trolling?!

WINDOWS ROOLZ!

Needz moar exclamationz!!!!!!1111oneoneoneeleventyone

[the_leander]

That's as may be, but I still think he could learn from your post.

This is me not caring about what you think.

Yes.

[the_leander]

And confirming what I thought.

Stay classy!

You just can't help yourself, can you?

[the_leander]

Sound and vision are perhaps the worst offenders. If we'd simply return to monophonic sound and monochrome displays, all our worries would be over. Let's ditch the fancy input devices as well. I'd much rather go back to systems that simply run what I tell them to run when I apply power.

None of that DMA rubbish either, also, what was wrong with simple CPU driven framebuffers eh?

And basic, it's gotta have basic!

:roflmao:

[the_leander]

I can remember running BeOS with 32MB on my 120MHz desktop quite happily about 10 years ago.

Thinkpad 390 with 233Mhz P1, 64Mb ram, Neomagic graphics chip here.

Ended up giving it to my sister, only to get a phone call about 3 weeks later to tell me that her puppy had chewed through the power cable

I actually got Windows 2000 to run on that laptop at one point, beyond taking an age to boot up, it was fairly snappy to use one it got going...

I know of one (well known) application that was ported to mobile devices only to find it ran like a dog.  The reason was it was doing some incredibly stupid things that were completely unnecessary. That app had to be rewritten.

Oh come on! Name and shame  :lol:

[the_leander]

basic in ROM or GTFO

Hehehe!

BASIC!? That implies an interpreter, probably in ROM. If anything, it needs a mechanical switch to keep power away from the CPU until a punch card is inserted.

Wow, we both got served here! :lol:

[the_leander]

One word "Windows" on just about every revision.

Right, so you're complaining about 20 years of continuous development, with all the differences and developments in both hardware and software? 'kay.

To a lesser extent Linux

Depending on what you want to do, you can still get Linux systems that are pretty damned small.  A single floppy disk do for you?

Want a top end kde based desktop OS, with all the trimmings? You'll need a DVD, but you do at least get all your basic software (office etc) included in that.

 and Amiga OS from 3.1 to 3.9 and then OS 4.0.

Cleaning out the assembler and BCPL made AOS slower.  Adding new functionality made it bigger.

If I was able to do everything I do now on an 8MB Amiga OS3.1 install and 16MB Windows 95 install what features am I getting now that take up 1GB+ RAM and a much much greater processor.

Multi user support, memory protection, support for modern hardware, filesharing, network stacks, bluetooth, usb stacks, backwards compatibility with 15+ years of software in Windows case...

I don't mind current web pages with flash taking up RAM and CPU cycles, but why does it so much just to idle the OS when you are playing a game.

...

[the_leander]

I didn't want to turn this into a Windows bashing thread... The example I'm using is the minimum system specs printed on computer game boxes. They have one minimum spec for Windows XP and another minimum spec for Windows 7/Vista. It is nearly double the CPU and double the RAM for 7/Vista.

You're aware that Vista, despite offering a less agile UI, often offers better framerates than XP does on more recent hardware, right?