4 ms·
Nowadays when I see "written in Rust" in the title, it reads like special pleading: "It's maybe not as good as what you use, but we are really proud to have got
by ncmncm 5y ago
Nowadays when I see "written in Rust" in the title, it reads like special pleading: "It's maybe not as good as what you use, but we are really proud to have got it working at all."
- omniscient_oce 5y agoAt least they went with "lighting-fast" instead of "blazing-fast"
- chrismorgan 5y ago“Lightning fast” is no less meaningless in practice than “blazing fast”. Both get used extensively by projects in such languages as JavaScript and Rust, on projects of similar scope that nonetheless have at least an order or two of magnitude’s performance difference.
- randomsearch 5y agoVite is a tool that deserves this moniker
- ncmncm 5y agoWhat would one use Vite in place of?
- randomsearch 5y agowebpack
- ncmncm 5y agoIf the title claims "lightning fast" or "blazing fast", I expect to see quantitative comparisons to alternatives. Which operations are faster than in other programs? alacritty is a Rust program that is promoted as uniquely fast, but is substantially slower than (e.g.) kitty.
- infinitezest 5y agoI myself only use software that is "made with <3"
- ASalazarMX 5y agoI still prefer it to the "performant and beautiful" Electron made famous. almost all of the applications that said that were neither performant or beautiful, unless you found web pages and their quirks more beautiful than native GUIs.
- gyulai 5y agoI think that's a perfectly valid appeal to altruism in a tech-savvy audience. It makes sense to take a hit on your individual needs and wants as a user in the short term, if it helps with keeping the tech ecosystem which we collectively inhabit healthy in the long term. Free market forces based on individual self-interest have proven to be really bad at doing that, so altruism is needed to fill the gap. ...by that logic, I prefer software written in Rust to software written in C++ or Java Script even if it's worse from a user perspective, as long as it's tolerably worse rather than just unusable.
- hgomersall 5y agoReally? I take it to mean "fast and won't randomly segfault".
- mhh__ 5y agoThat should really apply to any systems language other than C for a text editor. As long as you have bounds checking and a test suite you're golden.
- shakow 5y ago> As long as you have bounds checking and a test suite you're golden. And other hilarious jokes you can tell yourself
- mhh__ 5y agoI wouldn't recommend such a simple approach for something like a compiler, but for a text editor I don't think it's unreasonable. How many allocations can it actually need within any given subsystem which you can test individually?
- mburee 5y agoI can't remember the last time any C tool segfaulted on me
- lifty 5y agoWhich one is that?
- tekknik 5y agoSublime text is written in C, and before VSCode it was arguably the most popular editor on the planet.
- jstx1 5y agoAaand "written in Rust" got removed from the title.
- Findecanor 5y agoI take it as a declaration about the author: that he knows Rust now and can be hired to write Rust.
- playcache 5y agoI think 'safe'
- tekknik 5y agoWhat makes you think rust is more safe? The platform itself it’s flawed, so any language running on the platform is also flawed. Load a rust program into mem, change mem, run rust program. You’ve just lost safety.
- _fat_santa 5y agoThe same reason "native MacOS app" is a selling point, it's all Electron's fault (only half kidding here). For the tech savvy crowd, we care about stuff like this because we don't need another electron app hogging memory on our systems. Personally for me "written in rust" translates to "I care about performance" and "I care about my app not hogging your system memory"
- switchbak 5y agoI moreso see this as "Written by someone who's quite concerned about runtime performance and efficiency". Ripgrep has completely upended my expectations (in a good way) for what modern machines are capable of. I'm all for OCD perfectionism if it means the performance I dreamed of in the 90's in finally realized.
- petr_tik 5y ago> we are really proud to have got it working at all On the contrary, the rust crate ecosystem and tooling means a lone developer can compose specialised libraries to produce a working artefact that scratches her own itch. Such productivity is the opposite of getting something working at all. Trying to build an OSS cpp project or even worse, use an OSS Cpp library in your own project is more along the lines of "getting something working at all". Every third-party and some enterprise-internal Cpp libraries require one answers the following questions: - how do I build the damn thing? - how do I run the tests? - how do I use the library? Vendor into the repo? apt install? - what APIs does the system/library provide? - where can I find the documentation and examples? - how do I set up code completion? - how do I know am using the library interface correctly? - how do I know I didn't violate any invariants/safety guarantees? Compare with the list of dependencies across the Cargo workspace members. https://github.com/lapce/lapce/blob/master/lapce-core/Cargo.toml#L8-L16 https://github.com/lapce/lapce/blob/master/lapce-core/Cargo.... https://github.com/lapce/lapce/blob/master/lapce-ui/Cargo.toml#L8-L62 https://github.com/lapce/lapce/blob/master/lapce-ui/Cargo.to... https://github.com/lapce/lapce/blob/master/lapce-rpc/Cargo.toml#L8-L13 https://github.com/lapce/lapce/blob/master/lapce-rpc/Cargo.t... The cost of adding a new rust dependency when measured by the number of questions you need to answer beforehand is nearly constant. This means a layman can be more productive in rust.
- ncmncm 5y ago
- ncmncm 5y agoCorrect use, documentation, and other concerns are imporant for all libraries, whether got via cargo or otherwise, so this amounts to special pleading again. More importantly, though: how hard is it to use a library coded in C++ from your Rust program? You have to make and maintain some sort of shim layer. Even a C library needs some such effort. For any given need, you are much less likely to find an existing and suitable Rust library already written, released, and maintained than one in some other, more widely used, language.
- follower 5y ago
- dingoegret12 5y agoI don't understand this sentiment. Rust is the only language ecosystem where I find that anything works at all. Whenever I have to build something not built in rust, I'm praying. With rust made tooling, I just never have problems.
- tekknik 5y agoHave you tried go at all?
- ncmncm 5y agoI don't know of any essential tool coded in Rust. Literally every single thing I rely on is coded in other some other language, and works. There is exactly one in Haskell: pandoc. No Java or C# (although I guess some people feel they need Minecraft or Kerbal Space Program). No Lisp, except Emacs. No Erlang, Clojure, Scala, OCaml, Dart, or Ada. Does TeX still count as Pascal? The only case I know of where I would need a Rust program is to check a blake3 hash. That won't last.
- nooorofe 5y ago> No Java I am not sure what "essential tool" means if pandoc included in it. For me Intellij, Eclipse, Dbeaver are more essential (+ few other Specific tools based on Eclipse). C# - I am not sure, MS Office?
- ncmncm 5y agoI acknowledge that some people depend on Java and even C# programs.
- MrJohz 5y agoRipgrep is my essential codebase search tool. It's incredibly fast, very clear, and it just works how I expect. I use it a lot if I'm refactoring a larger codebase, particularly because it works well for more dynamic languages (where a compiler won't help) and for comments and documentation (where I want the naming to remain consistent). I've heard good things about Bat and Exa - I personally have never felt a huge need for them, but other people claim that they're pretty essential to them.