|Home||Switchboard||Unix Administration||Red Hat||TCP/IP Networks||Neoliberalism||Toxic Managers|
|May the source be with you, but remember the KISS principle ;-)|
When you open your Windows
you'll see a light blue sky filled with clouds.
If you look past the clouds, you'll only see the Sun.
-- Alan Orndorff
"The rumors of SPARC's death have been greatly exaggerated"
Nine factors framework for comparison of two flavors of Unix in a large enterprise environment
Four major areas of Linux and Solaris deployment
Comparison of internal architecture and key subsystems
Hardware: SPARC vs. x86
Solaris as a cultural phenomenon
Using Solaris-Linux enterprise mix as the least toxic Unix mix available
The key research area of the paper in not only comparative advantages of Solaris vs. linux on Intel platform, but also the cost of Unix flavors proliferation. The paper carries a strong "counter-proliferation" of Unix flavors stance. Sometimes I probably am too harsh about linux but that's just because in real life it makes sysadmin environment in large enterprises more complex then it was before its introduction just by adding two additional flavors of Unix to the current enterprise mix (start-ups and small firms are in completely different position here and most of the critique is not applicable). Excessive variety of Unix flavors in large enterprises is a widespread disease that is a sign both technically and politically weak IT management. Which is not uncommon: I've personally known one manager of Unix group of a large corporation who does not understand that Intel CPU and Power CPUs use different instruction sets and as such need different binaries ;-). Such despicable situations are also a sign of IT losing political influence within the large corporation hierarchy of departments. I think that interests of system administrators should be given a proper consideration in case of any new OS introduction in large enterprise environment. And if introduction of new Unix favors does bring savings part of them should be used for retraining. For me that means that if we need to add one flavor of Unix, we also need to remove one (or better two ;-) existing flavors: the best large corporate configuration is just two flavors of Unix on the floor as it is dangerous to put all eggs into one basket. This means adding linux in reality should mean killing HP-UX, AIX or even Solaris. As the hero of famous O. Henry story "The Roads We Take" quipped in slightly different from large enterprise IT circumstances "Bolivar cannot carry double." ;-) [O.Henry, 1910]. The article warns potential adopters of linux that it is difficult to capture value by just adding a new rider on the system administrator horse independently of which operating system we are talking about: be it linux with its two major enterprise personalities: RHEL and SLES, replaying Unix wars on a new level (with Ubuntu in the shadows) or any of the traditional troika of enterprise Unix flavors (Solaris, AIX, HP-UX).
The paper also introduces a generic framework of OS comparison that can be used for comparing other Unix flavors with Linux as well as between each other. It rejects simplistic approach dominant in comparative reviews of enterprise Unixes. In all such discussions it is paramount to separate tremendous price/performance advantages of Intel hardware from the advantages of the OS. As currently the only other enterprise flavor of Unix available on Intel hardware is Solaris X86 the paper is limited to comparison of those two Unix flavors but the methodology itself is more generic.
It is important to understand that operating systems kernels are a side show of open source movement or open distributed collaboration movement in a broader sense. Scripting languages and applications (especially scripting languages) are the key components of the open source movement and at the same time enablers of other forms of open collaboration exemplified by Wikipedia. So it's Perl, PHP, Python, Apache, Jboss, bind, postfix, Postgress and MySQL that are flagships of the movement with LAMP stack (for Linux, Apache, MySQL, and PHP/Perl/Python) as open source highest achievement. I would like to stress it again that the essence of the movement is in utilizing and, simultaneously, enabling distributed collaboration. Many Linux enthusiasts make a typical for technological utopians error. They think that their beloved OS due to this wonderful thing called distributed Internet development will wipe away all traces of its predecessors — as if when you change the fuel you change the car. That's proved to be false: Linux is and will remain just a flavor of Unix with its own (multiple) strengths and no less numerous weaknesses.
In a way Linux kernel is a new "SuperBIOS" on which open applications run and from the technical standpoint it has all the attractiveness of the good old BIOS (which is another way to say that it's pretty boring). Moreover, Linux is just one of many interesting open source kernels, which (for unrelated to its technical merits reasons) is the most popular and gets all PR ink. FreeBSD, OpenBSD and other BSD kernels are similar in technical capabilities, less bloated and have some subsystems (FreeBSD) or packaging (OpenBSD) that are more technically interesting. In many cases they can substitute Linux in LAMP stack and few will ever notice the difference. Actually the difference can be positive: FreeBSD pioneered jails -- a light weight virtual machine in 1999; OpenBSD pioneered integration of SSH and firewalls and defines the state of the art of secure X86-based Unix; NetBSD still defines the standard in Unix portability although Linux recently doing pretty well in this category too.
When one tries to provide a sober assessment of relative merits of those two OSes in large enterprise IT environment and concentrates on the nonpolitical, real world issues of administering multiple flavors of Unix servers one fact emerges as really startling: the current complexity (or, should we say, overcomplexity) of Unix environments lead to the situation in which most sysadmins can master well just one flavor of Unix. Better one might be able to support two (with highly asymmetrical level of skills, being usually considerably more proficient in one flavor over the other). And that's it. Sysadmin who supports three flavors of Unix is by definition a mediocre sysadmin as he has little chances to develop real mastery of any of those three flavors. That leads to natural specialization inside Unix department when each specialist is responsible only for its "own" flavor. Needless to say that this is not very healthy situation that often results in internal fractures, infighting and other corporate ills.
In those circumstances Linux often acts as a spoiler and tends to increase, not decrease the variety of Unixes in the large enterprise environment. Moreover Linux itself is suffering from famous Unix curse with Suse and Red Hat competing in enterprise environment (while rare in the USA Suse is more popular in Europe and large European multinationals). That's why positive effects of linux introduction without removing one of existing flavors of enterprise Unix (which in large enterprise environment is very difficult to do due to acquisitions) are much more questionable for large enterprises then for startups. That does not mean that adoption is slow or benefits are not existent. It just mean that financially linux introduction does not bring substantial savings, if Solaris 10 on Intel is already used in the environment. It bring other advantages such as ability to use open source ecosystem, and savings due to cheaper hardware, but as an OS the cost of support is similar. In few cases when linux is used on IBM Power architecture it can actually increase the costs. While linux is over 20 years old, not everything can be run on linux both for both technical (stability) and political reasons. That means that despite having important "home field" advantage for open source software deployment, the saturation point for Linux in large corporate infrastructures exists and might be lower then generally assumed. Few IT managers want to put all open source eggs into one basket.
The author argues that despite linux popularity and the role of standard de-facto for open source applications development instead of addition of linux one can add Solaris on Intel as it runs on the same high price/performance ration hardware and typically is already present in enterprise environment. Or you need to cut one existing flavors of Unix to preserve the current balance of enterprise OSes.
The paper was written with the explicit goal to serve as an antidote to primitive reviews on Linux self-congratulation sites styled like "I found old PC in the closet, dusted it off, tried to install Solaris on it; my God what a crap Solaris is in comparison with Linux". Such reviews are not only misleading, they disorient open source enthusiasts (especially among staff of large companies) conditioning them against a more stable and in several areas (virtualization is one; Java applications performance is another) more advanced server OS that has a lot to offer. The role of paper as an "antidote" to overselling of linux in enterprise environment somewhat influenced the style making the paper more polemic, then it probably should be. Please note the author consider Linux and Solaris to be two best enterprise OSes despite the fact that paper does not specifically criticize AIX of HP-UX ;-)
One of the non-trivial conclusions of my research that led to the writing of the paper is that the total cost of ownership of Unix as an OS class is highly correlated with the number of Unix flavors used: increasing the number of Unix flavors used in large enterprise datacenter typically results in increasing total cost of ownership independently of which flavor of Unix you are adding: Solaris, Linux or something else.
It is important to understand that large enterprises represent a different class of IT environments then home enthusiasts, startups or Internet service providers (ISP). For example there is no such thing as free enterprise Unix distribution: you need to pay one way or the other for such enterprise level features as regular patch updates and technical support (actually support-wise Red Hat Enterprise Server is more expensive then Solaris). Basically, large enterprises rightly consider Linux to be not free (as in beer) as it actually has a significant costs attached. TCO includes not only license costs, but also annual maintenance contract cost, administrators costs, hardware cost, training costs, consultant related costs (in case of difficulties with important applications), etc.
Also hardware compatibility generally is not an issue: servers are purchased only from top vendors, vendors which guarantee compatibility with the OS (given the complexity of the drivers of modern OSes it's risky to use them on arbitrary hardware). Large enterprises are accustomed to pay a slight premium for hardware that provides better reliability and manageability. They are also the main consumers for mid-range and large ("mainframe") servers. The latter still is an important battlefield of IBM and SUN for the large enterprise customers.
System administrators in large enterprises work in very different conditions that their colleagues in small firms and startups and have different challenges. The main difference is that they usually need to administer several different flavors of Unix that got into the company either as a result of mergers and acquisitions or because of changing preferences of different generations of IT brass at different periods of company history. Actually mergers and divestitures create unique challenges in large enterprises system administrator world as you need to merge two different cultures not only two different IT infrastructures. Often that means the choice of the lowest common denominator and not only ""expenses rise to meet income" type of application of Parkinson law to IT. The ideal of social stability often is viewed in the large corporate IT within the context of heavy spending for the purpose of setting up additional management positions. Outsourcing and downsizing definitely interfere with this ideal, but not to the extent many think.
While Solaris is currently one of most common large enterprise flavors of Unix (along with AIX and HP-UX) it not uncommon to have two of three bland of Unix deployed in the infrastructure. At the same time linux is a newcomer and as such brings the danger of an managing additional brand of Unix with the same staff as before. So attitude to the linux introduction among rank and file Unix administrators are mixed and quite complex despite the fact that most of them use linux on their office workstations and/or home computers for many years. It is one thing to use it on workstations and the other to use it as a part of infrastructure when each minute of downtime costs several thousand dollars. You need to be conservative in such an environment in order to survive.
Like linux, Solaris is an important part of Unix Renaissance and is the oldest and the most prominent commercial brand of Unix (out of commercial brands only SCO Unix is older). Now in addition to that Solaris became the most stable and well supported free OS. Sun (still) provides very good patch support (for Solaris 10 only security patches are free). For a free OS it has unsurpassed scalability. For only the cost of media and shipping, organizations can use the software on an unlimited number of computers with a capacity of 8 or fewer CPUs. Individual users can download Solaris for free.
The author argues that Linux is just "yet another" implementation of Unix and its developers has no monopoly over best technical solutions either in the area of technical innovations or in the area of large Unix server farms administration. For example Linus Torvalds completely missed virtualization train and here (as of end of 2005) Linux is inferior to other free OSes (both Solaris and FreeBSD). History of the first ten years of Linux development can be found in [Bezroukov2005a]. But the problem is that many Linux users do not know the history and deride Solaris not understanding that in many (but not all) important enterprise level features (for example the quality of light-weight VM support, the quality of NFS implementation, stability, scalability and manageability) Solaris is ahead of Linux.
Large enterprises less often make their choices on the base of religious or philosophical doctrines and more often base them on the capabilities and TCO of the products. Currently security, virtualization and reliability are three major areas were OSes are compared along with TCO. Solaris 10 is a pretty revolutionary OS in all those three aspects, the first flavor of Unix that deserves to be called XXI century Unix. Its ability to withstand hardware failures is probably the best in industry. It has stack overflow protection and light weight VMs called zones, two features that provide huge security boost for applications. It has kernel that is more technically advanced then Linux kernel and with the opening of Solaris 10 on X86 it definitely should be considered an option by those enterprise customers who already have significant Solaris deployment.
The same is true for enterprise software which is certified for specific OSes or even a specific version of a particular OS. The initial cost of software is only one factor in the complex large enterprise picture. And as Microsoft successfully demonstrated driving it to zero does not necessary mean winning large enterprise accounts even for powerhouses like IBM with it relentless and well-oiled Linux propaganda machine. The same is true for middleware.
The main problem for linux in large enterprise environment is that it's usually more cost effective to extend existing OS to a new platform (X86) then to add new flavor of Unix to the preexisting Unix flavours mix. The key problem here that adding linux to the enterprise Unix mix "disrupt exiting ecosystem" and overloads existing sysadmin staff. Without elimination existing flavor of Unixes such move tend always be more expensive then extending Solaris to Opteron platform in organizations that already have significant Solaris presence and sysadmins who know Solaris well.
Still, linux has its own value in large enterprise environment, the value which go beyond cost savings. For example, the ability to fight corporate bureaucracy by creating prototypes using existing workstations is one of the key factors that favors linux in large enterprise environment. We should never ignore the fact that Linux represents a significant advantage in pilot projects, permitting to shortcut corporate bureaucracy. It is especially valuable for those projects that can benefit from using new or wider spectrum of existing software technologies. Here the level of support of open source applications as well as much better availability of prepackaged open source applications makes linux more attractive then Solaris as it allows more easy experimentation. Unless Sun pays proper attention to this very important issue it might negatively affect the level of Solaris 10 adoption despite all its obvious technical advantages. Being the development OS for most open applications is an "home field" advantage. It is not that easy to overcome linux home field advantage without major investments. Beyond development tools, large vendors like IBM routinely provide free entry-level editions of products as competitive weapons to crash smaller competitors by releasing them for linux. As Gordon Haff noted "The general approach is to pick a non-strategic product segment or area that just happens to be important to a key competitor." [Haff2007]. IBM Eclipse story is a nice illustration of this approach. It really eclipsed other development tools for Java and served as a Trojan horse for selling IBM expensive, not that reliable and extremely complex Java middleware. Haff cites IBM’s release of its VisualAge software development tools to the open-source Eclipse Foundation in 2001 as a move that dealt a fatal blows to commercial Java IDEs such as Borland’s Jbuilder and Symantec’s Café. "Some collateral damage to competitors in the process is not something that IBM likely regrets," Haff wrote. Perversion of noble ideas and associated slogans for pretty nasty practices is a common metamorphose that occurred regularly in human history. The ideas of open source and free software are not the first and not the last in this long line.
Similar maneuvering for a better shot on competitor is clearly visible in attempts by various vendors to push enterprise linux adoption. In any large enterprise infrastructure "savings nullification effect" from the introduction of a new flavor of Unix mentioned above happens independently of real or imaginable OS virtues or costs of the hardware on which it can run. Articles that boast about huge savings due to introduction of a new flavor of Unix in a large enterprise environment without complete elimination of at least two old flavors of Unix are very misleading and claims about savings are open to review. They probably should be treated mostly as marketing materials (with elements of self-promotion, as the presence of the requisite large photo of smiling CIO strongly suggests). In reality adding another flavor of Unix in a large enterprise IT environment usually increases not decreases the TCO. One CPU architecture and one OS in large enterprise environment is like putting all eggs into one basket and the enterprise essentially became a hostage of a particular vendor, but too many architectures and too many OSes are also bad and very expensive to maintain. Extremes meet and here too an enterprise tends to become hostage, in this case the hostage of unscrupulous consultants. It is important to understand that label "open source" is regularly used for gaining a competitive advantage by one large vendor against another with IBM as a flagship of such usage. That explains some attempts to push linux though the throat of large corporations IT infrastructures: the last thing such often highly placed pushers are interested is benefits for a particular organization. It's all about elimination of competitors although it is sold under the disguise of noble slogans about of advantages of open source and lower costs. The fact that in many cases expected costs savings never materialize should not come as a huge surprise; this is just the nature of the game.
The paper also draws attention to such important but often neglected in OS comparisons area as frequency of patching and its cost for large enterprises. An OS which allows to use less frequent patching schedule has a tremendous advantage in such an environment. This issue might well be an Achilles' point of linux. I would like to stress that TCO for any OS in large enterprise environment now significantly depends on the frequency of patching. And that fact alone explains the rationale behind many Windows to Unix migrations, migrations that happen despite high quality of Windows Server 2003.
As Solaris has regular quarterly updates that have extremely high level of compatibility with previous versions, individual users generally can substitute quarterly updates for patching and thus, the absence of free recommended patch cluster in Solaris 10 is not critical for this category of the users. In this sense Solaris is as democratic OS as Debian and much more democratic then Red Hat or Suse with their artificial designation of alpha versions as "free community distributions" and more debugged versions as "commercial" that require support contract to use.
But the most important feature of large enterprise environment that the paper tried to stress is that Linux needs to be "implanted" into pre-existing Unix mix that usually already consists of two or more flavors of Unix. Enterprise Unix environment behaves more like a complex ecosystem and like in nature invasion of new species has often unpredictable effects. The author argues that this fact alone often nullify all the savings from adding any new flavor of Unix including Linux. Also with Solaris 10 availability on Opteron there generally should be other arguments then hardware cost savings: they are almost zero. Solaris 10 runs well on Opteron based servers both from Sun and HP. Also with the introduction of Intel Duo and Quattro CPUs high-end server (8 CPUs or more, 32G of RAM or more) are reality and Solaris has a very good track record in this segment. While there are differences between Solaris 10 on Opteron and Solaris 10 on UltraSparc they are much less then between any enterprise class Unix and linux as well as between any two linux distributions, for example Red Hat (as well as now Oracle Unbreakable Linux which is based on Red Hat) and Suse. Still due to the level of differences between UltraSparc and Intel platforms the cost of deploying Solaris on Opteron is definitely not a zero and is close of equal to the introduction of a new Unix flavor that increases the diversity of enterprise Unix ecosystem. Like is the case with linux there is no free lunch here despite low initial cost of the OS itself (actually the cost of OS is zero and the price we are talking about is the annualized price of maintenance contract).
All-in-all the paper is intended to provide "slightly skeptical" information about relative merits of linux and Solaris. Each has strong and weak points and as always weak points often represent the logical continuation of the strong. Neither is a dream OS for system administrators and we are mostly concerned about determining "lesser evil" then "clear winner". Also much depends of preexisting UNIX flavors mix: the real headache starts when you need to administer them in addition to one other Unix flavor.
The author hopes that the framework of comparison which was developed in the paper has value independently of whether the readers agree or disagree with some assessments of the author. I also hope that it might help current and future decision makers and might inspire other authors to revisit the topic and/or to extend it to the comparison of different pairs of enterprise class OSes.
Linux is a loaded word. It denotes a particular free "almost POSIX-compatible" OS kernel developed with a huge PR campaign for the last 15 years and, simultaneously, multiple semi-compatible distributions based on this kernel.
Here and below we will try to distinguish between Linux as an OS and Linux as a kernel by using lowercase word for the OS ("Red Hat is one of many distribution of linux" ) and upper case word for the kernel ("Linux 2.6").
We will use the word "Linux" to mean "Linux kernel" and "linux" to mean "Linux distribution"
When we are talking about linux as an OS we will generally mean Red Hat as the dominant linux enterprise distribution. In case we need to compare different enterprise distributions or stress the internal fragmentation of the enterprise linux market we will use the respective names of distributions, for example Red Hat and Suse. When talking about Red Hat we generally mean RHEL 4.x and about Suse, Suse 10.x: two versions that were current and were preloaded by Dell on its servers in the second half of 2006 when the bulk of the paper was written. The choice of Suse 10 is a little bit arbitrary as it was pretty new distro launched in August 2006 and I understand that, but I really prefer it to Suse 9 and I am reluctant to write about Suse 8: the last "good" Suse distribution before 10. In this sense the paper is slightly pro-Novell biased ;-).
There are two major types of open source software vendors: those who try to protect their profits at the expense of the open source community, and those who try to protect the community while leaving profits aside. The first type of vendors in the most numerous and includes both Red Hat and Novell. It also has better survival characteristics (Red Hat is already seven years old company). Canonical Ltd (Ubuntu vendor) currently belongs to the second type. I do not know how long it will stay in this role.
For the rest of the paper it is assumed that readers understand the differences in approaches between enterprise linux vendors as exemplified by Red Hat and Suse distributions and community distributions such as Debian, Gentoo, or the newest kid on the block, Ubuntu. Enterprise linux vendors need to survive and they consciously or unconsciously need to practice "free as in free lunch" approach to the distributions within the limits permitted by GPL (here they actually proved to be very inventive, beating RMS it his own game).
As I mentioned before the paper was written with the explicit goal to serve as an antidote to primitive reviews on Linux self-congratulation sites styled like "I found old PC in the closet, dusted it off, tried to install Solaris on it; my God what a crap Solaris is in comparison with Linux". Such reviews are not only misleading, they disorient open source enthusiasts (especially among IT staff of large companies) substituting wornout and most false clichés for critical thinking and conditioning them against a more stable and in several areas (virtualization is one) more advanced server OS that has a lot to offer. While Linux is a great achievement and now has an undisputable large enterprise penetration, with the current complexity of Unix it can benefit from the specialized hardware tuned to the OS, not the OS written with all the compromises inherent in the achieving the capability to run on mass-produced hardware and attract mass users.
That is another reason why in my opinion Solaris still plays and will continue in the foreseeable future to play an important role in the large enterprise IT environment.
FAIR USE NOTICE This site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available in our efforts to advance understanding of environmental, political, human rights, economic, democracy, scientific, and social justice issues, etc. We believe this constitutes a 'fair use' of any such copyrighted material as provided for in section 107 of the US Copyright Law. In accordance with Title 17 U.S.C. Section 107, the material on this site is distributed without profit exclusivly for research and educational purposes. If you wish to use copyrighted material from this site for purposes of your own that go beyond 'fair use', you must obtain permission from the copyright owner.
ABUSE: IPs or network segments from which we detect a stream of probes might be blocked for no less then 90 days. Multiple types of probes increase this period.
Groupthink : Two Party System as Polyarchy : Corruption of Regulators : Bureaucracies : Understanding Micromanagers and Control Freaks : Toxic Managers : Harvard Mafia : Diplomatic Communication : Surviving a Bad Performance Review : Insufficient Retirement Funds as Immanent Problem of Neoliberal Regime : PseudoScience : Who Rules America : Neoliberalism : The Iron Law of Oligarchy : Libertarian Philosophy
War and Peace : Skeptical Finance : John Kenneth Galbraith :Talleyrand : Oscar Wilde : Otto Von Bismarck : Keynes : George Carlin : Skeptics : Propaganda : SE quotes : Language Design and Programming Quotes : Random IT-related quotes : Somerset Maugham : Marcus Aurelius : Kurt Vonnegut : Eric Hoffer : Winston Churchill : Napoleon Bonaparte : Ambrose Bierce : Bernard Shaw : Mark Twain Quotes
Vol 25, No.12 (December, 2013) Rational Fools vs. Efficient Crooks The efficient markets hypothesis : Political Skeptic Bulletin, 2013 : Unemployment Bulletin, 2010 : Vol 23, No.10 (October, 2011) An observation about corporate security departments : Slightly Skeptical Euromaydan Chronicles, June 2014 : Greenspan legacy bulletin, 2008 : Vol 25, No.10 (October, 2013) Cryptolocker Trojan (Win32/Crilock.A) : Vol 25, No.08 (August, 2013) Cloud providers as intelligence collection hubs : Financial Humor Bulletin, 2010 : Inequality Bulletin, 2009 : Financial Humor Bulletin, 2008 : Copyleft Problems Bulletin, 2004 : Financial Humor Bulletin, 2011 : Energy Bulletin, 2010 : Malware Protection Bulletin, 2010 : Vol 26, No.1 (January, 2013) Object-Oriented Cult : Political Skeptic Bulletin, 2011 : Vol 23, No.11 (November, 2011) Softpanorama classification of sysadmin horror stories : Vol 25, No.05 (May, 2013) Corporate bullshit as a communication method : Vol 25, No.06 (June, 2013) A Note on the Relationship of Brooks Law and Conway Law
Fifty glorious years (1950-2000): the triumph of the US computer engineering : Donald Knuth : TAoCP and its Influence of Computer Science : Richard Stallman : Linus Torvalds : Larry Wall : John K. Ousterhout : CTSS : Multix OS Unix History : Unix shell history : VI editor : History of pipes concept : Solaris : MS DOS : Programming Languages History : PL/1 : Simula 67 : C : History of GCC development : Scripting Languages : Perl history : OS History : Mail : DNS : SSH : CPU Instruction Sets : SPARC systems 1987-2006 : Norton Commander : Norton Utilities : Norton Ghost : Frontpage history : Malware Defense History : GNU Screen : OSS early history
The Peter Principle : Parkinson Law : 1984 : The Mythical Man-Month : How to Solve It by George Polya : The Art of Computer Programming : The Elements of Programming Style : The Unix Hater’s Handbook : The Jargon file : The True Believer : Programming Pearls : The Good Soldier Svejk : The Power Elite
Most popular humor pages:
Manifest of the Softpanorama IT Slacker Society : Ten Commandments of the IT Slackers Society : Computer Humor Collection : BSD Logo Story : The Cuckoo's Egg : IT Slang : C++ Humor : ARE YOU A BBS ADDICT? : The Perl Purity Test : Object oriented programmers of all nations : Financial Humor : Financial Humor Bulletin, 2008 : Financial Humor Bulletin, 2010 : The Most Comprehensive Collection of Editor-related Humor : Programming Language Humor : Goldman Sachs related humor : Greenspan humor : C Humor : Scripting Humor : Real Programmers Humor : Web Humor : GPL-related Humor : OFM Humor : Politically Incorrect Humor : IDS Humor : "Linux Sucks" Humor : Russian Musical Humor : Best Russian Programmer Humor : Microsoft plans to buy Catholic Church : Richard Stallman Related Humor : Admin Humor : Perl-related Humor : Linus Torvalds Related humor : PseudoScience Related Humor : Networking Humor : Shell Humor : Financial Humor Bulletin, 2011 : Financial Humor Bulletin, 2012 : Financial Humor Bulletin, 2013 : Java Humor : Software Engineering Humor : Sun Solaris Related Humor : Education Humor : IBM Humor : Assembler-related Humor : VIM Humor : Computer Viruses Humor : Bright tomorrow is rescheduled to a day after tomorrow : Classic Computer Humor
The Last but not Least
Copyright © 1996-2016 by Dr. Nikolai Bezroukov. www.softpanorama.org was created as a service to the UN Sustainable Development Networking Programme (SDNP) in the author free time. This document is an industrial compilation designed and created exclusively for educational use and is distributed under the Softpanorama Content License.
Original materials copyright belong to respective owners. Quotes are made for educational purposes only in compliance with the fair use doctrine.
FAIR USE NOTICE This site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available to advance understanding of computer science, IT technology, economic, scientific, and social issues. We believe this constitutes a 'fair use' of any such copyrighted material as provided by section 107 of the US Copyright Law according to which such material can be distributed without profit exclusively for research and educational purposes.
This is a Spartan WHYFF (We Help You For Free) site written by people for whom English is not a native language. Grammar and spelling errors should be expected. The site contain some broken links as it develops like a living tree...
|You can use PayPal to make a contribution, supporting development of this site and speed up access. In case softpanorama.org is down you can use the at softpanorama.info|
The statements, views and opinions presented on this web page are those of the author (or referenced source) and are not endorsed by, nor do they necessarily reflect, the opinions of the author present and former employers, SDNP or any other organization the author may be associated with. We do not warrant the correctness of the information provided or its fitness for any purpose.
Last modified: September, 12, 2017