@jukan05@burkeholland As a result, other options get adopted. While waiting, we explored and added Cursor and Codex to the toolset. Personally, I think Copilot CLI is under-rated - but the playing-catch-up has taken a hit, in my opinion.
@jukan05@burkeholland IME it's suffered in part with playing catch-up, and in-part the mixed picture of what features are available in which IDE (VS has been painful vs VS Code). All the while, others were shipping and shipping. Copilot CLI took an age (relatively!) to go GA too.
Yeah, I could switch out to VS Code for Copilot and then back to VS. But would be great to have better first class support in VS for the in-IDE experience. I'm increasingly switching out to Codex CLI, which is working very well. Keen to make use of Copilot CLI once it goes GA
Biggest barrier I personally see to further adoption of GitHub Copilot is how far behind the experience and supported feature-set feels in Visual Studio compared to VSCode, Cursor etc. And combined with Copilot CLI being in Preview, it shifts attention elsewhere.
@DevLeaderCa@mkristensen This. Release cadence has improved, but VS feels so far behind with AI features. And often hangs during tool calling when e.g. running scripts.
@mjovanovictech SqlBulkCopy is a great approach - been my go to for many years when I need high perf loading. You can get more throughout too, with tweaks like Table lock, loading to a heap table and parallel loads. Blogged about that here - 20 million rows in 12.3s: https://t.co/RPtphFXdxK
One of my biggest UX gripes with GitHub Copilot (in VS) is that you have to wait for the whole response to be generated before you can read it due to the auto-scrolling as the response streams in. Would be a big plus to be able to stop the auto-scroll!
@GergelyOrosz This frustrated me recently too - ended up opening a separate browser, select the odd 1 seat temporarily to hold it, then choose the other seats I wanted back in my main session.
@mark_heath Not yet - closest thing to that I've done is to migrate .NET unit test projects away from FluentAssertions to native asserts (or in theory Shouldly). Handled over 95% of the migration
@mkristensen Never felt the pressing need. However, now it's much more noticeable with GH Copilot having to wait for features.
But, this would be the main blocker:
@rakyll Availability and ease of acquiring model quota (PAYG), within Europe. Especially for new models.
Without doubt, this is THE biggest challenge I've faced (on Azure OpenAI and AWS Bedrock - am currently onboarding Vertex AI atm).