Reading some of these comments from fellow seattleites, I'm really quite thankful for having the privilege of being able to completely ignore all of this noise.
There is zero push in my org to use any of these tools. I don't really use them at all but know some coworkers who do and that's fine. Sounds like this is a rare and lucky arrangement.
the only good git GUI that exists is Fork. Unfortunately, it doesn't run natively on Linux, although some people have had luck running it under Wine.
I found lazygit specifically so bad to the point that I was better off typing in git commands into the terminal manually like some sort of caveman. Somehow, lazygit has found a way to make git even more confusing and user hostile than it already is, which is a significant achievement.
Using it was a harsh reminder of what people running emacs or vim for the first time have to go through.
This idiotic ui paradigm where you have to actively learn to use what should be simple software by memorizing commands and shortcuts needs to die off. It's mind bogglingly inefficient and disrespectful of user's time.
Just think about it - I've literally never had to open Fork's manual (I am not even sure it has one) whereas in lazygit it is utterly impossible to do the most basic things without referring to the manual. Why do we collectively keep tolerating these shitty tools?
Wow, $60! It had better be really, really good for that price.
I managed to get on fine with lazygit during a quick trial this morning. It actually doesn't have a manual (`man lazygit`: `No manual entry for lazygit`) but I found the contextual help (e.g. press ?) useful.
Tower is also very good. Probably just due to having used it more, I prefer it over Fork, but I can get by if I have to use a computer not licensed for Tower.
As much as I heartily disagree with most of what you wrote - and seeing all the downvotes, I'm not the only one - there is a nugget of truth in what you wrote, which answers a lot of your complaints.
"Using it was a harsh reminder of what people running emacs or vim for the first time have to go through."
The benefit of keyboard-driven programs like Vim is that you're trading an initial learning curve for a vastly more efficient experience once the learning is done+.
Mouse-driven tools like VS Code don't demand that the user learns them. Keyboard shortcuts there are optional, since practically everything is in a menu or a UI that can be moused to. This adds on seconds per interaction, adding up quickly over time.
+And the "learning" for these tools can be shortened dramatically by keeping a printed-out cheatsheet. For Vim this can be a huge lifesaver; I made one for magit as well, back before I switched full-time to JJ.
> The benefit of keyboard-driven programs like Vim is that you're trading an initial learning curve for a vastly more efficient experience once the learning is done+.
I have never been rate-limited by my keyboard input speed. I have lost many minutes of time daily looking up cheatsheets for terminal tools that I use occasionally.
Ironically, when I see what impact AI has had on my programming, the biggest has been in saving me time crafting command line invocations instead of browsing <tool> --help and man <tool>.
The speed change you see is not due to raw input speed, but do to eliminating a context switch in the brain. I thinking I want to see X and already seeing it on the screen.
> Mouse-driven tools like VS Code don't demand that the user learns them.
Honestly, I found the barrier to entry way lower with lazygit than with vscode.
I realise I'm not adding anything useful to this discussion. I tried to start VSCode so that I could evaluate it and, maybe, add some info. as to why I find it more difficult to get into, but it just crashes now :shrug:
> The benefit of keyboard-driven programs like Vim is that you're trading an initial learning curve for a vastly more efficient experience once the learning is done+.
This is simply not true and I say this as a life long vim user. The only reason I have vim mode enabled in all the editors that support it, is the fact that it's immensely difficult to retrain muscle memory accumulated from a decade+ time sunk in that editor. Nothing about vim or any of these other tools being keyboard driven, make me more productive in a way that matters.
> Mouse-driven tools like VS Code don't demand that the user learns them.
Good. That's how all software should be. It's a means to an end, not the center of the universe. The whole reason for bringing a UI layer into all of this in the first place is freeing up my brain from having to deal with git's bullshit.
> Keyboard shortcuts there are optional, since practically everything is in a menu or a UI that can be moused to.
The shortcuts are still there if you care to learn them - it should absolutely not be a prerequisite.
> +And the "learning" for these tools can be shortened dramatically by keeping a printed-out cheatsheet.
Or, I could use some actually well designed software and save myself some printer ink :-)
> Or, I could use some actually well designed software and save myself some printer ink :-)
Or, you could use some well-designed and self-documenting software. Too bad there's not much of that besides Emacs - on the other hand, Emacs and occasionally a browser cover most of my computering needs...
I disagree that it's even socialism as NYC isn't outlawing or using the emoluments clause to take control of private stores. It isn't ceasing the means of production in any sense.
The Mamdani plan is to put in stores where no stores exist. That's just a city ran store. Something that used to be pretty common in the US.
Stores exist there. They have some foodstuffs even. They have bars on all the window and your money is handed through a rotating tray under a bulletproof glass with tiny holes in it so you can talk to the cashier (who also has a shotgun resting under their cash register).
That is because that is the viable model in those areas to actually run a store without having your staff egregiously injured/assaulted and not have everything not nailed down stolen.
This ends up getting reflected also in higher prices of foods in those areas, to reflect the cost and lower supply of those willing to take those measures. So people will call it a 'food desert' -- not because you can't get food there (though it mostly sucks and is shelf stable stuff) but because nothing there resembling a walk-around middle-class grocery store exists.
Failing to take those measures, or taking the measures and not raising prices enough to cover the costs, will likely end up in the state losing money, that is, they will be forced to seize the capital of private citizens to fund the state's commercial offerings.
I think you mean "eminent domain" – the emoluments clause prohibits government officials from accepting gifts, payments, or titles from foreign states.
Communism only happens after a revolution overthrowing the current government and replacing the entire economy with the state overseeing it. Note the word entire.
Socialism is when you have the public own entire industries. For example, how the oil industry in Norway is owned by the state.
Having the government do something or own a business is neither communism nor socialism. It's simply a state owned thing. It's not, for example, socialist for the government to have a parks department.
A city ran store is not the city owning the means of production. There will still be private stores throughout NYC. The areas where these stores are being targeted are where those private stores have chosen not to deploy.
Interestingly "no government" also appears to be exactly what is happening in the US with what some people might describe as end stage Capitalist society.
why is your marketing team a bunch of bumbling morons who decided to not only shit on an open source project but also declare your product a "successor" of said project? as if you have any ties to the jupyter project that would allow you to say these things?
There is zero push in my org to use any of these tools. I don't really use them at all but know some coworkers who do and that's fine. Sounds like this is a rare and lucky arrangement.
reply