[A. B. Carroll]
Theia is great. And it’s going to eventually be the greatest, I’m absolutely sure of it.
However, right now it’s still very unfriendly in my experience. Even for a developer. I’ve never implemented it in an organization but I’ve been trying to and wanting to switch from IntelliJ (aka PHPStorm+WebStorm+so on) to Theia.
Specifically, with a built-in full service, full spectrum development environment running on a remote system. This way I can just keep my data on AWS, Azure, and whatever… If I need to run a test using 500 CPUs, it just costs a few pennies. If I need to do something development wise that would save me an hour of time to use a machine with 64 cpus and 300GB of memory, … everything is already there waiting in the cloud infrastructure, and it costs a few pennies which is well worth it.
Right now, I am running my personal instance kind of split between Vultr and AWS. Vultr, because I personally am able to get <10ms latency to their Chicago DC. So I connect into Vultr, but have my bulk of data sitting on AWS. That way I can talk to the server with the lowest latency, but get the best price on storing data. For AWS, … spot instances are crazy cheap. Azure has similar which are similarly crazy cheap. Theia runs fine on all of this, of course.
What’s been difficult for me so far is
Getting used to things!
Missing features from IntelliJ. Honestly, Theia has 90%+ of the features for most languages. Quite easily. But, it’s the small things that saved me time that I miss. Example, just being able to write out a lot of PHP class boilerplate (the members, getters, setters, constructor args, etc).
But, this is of course what makes Theia so great. I’ll hopefully find time to write them in myself, … Opensource it maybe and brighten someone else’s day.
Not using VSCode … I know this sounds silly … But there are a FEW things VSCode still is beating Theia at. But see previous statement.
The community is still small right now. People still don’t quite get it… Yet. Keep spreading the name. Luckily, because of the compatibility, this is less of an issue, … However if you need something “Theia specific”, and it’s not something that would be covered by documentation and you just “need to ask someone”, … it can sometimes be hard to find someone. It can be hard to find answers to questions asked via google. Again, this will improve.
Consistency … Again, I’m actually really trying to change this by making a “Standard Theia Distribution” of my own. I haven’t OSS’d it yet, but perhaps I should soon. Think of theia-full on steroids.
ABOVE ALL … Confusion … Gitpod, VSCode, Code Server? … Theia! … No, wait, what’s Che? … Should I be using Che, or Theia or VSCode or !!! … This is got me in the beginning. It looks like you’re already past this, perhaps. I still get confused quite a bit from time to time.
PS there is a lot of criticism here. I don’t mean this in a harmful way. Thanks to everyone who makes this great piece of software.