MS Changes Things In VS AGAIN!
-
I have been using VS 2022 17.7.4 on my home box for a while. A few weeks again I set up a VM and installed VS2022 17.9.6. In 17.7.4, the region collapse/expand icons are plus/minus signs in a little box. Pretty clear to see and understand. In 17.9.6, they use ^ and > sumbols, which, IMHO, is a lot harder for your eyes to figure out. Why would they change this????
In theory, theory and practice are the same. But in practice, they never are.” If it's not broken, fix it until it is. Everything makes sense in someone's mind.
-
I have been using VS 2022 17.7.4 on my home box for a while. A few weeks again I set up a VM and installed VS2022 17.9.6. In 17.7.4, the region collapse/expand icons are plus/minus signs in a little box. Pretty clear to see and understand. In 17.9.6, they use ^ and > sumbols, which, IMHO, is a lot harder for your eyes to figure out. Why would they change this????
In theory, theory and practice are the same. But in practice, they never are.” If it's not broken, fix it until it is. Everything makes sense in someone's mind.
lol Personally, I don't mind it. At first I thought it was a resharper or visual assist thing.
CI/CD = Continuous Impediment/Continuous Despair
-
lol Personally, I don't mind it. At first I thought it was a resharper or visual assist thing.
CI/CD = Continuous Impediment/Continuous Despair
I do mind it. Not only do the new icons look horible, it's just the fact that they would change it. I mean, why??? This is the sort of thing that drives devs mad. Leave things alone!!! It wouldn't be so bad if they created an option to change it an defaulted it to the previous setting, but to just go about changing the UI that devs are used to with zero warning is just rediculous.
In theory, theory and practice are the same. But in practice, they never are.” If it's not broken, fix it until it is. Everything makes sense in someone's mind.
-
I do mind it. Not only do the new icons look horible, it's just the fact that they would change it. I mean, why??? This is the sort of thing that drives devs mad. Leave things alone!!! It wouldn't be so bad if they created an option to change it an defaulted it to the previous setting, but to just go about changing the UI that devs are used to with zero warning is just rediculous.
In theory, theory and practice are the same. But in practice, they never are.” If it's not broken, fix it until it is. Everything makes sense in someone's mind.
-
Um, what?
In theory, theory and practice are the same. But in practice, they never are.” If it's not broken, fix it until it is. Everything makes sense in someone's mind.
-
I have been using VS 2022 17.7.4 on my home box for a while. A few weeks again I set up a VM and installed VS2022 17.9.6. In 17.7.4, the region collapse/expand icons are plus/minus signs in a little box. Pretty clear to see and understand. In 17.9.6, they use ^ and > sumbols, which, IMHO, is a lot harder for your eyes to figure out. Why would they change this????
In theory, theory and practice are the same. But in practice, they never are.” If it's not broken, fix it until it is. Everything makes sense in someone's mind.
Because they are more interested in form than function, and to "be more inclusive." Squares, apparently, hurt people's feelings...
-
I do mind it. Not only do the new icons look horible, it's just the fact that they would change it. I mean, why??? This is the sort of thing that drives devs mad. Leave things alone!!! It wouldn't be so bad if they created an option to change it an defaulted it to the previous setting, but to just go about changing the UI that devs are used to with zero warning is just rediculous.
In theory, theory and practice are the same. But in practice, they never are.” If it's not broken, fix it until it is. Everything makes sense in someone's mind.
I know, right? And then they do NOT actually fix what devs have been begging them to fix, such as: Microsoft Developer Community - Full Git Submodule Support[^] Look in the comments in the thread of that post and you'll see what I mean. Look, it took them until VS2022 just to make the
devenv.exeprocess a 64-bit process. -
I have been using VS 2022 17.7.4 on my home box for a while. A few weeks again I set up a VM and installed VS2022 17.9.6. In 17.7.4, the region collapse/expand icons are plus/minus signs in a little box. Pretty clear to see and understand. In 17.9.6, they use ^ and > sumbols, which, IMHO, is a lot harder for your eyes to figure out. Why would they change this????
In theory, theory and practice are the same. But in practice, they never are.” If it's not broken, fix it until it is. Everything makes sense in someone's mind.
-
Um, what?
In theory, theory and practice are the same. But in practice, they never are.” If it's not broken, fix it until it is. Everything makes sense in someone's mind.
You missed it Kevin. He's poking at you. But seriously, changing defaults on developers is just an abortion. Dear MS, I have a really good elephanting idea. If you think what you are doing is better, let us have the option of "we disagree, make it go back". The only thing worse I have ever seen MS do (maybe I'll make a website and had ads...) is force reboots. Whoever made the final decision on that needs to be beaten to the point of hospitalization (not the morgue). Free points if you can cite the movie.
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
-
I know, right? And then they do NOT actually fix what devs have been begging them to fix, such as: Microsoft Developer Community - Full Git Submodule Support[^] Look in the comments in the thread of that post and you'll see what I mean. Look, it took them until VS2022 just to make the
devenv.exeprocess a 64-bit process.Ya, lot's of new 'features', but ZERO useful change
In theory, theory and practice are the same. But in practice, they never are.” If it's not broken, fix it until it is. Everything makes sense in someone's mind.
-
Because they are more interested in form than function, and to "be more inclusive." Squares, apparently, hurt people's feelings...
LOL - A more liberal IDE :-D :-D
In theory, theory and practice are the same. But in practice, they never are.” If it's not broken, fix it until it is. Everything makes sense in someone's mind.
-
Maybe they do it to reduce confusion. A squared + is a plus, but a squared - is also a plus. :-)
Religious freedom is the freedom to say that two plus two make five.
trønderen wrote:
Maybe they do it to reduce confusion.
They failed.
In theory, theory and practice are the same. But in practice, they never are.” If it's not broken, fix it until it is. Everything makes sense in someone's mind.
-
I have been using VS 2022 17.7.4 on my home box for a while. A few weeks again I set up a VM and installed VS2022 17.9.6. In 17.7.4, the region collapse/expand icons are plus/minus signs in a little box. Pretty clear to see and understand. In 17.9.6, they use ^ and > sumbols, which, IMHO, is a lot harder for your eyes to figure out. Why would they change this????
In theory, theory and practice are the same. But in practice, they never are.” If it's not broken, fix it until it is. Everything makes sense in someone's mind.
-
I do mind it. Not only do the new icons look horible, it's just the fact that they would change it. I mean, why??? This is the sort of thing that drives devs mad. Leave things alone!!! It wouldn't be so bad if they created an option to change it an defaulted it to the previous setting, but to just go about changing the UI that devs are used to with zero warning is just rediculous.
In theory, theory and practice are the same. But in practice, they never are.” If it's not broken, fix it until it is. Everything makes sense in someone's mind.
-
I have been using VS 2022 17.7.4 on my home box for a while. A few weeks again I set up a VM and installed VS2022 17.9.6. In 17.7.4, the region collapse/expand icons are plus/minus signs in a little box. Pretty clear to see and understand. In 17.9.6, they use ^ and > sumbols, which, IMHO, is a lot harder for your eyes to figure out. Why would they change this????
In theory, theory and practice are the same. But in practice, they never are.” If it's not broken, fix it until it is. Everything makes sense in someone's mind.
I thought it appeared different but only now know why. C’est La Vie[^]
-
I have been using VS 2022 17.7.4 on my home box for a while. A few weeks again I set up a VM and installed VS2022 17.9.6. In 17.7.4, the region collapse/expand icons are plus/minus signs in a little box. Pretty clear to see and understand. In 17.9.6, they use ^ and > sumbols, which, IMHO, is a lot harder for your eyes to figure out. Why would they change this????
In theory, theory and practice are the same. But in practice, they never are.” If it's not broken, fix it until it is. Everything makes sense in someone's mind.
Perhaps MS should make these icons configurable. Config files are as old as eternity, isn't it? Or, has MS already made these icons configurable ?
-
I have been using VS 2022 17.7.4 on my home box for a while. A few weeks again I set up a VM and installed VS2022 17.9.6. In 17.7.4, the region collapse/expand icons are plus/minus signs in a little box. Pretty clear to see and understand. In 17.9.6, they use ^ and > sumbols, which, IMHO, is a lot harder for your eyes to figure out. Why would they change this????
In theory, theory and practice are the same. But in practice, they never are.” If it's not broken, fix it until it is. Everything makes sense in someone's mind.
-
I have been using VS 2022 17.7.4 on my home box for a while. A few weeks again I set up a VM and installed VS2022 17.9.6. In 17.7.4, the region collapse/expand icons are plus/minus signs in a little box. Pretty clear to see and understand. In 17.9.6, they use ^ and > sumbols, which, IMHO, is a lot harder for your eyes to figure out. Why would they change this????
In theory, theory and practice are the same. But in practice, they never are.” If it's not broken, fix it until it is. Everything makes sense in someone's mind.
Some f$€k3r has a useless job and needs to justify their paycheck. Do they know we developers work mostly on muscle memory and instant pattern recognition? Mess that up and it's like cutting off our dominant hand. That's why we go to war with each other over code formatting after all.
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 The shortest horror story: On Error Resume Next
-
You missed it Kevin. He's poking at you. But seriously, changing defaults on developers is just an abortion. Dear MS, I have a really good elephanting idea. If you think what you are doing is better, let us have the option of "we disagree, make it go back". The only thing worse I have ever seen MS do (maybe I'll make a website and had ads...) is force reboots. Whoever made the final decision on that needs to be beaten to the point of hospitalization (not the morgue). Free points if you can cite the movie.
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
charlieg wrote:
force reboots
Especially the "computer will reboot in 15 minutes..." message when you are in the middle of a meeting.
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
-
I do mind it. Not only do the new icons look horible, it's just the fact that they would change it. I mean, why??? This is the sort of thing that drives devs mad. Leave things alone!!! It wouldn't be so bad if they created an option to change it an defaulted it to the previous setting, but to just go about changing the UI that devs are used to with zero warning is just rediculous.
In theory, theory and practice are the same. But in practice, they never are.” If it's not broken, fix it until it is. Everything makes sense in someone's mind.
Kevin Marois wrote:
It wouldn't be so bad if they created an option to change it an defaulted it to the previous setting,
You know the problem with that is that the code would be buggy, and every once in a while, in a completely random fashion, it would just ignore your selection. Or it'd reset it again to the selection you don't want during the next update. Then eventually you'd just give up. Sounds familiar?
