|
Linux won't fail... It's been around, that I know of when I personally 1st tried it, from around 1993-1994 or slightly beforehand (when I had Slackware 1.02 on CD)... IF it was going to just 'die'? It would have, years ago, & it clearly has not.
PLUS?
Hey, WAY too many BIG corporations use it for various purposes (notables lately are IBM, & GOOGLE (via their AJAX/Linux ANDROID (.apk packages too, lol, & that ENDEARS THEY to me in a weird way, my initials & all))...
One thing Linux has going for it, is FLEXIBILITY & multi-platform portability (which oddly, Windows NT had across PowerPC, MIPS, ALPHA, etc., not just x86) mainly & of course, the fact is it FREE to download + install!
(& since it comes with source, you can "tinker" with it & learn a LOT this way, too, on how the core of a modern OS really TRULY operates).
----
Now, being open source is nice, but... it has downsides imo!
E.G.-> A big 'LOT' of "Linux Penguins" also tout it as being 'more secure' than Windows, & both. outta the box/oem stock? Yes, even SeLINUX bearing distros?? Just plain are NOT...
NOT until YOU 'security-harden' them, yourself. CIS Tool (in the security guide here I did & across many other forums) show you ALL this, clearly. I had both tested is why, for a fair comparison (fair as is possible) AND, to illustrate this VERY POINT.
----
(Also, being an "open sores" (pun intended on THIS part of my statement), can be a 'downside' too, for security)
How? Well... the point here being that it is MUCH harder to find holes, via tracing vs. actual sourcecode perusal, in a closed source system like Windows NT-based variants (well, NT 3.51-4.0 code was 'leaked' to the web a few years back) vs. Linux being open sores!
Simply because you HAVE to 'disassembly trace' them (a running binary in CLOSED SOURCE like Windows), & that takes debug symbols builds, a GOOD debugger (SoftIce or WinDbg) + 2 machines generally AND have to deal in RAW ASSEMBLER code (& understand it well too - not an easy task, certainly not by comparison to looking @ high level language (C/C++ in Linux' case) sourcecode).
All you need in Linux? The source itself, plain jane text, & some programming know-how, really, to "spot weak spots/chinks in its armor" the simpler task, by far.
----
Personally?
It TRULY really doesn't matter to me IF Linux "takes the top spot" either, one day from Windows (The VISTA debacle didn't help MS any this is certain)... I will jump ship as necessary because I do both C/C++ &/or Delphi (which has Kylix for Linux) so, I am "good to go" on either language, & thus, either OS family.
APK
P.S.=> What matters to me is, "AM I USING THE VERY BEST, AS IT STANDS CURRENTLY" & "WHAT IS USED MOST/HAS THE MOST SURFACE AREA + USER ACCEPTANCE" & this? THIS IS WINDOWS NT-BASED OS of the past 2 decades almost now (2000/XP/Server 2003)...
& w/ 53 BILLION in disposable income?
MS hires the VERY best (Mr. Anders Heijelberg for one example, creator of Delphi)... brain-draining BORLAND, regularly, as per usual (even Chuck Jadzewski, co-creator of Delphi & Kylix in fact, quite recently)...
Hey - MS interviewed me, came to me, not I to they... 4 question test, hardest one I ever took, & I answer in 3 diff. languages (C++, VB, & Delphi to hopefully "WoW" them)... still, I did not "make the grade" for their 'crash debug analysis' team...
That told me I have a 'ways to go' before I can even consider THAT level of employ, w/ they... apk
__________________
"I'm Reese: Sgt. TechComVN38416, assigned to protect you - You've been TARGETTED FOR TERMINATION!"
Last edited by APK; Aug 23, 2008 at 09:20pm.
|