3 ms·

"This openness allows users to avoid a vendor-lock in for their development tooling, which is tremendously important.." I would question if you really do have

"This openness allows users to avoid a vendor-lock in for their development tooling, which is tremendously important.." I would question if you really do have vendor lock-in with an IDE, as usually the hardest thing about switching IDEs is learning the new keystrokes.

viraptor 2y ago
Between the vs-only extensions, vs-only Live share, and vs-only adapters to AIs, we're actually in the age of pretty strong vendor lock in, if you're invested in some features. Add some less common task management integration or review system, and the vendor lock in may be close to company-wide.
- freedomben 2y ago
  Exactly. Being a vim or emacs user these days is quite the upstream swim. Everything is made for VS code, and it's actually affecting productivity. In the past it was more of a personal preference, but that is becoming less true. That said, they'll have to take vim from my cold dead fingers if they want me to stop :-)
constantcrying 2y ago
Have you ever done embedded development? Usually you get shipped a more or less broken piece of IDE, which is the only supported way (meaning the only way you are allowed to use) to develop for the embedded hardware. I think most people are missing who this is for and what problem it is trying to solve.
- cassianoleal 2y ago
  > I think most people are missing who this is for and what problem it is trying to solve. I certainly am. Care to enlighten me?
  - constantcrying 2y ago
    As I wrote in my post, if you are working in embedded you will get an IDE from the chip manufacturer, which is the only real way to develop software for that chip. Generally those IDEs are not particularly good, as they are some hacked together toolkits based on some more or less flexible existing IDE. What Theia wants to accomplish is allowing chip manufacturers to build an IDE based on a flexible platform, with good extension support. More or less Theia isn't for you and it doesn't really try to compete with VSCode.
    - cassianoleal 2y ago
      Thank you, that’s very helpful!
  - daelon 2y ago
    He literally just said it.

viraptor 2y ago

Between the vs-only extensions, vs-only Live share, and vs-only adapters to AIs, we're actually in the age of pretty strong vendor lock in, if you're invested in some features. Add some less common task management integration or review system, and the vendor lock in may be close to company-wide.

freedomben 2y ago
Exactly. Being a vim or emacs user these days is quite the upstream swim. Everything is made for VS code, and it's actually affecting productivity. In the past it was more of a personal preference, but that is becoming less true. That said, they'll have to take vim from my cold dead fingers if they want me to stop :-)

constantcrying 2y ago

Have you ever done embedded development? Usually you get shipped a more or less broken piece of IDE, which is the only supported way (meaning the only way you are allowed to use) to develop for the embedded hardware. I think most people are missing who this is for and what problem it is trying to solve.

cassianoleal 2y ago
> I think most people are missing who this is for and what problem it is trying to solve. I certainly am. Care to enlighten me?
- constantcrying 2y ago
  As I wrote in my post, if you are working in embedded you will get an IDE from the chip manufacturer, which is the only real way to develop software for that chip. Generally those IDEs are not particularly good, as they are some hacked together toolkits based on some more or less flexible existing IDE. What Theia wants to accomplish is allowing chip manufacturers to build an IDE based on a flexible platform, with good extension support. More or less Theia isn't for you and it doesn't really try to compete with VSCode.
  - cassianoleal 2y ago
    Thank you, that’s very helpful!
- daelon 2y ago
  He literally just said it.