[ale] Gearing up for the future (wuz: boot speed, systemd, vi vs emacs, etc)

[Lightner, Jeffrey]

We are doing containers on our own systems (i.e. not cloud) using CoreOS.   CoreOS (the base OS) relies on systemd.   I don't know that going to the cloud for containers will eliminate the need to interact with systemd.  

I started working with DOS 2.0 and Lotus 123v1A in the early 80s.    Later I had to move on to Novell file servers and later yet to AT&T UNIX then various other UNIX flavors and finally to Linux.    

I use MS Windows workstations because that is invariably what my employer assigns no matter how much they   use open systems for servers.   Heck these days I even help my neighbor with her MacBook though I despise Apple's proprietary mindset.

Moving on is something I've done many times in my career and personal life.  I'll likely continue to have to do.    With every new thing comes the folks that equate it with Satanism and/or communism but all the gnashing of teeth has never halted any of these new things.   In the meantime things generally lauded by one and all (e.g. NeXT) seem to have gone by the way side.   

Come to the dark side Luke.   You know I am your farther...


-----Original Message-----
From: Ale [mailto:ale-bounces at ale.org] On Behalf Of Leam Hall via Ale
Sent: Monday, February 19, 2018 11:24 AM
To: Atlanta Linux Enthusiasts
Subject: [ale] Gearing up for the future (wuz: boot speed, systemd, vi vs emacs, etc)

On 02/19/2018 10:19 AM, Jerald Sheets via Ale wrote:
> So let me interject into this conversational process a “norm” that’s 
> evolving out in silicon valley.


Let me render an opinion based on Jerald's comments. Containerization will change "things" as much as VMWare. SMBs will use a cloud provider (AWS, Linode). Large enterprises will use thin clients or portable workstations to connect to their environment. We've probably all seen the signs.

Griping about systemd feels good but doesn't prepare me for the next career challenges. So, what to do?

We have, individually and collectively, at least a few choices.

	1. Change careers so systemd/boot times/containers don't matter.
	2. Hang out with the legacy systems.
	3. Join those moving to the "new thing".
	4. Help enable the "even newer thing".

I'd say the "new thing" (#3) is cloud and the "even newer thing" is containers (#4). There are multiple container technologies and the market is likely to settle on one.

As I look at my career and this list the path forward isn't clear. I get paid for #2 while #1 has been a long standing option. Would need energy and a team to do #4 while #3 is a safe forward option. However, "safe" 
is relative; they can find younger and cheaper cloud admins.

Thoughts?

Leam

_______________________________________________
Ale mailing list
Ale at ale.org
http://mail.ale.org/mailman/listinfo/ale
See JOBS, ANNOUNCE and SCHOOLS lists at
http://mail.ale.org/mailman/listinfo