new blog post blog.vulpine.solutions/blog/rust-is-good-just-not-for-me/
-
Noah Kennedyreplied to the foxes they warned you about :therian: last edited by
@sam as a longtime rust person...
yeah, this is totally fair and i think there's way too much of a "rust is universally the best programming language for anything" thing going on generally
i also think this is also reflected in a lot of the things people are asking for rust to introduce as well - what a lot of people want is really just a version of rust which fundamentally isn't a systems programming language and just carries over the nice type system
-
the foxes they warned you about :therian:replied to Noah Kennedy last edited by
@noah yeah. i've also heard people who do want a systems programming language complain that rust isn't low level enough sometimes. seems like these two conflicting groups are making the language (ever so slightly) worse for everyone
i wonder if a rust-like language that doesn't focus on performance as much, but keeps the syntax and type system, could ever take off like using a runtime for memory management instead of a borrow checker/manual management
gleam comes close to that but because it runs on the BEAM it's closer to erlang/elixir than rust in terms of functionality -
Noah Kennedyreplied to the foxes they warned you about :therian: last edited by
@sam honestly for systems programming i would say it's pretty much at the level i want it
do i want more low-level stuff, like bitmap syntax? of course i do, but i think it's way better than c++ for anything i want to do anyways and i have no desire to go back to c++ anytime soon
i kinda just want it to stay focused on systems programming because folks like me don't really have any other options here that actually hold up
and i also want to see a non-rust rust for everyone else like you said
-
@sam horrible way to put it, but something like go with a built in tokio-type runtime, garbage collection, and batteries-included stdlib
just not go's type system lol
-
the foxes they warned you about :therian:replied to Noah Kennedy last edited by
@noah go but without its type system and without its syntax, those are its two biggest weaknesses imo. rust has error handling down pretty well. go, despite having a similar system (errors are values and passed between functions like normal returns) doesn't have any of the syntax to support it and make it ergonomic to use
-
Noah Kennedyreplied to the foxes they warned you about :therian: last edited by
@sam the main thing i think go does well is its runtime
it's stdlib has some nice stuff too, but the language itself, sheesh
-
the foxes they warned you about :therian:replied to Noah Kennedy last edited by
@noah yeah, the runtime and the standard library are its biggest strengths. especially the standard library, it's really nice how you can feasibly make a full web app with only one external dependency (the database driver. not the database interface, that's in the standard library, just the part that communicates with the specific software)
hell, most larger projects will at least use a third-party router, but everything still conforms to the standard library's api so they're pretty interchangeable (i can use a go-chi middleware with the standard library and vice versa, for example)
this isn't something we've experienced with any other language, even python lacks some essential features once your program becomes more complicated than "this could be a bash script" -
Noah Kennedyreplied to the foxes they warned you about :therian: last edited by
@sam this is honestly what i liked about go when i used to use it, and one of the main changes i would love to see in a "rust for non-systems programmers"
ideally you'd also somehow have native-feeling rust ffi, but i don't know how to make that work (but i am not a proglang person and maybe people who are have figured stuff out here)
i think tokio would fit perfectly for the built-in async runtime here
-
kouhai, reliability officerreplied to Noah Kennedy last edited by
-
