Every time I read one of these, I kind of imagine management at Microsoft running round like the Three Stooges. I know it's not a perfect analogy, because of course I'm comparing a team of seasoned professionals with years of experience who know exactly what they were doing, how, and why, with a long history of satisfied customers to Microsoft management but hey...
Despite it being Ignite week for much of Microsoft, there was still plenty going on in the house that Bill built. The axeman cometh for Windows Insiders' Skip Ahead Windows Insiders expecting a quiet week keeping the Ignite booth staffed were to be disappointed as build 19018 of next year's Windows 10 (20H1) was pushed to …
Monday 11th November 2019 11:14 GMT a pressbutton
I think I am getting old
I spend nearly 10h a week on 'Teams'
In every meeting there will be someone ...
'on mute' = doing something else and not listening, eating or shuffling paper or (more rarely) going to the toilet, or cracking up due to latency issues
and at the end, the project manager will be none the wiser.
It is not always v. green and takes more time due to travel, but I far prefer it when I can see people rolling their eyes and sniggering.
Not a criticism of 'teams', just that it is better called Solipsism
This post has been deleted by its author
Monday 11th November 2019 11:15 GMT Zog_but_not_the_first
As an aside it should be noted that skippy-speak employs the most efficient compression algorithm known.
Four kangaroo voicebox clicks unpacks to "you say the doc's truck has crashed into the ravine and he's hurt real bad with a broken arm and leg. Petrol's pouring out of the truck and a couple of snakes are closing in. The sun is going down, etc."
Monday 11th November 2019 14:16 GMT alegr
> Fiinally, 4,622 issues were closed by the VS Code team last month during a frenzied bit of housekeeping.
Ha.Here's how they close such record count of bugs:
Visual Studio Feedback System changed the status of the following problem:
"A Git repository can't be opened if it has a remote with no fetch URL"
to Closed - Lower Priority and added a comment.
Thank you for the feedback, but our team was unable to prioritize it at this time as they are working on problems with broader customer impact. You can see details at: https://docs.microsoft.com/en-us/visualstudio/ide/report-a-problem?view=vs-2017#faq. Please comment below if you have additional data or details that will help us appropriately reprioritize this issue. It is possible that this problem has been addressed in our latest version which can be downloaded from: https://visualstudio.microsoft.com/downloads/ . Thanks for contributing to Developer Community.
Monday 11th November 2019 14:54 GMT iron
Monday 11th November 2019 22:32 GMT JasonT
Visual Studio != Visual Studio Code
Visual Studio Code is a very different beast than Visual Studio. The release cadence and overall responsiveness for VS Code issues (https://github.com/microsoft/vscode/issues) is much better than Visual Studio. This is one of the few applications that I look forward to the close-to-monthly releases. If you're not looking at VSCode because "it's M1cr0$haft" you're doing yourself a disservice.
Monday 11th November 2019 23:46 GMT Anonymous Coward
Re: Visual Studio != Visual Studio Code
I’m not looking at vscode because it is a horrible piece of software. Nothing to do with it being from MS. Bloated Electron mess that behaves how it wants instead of like the rest of the actual OS it is running on. I occasionally have a peek at it, never gets any better.
Tuesday 12th November 2019 19:37 GMT Michael Wojcik
Re: Visual Studio != Visual Studio Code
I'm not looking at it because I hate IDEs. I've been using IDEs on everything from PCs to mainframes since the 1980s, and I've yet to see one that comes close to the power of a good set of dedicated tools running under a competent shell.
JFTR, I did take a look at VS Code. It's better than Original Formula Visual Studio, but that's a mighty low bar. I didn't care for it.
Monday 11th November 2019 19:30 GMT bombastic bob
Edge on LINUX? *EW*
it seems to me that MS has no clue as to why people don't want to use their browser on Windows, let alone the reaction that will happen when they try to pawn it off for Linux users.
"Don't know what distros to support"
I have an idea: release the SOURCE, and if we want it, we'll build it and package it on OUR end. that would include the BSDs as well.
But, I expect that will NEVER happen. And that's the whole point.