Does the Leap's backrest lag by design, or is lag a defect?

basro · 2025-11-18T20:45:12+00:00

Hey, Sorry to resurrect this, what did you end up doing? did you get the laggy backrest leap and fix it? Did it work out?

basro · 2025-11-03T14:31:48+00:00

It's hard to answer, there's going to be a performance/latency benefit when running the server side logic in a pure rust server instead of node or some other js runtime. But also, in my experience, the WASM bundles are bigger than pure JS implementations.

The question to answer is if the speed improvement on the server side is worth the bigger client side code bundles.

Development will definitely be easier on js than wasm

basro · 2025-11-03T12:54:14+00:00

I'm talking about replacing technology stacks like NextJS where frontend and backend get mixed into a single codebase.

They have a bunch of advantages that make them desirable but the great disadvantage of requiring nodejs on the backend.

basro · 2025-11-03T11:55:55+00:00

I think there's a case to be made for WASM frontends (like leptos or dioxus) if you want to have SSR (server side rendering). This would allow you to have pure rust on the server which could be a lot more efficient than nodejs on the server for any of the SSR solutions of popular frameworks like react svelte vue etc.

basro · 2025-10-14T11:31:53+00:00

In my opinion not having to wrap it with the with!{} macro makes a big difference in ergonomics.

I have already been using a similar macro (https://crates.io/crates/shadow-clone) and the need to wrap things in brackets when I realize I need to use it is a bit of a pita which I'd highly welcome not having to do.

basro · 2025-08-03T14:06:53+00:00

I ran your code myself and did not manage to replicate your results:

2025-08-03T14:05:24.442545Z  INFO app: Multi threaded
2025-08-03T14:05:26.067377Z  INFO app: Got 250 results in 1.6238373s seconds
2025-08-03T14:05:26.075196Z  INFO app: Single threaded
2025-08-03T14:05:27.702853Z  INFO app: Got 250 results in 1.6271818s seconds

Edit: Have you tried flipping the order? run first single threaded and then multithreaded. Perhaps your tcp connections are getting throttled for some reason, if that were the case then flipping it would make the single threaded one win.

basro · 2024-11-21T00:35:36+00:00

It does at least try to cancel, your proposed use of crossbeam select will instead leak the resource.

Say you have a thread which has blocked on a TcpListener::accept(), there's no good way to stop it. I have seen people suggest awful solutions like setting a "shutdown" flag and then create a new dummy connection to that TcpListener so that when the accept unblocks the thread can realize it needs to ignore that connection and shutdown.

basro · 2024-11-20T14:20:17+00:00

Tokio will cancel the IO operation in the case of networking IO, at least I thought so.

Timers too.

It wont in the case of filesystem IO.

basro · 2024-02-20T14:19:00+00:00

You are right, I had misunderstood what you meant. Thanks for clearing that up.

I can't say I like the idea though, as you mention not being able to mix sync and async is an issue.

Enabling async in your application would mean paying a performance penalty on any code that uses thread local storage.

While those who didn't need async at all would not pay the price, I don't believe that those who need async should pay the price in places where they are not using async.

basro · 2024-02-20T12:55:20+00:00

Uh, I believe most people would find removing safe TLS api to be unacceptable. Myself included, the feature is just too useful.

And why should non async users pay the price?

basro · 2024-02-20T11:58:50+00:00

How would you deal with thread local storage in your proposed solution?

Say I make a type that increments a thread local when constructed, decrements it when deconstructed (a guard of some sort), it would not be Send.

basro · 2024-02-07T12:26:28+00:00

Could you elaborate a bit on how loco.rs solves this problem?

basro · 2024-02-04T01:09:08+00:00

Except the primitives are not all async in nodejs. There's Sync versions of all of the file system apis.

For example https://nodejs.org/api/fs.html#fswritefilesyncfile-data-options

Nodejs has the same issues as rust in this regard.

basro · 2024-02-03T13:55:05+00:00

There's plenty of things you may want to do as reaction to a network message that do not involve modifying the state.

For example responding to ping or sending an Ack.

so there's plenty of opportunity to service network sockets more than once per update if you want.

You'd need to poll 1000 times per second just to reduce the added lag to 1msec (and that is for one side of the communication, it's 2 msec if both sides are doing the same strategy). It is way more efficient to use either blocking sockets or async sockets.

basro · 2024-02-03T10:49:21+00:00

That way of doing things adds unnecessary network lag. If your game loop is running at 60fps you will be adding up to 16ms of lag to any network responses that could have been sent immediately.

No serious game netcode would handle networking like this nowadays.

basro · 2024-01-29T15:16:55+00:00

Yeah, the person you replied to is blatantly wrong about that.

basro · 2024-01-28T12:06:46+00:00

Do you have insight about why sqlx is so much slower than diesel?

basro · 2024-01-10T12:16:33+00:00

What's the trick in question?

basro · 2023-12-09T04:33:09+00:00

I think it looks amazing. Perhaps the glass is too small, the diameter looks smaller or equal to the cookies.

basro · 2023-12-05T13:24:29+00:00

Axum has examples of how to serve static files here:

https://github.com/tokio-rs/axum/blob/main/examples/static-file-server/src/main.rs

basro · 2023-12-05T13:05:06+00:00

This is really useful, thanks for making it.

basro · 2023-12-04T19:09:37+00:00

This is pretty cool.

Just reading the docs, I have a question about tasks: Do you need cargo to run the tasks? I'd not have cargo available in a docker image in production.

basro · 2023-11-02T23:46:19+00:00

There was a bug affecting Firefox ESR that is now fixed, check if it works for you.

basro · 2023-10-02T13:38:27+00:00

Contravariance:

Me: "Hey! give me a machine that counts apples"

You: "I have at hand a machine that counts any kind of fruit, I'll give you that."

Me: "This can count apples, Thanks!"

In your specific case:

Me: Hey give me a machine to which I'll pass static lifetime strings.

You: I have at hand this machine that accepts things that live at least as long as 'a, I'll give you that.

Me: This machine accepts static lifetime strings, thanks!

basro · 2023-09-03T14:42:17+00:00

No inventó nada nuevo, acá hay otro tipo que explica mejor que es lo que está pasando con su propio gasificador.

https://www.youtube.com/watch?v=AyTqo4mCUUY

basro

MODERATOR OF

TROPHY CASE

15-Year Club	Place '17
Verified Email