I'm making an app with a Typescript+React front end and a Go back end. While in local development, I serve it with Vite. Could I use Deno in place of Vite+Node?
How we built JSR
31–40 of 41 posts
Re: How we built JSR
#32> The JSR API server is written in Rust, using the Hyper HTTP server. It communicates with the Postgres database via the sqlx Rust crate.
Looks like most of the backend is written in Rust. Must be a bummer working on a JS runtime, and not being able to test it out at such a scale.
Re: How we built JSR
#33> We use the excellent sqlx Rust package to handle migrations. > The JSR API server is written in Rust, using the Hyper HTTP server. It communicates with the Postgres database via the sqlx Rust crate. Looks like most of the backend is written in Rust. Must be a bummer working on a JS runtime, and not being able to test it out at such a scale.
Re: How we built JSR
#34Earlier quoted context omitted.
The Javascript and Python ecosystems, somewhat ironically, have begun using rust for their tooling, because the actual language is too slow. Aside though: IMO python is good as "glue" between low level code. JS... I don't know man.
My dream language/environment would be something that is ubiquitous, has a straight-forward learning curve, has a REPL, and empowers dev productivity - like python - but then, if i should choose, there would be an additional straight-forward path for me to push my code thhough some compilation process in order to supercharge the performance/speed of my code - like Go or Rust, etc...Basically let me choose to employ m…
Re: How we built JSR
#35Earlier quoted context omitted.
The Javascript and Python ecosystems, somewhat ironically, have begun using rust for their tooling, because the actual language is too slow. Aside though: IMO python is good as "glue" between low level code. JS... I don't know man.
My dream language/environment would be something that is ubiquitous, has a straight-forward learning curve, has a REPL, and empowers dev productivity - like python - but then, if i should choose, there would be an additional straight-forward path for me to push my code thhough some compilation process in order to supercharge the performance/speed of my code - like Go or Rust, etc...Basically let me choose to employ m…
Re: How we built JSR
#36Earlier quoted context omitted.
My dream language/environment would be something that is ubiquitous, has a straight-forward learning curve, has a REPL, and empowers dev productivity - like python - but then, if i should choose, there would be an additional straight-forward path for me to push my code thhough some compilation process in order to supercharge the performance/speed of my code - like Go or Rust, etc...Basically let me choose to employ m…
Clojure is probably closest to that right now.
Re: How we built JSR
#37Earlier quoted context omitted.
My dream language/environment would be something that is ubiquitous, has a straight-forward learning curve, has a REPL, and empowers dev productivity - like python - but then, if i should choose, there would be an additional straight-forward path for me to push my code thhough some compilation process in order to supercharge the performance/speed of my code - like Go or Rust, etc...Basically let me choose to employ m…
That's Java. You can work in the REPL, and when you put your code in a file and launch it it runs fast; very fast.
Re: How we built JSR
#38Earlier quoted context omitted.
My dream language/environment would be something that is ubiquitous, has a straight-forward learning curve, has a REPL, and empowers dev productivity - like python - but then, if i should choose, there would be an additional straight-forward path for me to push my code thhough some compilation process in order to supercharge the performance/speed of my code - like Go or Rust, etc...Basically let me choose to employ m…
I believe this is essentially the goal of Mojo [0][1], at least for ML/AI development. [0] https://www.modular.com/max/mojo [1] https://news.ycombinator.com/item?id=35790367
Re: How we built JSR
#39Earlier quoted context omitted.
The Javascript and Python ecosystems, somewhat ironically, have begun using rust for their tooling, because the actual language is too slow. Aside though: IMO python is good as "glue" between low level code. JS... I don't know man.
My dream language/environment would be something that is ubiquitous, has a straight-forward learning curve, has a REPL, and empowers dev productivity - like python - but then, if i should choose, there would be an additional straight-forward path for me to push my code thhough some compilation process in order to supercharge the performance/speed of my code - like Go or Rust, etc...Basically let me choose to employ m…
Scala has its own downsides tho. It is a "big" language in the sense that because it tries to do everything, there are too many ways to do one things.
Re: How we built JSR
#40Earlier quoted context omitted.
That's Java. You can work in the REPL, and when you put your code in a file and launch it it runs fast; very fast.
I can't deny the performance and scalability of Java. But I've never been a fan of the need to be so verbose when coding for it. Also my memory of Java is from the late 90s...so maybe I'm missing something but I can't recall there ever being a REPL in Java. So I guess TIL :-)