Microsoft thinks my time is worthless.
-
That's why they push a DVD worth of updates to visual studio every 3 weeks. And you can't abort an update, even on a metered connection. My time doesn't matter to them. My money doesn't matter to them. My work doesn't matter to them. Thank you Microsoft, for turning your best product into to the best reason I shouldn't give you any more money.
Real programmers use butterflies
-
honey the codewitch wrote:
My money doesn't matter to them
Ow, it does. It's actually the only thing that does.
Bastard Programmer from Hell :suss: "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
And you can't blame the lowly Microsoft worker either. I survived when the C-levels pushed through HR changes from what used to be a total of 20 levels promotion of workers to 100+ levels of career level and promotion. They told us that we would be promoted twice as much as before, but in fact that never happened. It was like The C-levels who decided that had just time-dilated our existence so that we could never ever reach their level again. Check. we are now protected they thought. SO these C-level employees then ran the ship for many years in the shadows for a while, before becoming wholly beholden to the stock price used for their extremely high pay (100's of thousands of stock shares per year) and that of the countless money funds out there who want it to increase all the time. So Microsoft is not really a company anymore, but a zombified company whose only motivation is extracting more money(brains) from you at any cost in order to increase the stock price. So I agree with you. They just want your money :):mad::mad: :omg: :omg:
-
For the second time in 2 days VS 2019 has decided to fail on opening a current nagware project. (nagware in this context means that I get asked about progress at least 2x daily by the Sr. partner! :mad:) By fail, I mean it starts loading, then hangs...any clicks are pointless..it just laughs at me! :laugh: I got it to work yesterday by turning off a feature preview option, then bravely and foolishly closed the project and tried to re-open...and fail. :| Thanks MS! I'm trying to get some work done here and instead, I'm resorting in desperation to trying the update again after the first attempt failed. Fingers are crossed. So far trying to get the development environment working has cost me over 90 minutes and counting...:mad: At least I have VS 2017 in the very possible outcome that this update doesn't fix my problem. :sigh:
"Go forth into the source" - Neal Morse "Hope is contagious"
I had a project that started to not open well in VS2019 earlier this year. Still don't know the real reason why. Other projects were just fine and it compiled in VS2017. "Luckily" my version of Windows 10 had reached end of support but wouldn't successfully update. Windows update had pushed it off for a very long time because of a sound driver problem. I ended up have to wipe the drive and install Windows 10 21H1 and all my other apps. Now the project works just fine again in VS2019. The laptop in general has been running very well and I may be able to get it to last until Windows 10 goes out of support. 5 years down 4 to go.
-
Start by switching to JetBrains Rider. Then, once accustomed, switch to Linux. Can you imagine a life without forced reboots? A life where your computer and your software belong to you again?
I will never run linux as a host OS again. It is unstable trash
Real programmers use butterflies
-
That's weird. I'm using VS as well, but I never get mandatory updates, only optional ones (as in "you can click here to update now or just ignore everything as long as you like"), that solves the problem with metered connections. The updates themselves ain't huge either. The ones I'm getting are more CD-sized. Maybe 2 of them, but certainly not a whole DVD worth. When something like this happens with Steam, it's a sign of the installation being FUBAR.
First of all I didn't say they were mandatory. I said they couldn't be canceled. Second, it wasn't my machine. I had no control over what my client, the user did when he started visual studio, 3000 miles away from me I had to end our session for the day, because once the update triggered we were dead in the water.
Real programmers use butterflies
-
I will never run linux as a host OS again. It is unstable trash
Real programmers use butterflies
Unstable - yes. Trash - in some ways. Windows is definitely a higher quality OS with a much smoother experience. Only problem is the constant repeating fuck-you from Microsoft. I work on Linux inside VMWare. I make snapshots before applying updates or even installing a new program. It helps...
-
Unstable - yes. Trash - in some ways. Windows is definitely a higher quality OS with a much smoother experience. Only problem is the constant repeating fuck-you from Microsoft. I work on Linux inside VMWare. I make snapshots before applying updates or even installing a new program. It helps...
Archlinux is stable enough, but it's not a proper primary OS - it's for embedded and the like. Yeah, I dislike Microsoft too. And Apple. I was almost going to switch to apple because i was tired of running windows, and Apple's operating system is in theory at least, better, but then they ripped off a teenaged orphan I know to the tune of $800 bucks. He worked all summer for that garbage phone. Poor kid. I will never buy a product from them now.
Real programmers use butterflies
-
And you can't blame the lowly Microsoft worker either. I survived when the C-levels pushed through HR changes from what used to be a total of 20 levels promotion of workers to 100+ levels of career level and promotion. They told us that we would be promoted twice as much as before, but in fact that never happened. It was like The C-levels who decided that had just time-dilated our existence so that we could never ever reach their level again. Check. we are now protected they thought. SO these C-level employees then ran the ship for many years in the shadows for a while, before becoming wholly beholden to the stock price used for their extremely high pay (100's of thousands of stock shares per year) and that of the countless money funds out there who want it to increase all the time. So Microsoft is not really a company anymore, but a zombified company whose only motivation is extracting more money(brains) from you at any cost in order to increase the stock price. So I agree with you. They just want your money :):mad::mad: :omg: :omg:
-
That's why they push a DVD worth of updates to visual studio every 3 weeks. And you can't abort an update, even on a metered connection. My time doesn't matter to them. My money doesn't matter to them. My work doesn't matter to them. Thank you Microsoft, for turning your best product into to the best reason I shouldn't give you any more money.
Real programmers use butterflies
About a month ago I had an issue with MS updates They kept trying to update a security patch for something that had been updated more than 3 weeks prior to the FAIL update patch. All updates kept failing So after this little fiasco repeated itself 3 times I emailed Nadella MS opened a ticket OK I will play along. Next I was offered a phone call by a live person. He wasted my time fishing around in my Windows 7 machine and said everything looked OK Duh I knew that. So a week later he called back and said he had reached out to the update team and said the matter was fixed. I requested a phone number so I could call in if I had issues Here you go guys 425-635-2970
-
About a month ago I had an issue with MS updates They kept trying to update a security patch for something that had been updated more than 3 weeks prior to the FAIL update patch. All updates kept failing So after this little fiasco repeated itself 3 times I emailed Nadella MS opened a ticket OK I will play along. Next I was offered a phone call by a live person. He wasted my time fishing around in my Windows 7 machine and said everything looked OK Duh I knew that. So a week later he called back and said he had reached out to the update team and said the matter was fixed. I requested a phone number so I could call in if I had issues Here you go guys 425-635-2970
Nice, - that's a redmond phone # I probably won't get much mileage out of it because this isn't a support issue. It's more of a "Microsoft treats their uses with contempt" issue. VS updates are "Broken As Designed" and I don't think they intend to change them if I complain. :sigh: That said, I may call it anyway to complain. I'm sure it runs to some internal elevated support, they'll probably wonder where I got the # without a support ticket to go with it. :-\
Real programmers use butterflies
-
That's why they push a DVD worth of updates to visual studio every 3 weeks. And you can't abort an update, even on a metered connection. My time doesn't matter to them. My money doesn't matter to them. My work doesn't matter to them. Thank you Microsoft, for turning your best product into to the best reason I shouldn't give you any more money.
Real programmers use butterflies
I believe what all developers are seeing from Microsoft as it regards the Visual Studio and .NET environments is a company that is slowly getting ready to jettison these tools into the Open Source Community as much of it is already Open Source in the .NET Core area while parts of the .NET Framework has been Open Sourced. If I remember correctly, Microsoft does not make a lot of money from these developer tools and with Nadella's focus on the Cloud, many of the tools no longer support his own agendas. This is why so many tools have been abandoned in the past several years and in the development of .NET Core which primarily focuses on Internet development or use of TCP-IP protocols. WinForms was kept for Microsoft's gaming franchise, which requires WinForms and the Windows API. WPF was slated to be tossed but was kept most likley as a result of its linkage to UWP, which is actually a subset of WPF. In my view, Nadella wants to follow the Amazon technical model, which primarily only offers technologies based upon their AWS Cloud Services. As a result, Microsoft wants to get .NET Core sufficiently robust and clean to allow it to be given out to the communities along with Visual Studio or they may even stop supporting this development environment altogether since other vendors are already in the process of developing alternatives (ie: JetBrains' "Rider" IDE). .NET Core then will primarily be the API to access Microsoft's Cloud services.
Steve Naidamast Sr. Software Engineer Black Falcon Software, Inc. blackfalconsoftware@outlook.com
-
I believe what all developers are seeing from Microsoft as it regards the Visual Studio and .NET environments is a company that is slowly getting ready to jettison these tools into the Open Source Community as much of it is already Open Source in the .NET Core area while parts of the .NET Framework has been Open Sourced. If I remember correctly, Microsoft does not make a lot of money from these developer tools and with Nadella's focus on the Cloud, many of the tools no longer support his own agendas. This is why so many tools have been abandoned in the past several years and in the development of .NET Core which primarily focuses on Internet development or use of TCP-IP protocols. WinForms was kept for Microsoft's gaming franchise, which requires WinForms and the Windows API. WPF was slated to be tossed but was kept most likley as a result of its linkage to UWP, which is actually a subset of WPF. In my view, Nadella wants to follow the Amazon technical model, which primarily only offers technologies based upon their AWS Cloud Services. As a result, Microsoft wants to get .NET Core sufficiently robust and clean to allow it to be given out to the communities along with Visual Studio or they may even stop supporting this development environment altogether since other vendors are already in the process of developing alternatives (ie: JetBrains' "Rider" IDE). .NET Core then will primarily be the API to access Microsoft's Cloud services.
Steve Naidamast Sr. Software Engineer Black Falcon Software, Inc. blackfalconsoftware@outlook.com
That's really a shame if you're right. It's their best product.
Real programmers use butterflies
-
That's really a shame if you're right. It's their best product.
Real programmers use butterflies
Actually, Microsoft has an umber of excellent products, SQL Server being one of them. As developers we are primarily affected by those products that directly affect our own type of work, which would be the frameworks and the IDEs. I really don't see Microsoft having a future with these tools as part of their long-term strategies...
Steve Naidamast Sr. Software Engineer Black Falcon Software, Inc. blackfalconsoftware@outlook.com
-
Actually, Microsoft has an umber of excellent products, SQL Server being one of them. As developers we are primarily affected by those products that directly affect our own type of work, which would be the frameworks and the IDEs. I really don't see Microsoft having a future with these tools as part of their long-term strategies...
Steve Naidamast Sr. Software Engineer Black Falcon Software, Inc. blackfalconsoftware@outlook.com
I don't share your love for SQL Server. I'm biased about Microsoft though, having worked there.
Real programmers use butterflies
-
I don't share your love for SQL Server. I'm biased about Microsoft though, having worked there.
Real programmers use butterflies
I have worked with SQL Server, Oracle, Sybase, MySQL, and Firebird. After SQL Server I probably liked working with Sybase the best. Why don't you like SQL Server?
Steve Naidamast Sr. Software Engineer Black Falcon Software, Inc. blackfalconsoftware@outlook.com
-
I have worked with SQL Server, Oracle, Sybase, MySQL, and Firebird. After SQL Server I probably liked working with Sybase the best. Why don't you like SQL Server?
Steve Naidamast Sr. Software Engineer Black Falcon Software, Inc. blackfalconsoftware@outlook.com
When it works it's fine. When it does something stupid or insecure, Microsoft doesn't care enough about it to patch it until the damage is already done. Maybe they've changed that in recent years, but usually I avoid anything with both the words Microsoft and Server in it because I prefer my data stays where I put it, and not in the hands of strangers.
Real programmers use butterflies
-
When it works it's fine. When it does something stupid or insecure, Microsoft doesn't care enough about it to patch it until the damage is already done. Maybe they've changed that in recent years, but usually I avoid anything with both the words Microsoft and Server in it because I prefer my data stays where I put it, and not in the hands of strangers.
Real programmers use butterflies
There must have been some severe deterioration with SQL Server over the years. I stopped working with it after SQL Server 2008. But up until then, it was a very reliable and easy to use database engine. Admittedly, now that I am retired, I prefer to work with Firebird and MySQL even though I have various versions of SQL Server lying about on my workstation and backups.
Steve Naidamast Sr. Software Engineer Black Falcon Software, Inc. blackfalconsoftware@outlook.com
-
There must have been some severe deterioration with SQL Server over the years. I stopped working with it after SQL Server 2008. But up until then, it was a very reliable and easy to use database engine. Admittedly, now that I am retired, I prefer to work with Firebird and MySQL even though I have various versions of SQL Server lying about on my workstation and backups.
Steve Naidamast Sr. Software Engineer Black Falcon Software, Inc. blackfalconsoftware@outlook.com
I had problems with it before that. We got hit with an attack on SQL 2000 servers (it was an attack that affected many) - it's been 20 years so I don't remember the nature of it, but I do remember Microsoft basically screwing everyone and taking their own sweet time. Since then, I've seen problems with 2005, and 2008. Probably patched now, but you can't afford to run their latest bits for years. It's ridiculous. We wound up going back to 4 and implementing an OLE DB compliant SQLXML compatible layer on top of that.
Real programmers use butterflies
-
I had problems with it before that. We got hit with an attack on SQL 2000 servers (it was an attack that affected many) - it's been 20 years so I don't remember the nature of it, but I do remember Microsoft basically screwing everyone and taking their own sweet time. Since then, I've seen problems with 2005, and 2008. Probably patched now, but you can't afford to run their latest bits for years. It's ridiculous. We wound up going back to 4 and implementing an OLE DB compliant SQLXML compatible layer on top of that.
Real programmers use butterflies
Very interesting. When I worked at Credit Suisse from 2001 to 2007, we used SQL Server and Sybase. However, our DBA groups handled all of the issues so we were not affected by them. Nonetheless, we never ran into problems when using either. I have used SQL Server at quite a few companies, where basically I had to do DBA work as well and still found no issues working with this database engine. As I mentioned previously, I cannot say for any version after 2008. Up until 2008, I had worked with SQL Server since 6.5.
Steve Naidamast Sr. Software Engineer Black Falcon Software, Inc. blackfalconsoftware@outlook.com
-
Very interesting. When I worked at Credit Suisse from 2001 to 2007, we used SQL Server and Sybase. However, our DBA groups handled all of the issues so we were not affected by them. Nonetheless, we never ran into problems when using either. I have used SQL Server at quite a few companies, where basically I had to do DBA work as well and still found no issues working with this database engine. As I mentioned previously, I cannot say for any version after 2008. Up until 2008, I had worked with SQL Server since 6.5.
Steve Naidamast Sr. Software Engineer Black Falcon Software, Inc. blackfalconsoftware@outlook.com
You firewall anything enough it's "secure" - at least until it isn't. probably were running strictly DMZ'd servers. We made the mistake of proxying into the DB behind our cisco firewall, because microsoft advertised that the DB could serve pages. We had some management pages coming off of SQL server, and that's how they got in. If I remember right, there were buffer overrun exploits in the sqlxml processing back then, but like I said it has been 20 years now. We weren't the only ones affected, like i said.
Real programmers use butterflies