77 karma · joined September 30, 2013
That’s actually one reason why I don’t think it’s current incarnation is a good fit for learning new apis, it’s been trained on a lot of code, not all of it good.
Seems like something a future version might be able to fix, perhaps by training a new layer using just demonstrably ‘good’ code?
I've got a sneaking suspicion that this is what we'll be doing in the future, I see Copilot as a taste of what future compilers will be like.
In a few years I expect to have most of an application built by an AI, with me developing the business/core logic by hand.
The way I see this, GitHub Copilot and the like are true next-gen compilers, translating English into code. They'll only get better with time.
> One challenge researchers should consider is that as capabilities improve, it may become increasingly difficult to guard against “automation bias.”
I fear hordes of inexperienced developers, mindlessly clicking accept on the first suggestion, and then on the second, third, and so on, until one seems to work. And the more advanced tools like this get, the harder it'll be to review the code and make sure nothing's messed up.
I guess we'll have to think long and hard about what safeguards to build against these risks.
2 - the platform is not stagnant, be it Windows or .NET - new things are coming out;
3 - there is a proper direction, less towards Windows/Office as desktop apps and more towards services;
5 - the updates do happen more often, and at least for .NET they're done in a transparent way (being open source and all)
Same thing as with Instagram.
The fact that they can spend so much money on this (and that their investors allow it) shows just how much they want to remain on top.