Oron Peled wrote:
On Thursday, 22 בMay 2008, Ira Abramov wrote:
Quoting Mike Kemelmakher, from the post of Thu, 22 May:
I completely agree and support Gilads opinion - developing commercial
product on Fedora is a bad idea.
great. so we all agree.
No we don't ;-)
Fedora is bad for production.
That's correct. But we were talking about a *development* environment.
A development environment for a commercial product developed by non
developers which are not Linux savvy.
If there are hundreds of developers, than there's a point to
what Gilad said in that this environment is "production" in itself
and need long maintenance periods.
A development environment for a commercial product is always production.
However, if there are 10-20 developers it should be pretty easy to
set a uniform deployment of Fedora and upgrade it e.g. once a
year (skipping one click). The software selection is bigger by
Oron, I love you like a brother but this is complete bull, No one
upgrades a development environment :-)
Here what will happen:
Everything is running smoothly then "Upgrade Day" arrives.
The chief IT mangler takes one pilot workstation and upgrade it as a test.
A new bug fix version GCC fails to compile the utterly broken code which
happily compiled just
find with the older release, due to a compiler bug.
A developer is requested by the head of IT from the head of R&D to help
locate the problem.
As things happen in production development environments, the least
capable developer is given the task, on the premise that this is the way
he can do the least damage.
The developer, which up to this point have been surviving this whole
"Linux thing" by carefully cutting and pasting random code he finds in
the Internet does what he always does when he has no idea and calls his
"guru" friends that explains that the only way to fix the problem is to
re-write the whole code base in JAVA.
Hearing this news the head of R&D explodes and tells the head of IT to
forgot the upgrade. The head of IT, which never resisted the upgrade in
the first place because "why touch something that works" happily agrees.
Obviously, if your target is RedHat/Centos, you'll have to set up
a RedHat/Centos server for final integration/testing. But that's no
reason to punish all developers desktop experience.
The developers work on Windows workstations. In the good scenario they
pull an Eclipse session with X windows. In the bad scenario they run
Linux + Eclipse and toolchain in VMware. In the really bad situation
they program everything in Visual Studio and copy the files manually
using CIFS or FTP to a remote outdated Linux machine and compile it by
hand using a shell script written by an outside consultant.
What "developers desktop experience" are you talking about?
And again, just in case this is somehow lost - I am NOT talking about
old hand VI and Emacs yielding Linux developers. I am talking about your
average Joe Programmer in a typical commercial development environment
doing a Linux commercial program.
Do I sound bitter? nope. I'm being realistic.
Gilad
--
Gilad Ben-Yossef
Chief Coffee Drinker
Codefidence Ltd.
The code is free, your time isn't.(TM)
Web: http://codefidence.com
Email: [EMAIL PROTECTED]
Office: +972-8-9316883 ext. 201
Fax: +972-8-9316885
Mobile: +972-52-8260388
