I tried it but I too felt it was clunky for the above reasons (3 being the fatal one). In addition:

• can't use it on a cluster that autoterminates/actually had to have a dedicated cluster for each user I believe
• the login process for the open source version is bad (allowing one user and having to share the credentials)
• persisting the workspace at all is a pain

All of this work is to avoid using a notebook that is tightly integrated with databricks. The reward isn't worth the effort.

@Jonathan Dufault​ Thanks for the response, and glad I'm not alone. My problem (and this is probably just a preference thing) is that the 'reward' of using a full-fledged IDE is huge, compared to bouncing between notebooks in multiple tabs. The integrations are all (mostly?) Databricks specific and my team hasn't fully committed yet to try and keep some platform independence so we're not getting much benefit there.

There's a submitted idea on the azure databricks feedback page https://feedback.azure.com/d365community/idea/4a538c5f-f124-ec11-b6e6-000d3a4f0da0 if you wanted to upvote.

wow ... the idea was submitted 4 years ago 😞 i guess i won't get my hopes up for a quick change