I see this a lot in the corporations that i've visited and the one I am with now, they seem to issue work macs to most of their developers. I'm not completely sure why, but it seems to grow on them.
That sounds like a ridiculous reason to move to Mac rather than spend the 10 minutes it takes to set up the most user friendly linux environment. Better Coding ENV, and honestly...They should know GIT command line or shouldn't be using GIT. I can understand Mac in a work environment, it does work well in a highly controlled enterprise environment for upgrades and domain controllers ,etc... But SourceTree is a really silly reason.
Up until recently they had the most ridiculous environment imaginable - Eclipse, and it's equally ridiculous on every single platform. Now they are using Android Studio, which is based on IntelliJ IDEA, which is developed on Macs. But let's ignore that. It offers the same experience on all three platforms it is offered on. So what exactly do they gain from using Linux? Where not even one proper mail client supports exchange interop. Even the native Mac mail app supports more exchange functionality. What a silly thing to say "know command line". Command line. This is not the 60s. If there is a UI tool which removes any need for a command line, then choosing the command line is ridiculous.
I would like to know what a "better coding ENV" is in your eyes. In mine, it is the comfort of the developer. It seems our other guys agree.
Hmm, I suppose I see your point as I do not have any experience with Android and working highly within a Python development. Most of the pushes to our public releases come from people with vim open and keeping things within PEP8 standards.
I think to assume that any of the environments is better than the last is a bit trivial as they have all made some good improvements over the past few/5 years and it often depends on the language, environment, and specifications of the product.
I will admit that I don't have any experience with Android development however and my reply was a snap-reply, my apologies, and I agree it does come down to the comfort of the developer; It is possible within my eyes that developer should have a good knowledge of the lower level infrastructure rather than just building on top of magical unicorns, but honestly for someone building application layer software, why know what drives the unicorn when you have your fingers on the brain eh?
However...
Git Clone/Git Push..is that too much to learn in command line? C'mon!
Even if we have this low level understanding, does not mean you have to reinvent the wheel.
Spazmotic wrote:
Git Clone/Git Push..is that too much to learn in command line? C'mon!
Hmm you are only considering really simplistic scenarios. With multi-branch multi-commit, cherry pick, code reviews CLI is a chore. I still don't see the point of even clone/rebase/push in CLI, when an equally capable tool will do it so much easier faster. Why have UI at all then, when CLI is all you need?
I don't think that any CLI Linux user argues that GUI is simplistic or anything of the sort, but it seems fairly common that those that use GUI do not have that same understanding.
To assume because you can use your mouse and visuals to quickly accomplish tasks does not mean that those that do know how to use CLI effectly cannot accomplish the same task as fast, or honestly faster than GUI. I know many people that have self coded environments that can push to multi-branch environments without a problem without loading a GUI environment.
I was not at all stating that GUI was a bad thing as for many of the things that I use on a day to day basis I use a GUI environment to do that, but to simply assume that a few companies that provide GUI wrappers around a CLI application is better because it fits your aesthetic needs and you think you can do it faster is a better means to do those things. The majority of the people that I do know that run highly in CLI (excluding normal desktop operations), spend much of their time automating tasks in a large scale development infrastructure; not because they dislike GUI, but because in certain cases it simply does not ft their needs, they require a specific set of programmatic events to occur.
LeoNatan wrote:
Why have UI at all then, when CLI is all you need?
CLI is without a doubt all you "need". But I think we can both agree that we "Want" UI, but there is no way for a limited selection of UI applications to fit all developers needs. Saying that reinventing the wheel by redeveloping a UI/Method because a UI exists is not a fair assessment, many people wish their own code there, to know they can add new features that they know are secure when they desire them, an not have to wait on a possibly erroneous code release.
Last edited by Spazmotic on Fri, 12th Jul 2013 08:32; edited 1 time in total
"many people that have self coded environments that can push to multi-branch environments without a problem"
Without a problem, just let me create some shit that requires so much work to "perfect" just so I don't have to open UI, in fact, more time work on my 'wheel invention' than on the actual work or task that the tool was needed for.
But actually, exactly because these GUI apps and OS fit my aesthetic need, means that it is better. Please do point some tasks where GUI cannot be applied. And just because there isn't currently a satisfactory tool, does not mean there can't be. I would argue, that on Linux, for the most part, there is no satisfactory UI. Not just in development, but UI in general, is just horrible. Bad design, highly inconsistent, full of motifs from yesteryear, buggy, amateurish, lacking in features, etc. I blame the CLI community for this, to be honest. They have held back the Linux UI. Now Canonical is attempting to break from the shackles of the nerds, and are eating shit from every direction.
No, CLI is not all I need. Define "need". If you think staring at a cmd is acceptable, then maybe it is all you need. The world has proven it needs UI and silly CLI will not do. We've moved on, thank you very much.
SourceTree does. Works on Windows as well. Thanks to SourceTree I've managed to get all of our frontend devs to branch and merge properly (most of the time ).
BTW, Adobe Source Code Pro Light is an amazing font. I have moved all my monospaced needs to that. On the Mac I use Extra Light in Xcode with my dark theme.
BTW, Adobe Source Code Pro Light is an amazing font. I have moved all my monospaced needs to that. On the Mac I use Extra Light in Xcode with my dark theme.
So old, been using that since forever, first thing I set up on my Mac when I got it
And get iTerm2 instead of OS X's own terminal if you use it regularly Leo. Behaves like a standard UNIX shell instead of Apple's bastardised implementation, has tabs, trackpad gesture support and so on
Signature/Avatar nuking: none (can be changed in your profile)
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
u
).
