Rune IDE goes open source under GPLv3 with a revenue-sharing contributor program
Rune is now open source
Unstable Build has open-sourced its Go-based Rune IDE under GPLv3, keeping contributor copyright intact and launching a novel program that shares service revenue with contributors via an auditable ledger. Rune's terminal, initially nearly 100x slower than Rust and Zig terminals, was tuned to competitive performance through algorithmic improvements and goroutine balancing, proving Go can deliver both speed and iteration velocity.
The company should not gain special rights from contributors while keeping all of the economic upside for itself.
- _hao
For a brief moment I thought this is about the game Rune[1] and got excited as I have played that a lot when growing up. Alas, that wasn’t it.
- rao-v
I like the idea of making it trivial to work across multiple machines but I’d really prefer not to have to trust your coordination server and encryption approach etc.
Could this (optionally) just run over Tailscale (I suppose ssh is always an option)
- threecheese
You mentioned “it’s like driving a new car” in another thread; I tried Rune in an earlier incarnation, and it was more drastic than a new car. I’m a vim user, and so enabled the Vim option in onboarding - that was a big mistake, because I literally could not do anything without using vim motions. I felt like a helpless noob on my first unix, how-do-I-exit-this-dam-text-editor.
I realized that your onboarding was also training, and that I could not do anything with Rune without going through that training, and so I immediately exited and uninstalled. The friction was much too much.
I’m not sure if the onboarding is still like that :) If it is, my feedback would be have much much lower friction to try (or warnings for those who claim to use vim :).
- _bent
> we will give participating contributors a contractual right to share in the revenue generated by Rune, directly or indirectly.
this sounds like a terrible idea.
the only incentive to contribute to your project should be to fix a bug or contribute a feature upstream you yourself need.
consider the fallout of Hacktoberfest, 'Tide' or the ai produced PR spam for social clout on GitHub as of today and then imagine what happens if someone provides a direct financial incentive to do it.
- ramon156
Lovely write-up! Will take a look at rune as an alternative to my Zed setup.
Not because I dislike Zed, I'm just addicted to trying out IDEs :)