premun
It also predicts comments and logging messages amazingly well (you type "logger." add 7/10 times get what you want, sometimes even better), incorporating variables from the context around. This speeds up the tedious parts of programming when you are finalizing the code (adding docs + tracing).
Honestly, Copilot saves me so much time every week while turning chores into a really fun time.
Aside the apparent advantages of the strong typed environment, I was able to bake in many more features that make your life easier. Code reuse is also super easy.
.NET Announcing a Monorepo
[0] https://github.com/omnisharp/omnisharp-vscode/issues/5276#is...
Disclaimer: I am a Microsoft employee and this is my opinion only but I say this because I know what it's like to work on apps used by tens of millions of people and I can tell you that you're dead in the water when you have no idea how people use your product. And no, at this scale, controlled user testing is not sufficient. I've worked on countless Microsoft products over the years from Office through Skype to Teams. I've also been personally adding some telemetry into these but ALWAYS to be data driven when making product decisions such as "which button should we display here", "did we improve latency/stability/discoverability/.." and "which new feature will be actually useful".
Now.. I don't know VS Code 100% but I did see some internal talks, have access to some telemetry (didn't browse it much) and I can say that the team is full of good intentions. They just deal with difficult UX problems. I've also worked at Google and I think it's much different when your product/business is using/selling data about customers as compared to creating tools for developers. You are after a very different type of data in essence and I think the actual privacy is not contended here.
I am sure people will spin this the usual way "big company big bad" and "you never know what they will try to collect next" but in that case, I can only suggest you get a job in one of these companies and see how you will develop anything without real data to back your decisions and assumptions about the real world.
I would personally think next ones would be non NATO or non EU countries like Moldova. Then countries that are on Russia's list up high like Lithuania.
I guess no one says that's the way you want to maintain the project. The final `index.php` with HTML/CSS/JS can just be built out of parts that can be maintained separately.
Sharpliner – Use C# to define Azure DevOps pipelines (instead of YAML)
But it gets worse. If you have only 1 window with some app open (browser, terminal..), and this window has two tabs inside, clicking on the taskbar icon representing this window won't bring the window up. It will first bring up these small previews above the taskbar for every tab that you then have to click again (pick any) and then finally you get the window brought up. This is horrible because when you have tabs side by side in the window (terminal example), it doesn't matter which tab you choose as the same window pops up showing both tabs anyway. However you have to click twice (or hover for a bit to get the previews and then click again).
Congratulations to "Windows" version where switching "windows" is painful.
FWIW, I'm a Microsoft employee (not in Windows org) and I complain about "never combine" in any feedback forms we get. Maybe it will make a difference somewhere. (opinions are my own)
In CodeFlow any comment is a floating object with a line connecting it to whatever selection it was created for and you can move it around as you like. You also can easily filter out visible comments by state, author, participation in them.. Features around comparing iterations, marking already reviewed files and similar are the same as far as I remember.
Another reason for my opinion might also be that CodeFlow is probably better optimized for large screens, but this might be caused by the weird Google standard of 80 column limit for source code which I will just never understand in the 21st century where everyone has 24" and up full HD to 4k screens.
I am comparing state of both from 2015 where I worked with both in the same year.
While we were starting the project we found ourselves trying to emulate class behaviour, inheritance, singleton patters etc. because it was natural for us and pretty much desired for that kind of project. There are many ways how to imitate such behaviour in JS but each and every one of them lacks some kind of a feature such as multiple inheritance or interface implementation to which you are accustomed to in modern OOP languages like C# for instance. We had a lot of trouble with prototypes and I think we never accomplished getting to a OOP pattern on 100%.
I am very excited about Poof because it gives me a lot of hope and I am quite sure we will invest in researching spoof (I just found out about it through HN). If it proves OK after several tests and delivers its all promises such as speed, I am quite sure we will be rewriting whole project under spoof style.
Of course that if you are using JS only in front-end web environment, there is no need for such a thing, but a framework like this is a big helper in a project like the one we are dealing with.