Hacker News new | past | comments | ask | show | jobs | submit login

Actually I would say collaboration is a huge win. Right now we do shared screens when we have to do some CLI operation.

I know and have worked at companies with very complicated setups for CLI-based workflows where you need 2 people to agree for each command. This could potentially solve all of that.

That being said, with the move to containers there's a lot less CLI surgery to do.




But hasn't collaboration and stuff been a thing for as long as time-sharing machines have? Besides, Service as a Software Substitute is NEVER a good idea, I don't want to go to someone else's server to do something I could on my own, especially when I have to pay taxes for it... By the way, can you define "CLI surgery" for me? I used Unix for a while but haven't played with containers beside chroot jails, and I suspect all that is just your company overcomplicating simple things.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: