|
Despite what some luddites may say about newer versions, VS2022 has been very responsive for me since I first installed it last November - I've liked this version a lot. MS has been doing some really good things with VS lately.
A couple of versions ago (VS2017 I think) I noticed VS getting very laggy for me all the time. At the time I used Resharper. I disabled that and everything was nice and responsive again. So I wrote a small extension that did a couple of things I mostly was using Resharper for, and uninstalled Resharper and haven't looked back. My colleagues have done the same - enough of the really useful Resharper functionality has been added to vanilla VS to make living without Resharper doable.
My first suggestion is that if you have Resharper, disable that and see if your issues go away. Resharper has gotten quite bloated over the years.
If there's some Resharper functionalities that you really need, but only from time to time, one of my colleagues uses my extension and then just keeps Resharper disabled, enabling it only when he needs to use those functionalities, then disables it again.
If you're not using Resharper, then try disabling all extensions, see if the issue goes away, then if so, re-enable extensions one at a time until you get the lag.
If it's not extensions, one of my colleagues had issues with VS lag due to the company-installed anti-virus doing constant checks against some VS-used files that get changed frequently by it, which would lock the files when doing the checks, causing the lag. Might be worth checking that out and getting some folders excluded from the antivirus check if so.
|
|
|
|
|
Gjeltema wrote: If it's not extensions, one of my colleagues had issues with VS lag due to the company-installed anti-virus doing constant checks against some VS-used files that get changed frequently by it, which would lock the files when doing the checks, causing the lag. Might be worth checking that out and getting some folders excluded from the antivirus check if so.
That's hitting me hard, and not only with VS
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
It happens to me w/ some regularity. I always utilize the latest Preview version. I have few extensions installed. The swirling blue circle I quite dislike. Why everything does not happen instantly I do not understand. Maybe it is my pig of a machine.
|
|
|
|
|
Preview versions tend to have a lot of debugging and telemetry enabled, which can cause them to be inconsistent in their responsiveness to keyboard and mouse inputs.
|
|
|
|
|
Wordle 457 4/6
⬛🟨⬛⬛🟩
⬛🟨⬛⬛🟩
🟨⬛⬛🟨🟩
🟩🟩🟩🟩🟩
|
|
|
|
|
Annoying as elephant
Wordle 457 X/6
⬜⬜⬜⬜🟩
🟩⬜🟨⬜🟩
🟩🟩🟩⬜🟩
🟩🟩🟩⬜🟩
🟩🟩🟩⬜🟩
🟩🟩🟩⬜🟩
"If we don't change direction, we'll end up where we're going"
|
|
|
|
|
I got lucky. 
I was convinced the same was going to happen to me!
|
|
|
|
|
Wordle 457 5/6
⬜⬜🟩⬜🟩
⬜⬜🟨🟨⬜
⬜⬜⬜⬜⬜
🟩🟩🟩⬜🟩
🟩🟩🟩🟩🟩
Software rusts. Simon Stephenson, ca 1994. So does this signature. me, 2012
|
|
|
|
|
Wordle 457 5/6
⬛🟨🟨⬛⬛
🟩🟩⬛⬛🟩
🟩🟩🟩⬛🟩
🟩🟩🟩⬛🟩
🟩🟩🟩🟩🟩
It's amazing how many 5 letter words differ by 1 letter!
|
|
|
|
|
Wordle 457 3/6
🟨🟩⬛⬛🟩
⬛🟩⬛🟨🟩
🟩🟩🟩🟩🟩
|
|
|
|
|
Wordle 457 3/6
⬜🟩⬜⬜🟩
⬜🟩🟩🟩🟩
🟩🟩🟩🟩🟩
Yay!
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Wordle 457 4/6
⬜⬜🟩🟨⬜
🟨🟨🟩⬜⬜
🟩🟩🟩🟨⬜
🟩🟩🟩🟩🟩
|
|
|
|
|
Wordle 457 3/6
🟨⬜🟩⬜⬜
🟨⬜🟩🟩🟨
🟩🟩🟩🟩🟩
A rare occasion where I have it in three guesses 
|
|
|
|
|
Wordle 457 X/6
🟨⬛🟨⬛⬛
⬛⬛⬛⬛🟨
🟩⬛🟨🟨🟨
🟩🟩🟩⬛🟩
🟩🟩🟩⬛🟩
🟩🟩🟩⬛🟩
GCS/GE d--(d) s-/+ a C+++ U+++ P-- L+@ E-- W+++ N+ o+ K- w+++ O? M-- V? PS+ PE Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X
|
|
|
|
|
Wordle 457 3/6
⬜🟨⬜🟨⬜
⬜🟩🟩🟩⬜
🟩🟩🟩🟩🟩
Life should not be a journey to the grave with the intention of arriving safely in a pretty and well-preserved body, but rather to skid in broadside in a cloud of smoke, thoroughly used up, totally worn out, and loudly proclaiming “Wow! What a Ride!" - Hunter S Thompson - RIP
|
|
|
|
|
Wordle 457 6/6
⬛⬛⬛⬛🟩
⬛🟩🟩⬛🟩
🟩🟩🟩⬛🟩
🟩🟩🟩⬛🟩
🟩🟩🟩⬛🟩
🟩🟩🟩🟩🟩
Get me coffee and no one gets hurt!
|
|
|
|
|
Wordle 457 5/6*
⬜🟩⬜⬜🟩
⬜🟩🟩⬜🟩
🟩🟩🟩⬜🟩
🟩🟩🟩⬜🟩
🟩🟩🟩🟩🟩
This was beginning to look familiar.
|
|
|
|
|
Wordle 457 5/6
⬜⬜🟩⬜⬜
🟩🟩🟩⬜🟩
🟩🟩🟩⬜🟩
🟩🟩🟩⬜🟩
🟩🟩🟩🟩🟩
Got off to fast start then too many options.
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
I wonder how many of us do it? I do.
I frequently mentally compare code I see with what I would have written myself, and I do so not to critique other people's code (though it happens) so much as to understand myself and the way I write. Introspection after all, isn't automatic, be it with code or otherwise.
I've noticed some pretty interesting things in the process. I don't know how much the activity has actually influenced my coding style. The biggest change to the way I code that has ever happened to me happened in 2018. I don't solve problems by breaking them into their component pieces anymore. I attack problems more ... holistically? now. It generally makes for efficient, but less intelligible code. The way I think changed. Some ways for the better, other ways not, but it impacted how I write software, among other things.
Cons: Compared to much of the code I see in the wild, my functions are long, my solutions aren't as readable, some things are so instinctual to me I forget to comment.
Pros: My code generally works, and does so well when it does. In some ways, cutting down on the abstractions leads to simpler code, or at least the surface area/API of said code is simpler, if I'm making a library for example.
I see the above as a net win, but only marginally so, and maybe most of that small net advantage can be chalked up to natural, incremental evolution rather than my 2018 watershed event.
I enjoy thinking about this stuff, but I'm not sure if it's beneficial, or me just passing time.
Your thoughts?
To err is human. Fortune favors the monsters.
|
|
|
|
|
It sounds like we start similarly but have different outcomes. Most of the code in my repository--some 235 KLOCs--had little up-front design. I just have something in mind and start coding. But with empty functions to be filled in later, merciless refactoring, and creating new functions whenever code fragments are duplicated. This usually results in small functions, though I don't mind a long function if breaking it up would add no value other than satisfying some arbitrary maximum length.
The downside is that I could sometimes save time by doing more up-front design. The upside is that time spent on more than a cursory up-front design is usually wasted. The code has to be written so that it can speak to me.
|
|
|
|
|
I've always been blessed by being able to quickly produce and visualize even complex designs without writing them down, which I primarily do for the benefit of others.
And I can do it in tandem with coding. It's a gift. I was a software architect for a time, so I understand design principles, and the rules of engagement. I just break them because I can get away with it and still produce solid designs.
https://honeythecodewitch.com/gfx
I've been adding to this for over a year without fundamentally changing the architecture. I started with gfx_pixel.hpp and went from there, building up bitmaps, and then drawing functions, and then on to more complicated things. And I future proofed it for the most part. It hasn't had a major refactor because aside from some necessarily grotty internals I'm not sure *how* to refactor, it doesn't need one.
But I am abysmally bad at defensive coding, or coding to a precise specification, like you find with bare metal embedded sometimes, or medical or bank software.
To err is human. Fortune favors the monsters.
|
|
|
|
|
Heh, bare metal embedded design/coding is exactly what I've been doing for most of my career (retired now). It's what I enjoyed the most. And yes, after a number of years in the business, the overall design of a project just seemed obvious after reading a spec.
|
|
|
|
|
Mostly ditto.
I do a little more up front designing but it's mostly a research of previously written applications. I do try hard to be consistent with naming, etc. for my future benefit and the benefit of those who might have to maintain it. BTW it's all various generations of ANSI C.
Honey's approach is a gift many of us do not have.
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
You don't write code for yourself, or even for the compiler; you write it for the poor soul who has to maintain your code when you have moved on. Therefore:
- The code should, as far as possible be self-explanatory - meaningful variable /function / ... names, etc.
- Where the code is not self-explanatory, it must be commented sufficiently to explain what you have done.
- Ideally, all functional blocks should appear once, and once only, in the module. This implies refactoring common code into functions, etc.
- A design document is typically necessary in order to explain your decisions. This cannot be replaced by comments in the code!
Anything and everything else (code formatting etc.) is a matter of personal taste. Many companies have guidelines that might clash with your preferred style, but this is not a hill to die upon.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
An upvote despite (a) after I've moved on, I no longer care; (b) formatting guidelines that clash with my style are simply wrong. 
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
