I see the point in developing directly on atomic as it is something I desire as 
well, but with that said at what cost does it come? 

Atomic's minimal nature not only makes it optimized for speed but also for 
reliability and manageability at scale, and most importantly security. It is 
what attracted us to the project to begin with.

The more packages that are added the more that is sacrificed. I for one will be 
happy dealing without all the bells and whistles to have peace of mind knowing 
the clusters are rock stable and have the smallest security attack footprint 
out of any other available operating systems.

The please add feature x will never stop and it is a slippery slope that has 
already been asked many times which will further pull atomic away from the very 
purpose it was designed and that purpose was not to be just another Linux 
flavor. It is intended to be a stripped down secure o.s. With one purpose; 
hosting containers and nothing else.

Because it is designed for hosting containers the age old method of developing 
on the target platform just doesnt need to be.

Just an example:
http://www.cvedetails.com/vulnerability-list/vendor_id-72/product_id-1860/GNU-Screen.html

http://www.cvedetails.com/vulnerability-list/vendor_id-11380/product_id-20683/Nicholas-Marriott-Tmux.html


-----Original Message-----
From: "Trevor Jay" <[email protected]>
Sent: ‎4/‎20/‎2015 9:37 AM
To: "Joe Brockmeier" <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [atomic-devel] Screen in Atomic

On Mon, Apr 20, 2015 at 11:06:53AM -0400, Joe Brockmeier wrote:
> Other than personal preference, is there a reason Screen is needed
> rather than tmux?
> 

Not at all. Others have mentioned that some debugging tools haven't made the 
switch yet. Ignoring that, I'd agree that tmux--being more modern---makes more 
sense.

> Note - we are currently shipping Fedora with a bunch of packages that         
>                         > are really unnecessary in practice for anyone using 
> Atomic as it's meant                              > to be used. Short term, 
> this is OK b/c most people using Atomic are                                   
> > doing so as you are -- long term, that's a severely broken practice.
>

Yes and no. Sure Atomic's main use will be as cloud host, but why not develop 
your containers on the host you'll ultimately be using? Plus Atomic is a very 
good *as an OS* full stop. I actually prefer virtualizing and working with 
Atomic to the other minimal OS's or even real Fedora. I don't think I'll be 
alone in this, especially when you consider the "I use OSX and virtualize 
Linux" crowd. Once you embrace the "everything in a container" model of Atomic, 
it's a really good experience in and of itself.

_Trevor

-- 
Sent from my Amiga 500.
(Trevor Jay) Red Hat Product Security
gpg-key: https://ssl.montrose.is/chat/gpg-key

Reply via email to