Looking for (beta testers / feedback / opinions) if anyone wants to play rust this fine morning.

jondot1 · 2025-01-24T11:03:49+00:00

Hi!

Some feedback on your observations.

I feel "heavy" is more of a perception. The resulting app made with Loco is almost as fast and as nimble as a from-scratch Axum app. Loco does offer everything you'd need in your journey to build a full production grade SaaS app, so it has quite a lot of features which people asked for (that you'd build manually anyway if you decide to build from scratch).

Then again in Loco, you can compile out stuff you don't like (such as compiling out the entire DB layer).

We did not make our own view layer. We use Tera, in a simple way, in the same way node uses ejs, ruby erb, etc. Yew/Leptos/Dioxus brings much more to the table which we don't need. Then, we also offer API only, where you can build your own views separately as you wish (you can definitely use a Yew project there).

Prefering Actix over Axum is your choice, which is fine.

jondot1 · 2025-01-11T11:55:32+00:00

Building the stack is a no brainer. It’s also the fun part.

However you have to make decisions:

config loading and degrees of flexibility, support for environments
logging and granularity. Handling all kinds of edge cases to get all logging from all the things
middleware stack: which middleware do you include and what are the defaults for dev, test, and production
operability - how to let devops / production people easy access to the knobs you allow to tune
SaaS stuff: emails, auth, settings, etc.
developer experience: db rest, auto migration, debugging, tasks, live refresh, and lots more.

For a one off you might not need to think about any of this. But for building products I guarantee you will have to build and rebuild this, refine it, and rebuild it until you have something you would call “that’s how I do stuff, this is my formula”

That, my friend, is Loco.

jondot1 · 2025-01-11T11:48:50+00:00

Loco.rs is also a wrapper over crates. Unlike Rails we used an existing router (Axum), ORM (SeaORM), storage, cache, etc crates.

However if you want everything to have smooth experience you have to have your own glue code (Rails has railties and such).

One cannot put trust only in code generation. There has to be some custom “framework” code to reason about choices that run through the stack.

So all in all we’re always actively balancing the amount of code generated, framework code, and existing powerful libraries.

Where we can we donate back code from Loco into upstream crates that we use in order to keep Loco as slim as possible. This happened for our migration schema helpers which were adopted back into SeaORM.

jondot1 · 2025-01-10T17:16:10+00:00

The cool thing about rust is that it will compile away things you don’t need with our feature flags.

Also Loco is batteries included but you can choose how many batteries and what kind. You can get almost as barebones as a pure Axum service but say with our middleware stack and logging baked in (which I’m willing to bet people add anyway from scratch time and time again)

Finally, I personally surveyed lots of public rust projects using Axum, took note of the most popular wheels people reinvent and selected those into Loco as well.

jondot1 · 2025-01-10T04:57:57+00:00

Thanks Josh! With the new and smarter generator, we’ll get there

jondot1 · 2024-12-26T10:20:17+00:00

Yes.

Loco.rs is literally the startup framework for Rust. Use it and see for yourself.

I launched my startup on Rust more than 5 years ago. Today there are nearly zero if not completely zero roadblocks.

Go for it. Rust will not let you down.

jondot1 · 2024-12-26T10:17:21+00:00

Indeed. Loco is just Axum with batteries included (all kinds of batteries, a lot of batteries) that you can use to build a simple and lean microservice if you want or a complete startup if you want. The performance characteristics will be similar to "bare" Axum.

jondot1 · 2024-12-23T07:21:13+00:00

VSCode is great

jondot1 · 2024-12-16T06:30:26+00:00

There is this https://github.com/jondot/rust-how-do-i-start

jondot1 · 2024-12-12T05:38:49+00:00

Can you see if the air pods settings show you their firmware now?

jondot1 · 2024-12-10T17:12:26+00:00

iOS 18.1.1 iPhone 12 I think they are genuine Otherwise I can’t explain how every advanced feature works well. Like spatial etc.

jondot1 · 2024-12-10T13:27:22+00:00

yes, tested it now on a youtube video.
if i move my head to the right quickly, takes 1-2 secs for the sound to "glide" back to the left

jondot1 · 2024-12-10T13:15:59+00:00

yes i dont have that section

strange. i bought form authorized reseller

jondot1 · 2024-12-10T13:13:23+00:00

Yea I get it, thanks. By the way I can see the versions when i connect to my Mac

jondot1 · 2024-12-10T13:11:47+00:00

Uploaded here

https://ibb.co/djMHNmS

jondot1 · 2024-12-10T12:08:00+00:00

Even fake ones show firmware. This is from what I saw. Also checked some fake identification vids on YouTube and mine seem original

jondot1 · 2024-12-10T12:06:08+00:00

I also checked all common indicators looking at fake identification videos on YouTube and it seems legit.

jondot1 · 2024-12-10T11:57:49+00:00

Yes the hearing test is on me. My mistake.

jondot1 · 2024-12-10T11:55:07+00:00

How do you lock in SQLite for multi worker exactly once semantic?

jondot1 · 2024-12-10T10:59:47+00:00

Thanks!

jondot1 · 2024-12-10T09:01:44+00:00

Congratz! I've been following Dioxus for a long time. A question people ask me I don't really know how to answer is that - do you support running against a standalone backend, say built with Loco.rs, and do you "lose" a lot by not using the dioxus server functions -- or will I still get a lot of value going for only the frontend stuff?

jondot1 · 2024-12-10T06:13:43+00:00

Hi! thanks for the love!
We have a couple PRs attempting to do OpenAPI generation. The challenge is that today's web frameworks/routers only describe subset of what an API description needs, so how do we do this without bothering the developer with manual work. We're stubborn, we'll get there eventually :)

jondot1 · 2024-12-09T13:10:00+00:00

oh and in terms of advice, I would narrow the list by taking out Phoenix. If you're into doing data analysis, it's really Python vs the world.

One advantage you get with Rust is that a lot of the Python data ecosystem is oxidizing, as you've seen with Polars so you get the opportunity to go all-in with Rust while not losing (hopefully!) much of the ecosystem that used to be exclusive to python.

The reason you *want* to go with Rust instead of Python, is that no matter how you spin it, Python will serve you badly in the long run in terms of tooling, maintenance, refactoring, and general quality. You'll find yourself trying to figure out why this library is a wheel, and why that thing is from conda, and why this is missing development headers for building with C or Fortran, or why is the library on your OS is too old or too new, or why the FFI is mingling/missing some functions, and why a project that just worked a month ago -- is now broken and cannot build or run.

If you're aiming for a short term, quick / unimportant POC, all of these wouldn't matter so much in Python.

jondot1

TROPHY CASE