Hi just to confirm as I cannot find anything related to security or your use of using submitted code for training purposes. Where is your security policies with regards to that.

Neither of them are official which is often a non starter for some large enterprise customers.

One of the most critical aspects a Lakehouse is protecting data for security and compliance reasons and this article completely just glosses over it which makes me really uncomfortable.

They literally have that it is called Junie and after comparing cursor to it we settled for Junie as it does a good job with rust unlike cursor.

I just wanted to make a tool to help developers. Then when the SaaS launched they instead focused on adding $$$ features instead of fixing bugs, and started heavily pushing their SaaS anytime you used the tool.

They ended up switching to a terrible model with a previous release where if you were a business or in anyway making money you now needed to pay for licenses and it was comically expensive.

The reality is I could have forked it but I don't have the time and patience to deal with everything that comes from a massive project.