5 ms·

Great answer!, and… well, I’m adding it to the article. In my head :) My experience with fish is quite different, and that’s exactly why I find this discussion

Great answer!, and… well, I’m adding it to the article. In my head :) My experience with fish is quite different, and that’s exactly why I find this discussion so good. Regarding how shells are made more than the shells themselves, I wish to point to the design document itself in case you haven’t had the chance to read it yet; It’s one of the better texts on this sort of thing. I’d be interested in your take on it if one is available :)

hnlmorg 5y ago
I like the layout of the design document and I might steal this page idea myself. However I don't agree with all of the contents: > The law of orthogonality For better or for worse I went the other way and crammed murex full of builtins. Most builtins are single purpose too. Rational: while it creates additional work learning murex it does make pipeline more descriptive > The law of responsiveness This I do agree with an murex does a lot of tasks asynchronously for exactly the same reasons too > Configurability is the root of all evil I actually don't disagree with their point on principle but I think a better stance should be "Defaults should not leave most users itching for configurability" because I think configurability is a good thing however a product should ship already configured so that users aren't left having to enable features they want. The early versions of murex came with features turned off so it behaved a lot more like Bash. Then I realised nobody is going to enable spellchecking, syntax highlighting, etc because nobody is going to know it is there. So now most features are enabled by default. > The law of user focus The description I agree with, the examples I do not. You don't need to remove features to make something user focused. You just need to make those features usable and discoverable. Which leads nicely onto the last item... > The law of discoverability This I agree with wholeheartedly.

hnlmorg 5y ago

I like the layout of the design document and I might steal this page idea myself. However I don't agree with all of the contents: > The law of orthogonality For better or for worse I went the other way and crammed murex full of builtins. Most builtins are single purpose too. Rational: while it creates additional work learning murex it does make pipeline more descriptive > The law of responsiveness This I do agree with an murex does a lot of tasks asynchronously for exactly the same reasons too > Configurability is the root of all evil I actually don't disagree with their point on principle but I think a better stance should be "Defaults should not leave most users itching for configurability" because I think configurability is a good thing however a product should ship already configured so that users aren't left having to enable features they want. The early versions of murex came with features turned off so it behaved a lot more like Bash. Then I realised nobody is going to enable spellchecking, syntax highlighting, etc because nobody is going to know it is there. So now most features are enabled by default. > The law of user focus The description I agree with, the examples I do not. You don't need to remove features to make something user focused. You just need to make those features usable and discoverable. Which leads nicely onto the last item... > The law of discoverability This I agree with wholeheartedly.