161–170 of 294 posts
Earlier quoted context omitted.
So, F# with NuGet/Fake, Scala or Kotlin with Maven/Gradle, OCaml with OPAM. Those points are hardly Rust specific and apply to any compiled language with ML influences.
These comments are still in context of using the language in a startup. Good luck with finding Ocaml, F# or Scala devs.
Earlier quoted context omitted.
Do you pine for the nice days of C/C++, when men were men and spend hours on debugging segmentation faults?
The myth of segmentation faults being hard needs to die. A fault is like an exception in Java (or a panic in Rust for that matter), only generated by hardware. It's the best case scenario for your buggy code. It's when you don't get a segfault, but your buggy code keeps chugging along, that's a problem. If after using an out-of-bounds index into an array I get a segfault instead of a memory corruption, I thank god fo…
Blog post is just rationalization for their choice. Rust is actually terrible choice for startups. It will take 2x more time to develop same thing than using something like TypeScript/Python and you will have much smaller and more expensive talent pool. Startups usually have to make, at least minimum viable, product quickly and start selling it before funds dry out. That means using familiar tech with big ecosystem.…
Earlier quoted context omitted.
I understand the comparison with C (the memory management) but I wonder how do you compare Rust to Java? What is it that makes you feel more confident in Rust compared to Java?
Java _used_ to give me that "it just works" feeling when I started using it... in 1999. The rich type system makes the biggest difference. In Rust, you can solve a problem by first modelling it through structs and enums and then define operations pertaining to elements of the model. rustc (the compiler) has such a grasp on the implications of a given model that it will most often guide you toward a near-optimal (and…
Other than checking mutability and nullness, I really don’t think that Rust would be that much ahead compared to even an “older” language like Java.
Also, java now has ADTs so “exhaustive checks” are available there as well.
Earlier quoted context omitted.
So, F# with NuGet/Fake, Scala or Kotlin with Maven/Gradle, OCaml with OPAM. Those points are hardly Rust specific and apply to any compiled language with ML influences.
From the official "Maven in 5 Minutes" tutorial: mvn archetype:generate -DgroupId=com.mycompany.app -DartifactId=my-app -DarchetypeArtifactId=maven-archetype-quickstart -DarchetypeVersion=1.4 -DinteractiveMode=false From the official Rust lang book, Cargo section: cargo new my-project I guess it's a matter of taste...
Earlier quoted context omitted.
So, F# with NuGet/Fake, Scala or Kotlin with Maven/Gradle, OCaml with OPAM. Those points are hardly Rust specific and apply to any compiled language with ML influences.
These comments are still in context of using the language in a startup. Good luck with finding Ocaml, F# or Scala devs.
Earlier quoted context omitted.
I'm doing some work on a friend's startup, and we have a pretty stark divide between our hot path gateway service and our lower traffic services. All three of our services are currently written in typescript with no plans to change, but I've earmarked the gateway as "maybe we'll rewrite it in Rust in three years." It's so small it's nearly trivial (so a rewrite of that specific service will be quickish) and infrequen…
> Not sure how a hybrid approach will work. The hybrid approach works great. We use typed scripting languages for business logic and Rust CLI tools for "inner loops", and this balance gives us the best of both worlds. There is an important caveat here: If you are already comfortable in Rust, then it's a fantastic tool for all sorts of things. But if you're just learning Rust, then there's a one-time cost for getting…
Rust is a great choice for startups because most startups fold and so will not need to try to find people who know how to maintain it.
Maintenance is where Rust really shines and makes up for it's initial learning curve and slightly slower writing speed. In terms of hiring I can't imagine it being a problem either. There are lots of developers who would jump at the chance to work with Rust, and comparatively few Rust jobs (especially ones that don't involve working with cryptocurrency).
Don’t get me wrong, Rust is a really great language, but if the domain doesn’t require low-level programming, don’t choose a low-level lang, in my opinion.
Earlier quoted context omitted.
Do you pine for the nice days of C/C++, when men were men and spend hours on debugging segmentation faults?
The myth of segmentation faults being hard needs to die. A fault is like an exception in Java (or a panic in Rust for that matter), only generated by hardware. It's the best case scenario for your buggy code. It's when you don't get a segfault, but your buggy code keeps chugging along, that's a problem. If after using an out-of-bounds index into an array I get a segfault instead of a memory corruption, I thank god fo…
It is extremely common to start diagnosing a segfault and find that the location of the segfault, in code, is unrelated to the code which caused the segfault.
Rust is a great choice for startups because most startups fold and so will not need to try to find people who know how to maintain it.
Maintenance is where Rust really shines and makes up for it's initial learning curve and slightly slower writing speed. In terms of hiring I can't imagine it being a problem either. There are lots of developers who would jump at the chance to work with Rust, and comparatively few Rust jobs (especially ones that don't involve working with cryptocurrency).