Forgot your password?

Comment: Re:The UK Cobol Climate Is Very Different (Score 1) 256

by Lotana (#47924527) Attached to: College Students: Want To Earn More? Take a COBOL Class

Ah! That is the first insightful reply and one I agree with.

Indeed, you are being judged by the clothes you wear. This is something I had to learn back in high school when I had to go for my first job interview. It is all about the first impression and regardless of what you know, it will be formed before you even speak. It is tragic that regardless of what you know, it is how you look like that makes the most difference :-(.

Alas, that is human nature and there is no changing that. At some point one has to give up on idealism and just accept that certain realities of society are just not-nogotiable. I guess developers are one unique group that can get away with since they can work from home and avoid seeing clients.

Thank you for your explanation.

Comment: Re:The UK Cobol Climate Is Very Different (Score 1) 256

by Lotana (#47924509) Attached to: College Students: Want To Earn More? Take a COBOL Class

It puzzles me because it is quite petty (You wear one additional piece of clothing over the usual), this aversion is quite widespread among developers and from my interactions among several white-colar industries it is only in IT that it is present.

Hence I find it odd... Especially since they are willing to sacrifice money to get around this requirement.

Comment: Re:The UK Cobol Climate Is Very Different (Score 2, Insightful) 256

by Lotana (#47924407) Attached to: College Students: Want To Earn More? Take a COBOL Class

Chances are you'll need to wear a suit to work.

This has always puzzled me why some developers list this as a negative. What is wrong with wearing a suit? Every professional workplace has an expectation of a formal atire. What is wrong with requiring suits over the usual office shirts and pants?

Comment: COBOL: Why the hate? (Score 1) 256

by Lotana (#47924383) Attached to: College Students: Want To Earn More? Take a COBOL Class

There is certanly a lot of hate directed at COBOL. However, since if it is still being used, then it still has some capability that is not available in other solutions. Also looking at the wikipedia, the language keeps being updated (COBOL 2014 standard is out for example) and supports object-oriented methodology.

COBOL is one language that I haven't encountered. Perhaps it would be insightful if someone can explain why there is so much animosity towards this technology.

Comment: Re:What's wrong with Windows Server? (Score 1) 613

by Lotana (#47821407) Attached to: You Got Your Windows In My Linux

Very true. I have encountered similar situation many times. No idea why you are modded to -1.

However the scenario is a failure of the initial admin not the software. Quite often they are young, inexperienced, "Open source is the best for everything" junior who is often a friend or a relative of someone in the company. This is because those small businesses are trying to save money on the IT and so they don't want to spend money on a professional consultant. Some inexperienced kid will make just as much of a unmaintainable mess with Windows servers.

  A properly setup system with documentation and training for the user will work just fine regardless of what OS is in use.

Comment: Re:The Future! (Score 4, Insightful) 613

by Lotana (#47813731) Attached to: You Got Your Windows In My Linux

I respectfully disagree. Fragmentation impacts both developers and the end users.

There are a finite pool of people that have the knowledge to improve/write software. That group is further divided down into those that have the time and motivation to contribute to the open-source software. From there they are further divided among the competing projects that are doing the same thing. Example: GNOME 3 vs Cinnamon vs MATE vs KDE vs Trinity. Debian vs Red Hat vs Arch vs Suse vs Slackware. Therefore this fragmentation needlessly reduces the pool of available contributors.

Also, any software package needs to be maintained for so many different configurations. A very good example is the package management: Debian, Red Hat, Gentoo, Slackware each have their own package format. This fragmentation adds more boring workload on the maintainers. Now that we will have distributions with or without systemd, it means that if the software deals with the area affected, TWO versions need to be developed! Doing something twice is again wasted effort.

End User:
Fragmentation adversely affects the user because the software he/she needs may not be available for the configuration that it being used. It is hard to come up with example for systemd since it is such a system-level system. Much easier to use an example of window-manager fragmentation: A certain package may look terrible on the one that the user chose.

Even if the software is available, documentation may be only written for another distribution.

Finally, the user needs to choose a distribution to start with. The choice is literally overwhelming. Have a look at this timeline: Distribution Timeline. Now imagine it exploding even further into systemd using/rejecting versions. That much amount of choice is paralyzing.

In the end, fragmentation just wastes resources on doing the same things more than once. It is necessary if the constrain is quite severe, but right now in the community forks happen over something as trivial as library versions or the visual look!

Comment: Re:Why the fuck is this on Slashdot? (Score 1) 789

Please, keep Slashdot about technical topics. Leave the politics for other sites! Please!

Unfortunately it is too late.

Slashdot was the first to report on 9/11 when other news sites were down. Ever since then the readership has changed and Slashdot became MUCH more political. Front page had Your Rights Online articles much more often since then.

Testing can show the presense of bugs, but not their absence. -- Dijkstra