100% agree'd. XML done "right" (with all the abstraction fluff that your eclipse-jockeys deem necessary) quickly becomes totally unreadable.
And as if the brace and quotes soup wasn't bad enough the XML files that you meet in reality are usually poorly indented, too.
This means that in practice you need a special XML viewer software (or editor support) to make sense of a non-trivial XML document anyways.
So, why not just store the meat as well condensed binary blob that can be sliced, diced and transferred without expensive serialization? Well, because XML parsers are "standard" and "XBLOB" parsers are not...
Obviously this is purely anecdotical and we're not running an equal number of drives of each brand (actually we had only 10 WD total...) but nonetheless whenever someone asks me what to buy I say: Try seagate.
1) You can't go 2-3 years without having to update your toolchain, either because of an explicit dependency on it or (and this is a problem in its own right) something that won't compile correctly, dependency or no, with your older versions. Eventually you have to pay the piper with a 400 package update, and then you're screwed. Read some of the other comments in this thread.
Well, depends on what you do I guess. I survived the first year quite easily without feeling a need to rebuild the world. *If* such a 400 pkg update hits me (and breaks on me) I'll probably reconsider another distro but until then I stick with my opinion that gentoo is the most stable and flexible distro that I have come across so far. (and, being a sysadmin for a living, I've had my share of all the major ones)
2) At any rate, even if you can get away with never updating key system components, that's hardly the incredible ease of use of Portage that hooked me on Gentoo in the first place!
Not so sure what you mean. I don't find "emerge k3b" much harder than "apt-get install k3b". True there is some madness in the package.keywords but nothing too pull hair about.
For me there are two major selling points for gentoo and those are: Most things "just work" (after emerging) and it's easy to mix and match custom builds of whatever software you like.
Too many times have I had to mess with things like "getting sound to work" and outdated or dysfunct packages on debian (and recently ubuntu). Gentoo just feels smoother to me, despite the more bleeding edge pkg repository.
Maybe I've been lucky. But as of now I can count my negative gentoo expiriences on two fingers whereas my debian problems would require many more hands than I have...
Of course *I* don't need a new version of glibc every week. But unless you update nothing, sooner or later you need to update everything.
I think you're a bit confused about how portage works vs how, for example, apt-get works.
With apt-get most new packages have to pull in the glibc version that they were linked against. With portage most new packages will simply compile against whatever version of glibc happens to be installed. Consequently your glibc will be updated much less frequently (read: never) on a gentoo box, which is good.
Even better: it is quite easy to completely avoid glibc updates because the number of pkgs that directly depend on it is very small.
The Portage system still works well *if* you're a Gentoo obsessive and emerge sync; emerge -uD world at least once a week. If you get behind, and need to update Portage, layouts, gcc, X and the kernel all at once, you start running into all sorts of really nasty collisions and breakages.
Well, I've used gentoo for a bit over a year and I have never done an "emerge -uD world". Not once.
Also I don't grok your "If you get behind, and need to update... all at once" statement. Why do you "need" to update these things?
I for one update packages when I notice that a newer version has been released that has feats or bugfixes that I care about. The last bigger things I remember updating were amarok and I moved to modular X. All without the slightest hitch. I don't see why anyone would want to update their X or glibc without a good reason or even on a weekly schedule (are you nuts?!). In fact, gentoo's ability to compile against whatever version is there instead of updating glibc for each "apt-get install gnuchess" is a major advantage over other distros.
I think you suffer from the (quite common) misconception that "newer" means "better". This is simply not the case, especially not for essentials like glibc.
Well along came this distraction called 'the internet' and 'netscape'. And then another distraction called 'open source' and 'linux'. As a result of those distractions it set natural language recognition back 10 years. Yep, this is case where competition has stifled a particular innovation.
Nonsense.
Just in case you have been living under a rock for the last 15 years I have some news for you: That kind of innovation doesn't come out of the microsoft campus. It comes out of universities. And those couldn't care less about the NASDAX buzzword of the week...
I'm using it. And beware, it's a buggy hack. Reminds me that I need to finish up my replacement - which is a simple perl script of about 300 lines. Nothing like the mess that nocat is.
Every airline, every bank, every govenrment agency, every healthcare org, every big company you can think of uses proprietary software and languages instead of OSS.
(yes, it is a generalization, just like the one in the parent assuming 8 web companies comprise "most large companies")
Well, most large corps do indeed use Windows in some areas. Usually on Desktops. But "every big company you can think of uses proprietary software and languages instead of OSS." is just wrong. Hardly anyone uses windows for critical services for obvious reasons. Your ATM frontend may be running windows. The backend machine it talks to will more likely be some mainframe or unix derivate.
If people can make high-traffic sites that run on a single machine, then why on earth would they want to add the complexity of making it run off of several machines? I fail to see how simplicity and ease of use are design flaws.
Because otherwise your game will end once your load exceeds the capacity of the biggest single machine that you can afford. Get a quote from Sun/IBM for one of their bigbabies and you'll know what I mean.
And perl is even faster than PHP in most situations - if only by a small margin.
I guess the main reason everybody uses PHP is because, well, everybody else uses PHP.
Perl just doesn't have the ease of "just drop your.php file into docroot" nor an established, ready to go "build a website in 3h" framework like ruby-on-rails. To get decent results with perl you need not only some intimate knowledge of the perl-language itself but also a pretty good idea of how a webapp (or even "servlet engine") smells from the inside because, basically, you'll be writing one from scratch.
Anyways, as I was taught recently, real men write their webapp in LUA.;-)
Slashdot Mirror
That's still quite slow.
I took the "Strategic alliances with Competitors" test and scored 90 wpm gross / 78 wpm net.
Needless to say I can't type as fast on anything but a model M.
Nothing like a buckling spring to get into the "flow"...
100% agree'd.
XML done "right" (with all the abstraction fluff that your eclipse-jockeys deem necessary)
quickly becomes totally unreadable.
And as if the brace and quotes soup wasn't bad enough the XML files that you meet in reality
are usually poorly indented, too.
This means that in practice you need a special XML viewer software (or editor support)
to make sense of a non-trivial XML document anyways.
So, why not just store the meat as well condensed binary blob
that can be sliced, diced and transferred without expensive serialization?
Well, because XML parsers are "standard" and "XBLOB" parsers are not...
With commercial software, they take the time to design and make a product usable BEFORE launching it to customers.
Seems your reality.sys got a bit scrambled by the last service pack...
Does anyone know what the current state of "cheap" fingerprint scanners is?
I mean the kind that is built into laptops from lenovo and the like.
Are these things still as easily fooled as they used to be?
Lesson learned: Never wear a suit.
Try seagate.
We have over 70 of them spinning at work in various servers and desktops,
about 20 are older than 3 years. Models range from 40 to 300gig.
And here comes the kicker: In my 4 years on the job only *one* seagate failed.
In my little failed-drive box I count:
7x IBM
5x WD (50%)
4x Exelstor (100%)
4x Hitachi
1x Samsung (2,5")
1x Seagate (80gig)
Obviously this is purely anecdotical and we're not running an equal
number of drives of each brand (actually we had only 10 WD total...)
but nonetheless whenever someone asks me what to buy I say: Try seagate.
Well, depends on what you do I guess.
I survived the first year quite easily without feeling a need to rebuild the world.
*If* such a 400 pkg update hits me (and breaks on me) I'll probably reconsider
another distro but until then I stick with my opinion that gentoo is the
most stable and flexible distro that I have come across so far.
(and, being a sysadmin for a living, I've had my share of all the major ones)
Not so sure what you mean. I don't find "emerge k3b" much harder than "apt-get install k3b".
True there is some madness in the package.keywords but nothing too pull hair about.
For me there are two major selling points for gentoo and those are: Most things "just work" (after emerging)
and it's easy to mix and match custom builds of whatever software you like.
Too many times have I had to mess with things like "getting sound to work" and outdated
or dysfunct packages on debian (and recently ubuntu). Gentoo just feels smoother to me, despite
the more bleeding edge pkg repository.
Maybe I've been lucky. But as of now I can count my negative gentoo expiriences on two
fingers whereas my debian problems would require many more hands than I have...
I think you're a bit confused about how portage works vs how, for example, apt-get works.
With apt-get most new packages have to pull in the glibc version that they were linked against.
With portage most new packages will simply compile against whatever version of glibc happens to
be installed. Consequently your glibc will be updated much less frequently (read: never) on a gentoo box, which is good.
Even better: it is quite easy to completely avoid glibc updates because the number of pkgs
that directly depend on it is very small.Generally I cannot quite imagine how a gentoo system is supposed to "collapse" during a k3b install...
Well, I've used gentoo for a bit over a year and I have never done an "emerge -uD world". Not once.
Also I don't grok your "If you get behind, and need to update
Why do you "need" to update these things?
I for one update packages when I notice that a newer version has been released that has feats
or bugfixes that I care about. The last bigger things I remember updating were amarok and I moved
to modular X. All without the slightest hitch. I don't see why anyone would want to update their
X or glibc without a good reason or even on a weekly schedule (are you nuts?!). In fact, gentoo's
ability to compile against whatever version is there instead of updating glibc for each
"apt-get install gnuchess" is a major advantage over other distros.
I think you suffer from the (quite common) misconception that "newer" means "better".
This is simply not the case, especially not for essentials like glibc.
+5 Insightful.
Correct. The device in the article is not silent.
If you're looking for a really silent (as in fanless) system then I'd
recommend to look at an mCubed.
I have an "HFX classic" myself and it runs my Athlon64 3500+
perfectly. No overheating, not even in the summer.
I am "old age" and I can still determine whether a CRT or TV is on without looking. These devices emit a very high frequent sound when powered on.
Now is the mosquito frequency below or above that of CRT devices?
I don't think that would ever happen. I just bought this fresh new... hrmmm, wait.. what's this clicking noise..
Name one, beauty.
Nonsense.
Just in case you have been living under a rock for the last 15 years I have some news for you:
That kind of innovation doesn't come out of the microsoft campus. It comes out of universities.
And those couldn't care less about the NASDAX buzzword of the week...
Then why would they complain?
I'm using it. And beware, it's a buggy hack. Reminds me that I need to finish up my replacement - which is a simple
perl script of about 300 lines. Nothing like the mess that nocat is.
Ladies, I'm 2000% convinced that you are wasting your f..ing time.
Thanks for correcting me, I didn't know that. But it makes sense anyhow...
Okay you have a point. I read too much "microsoft" into your post. ;-)
You either replied to the wrong post or you misread mine...
Well, most large corps do indeed use Windows in some areas. Usually on Desktops.
But "every big company you can think of uses proprietary software and languages instead of OSS." is just wrong.
Hardly anyone uses windows for critical services for obvious reasons. Your ATM frontend may be running windows.
The backend machine it talks to will more likely be some mainframe or unix derivate.
Because otherwise your game will end once your load exceeds the capacity of the biggest single machine that you can afford.
Get a quote from Sun/IBM for one of their bigbabies and you'll know what I mean.
And perl is even faster than PHP in most situations - if only by a small margin.
.php file into docroot" nor an established, ready to go
;-)
I guess the main reason everybody uses PHP is because, well, everybody else uses PHP.
Perl just doesn't have the ease of "just drop your
"build a website in 3h" framework like ruby-on-rails.
To get decent results with perl you need not only some intimate knowledge of the perl-language itself
but also a pretty good idea of how a webapp (or even "servlet engine") smells from
the inside because, basically, you'll be writing one from scratch.
Anyways, as I was taught recently, real men write their webapp in LUA.
huh?!
flickr, slashdot, google, myspace, amazon, delicious, youtube, ebay... all unix.
who uses MS? microsoft.com?