kilocode VS vscode-dotnettools

I've been a software developer for over 8 years and recently started using AI to help me code.

The OSS project I'm currently working on (Kilo Code [1]) basically also attracts the same type of people: People with software dev. experience who like to use AI to help them do things they already know, just faster.

They also don't want to be called "vibe coders". A few days ago, I created a question on a subreddit called "ChatGPTCoding" (which you'd expect to be filled with "vibe coders")[2], asking people if they do "vibe coding" or "AI assisted coding".

Surprisingly, almost NOBODY replies that they do "vibe coding". One guy described vibe coding as "using AI while not having a clue what you're doing."

Am I the only one who wants to be using AI to help me code/design/etc., but I don't want to put under the umbrella of a "vibe coder"?

If yes, is there a better phrase to distinguish ourselves from the "vibe" folks out there?

[1] https://github.com/Kilo-Org/kilocode

I learned about your project from your comment on the Windsurf post but wanted to suggest that you plug your URL anytime you plug the project since it can make the difference between someone "adding it to their eventual list" versus "open in new tab, read, enjoy, engage"

https://github.com/Kilo-Org/kilocode#-kilo-code (Apache 2)

It's open source: https://github.com/Kilo-Org/kilocode, so they are giving back.

Exactly. From: [0]

> I know it works as intended. Just curios why Microsoft decided to enforce this all of a sudden.

> Did GitHub Copilot just give up on playing fair with Cursor, admitting it's winning?

The game wasn't 'fair' to begin with and it was rigged for Microsoft to win anyway. (Cursor being based on VS Code).

If you're competing against Microsoft, expect them to race you to zero for years and at close to no cost for them.

It is all for Cursor to lose if they continue as they are.

[0] https://github.com/microsoft/vscode-dotnettools/issues/1909#...

Compared to what? To visual studio? It's bad. To rider? It's bad.

To using a potato? It's pretty good!

Seriously though, if you want an honest answer: It's bad... but, they're now investing in making it better (1), and it better than I was a year ago.

Expect to see more improvements in this space.

..but like, yeah. Right now, it kind of still sucks if you're working in C# full time, compared to the serious alternatives. You can see common themes on the issue tracker (2), if you want a less anecdotal response, or perhaps dig through a couple of the juicy threads (3), that give you sense of the state of play right now.

tldr; watch this space; if you're already heavily invested vscode, give it a whirl... but, if you're using a mostly-c# code base, you probably won't want to have it as your primary editor right now.

[1] - https://devblogs.microsoft.com/visualstudio/announcing-cshar...

[2] - https://github.com/microsoft/vscode-dotnettools/issues

[3] - https://github.com/microsoft/vscode-dotnettools/issues/329

possibly https://github.com/microsoft/vscode-dotnettools/issues/120

Looks like a known issue having something to do with spaces in paths, and reported here: https://github.com/microsoft/vscode-dotnettools/issues/59