Are you naturally this off topic, or did it take effort.
Ignoring for the the moment I agree with *some* of your points, Linux on the desktop has nothing to do with this post, it is entirely about Linux as an enterprise grade server OS.
Actually, the discussion involves using EM Flux as a way to calibrate mass measurements.
Or, using the duck analogy further - then finding (or making) a duck that precisely matches the needed measurements...
Regardless, the goal here is to get a reliable way to reproduce accurate mass meausre, without having a chunk of known mass available at or available to the reproduction site.
maybe because you are using the lump of known mass to measure something else.
Duck Measurer: "I put a duck on one side of the scale, and use weights (lumps of known mass) on the other side to determine the mass of the duck." Some Guy: "Umm, but you already know the mass of the weights, why are you bothering?"
Agreed, those can be *really* nice for setting up your initial GUI, and you can still get under the hood later to make the changes you want if the IDE doesn't have the capabilities to make the GUI do everything you want (which it probably won't)
And, as someone else posted, you can get IDEs in Linux too, with plenty of pretty GUI stuff.
I'm just putting in this reply because I lack the mod points to give you the +1 insightful you deserve. (or at least +1 captain-obvious-that-everone-else-missed)
Then again, they usually reply-to's that cant be sent to... But if they caught on, they might change that and have somethign to determine the required string.
have a random or semi random set of field names, with an associated "key" field. Use the key field to retrieve the field names of interest. Also have a "name" and "password" field set up so they are invisible to a normal user.
Block any IP submitting a non-blank "name" or "password" field.
Wouldn't testing an untested/less tested piece of technology be considered a scientific experiment. In it's intended environment, that would be called a "field test" which is very much science. Without such tests, you are still in philosophy and mysticism. Testing is the major difference between those two fields and science.
I agree to your post almost completely (the */bin directories are relevent to many users because applications are there - but the users shouldn't have to care about that, with desktop menus and such, they shouldn't need to see or know about them, just be able to use what is in them, same as the/etc dir).
But consider my previous post *ONLY* in the context of how it related to the prior post. Your post would be better in response to the prior post than mine I think.
I actually have had several years of working with Linux. And while much stuff can be obtained by package fetchers, I have found them to still be buggy as of my last use, and I have never had an install where other methods of installing a package were avoidable.
I'll grant you the maintenance portion of the package manager is nice, but "bye-bye DLL hell" overstates it's current functionality.
(1) They require repositories that have the package. I've had situations, especially with RPM, least often with Ubuntu, where the default list has some packages but not their requirements. (2) I've also had situations where packages wouldn't install because there were two two packages I needed, each only accepting a slightly different version of a requried package, and the only way to fix this was to go back several version on each package, loosing security, features, etc.
Also, if you looked at it, I wasn't saying package management is worthless, I'm simply saying that his comments, for the average user, weren't really very applicable.
And, I've had more breakage from Linux package managers than from windows updates, especially Ubuntu's and Up2Date (redhat). I've never actually had Windows Updates break anything on me yet (then again, I can easily see when a patch was put in, so I can make sure it's at least two weeks old before installing - that pretty much limits my chances of getting a system killer patch).
Also, with windows, typically you have the older versions of your software available, until you get the new software tested out (a nice thing about CDs), so you can easily revert to the older versions. What few things don't have CDs are usually free to obtain anyway (ex. Windows Updates, Drivers, etc.)
Of course, for any pay software, you are still out of money.
So please, dont assume my views are from lack of understanding or comprehension or experience with the subject, but rather a different perspective and set of experiences.
Slashdot Mirror
I'd grab the briefcase, throw my phone at them, and run before they could change their minds!
I hope they'd find that a sufficient answer.
Actually, I think they are more worried about people finding Aspasia's Base on Mars
I ran NetBSD on my toaster! But the edges of the windows started getting black and crispy, so I went back to just using it for toast...
And NetBSD isn't Linux, but you did mention running things on toasters.
Are you naturally this off topic, or did it take effort.
Ignoring for the the moment I agree with *some* of your points, Linux on the desktop has nothing to do with this post, it is entirely about Linux as an enterprise grade server OS.
620K RAM + a 20Gig hard drive, there's an odd system.
Was there any non-mainframe computer that could use that little memory with that large of a disk?
Or did you me 20Meg?
1. 2 H2 + O2
2. ???
3. Profi- err... CO2!
they are using flux to measure mass.
Actually, the discussion involves using EM Flux as a way to calibrate mass measurements.
Or, using the duck analogy further - then finding (or making) a duck that precisely matches the needed measurements...
Regardless, the goal here is to get a reliable way to reproduce accurate mass meausre, without having a chunk of known mass available at or available to the reproduction site.
maybe because you are using the lump of known mass to measure something else.
Duck Measurer: "I put a duck on one side of the scale, and use weights (lumps of known mass) on the other side to determine the mass of the duck."
Some Guy: "Umm, but you already know the mass of the weights, why are you bothering?"
Hey, Mac users are the ones who insited the other category of home computer was a PC, and they were Macs.
If they don't like the idea, they should be more consistant.
Then it takes a stick of bubblegum (actually, just the wrapper), a shoelace and a pair of toenail clippers.
Agreed, those can be *really* nice for setting up your initial GUI, and you can still get under the hood later to make the changes you want if the IDE doesn't have the capabilities to make the GUI do everything you want (which it probably won't)
And, as someone else posted, you can get IDEs in Linux too, with plenty of pretty GUI stuff.
I'm just putting in this reply because I lack the mod points to give you the +1 insightful you deserve. (or at least +1 captain-obvious-that-everone-else-missed)
Is that Lisp Interface for Non-Unix eXtensions?
I've yet to try that one out?
Should I use
Written Interfaces Normalized Definitions On Wacky Systems instead?
or maybe
Freaky but Rational Enhanced Extensible Basic System Development?
how about
Machine Accessibly Control on Occult Systems eXtended?
Actually, I was thiking about the reply part
Then again, they usually reply-to's that cant be sent to... But if they caught on, they might change that and have somethign to determine the required string.
That's a neat setup, though if it became common, spammers would get around it quick I suspect.
have a random or semi random set of field names, with an associated "key" field. Use the key field to retrieve the field names of interest. Also have a "name" and "password" field set up so they are invisible to a normal user.
Block any IP submitting a non-blank "name" or "password" field.
bah, just have somebody ram soff offsets into your back, and screw on a extended-atx mobo like a real man!
Given the state of current media, I'd like to see one the size/shape of a CD, without a hole in the middle.
Then again, if flash or similar small stuff ends up replacing standard sized optical media, that'll be a waste of time and effort...
You said "powerful" about a VIA product...
Are you feeling well? Maybe you should get some rest, have a doctor take a look at that bump on your head.
TFA said 227KG/500lbs
That would be like releasing an FPS Final Fantasy...
Or a turn based RPG for Quake.
Actually, with the gradual changes they are making for each FF release, I can see the former happening and no one noticing.
Not quite - it's designed so that any contributions to it, if the result is distributed, are given back to the community.
I think this also includes contributions that would allow non-GPLed software to access it.
Selling the non-GPLed + GPLed = make money off of other peoples work.
Though, to my knowledge, there isn't an OSS license out that prevents making money off of other peoples work.
That's what's great about slashdot.
It's dangerous to everyone.
Wouldn't testing an untested/less tested piece of technology be considered a scientific experiment. In it's intended environment, that would be called a "field test" which is very much science. Without such tests, you are still in philosophy and mysticism. Testing is the major difference between those two fields and science.
I agree to your post almost completely (the */bin directories are relevent to many users because applications are there - but the users shouldn't have to care about that, with desktop menus and such, they shouldn't need to see or know about them, just be able to use what is in them, same as the /etc dir).
But consider my previous post *ONLY* in the context of how it related to the prior post. Your post would be better in response to the prior post than mine I think.
I actually have had several years of working with Linux. And while much stuff can be obtained by package fetchers, I have found them to still be buggy as of my last use, and I have never had an install where other methods of installing a package were avoidable.
I'll grant you the maintenance portion of the package manager is nice, but "bye-bye DLL hell" overstates it's current functionality.
(1) They require repositories that have the package. I've had situations, especially with RPM, least often with Ubuntu, where the default list has some packages but not their requirements.
(2) I've also had situations where packages wouldn't install because there were two two packages I needed, each only accepting a slightly different version of a requried package, and the only way to fix this was to go back several version on each package, loosing security, features, etc.
Also, if you looked at it, I wasn't saying package management is worthless, I'm simply saying that his comments, for the average user, weren't really very applicable.
And, I've had more breakage from Linux package managers than from windows updates, especially Ubuntu's and Up2Date (redhat). I've never actually had Windows Updates break anything on me yet (then again, I can easily see when a patch was put in, so I can make sure it's at least two weeks old before installing - that pretty much limits my chances of getting a system killer patch).
Also, with windows, typically you have the older versions of your software available, until you get the new software tested out (a nice thing about CDs), so you can easily revert to the older versions. What few things don't have CDs are usually free to obtain anyway (ex. Windows Updates, Drivers, etc.)
Of course, for any pay software, you are still out of money.
So please, dont assume my views are from lack of understanding or comprehension or experience with the subject, but rather a different perspective and set of experiences.