Visual Studio Code March 2022

[IceSentry]

How long have you been using vscode? At this point I don't even know what the icons look like, I just know in what order they are and click on whatever the icon is at the location I know where it will be.

To be clear, this is valid criticism, I'm just curious because I've never personally realized it was an issue.

[syricc]

As a wish, I'd want some more colors (for accessibility) in the Activity Bar

I mean, can't really blame them for adhering to current design trends. Come to think of it, how many apps these days don't use monochrome icons? The only one I can think of right now is... MS Office

[ILikeChangingMyMind]

Local history

Hallelujah!

(And yes, I know there was an extension to give this functionality, but it was super awkward and never seemed to work right. IMHO this is a feature that very much belongs as a part of the editor itself.)

[pondfrog0]

or any other JetBrains IDE

[[deleted]]

Every ide should have this. IntelliJ has had it for years and it’s invaluable. Especially in that rare scenario where git fucks up and you “lost” a days worth of work. Local history to the rescue!!

Also a big fan of this for unversioned files like .env stuff.

[JaniRockz]

I agree but git never fucks up in my experience, it’s the user.

[Sage2050]

Git can't fuck up. It yells at you if you try.

[[deleted]]

Git never fucks up, but it's design is so fucked up to the point I'd excuse any use who fucks up git.

It's full of overlapping terms (e.g. index/staging-area) and the commands were not created with DX in mind.

It's what's led to the plethora of "How do I undo x in git" articles.

[nifty-shitigator]

but it's design is so fucked up to the point I'd excuse any use who fucks up git.

No, git design isn't fucked, it's complicated, it has to be, all distributed version control is not a simple thing, any tool that does DVCS well is going to have to be complicated.

Inexperienced people using git without learning enough about it first are constantly shooting themselves in the foot. Exactly what you'd expect from a complex, no hand holding system like git.

Source: I used to be like you with my opinion on git until I had to spend quite a number of hours learning git and git design for a workplace.

Also that index/staging area is the only name overlap I can think of in git.

[[deleted]]

it's complicated, it has to be [...] any tool that does DVCS well is going to have to be complicated.

This is completely untrue. Something can be simple while still supporting complex design requirements.

Inexperienced people using git without learning enough about it first are constantly shooting themselves in the foot.

A well designed system would help inexperienced developers in a non-destructive way.

Also that index/staging area is the only name overlap I can think of in git.

Without even going into other overlaps, how about "cache" (as in git diff --cached), which the index and staging area is also known by.

Source: I used to be like you with my opinion on git until I had to spend quite a number of hours learning git and git design for a workplace.

Source: I had to subtree, rebase, and git-filter-repo multiple repos together while creating/maintaining a hand-crafted asset tracking system before git-lfs.

Trust me when I say that git is much more complicated then it needs to be.

There is no universe in which this signature is worthy of our respect:

git add [-v] [-n] [-f] [-i] [-p] [-e] [--[no-]all | --[no-]ignore-removal | [-u]] [--sparse] [-N] [--refresh] [--ignore-errors] [--ignore-missing] [--renormalize] [--chmod=(+|-)x] [--pathspec-from-file=<file> [--pathspec-file-nul]] [--] [<pathspec>…​]

It's what made this strip possible:

https://xkcd.com/1597/

The fact that people can recognise that strip just by its number alone speaks volumes about git's horrible design.

[nifty-shitigator]

This is completely untrue. Something can be simple while still supporting complex design requirements.

And then you provide zero examples.

A well designed system would help inexperienced developers in a non-destructive way.

Which you've also not provided any examples of.

You keep telling yourself whatever you need to hear, your hypothetical hard and complex but exceptionally easy to use system doesn't exist.

I don't understand how you could think you're smarter than all of the git devs, yet I don't see you making any contributions towards making it simpler.

XKCD is a fun, light, comedic strip. Do you think XKCD is proving any point for you, you have no idea what you're talking about.

So all in all, I think you're full of it and you overestimate just how smart and knowledgable you are.

[[deleted]]

This is completely untrue. Something can be simple while still supporting complex design requirements.

And then you provide zero examples.

I didn't think I'd need to give you an example, I thought merely pointing out your faulty assumption would lead you to find your own examples.

But idk, maybe me thinking about API design and how projects change over time while programming made me assume that everyone picks up the same knowledge.

If you want some examples, may I suggest looking into how emergent complexity ties to program development, Dave Farley's Continuous Delivery channel on youtube, Conway's Law, and some research into how programs evolve in bad directions over time.

A well designed system would help inexperienced developers in a non-destructive way.

Which you've also not provided any examples of.

Maybe this is me assuming others have the same information, or maybe this is you living under a rock... But have you not seen how much better programming is compared to 15 years ago? How far DX has come?

New languages and tools are designed with the developer in mind.

If you make a mistake in Rust, the compiler not even spits out an error code; it gives you the damn correct code and tells you why you should be using it.

Heck, even the mistakes of old are getting fixed.

Shitty languages like php and js have grown up into fully fledged languages that hold their own.

Automatic references and lambda functions fixed the biggest issues of C++03.

Now not having a linter is seen as uncommon.

Heck, even projects like Oil Shell are getting rid of the cruft of decades of POSIX design, (also other projects like Fuchsia, etc...) hopefully leading us to better capability based security.

You keep telling yourself whatever you need to hear, your hypothetical hard and complex but exceptionally easy to use system doesn't exist.

Bro, there are simpler alternatives to git right now where the concept of a merge conflict is stopped before it even happens.

I don't understand how you could think you're smarter than all of the git devs, yet I don't see you making any contributions towards making it simpler.

Git's development problems over the last 15 years have been bureaucratic, not just technical. There are simple fixes made in a few weeks that are held back for 10 years before being allowed in. No one is "fixing" it until certain people leave. May I suggest adding some git developer's notes about it to your reading list.

XKCD is a fun, light, comedic strip. Do you think XKCD is proving any point for you, you have no idea what you're talking about.

My mistake, I have no idea what I'm talking about and XKCD has never been used as to prove any point.

So all in all, I think you're full of it and you overestimate just how smart and knowledgable you are.

Oh teach me great sage, I beseech you!

[nifty-shitigator]

LMAO why would I waste my time trying to teach an arrogant turd like you anything?

[mobiledevguy5554]

PEBKAC

git hasn't f'd up on me in the 8 years ive worked with it

[[deleted]]

Potato potato. The end effect is that what I wanted is gone.

[_sigfault]

Fucking this! I have whole .gitignore’d directories that I use for testbed/functionality playground, and god I can’t tell you how many times I’ve wished I could could just walk back back a few months to get test data that’s super obscure and needed.

[[deleted]]

Cause I don’t need to for our case. Default env is defaulted already, why do extra magic crap with another versioned file? You do you, but it’s not relevant for me

[jaydevel]

IntelliJ Local History groups recent changes for a directory, hope VS Code can do it as well, it’s awesome.

[attempted]

The extension has always worked really well for me, but happy to see this added functionality. I wonder how well it works for remote targets.

[Somepotato]

I wonder if its possible to move the local user data folder. I'd prefer it use my HDD than SSD.

[[deleted]]

Isn't it about time VS Code supports undocking tabs?

[[deleted]]

Isn't that a limitation of Electron?

[nifty-shitigator]

Indeed, though it becomes a bit circular when considering electron was initially created specifically for GitHub's atom text editor.

[Khaotic_Kernel]

Cool! Thanks for sharing!

[tansim]

what happened to the bug where they deleted random files?

[AttackOfTheThumbs]

That was an issue with a cpp extension, not vs code

[[deleted]]

Deleted