masterspace

and if I do not want the GUI part, how come it surprises you that I do not use that superset?

Go ahead and represent an arbitrary 3d shape using the command line, suddenly you may realize that a typewriter's interface isn't the fastest for accomplishing every programming task.

Regardless, you can be happy with a limited subset of functionality and trying to cram every interaction into text, that's not an argument that that way is better or that a new dev should go that route, just that you can get by using that method.

Lmfao bro,

article CLEARLY states and in house glasses are SIGNIFICANTLY more expensive than Gorilla Glass for some manufacturers.

no man, it does not. It quotes a single Chinese manufacturer's spokesperson who said that off hand about a single type of screen. It has no information on whether or not that's actually true for Honor, it has no information about whether or not that would be true if they produced their screens at the same scale as Corning or whether they expect production to get cheaper, and it doesn't mention anything about literally any of the other brands or any of the the other in-house screen technologies in use.

Your mistake was buying derusting solution. Just use vinegar with some salt.

Either way, if you don't paint it, atleast make sure to oil it afterwards, otherwise it will rust again immediately.

I said continuous vertical lines and literally posted a screenshot of it not being able to do it.

It's functionally the same visual representation of data so you're literally arguing over it not looking like you want it to look.

No, it's not. The human brain does not process dashed lines as easily as it does continuous lines. A whole bunch of dashed lines are objectively harder to follow than continuous ones.

You can think that's not important, but the literal decades of UX research and attention to fine grained user interaction, can prove that you're just flat out wrong.

You look at the above and think they're the same, but they're fundamentally not. Literally just go ahead and try and visualize a basuc cube with this base point and dimensions through a CLI and watch that wow, maybe a fucking typewriter interface isn't the best for absolutely everything:

Cube([0.37, -300, 45], [37,-98,-100])

To be fair, in his 20 YEARS in parliament, his name has been attached to seven bills, one of which have passed, but that was one of Harper's omnibus bills that crammed a million different things into one, guaranteeing that he did not write it.

https://www.parl.ca/legisinfo/en/bills?parlsession=all&sponsor=25524&advancedview=true

His earliest ones were during Paul Martin's tenure, and his latest were during Trudeau's. A single one of his earliest bills seems halfway reasonable, but it's also hard to analyze without the context of what else was being introduced at the time. Otherwise, his bills have basically been what I would describe as jerk off motion partisan troll bullshit that had no actual hope of actually passing or influencing anyone.

He's not a person who's actually serious about improving the country in a meaningful way, he's a dipshit high school debate kid who got a job in government and has then spent 20 years doing nothing but whine about government.

No, the conclusion I've been saying is that CLI developers are smart people who have spent a long time memorizing commands to get fast at things that can be done quickly and intuitively through basic 2d graphical interfaces.

They're now either in a situation where the gains from learning the new process aren't going to outweigh the costs (though still doesn't mean anyone else should follow their path), or they would, but they're just stuck in their ways because of sunk cost fallacy.

No, I'm not. I'm just pointing out how lazygit is still limited by being a line by line, text based, CLI interface, and thus cannot draw a continuous vertical line, even if drawing a continuous vertical line would make sense in that situation:

Ok, cool beans bro, try and write 3d modelling software with just a command line interface and you'll quickly see how a typewriter's format for displaying text isn't the fastest for every programming task.

But the VSCode plugin ecosystem still lacks some features available in the Vim ecosystem, and (fl just for example)

Isn't that basically the same as Command Shift P and / or the search feature?

At the end of the day, the biggest difference is speed. Even very brief unexpected delays can break my concentration. While VSCode is no slacker, it still has some delays, probably mainly because it's still JavaScript under the hood.

Once there's a GoLang, Rust or C port of VSCode, I may well switch permanently.

I can 100% understand how big of a deal speed delays can be, but at the same time, not to probe too hard, but what are you experiencing delays in? In all honesty waiting for ohmyzsh to start, or waiting for a git pull to run, takes far longer than any task I can think of in VSCode. Files open faster than notepad, the file browser is fast, the shortcuts and commands are fast, I honestly haven't experienced any slow downs with it anywhere, and I've used it with monorepos that are TB in size.

Actively sticking a stick in your own spokes feels like more effort and agency than PP's ever experienced in his life.

I cannot fathom voting for someone who has been in government his LITERAL entire career, and has never once passed legislation. He is the epitome of an empty soundbite in vaguely human shaped form.

Literally not, since I'm advocating for a superset of what they are.

I use command line tooling perfectly happy within VSCode, they don't use graphical tooling within VIM.

I'm literally just advocating for a toolset that lets you use graphics or a cli, depending on what makes most sense for the task at hand, they're advocating to only use the cli.

This is a nothing article with no real substantive information or answer to the question.

The answer is undoubtedly 1. cost, and/or 2. trade war.

1. As the article notes, Gorilla Glass is expensive, companies would rather not pay for it and use older versions in cheaper phones, quite frankly this is a plausible enough of a reason to not even bother writing the "article".

2. If the author had wanted to spend another minute thinking about it before posting, they might've realized that Corning is an American company, and Chinese smartphone makers might be hedging their bets and investing in in-house / in-country alternatives in case they get cut off by the petulant child of a country that is America.