masterspace @ masterspace @lemmy.ca

Posts

4

Comments

2,065

Joined

2 yr. ago

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.

Sure, if the only criterion you are trying to fulfill is "have as many options and different ways to complete the task at hand as possible,"

Except that's not what I'm saying.

I'm saying it's important to have the right tool available for the job.

If you limit yourself to VIM and command line interfaces, it will mot matter if a GUI is the right tool, it's not in your tool chain, you can't use it.

i.e. I don't use VSCode because it provides me with multiple ways of viewing git's branching history, I use it because it provides me with the better way of doing so. And when the better way of doing something involves using the command line, it lets me do that too.

People insisting on using the command line for everything is like a carpenter that only buys a circular saw and refuse to buy any other saws. Like yeah, you can do almost any cut with a circular saw, and it's not a bad place to start, but theres a reason professional carpenters who need to do repeated cuts quickly, accurately, and in a way that is teachable to others, don't limit themselves to a single type of tool for every scenario.

Getting an automatic terminal window when you start up vs code is no different having two panes in tmux, one for VIM and once for terminal.

Yes it is, and I honestly cannot fathom how you cannot seem to comprehend the difference between text, and an actual pleasant to use and look at graphical interface.

Lazygit looks exactly as trash as the OOTB command line git. How do you not understand that the human brain processes a smooth connected line more easily than a pseudo line broken up by the line space height, made out of pipes and slashes? This is like product design and UX 101.

Again, VSCode does everything VIM does. Not vice versa, one is a superset of the other.

GUI has objectively way more visual noise

Nope. You can open up VSCode and just have it open to a terminal window if you want.

A GUI + Terminal gives you more options than just a terminal. It's not complicated and it's not arguable, one is a superset of the other.

But the points you're bringing up tell me that you don't actually know how to use a terminal environment for development

In what way? That you can have multiple terminal panes open to accomplish a small portion of the above?

It's literally just a basic part of debating something. You say X is bad, I say ok, then what's your alternative?

I'm this case apparently it's a clown emoji. So clearly they have a very valid point and definitely weren't just making an empty pointless comment cause it sounds edgy.

I've posted a reply that basically covers my feelings on this here: https://lemmy.ca/post/41497148/15556917

If you open a repo / folder in VSCode, you immediately have a terminal window pointing to that folder that you can execute any of your VIM or other command line programs in. You also immediately have a graphical file browser that's always available in a pane to the side if you want, a visualizer of your current git branch and history, tooltips and the ability to hover over things for more info, panes that can preview images, pdfs, 3d files, assets etc, tooling and plugins for things like your dev servers / kubernetes / docker so that you can immediately see what services are running in what state, rich debugging, etc.

Fundamentally, I just don't understand ideologically insisting on using the command line for everything. There are times when keeping it simple and text based makes sense, and it's almost always necessary as a fallback, but if you have the option, you can represent things faster and more cleanly with modern graphical interfaces.

Like just compare the command line version of your git history:

With the Git Graph extension version in VS Code:

The Git Graph extension is built on top of those git CLI commands, but it's an actual GUI that let's you represent your git history in a much more readable and scannable format, with quick and immediate access to related commands like viewing the files that were changed in a commit, or jumping to specific commits and branches.

Ignoring the related workflow improvements, even just from a pure graphical standpoint, if a developer honestly cannot comprehend why the human brain more easily processes stuff like a single connected git branch like the above, compared to a bunch of disconnected pipes | and slashes \ on separate lines, then I feel like they need more design training, or perhaps they've just evolved into such pure text based beings that they can no longer comprehend how normal people's brains work, but either way, it's not going to tend them towards good frontend development. I've worked at MAANG companies and I've seen the internal research on how much of a difference a slight feeling of being overwhelmed can make towards someone's enjoyment and usage of software, I don't see why that's so controversial or unexpected in some circles.

Like at work, if a developer wants to use VIM and command line tooling to do their job and has a setup that lets them work as fast as someone using a graphical IDE, I have zero issue with it, but the default Dev Environment that we're going to setup and document is going to use something like VS Code that can do more OOTB without a huge amount of learning CLI commands and workflows.

Name your preferred IDE so they can be compared.

VS Code is not an IDE is the dumbest most pedantic argument.

It is a text editor explicitly designed to have plugins that turn it into whatever IDE you want it to be.

i.e. it's an IDE that you get to specify yourself rather than being locked into the exact toolchain that the IDE developers think is best.

It's wild to me that people that people use VIM in professional software development settings (especially front end).

Like, I get it if you're a sysadmin who's spending all day in command lines and ssh terminals, but when you're working on high level, user facing software, it's just absurd to have the mindset that a command line interface will be better than a command line interface + a graphical interface.

GUI || command line, objectively provides you with more UX tools and ways of presenting data and interactions to the user, than just command line. Everything you can do in VIM, you can do in VSCode running VIM in a terminal, but not the other way around.

Maybe it's because I got my start programming 3d modelling software, but there are fundamentally things that command lines are bad at representing.

I think it might depend what you're into, I don't know much, I've flown my Mavic mini a few times, and have been watching the Ukraine war at a distance.

But if you're into photography and videography you might get more enjoyment out of something like a 249g Mavic that has a solid camera and is an overall very solid drone.

If you're more into sports and piloting, you might have more sustained interest in an FPV drone where you use goggles to see through the stone's eyes as it flies. In that case I've heard good things about the DarwinFPV drones as they're a pretty dirt cheap entry point and you're likely to crash them.

In terms of usefulness for civil defense, I'm guessing that the most useful skillsets are probably FPV flying and drone building and repair, but I'm not sure. In Ukraine it seems like they use some off the shelf quadcopters like mavic minis for basic reconnaissance and observation, and then use FPV drones for carrying munitions and striking targets, and those are a mix of quadcopter style and more plane style.

Another option for civil defense preparedness is to do first aid training.

Also, it seems like kind of a specialized tool. You want it to have a low stall speed but also high maximum speed. The F-14 was a naval interceptor -- intended to take off from and land on carriers at low speed, buy also dash out quickly enough to intercept incoming strikes against that carrier.

Completely agree with you, they're awesome and should be used everywhere.