HN user

stmblast

65 karma

Full stack developer that works with Express/Node, React, Postgres/Mongo and Rust.

Posts11
Comments43
View on HN
[dead] 2 years ago

Hey HN!

We’ve just launched our new event for AoC-style Rust code challenges, Shuttle Christmas Code Hunt 2024. We’re looking forward to having you join us and get started on learning Rust for web development, as well as sharing your progress on our Discord server.

Happy hunting!

Probably LMMs (Large Multimodal Models) maybe?

I am not entirely sure if this'll be the future, but having one model that has relatively good performance over a huge range of types of data feels pretty good tbh

Interesting article!

Do you think Mintlify could be a viable choice if and when it supports OpenAPI more comprehensively? Currently, my company uses Mintlify and I find it to be suitable for purpose but in the future, we may end up using OpenAPI.

Not a SWE - I'm a WFH DevRel Eng who is starting to get back pain.

I work on the sofa and my colleagues are urging me to get a proper office chair, but I don't really want to because my living space is tiny and I intend to move out soon (3-4 months ish).

You cut down a chunk of tests by not needing to figure out what type something is. You can also use assert! and assert_eq! in your main code without even using tests which also cuts down on tests, where applicable.

You can also write unit tests in the same files as your main code. Eventually you'll want some kind of test suite when your codebase gets big enough, but it works well enough that you don't need to if you don't want to (for a small codebase).

Frameworks like Axum also of course support testing - for instance this crate lets you quickly mock up your server without having to do much: https://docs.rs/axum-test/latest/axum_test/

This is likely just a me problem, but I always found Jest extremely annoying to set up with React and TypeScript - particularly with attempting to follow the documentation for jest and then failing spectacularly (in spite of using React Testing Library, jsdom + jest).

Cypress on the other hand I found to be really, really good

Totally agree with this.

I can spin up a generic Axum backend service within probably about half an hour to an hour that contains most of the things I need (auth, CRUD, similar things) once I know what I need, configuration and business logic depending. I think the key phrasing is primarily "when you're familiar with Rust" - if you're not familiar, then it will definitely be a slog.

Certain things that would require you to manually implement a complex trait (for example, Send + Sync + 'static plus whatever else) would probably slow you down though, but presumably by that time you probably already know what you're doing.

Definitely! I remember my first thoughts when moving from Next.js 13 to using a HTML templating engine were "wow, this is much simpler" and "should've done this sooner". It's saved me quite a lot of time in terms of not having to think about props/SSR

Here's to hoping Rust's ecosystem becomes more stable in the future!

I'm very much looking forward to things like generators/coroutines (or whatever they're called now) once they're made stable as well as async traits and whatever makes the Pavex framework able to be used on stable Rust.

It depends, but typically you wouldn't keep a page open long enough to be able to do this.

If you were, you could probably use an SSE stream that maps to humanised time and then send an event every second. However, I'm not sure this is 100% optimal as it requires an update every second which is probably more overhead than you want.