5 ms·
I use oh my zsh for exactly one reason: I can get a good shell experience out of the box and immediately start working on stuff productively, whether it's a new
by g947o 10mo ago
I use oh my zsh for exactly one reason: I can get a good shell experience out of the box and immediately start working on stuff productively, whether it's a new machine, a new remote host or a container.
I could spend hours figuring out all those things, bit I'd rather use that time for something more important.
- MeetingsBrowser 10mo ago> I could spend hours figuring out all those things, This post is explaining how to set up those things. Less than five minutes to read.
- namuol 10mo ago> Less than five minutes to read. OMZ is still easier to set up consistently. That’s why we use it. If the concern is the bloat of OMZ then make FMZ - fast my zsh - that is just as quick to set up and doesn’t add “bloat”?
- do_not_redeem 10mo agoI won't spoil the article, but if you read to the end you'll find out what this "FMZ" project is called.
- Liquid_Fire 10mo agoCan you spoil it for me, because I read it to the end and saw no mention of such a project. Unless you are referring to the DIY approach the article suggests.
- einsteinx2 10mo agoSomewhere else in the comment thread Zim (zimfw) was mentioned which after reading their website sounds pretty much like that.
- SkyPuncher 10mo agoThat misses the point. I don’t even want to think about any of that stuff. It’s a single command to install oh-my-zsh. I can fire it off, check Slack, and come back in 5 minutes. If I have to take 5 minutes to setup it up, I’m just not going to do it.
- deleted 10mo ago[deleted]
- MeetingsBrowser 10mo agoCaring enough to read a blog post and comment on hackernews, but not enough to copy/paste the changes from the blog post is a very fine line.
- deleted 10mo ago[deleted]
- SkyPuncher 10mo agoNot sure what your point argument is.
- darkwater 10mo agoTheir point is that what you complain about as "time consuming" is not time consuming at all and that you consumed more time reading the post and commenting on HN that actually installing starship. In your defense I must say I installed starship ages ago but still not migrated to it from powerline-go because I'm lazy.
- subsection1h 10mo ago[flagged]
- happytoexplain 10mo agoThis is common low-quality internet arguing ("you care enough to come into this thread but..."). You can avoid this by keeping in mind that different things are different things, and analogies have many holes by default.
- g947o 10mo agoLess than five minutes to read but how long to set up my own? The author only showed what he needs/prefers ("Here is my config for starship"). I'll need to navigate the documentation of starship to figure out all those options, which defeats the purpose. Their config documentation (https://starship.rs/config/ https://starship.rs/config/) already gives me headaches. And from the article > Because cloud services are available globally, I've disabled them. That's some bad defaults right there. > When you run a command, it also shows how long it took to execute. No I absolutely don't want this thing done by the author. Now I am fully in the "customize my config" territory. Also, most of us are unlike the author, and 0.07s vs 0.38s startup time means no difference. I think the point of the previous comment has been more than clear enough.
- bostik 10mo ago> Also, most of us are unlike the author, and 0.07s vs 0.38s startup time means no difference. That's quite likely a workflow thing. If you are popping up new (transient) terminals frequently, then a ~400ms wait time for each adds up and makes the entire machine feel really slow. I'm willing to wait extra half a second for a new terminal -- once -- after I've changed my autocompletion configs (rebuild + rehash takes a while), but if I had to wait for that long every time I hit Win+enter and wait for the terminal to become active, I'd be irritated pretty damn quickly too. You get conditioned to immediate responses pretty fast.
- tcoff91 10mo agoYeah but you can use something like zim that is better than omz but still easy. The shell starts so fast with zim and it is a breeze to set up
- jauntywundrkind 10mo agoExactly. The popular culture has bad picks. We can be low effort without necessarily being 100% unselective! No taste is not mandatory! Just the littlest bit of trying & listening to our peers can make a better world. There's so many better non-shite alternatives. Just one: Zim aka zimfw is one. It's just so sad that there's such a negative creep energy towards "I tried nothing and did nothing and this is where I am". Bad hacker bad. You deserve no voice.
- bovermyer 10mo agoPeople should be encouraged to play and explore. I landed on Zim eventually, but it's far from universally installed on my machines.
- deleted 10mo ago[deleted]
- FrenchTouch42 10mo agoTry https://starship.rs https://starship.rs then. Starship gives you the same "drop in and go" experience but without the 200ms+ prompt lag. One curl -> one line in your rc file, works on zsh/bash/fish/whatever. Configuration is straightforward and easy imo: https://starship.rs/config/ https://starship.rs/config/ Give it a spin, I think you won't regret it.
- baby 10mo agoOh my zsh makes installing extension so easy, just edit .zshrc and add extract, fzf, z, etc. To the list of plugins
- shimman 10mo agoNever heard of this, looks pretty good. Are there any community themes based on starship like powerlevel9k/10k?
- sigwinch 10mo agoIt requires a nerd font.
- sandreas 10mo agostarship is great. I use it with a powerlevel10k fallback in my dotfiles for systems, starship is not installed yet to not break the shell entirely.
- vbezhenar 10mo agoI've spent few days and got some basic zsh settings adjust for me. Since then I'm mostly using zsh with very little configuration and I like it a lot. Yes, it's a steep curve, but I'm spending all my life in zsh, so I think that was good time investment for me. In my experience default zsh settings are good enough and require very little customization.
- esseph 10mo agoI just use fish shell. Way easier. https://fishshell.com/ https://fishshell.com/
- petepete 10mo agoI recreated my several hundred line + several plugins zsh config in a few dozen lines of fish and one plugin (fzf.fish), about 8 years ago. It’s been a joy to use.
- mekster 10mo agoBiggest problem being not being able to paste much of the complicated code found online. You can save it and run it via bash command though. oh my zsh can recreate much of the fish functionality while maintaining good bash interoperability.
- your_fin 10mo agoThis is the most common complaint I see for switching interactive shells to fish/nushell, but it's not a problem in practice. You don't ever uninstall bash, so if you've got a command to paste: bash <enter> <paste> <enter> exit <enter> Tada!
- cromka 10mo agoExactly this, couldn't be easier. Heck, I run into this all the time on macOS whenever an LLM gives me a Bash one-liner that for some reason doesn't work with ZSH. It's easier to just pop into Bash than analyze and adapt that command line to ZSH.
- opan 10mo agoFWIW if you're on a machine where you're allowed to use non-default configs like oh-my-zsh, you could also just copy over your own custom config. It seems like you're implying the alternative to using oh-my-zsh is to rewrite your config from scratch every time or use the default. It doesn't quite add up to me. If you craft a config file of your liking one time, then back it up somewhere, track it with git, whatever, you can keep making use of that config across other machines. I just set up a new personal machine recently, grabbed my dotfiles, now it's the same familiar feeling as my other machine.
- g947o 10mo ago> just copy over your own custom config That already defeats the purpose: I don't want to copy things around I never spend time crafting a custom config
- RHSeeger 10mo agoCrafting a custom config is right up on the list of things I enjoy. Right up there with creating new characters in video games that allow lots of customization.
- theK 10mo agoHmm, weren't dotfiles invented just for that reason? I'm joking but on a more serious note, installing a shell as a default shell seems more complicated than copying over your .bashrc
- b40d-48b2-979e 10mo agomore complicated than copying over your .bashrc In case you weren't aware, MacOS uses zsh as the default installed shell. The bash version that comes with MacOS is some ancient 3.x version, from 2005.
- theK 10mo agoI think you where trying to say something and then stopped just short of actually making your point. Please continue.
- b40d-48b2-979e 10mo agoJust that it would be `.zshrc` since zsh is already the default shell in the context of this post unless you enjoy a mid-2000s existence and none of the nice bash features of this generation (in which whatever `.bashrc` you've crafted is likely broken by time passing). Maybe I'm underinformed, but I don't personally know any Linux users who convert to zsh, instead opting for fish or something else (oilsh? nushell?).
- al_borland 10mo agozsh has similar files that can be copied over to other systems.
- latexr 10mo agoI stopped using Oh My Zsh for exactly one reason too: It was so freaking slow it had a noticeable effect on my shell and my mood. It frustrated me that I had to stop and wait every time I opened a tab. So I removed it, then continued using Zsh and whenever I missed something from before I looked up what it was and installed the plugin easily with Homebrew. The whole process took under an hour. I realised I only needed two or three plugins. Now my shell is fast, without unnecessary bloat, and does what I need. I’m much more productive and happier, and at the end of the day I don’t really see what’s more important than that (within the scope of the conversation).
- ozim 10mo agoOne man’s bloat is another man’s feature.
- qudat 10mo agojust install fish then
- sodapopcan 10mo agoYou really only have to go through that once and it's a good learning experience.
- yolovoe 10mo agoI will have forgotten almost everything by the time something inevitably breaks in a few years. Unless I am constantly recalling the knowledge and applying it, I don't find it worth it. And I _don't_ want to be constantly recalling this knowledge. I want it to just work. OMZ has been working steadily for me for the past 8+ years. Autocomplete, syntax highlighting, and a concise prompt--really all I need.
- sodapopcan 10mo agoI mean you learn things about the shell ans shell scripting in general which you do retain. Also shell config is one of those rare things that doesn't "inevitably break." The only stuff that breaks are related to program settings which omzsh isn't going to handle anyway. You end up learning a bit and have a much lighter config. Case-in-point, you had to spend some time combing through and learning all the aliases it defines you when you could maintain a small few that you actually want. Also, zsh has plugins natively.