5 ms·
Interesting this is a google project. https://github.com/google/xi-editor/blob/master/rust/rope/src/rope.rs https://github.com/google/xi-editor/blob/master/rus
by educar 10y ago
Interesting this is a google project.
https://github.com/google/xi-editor/blob/master/rust/rope/src/rope.rs https://github.com/google/xi-editor/blob/master/rust/rope/sr... was quite interesting to read (for someone who has never looked into rust)
- retbull 10y agodoesn't s/he say at the bottom that this isn't a google project?
- raphlinus 10y agoIt's a project by a Googler (me), but it's a personal (20%) project, not an official Google one.
- namelezz 10y agoWhat's your thought of Rust? What dev env did you use?
- raphlinus 10y agoRust is working out very well so far. If you look at the rope implementation, you'll see that it's high level and mathematical almost like a functional language, but performance is first-class. I'm also very much looking forward to retrofitting parallelism using libraries such as Rayon and crossbeam. I'll probably write a retrospective when I'm farther into the project. My current development environment is just Sublime Text for the Rust parts, and Xcode for the parts written in Swift.
- wbond 10y agoIf you are using the recently-added default Rust syntax for Sublime Text and run into any issues, please let me know by filing an issue at https://github.com/sublimehq/Packages/issues https://github.com/sublimehq/Packages/issues.
- rudedogg 10y agoWhat made you decide to not write everything in Swift? Is it the lack of Windows support?
- geofft 10y agoIt seems Google has been releasing employees' personal projects at github.com/google if Google owns the copyright. (I'm not a Googler, so I don't know if this just applies to stuff you hack on while at work, or anything plausibly in Google's business interests that you do at home while you're an employee.)
- geofft 10y agoIt seems Google has been releasing employees' personal projects at github.com/google if Google owns the copyright. (I'm not a Googler, so I don't know if this just applies to stuff you hack on while at work, or anything plausibly in Google's business interests that you do at home while employed by Google.)
- skybrian 10y agoIf you don't care whether you own the copyright (just that it's open source), this is the easiest way to get permission.
- cyphar 10y agoThe issue with ditching the copyright is that you have no guarantee that they won't make a proprietary fork (if you use a copy left license). But if you don't care about the copyright you almost certainly don't care about ensuring the perpetual freedom of users.
- burntsushi 10y ago> But if you don't care about the copyright you almost certainly don't care about ensuring the perpetual freedom of users. That's ridiculous. If I release something into the public domain, then it is forever in the public domain and is perpetually free to use by anyone.
- cyphar 10y agoIgnoring the issues with public domain (that it doesn't exist in many places, so the default you-cant-do-anything copyright rules apply), you misunderstand what I mean by freedom in perpetuity. If someone can take your code and make it proprietary (as well as adding some enticing features), your code is now used to take away users freedom -- even though your original code was free software. Copyleft is the only defence against that form of attack on user freedom -- attack by distribution.