Please create an account to participate in the Slashdot moderation system

 



Forgot your password?
typodupeerror

Comment: Wow this was a waste of paper... (Score 1) 486

by aethelrick (#49336439) Attached to: No, It's Not Always Quicker To Do Things In Memory

The research tells us that repeatedly concatenating strings together is a bad thing... WE ALREADY KNOW THIS!!! good grief, who taught these guys to code? The title of their paper "When In-Memory Computing is Slower than Heavy Disk Usage" implies heavy disk access where none exists. They actually go on to point out that it's the OS doing magic things that helps out. i.e. it's the OS using RAM to buffer the disk that keeps your app speedy. So erm... memory being used instead of disk then... the exact opposite of their claims

Comment: Re:Not unambiguously bad (Score 1) 318

Yes but usually both sides regard territory (or people within it) as their own... otherwise they would not be fighting about it in the first place. War is stupid. It would be better to let robots duke it out to decide who wins rather than having people kill each other. Maybe it would be more of a game and less of a human tragedy if we followed this crazy path instead of the crazy path we're already on.

Comment: Re:Yes. Yes they are (Score 1) 318

definition of robot...

A machine capable of carrying out a complex series of actions automatically, especially one programmable by a computer

landmines on the other hand only have a few simple states, "safe", "armed", "detonated", "dud" they are simple single purpose constructs. It's not right to call them robots in any technical sense.

Comment: Re:You are free to have killer robots (Score 2) 318

probably more of a land-mine-layer than a mine itself... unless it's got a pretty gnarly self-destruct sequence and a really low total cost of ownership. Also, I would hope that robots would be equal opportunity killers, slaying all in their path irrespective of age, gender etc... it'd be much simpler code for the IFF module not having to distinguish between short adults and tall kids for example. I wonder what OS they'd run... Windows 11 Terminator edition? Robobuntu?

Comment: Re:systemd needs to stay optional (Score 1) 928

by aethelrick (#48279627) Attached to: Ask Slashdot: Can You Say Something Nice About Systemd?

Yes I could do as you say, but that is besides the point. The point is that the system works and does so within the resources limitations of a single board ARM computer despite the fact it is running systemd.

Don't get me wrong, I'm not a systemd advocate, I don't have it on any of my work servers yet, but equally where I have used it, it has been stable and simple enough and I have not noticed any particular "RAM bloatyness".

I remain open minded about the whole debate, I'll use whatever comes along next as long as it is stable, simple and it gets the job done. Systemd is different to sysvinit and it takes a bit of getting used to but it hasn't done anything evil to my system (yet).

I take a pragmatic approach to this sort of thing, If you don't like, don't use it. The guys building the main distros seem to like it however so you may end up having to use it if you are a Linux admin.

Comment: Re:systemd needs to stay optional (Score 1) 928

by aethelrick (#48277835) Attached to: Ask Slashdot: Can You Say Something Nice About Systemd?
I'm running Arch Linux ARM on a Wandboard Quad single board computer. The system runs apache, dovecot, postfix and samba for a small network. Systemd is in use as it was the default when I installed the OS. The machine only uses 224M of RAM, it has 1.6G free. systemd-journald is the biggest RAM-muncher with 64M is use, but I don't mind this because it's configured to not batter the flash by keeping current logs in RAM only.

Testing can show the presense of bugs, but not their absence. -- Dijkstra

Working...