Bear Giles <[email protected]> wrote: > Hiking boots, since you never know when a mountain will appear in the > middle of the computer room. > A lot of docker images don't contain 'vi'. You can load them with apt and > yum after an update or two but it's a real PITA when all you want to do is > make a small change to /etc/resolv.conf or something. >
That's why I'm looking at this being all-or-nothing thing. If we nuke even busybox (vi, sed), then we should yank a lot more with _'interactive.'_ Because once we open this _'we don't need text editing'_ argument, or reducing it by 2/3rds, we're looking at a lot of other things. _"Wait?! We reduced Vi to nothing (or next to nothing). Why is this legacy still there too? It's even less important!"_ Kick _'interactive'_ to the curb altogether, or in 1 exam, or an alternative set of exams. Let's really look at it. And get away from this _"My VisualStudio Code** kid hacker beat up your Vi honor student coder!"_ debate. - bjs **P.S. Microsoft VisualSudio Code is actually unrelated to the legacy fat mammoth, so it runs pretty good on all platforms, and is quite useful, despite the trademark. It's still lacking some things that are easily done in Vi though, like ctags (it's equivalent is not well done in many respects).
_______________________________________________ lpi-examdev mailing list [email protected] https://list.lpi.org/mailman/listinfo/lpi-examdev
