View Single Post
Old 02 August 2015, 18:46   #192
son of 68k
meynaf's Avatar
Join Date: Nov 2007
Location: Lyon / France
Age: 45
Posts: 2,902
Originally Posted by Mrs Beanbag View Post
ok, but now i'm puzzled... how is that so? Apart from that m68k is so much nicer, i would certainly rather implement any algorithm in m68k asm than in x86 asm. But if it is only pure computation, and not interactions with the OS, surely there can be no difference? Or you mean, the same computation can be done on a less complex OS?
You never have a program that's only pure computation. At one place or another, you have interactions with the OS.

Originally Posted by Mrs Beanbag View Post
you mean at the same time they started having an MMU... which can do not only memory protection, but virtual memory. Windows did seem to like using swap space a lot. Having more RAM helps. Feel free also to blame bloatware at this point (which i don't deny exists).

i just ran ioctl on my (Linux) PC. The biggest culprit for occasional HDD access was Firefox. After i closed that and Thunderbird (the only things running), there was no disk activity at all. I guess mounting /tmp and /var/tmp as ram filesystems makes a difference.
Well, you can eventually redirect hd activity to some ram disk, it's nevertheless disk activity.

Originally Posted by Mrs Beanbag View Post
Points to note:
* Amiga became more secure after software update
* One of the most complex software had a bug

Usually these things are simple to fix. They are just situations nobody thought of, because you can't think of everything. The more complex the code is, the more things there are to think about. Also i just remembered the things i was thinking about last night, that being the perils of development by teams.

Sometimes what you get is two bugs, that are very simple to fix individually, and are by appearance quite unrelated, but it turns out fixing both at once requires a little more care. The problem is, each bug was assigned to a different person...

We also had on our team once, a guy who was from a military embedded systems background. He was a disciplined coder, and he knew his stuff, and he'd write some fix and one of us would review it, and it would be very nice and neat and logical, and simple and clear and easy to understand. And we'd go "yeah, that all makes sense". And it would get pushed. And it would break everything. And there would be "oops" and red faces.

There exist competitions for writing this sort of code.
I could give my own stories about team development, but during all that time i'm still waiting for someone to hack my amiga config.

Originally Posted by Mrs Beanbag View Post
It's a good old chicken-and-egg scenario.
The egg came first
meynaf is online now  
Page generated in 0.03984 seconds with 10 queries