3 ms·

If they didn’t tell us it was built in Rust how would we ever know how smart the developers are?

by padjo 2y ago

michaelmior 2y ago
Personally, I appreciate knowing when something is written in Rust. I know it is very likely I can easily install it and try it out immediately and that it is likely faster than any non-native tool I'm currently using. However, I do find "based on Rust" instead of "written in Rust" to be an odd choice of terms.
- necovek 2y ago
  Just looking at their benchmarks, it's not particularly fast. es-build looks much better in benchmarks, but it's not written in Rust. It seems they wanted a tool in Rust just-because (experience on the team, preference foe the language...), and then only compared against those. As for the language "based on Rust", it's likely bad wording due to them not being native English speakers.
  - IshKebab 2y ago
    esbuild is written in Go, which has similar "probably quite fast and easy to install" properties to Rust. Compare that to the expected experience if it was written in C++ or JavaScript or Python or Java or ... All of those are either likely to be slow or painful to use.
    - nine_k 2y ago
      To be fair, you can package a modern Java app into a single executable [1], without the entire JRE shipped inside. Few people do that though. [1]: https://www.graalvm.org/latest/reference-manual/native-image/ https://www.graalvm.org/latest/reference-manual/native-image...
      - pas 2y ago
        A native executable includes only ... the language runtime, and ... How small is that compared to the JRE? Also I guess this means the program cannot load arbitrary classes?
      - michaelmior 2y ago
        One of the reasons few people do that is because the build process becomes much more complicated. It's also much more complicated to do any sort of dynamic loading which is not terribly uncommon.
jokethrowaway 2y ago
Yeah, that's how I ended up using prisma... until I realised they didn't have joins All this aside, knowing something is in Rust tells me: - It's fast - It's maintainable (imagine the same project but in C)
- hu3 2y ago
  prisma not having SQL JOINS for a ling time is how I know I should just ship it when it comes to my projects.
  - efilife 2y ago
    It's probably just me, but I read this sentence over 3 times and I still don't understand what you meant. Care to explain?
    - hu3 2y ago
      Sorry I could be much clearer. Was typing amidst cooking. I meant that Prisma got so much traction despite not supporting JOINs early on. And then there's me postponing projects because 80/20 doesn't cut it for me. I need to get each and every feature completed before launching.

If they didn’t tell us it was built in Rust how would we ever know how smart the developers are?

by padjo 2y ago

If they didn’t tell us it was built in Rust how would we ever know how smart the developers are?

Personally, I appreciate knowing when something is written in Rust. I know it is very likely I can easily install it and try it out immediately and that it is likely faster than any non-native tool I'm currently using. However, I do find "based on Rust" instead of "written in Rust" to be an odd choice of terms.

necovek 2y ago
Just looking at their benchmarks, it's not particularly fast. es-build looks much better in benchmarks, but it's not written in Rust. It seems they wanted a tool in Rust just-because (experience on the team, preference foe the language...), and then only compared against those. As for the language "based on Rust", it's likely bad wording due to them not being native English speakers.
- IshKebab 2y ago
  esbuild is written in Go, which has similar "probably quite fast and easy to install" properties to Rust. Compare that to the expected experience if it was written in C++ or JavaScript or Python or Java or ... All of those are either likely to be slow or painful to use.
  - nine_k 2y ago
    To be fair, you can package a modern Java app into a single executable [1], without the entire JRE shipped inside. Few people do that though. [1]: https://www.graalvm.org/latest/reference-manual/native-image/ https://www.graalvm.org/latest/reference-manual/native-image...
    - pas 2y ago
      A native executable includes only ... the language runtime, and ... How small is that compared to the JRE? Also I guess this means the program cannot load arbitrary classes?
    - michaelmior 2y ago
      One of the reasons few people do that is because the build process becomes much more complicated. It's also much more complicated to do any sort of dynamic loading which is not terribly uncommon.

jokethrowaway 2y ago

Yeah, that's how I ended up using prisma... until I realised they didn't have joins All this aside, knowing something is in Rust tells me: - It's fast - It's maintainable (imagine the same project but in C)

hu3 2y ago
prisma not having SQL JOINS for a ling time is how I know I should just ship it when it comes to my projects.
- efilife 2y ago
  It's probably just me, but I read this sentence over 3 times and I still don't understand what you meant. Care to explain?
  - hu3 2y ago
    Sorry I could be much clearer. Was typing amidst cooking. I meant that Prisma got so much traction despite not supporting JOINs early on. And then there's me postponing projects because 80/20 doesn't cut it for me. I need to get each and every feature completed before launching.