Our great sponsors
-
Nim
Nim is a statically typed compiled systems programming language. It combines successful concepts from mature languages like Python, Ada and Modula. Its design focuses on efficiency, expressiveness, and elegance (in that order of priority).
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
Prisma
Next-generation ORM for Node.js & TypeScript | PostgreSQL, MySQL, MariaDB, SQL Server, SQLite, MongoDB and CockroachDB
-
ref-eRp-FD-Server
Discontinued ARCHIVED - This project acts as reference implementation of main aspects of an e-prescription server designed by gematik.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
goth
Package goth provides a simple, clean, and idiomatic way to write authentication packages for Go web applications.
That would much rather be https://nim-lang.org/
Another would be prisma, an ORM where the core engine is written in Rust.
Another place it's getting common is in developer tooling where correctness and performance are priorities. Some examples are Ruby's JIT compiler, a JS/TS compiler/bundler, or even more ambitious (incomplete) tooling for all linting/formatting/bundling for JS/TS.
There's a bunch, exposing a Rust library to Python is straightforward with PyO3 and to Node with napi. One example is Polars, a dataframe library (an alternative to pandas).
Found it: https://github.com/gematik/ref-eRp-FD-Server
For the kind of websites I prefer to build -- server side rendered with HTMX/Alpine for the extra niceness -- Rust I think could be a very good fit. The main downside for my personal projects is the ecosystem. E.g., a good standard way to handle CSRF tokens, standardised oauth2 implementations (like https://github.com/markbates/goth in Go), things like that. I found myself having to write a lot of code that just exists in the Go ecosystem. The main downside for a business is that it's going to make it harder to hire, since Rust genuinely requires more skill. Yes, developers will make mistakes in Go, as it's far too easy to do things like access shared memory in dangerous ways. But on the flip side, it's a lot easier for them to deliver a feature. In a choice between shipping a feature that is buggy in hard to detect ways, vs not being able to deliver at all because you can't get developers, I think it's better to ship.
There's a new framework that automates prefetch and lazy loading, all without hydration. You can make an interactive app that's faster than some static sites with practically zero effort.
If you already know Rust making your backend with something like Rocket is a no brainer. More speed is always good and static types save dev time in the long run.