| ▲ | MisterTea 4 days ago |
| > I'm not sure I follow you but it wasn't a joke. Shell scripts are notoriously error-prone. I absolutely do not trust shell script authors to get everything right. This is an extremely naive take as are the rest of your comments. Any language in the wrong hands is error prone. |
|
| ▲ | IshKebab 4 days ago | parent [-] |
| > Any language in the wrong hands is error prone. Talk about naive! |
| |
| ▲ | linksnapzz 3 days ago | parent [-] | | Feel free to implement system utilities in whichever language you feel will completely eliminate the possibility of bugs. I wait with bated breath. | | |
| ▲ | IshKebab 3 days ago | parent [-] | | "error-prone" means bugs are more likely than the alternatives. It doesn't mean that the alternatives completely eliminate the possibility of bugs. Come on. | | |
| ▲ | linksnapzz 3 days ago | parent [-] | | I wonder what the tally is for "things posted to HN that'll replace bash/ksh/zsh in every respect REAL Soon Now". It's a genre of post unto itself. | | |
| ▲ | IshKebab 3 days ago | parent [-] | | What language is Systemd written in? I'm pretty sure it's not Bash. | | |
| ▲ | linksnapzz 3 days ago | parent [-] | | I've never been able to use systemd as a command interpreter. | | |
| ▲ | IshKebab 2 days ago | parent [-] | | An init system doesn't need to be a command interpreter. Why are you being so obtuse? | | |
| ▲ | linksnapzz 2 days ago | parent [-] | | It doesn't need to be, but there are some advantages in being able to have system startup scripts in the same language that you do one-liners in at the terminal. |
|
|
|
|
|
|
|