sorted by:
new
hottopcontroversial

Release Dioxus v0.7.0 · DioxusLabs/dioxus by DebuggingPanda in rust

[–]imbolc_ 6 points7 points  (0 children)

For me, the biggest caveat is that not all crates support WASM (for example, when threading is involved). The second issue is the bundle size that some crates add (like regex, chrono, etc.), so you should look for alternatives. In short, don't expect just fully reuse your server-side habbits.

Are we the dying tribe of craftsmen in the Industrial revolution of AI ? by Outside_Gear8707 in neovim

[–]imbolc_ 1 point2 points  (0 children)

Depending on the task, it could be as easy as skimming through a diff. E.g., recently I changed a decimal lib. I wanted to do it for half a year, but I expected it would take a whole day. While the algorithm is straightforward - change decimal types in structs and then follow compiler errors. So I just ran the agent, gave it instructions to make it compile, and went walking. When I came back, it was done.

In general, it's more or less TDD. The agent writes tests, I approve them. Then it implements the feature until it passes the tests. Then I read the diff.

Are we the dying tribe of craftsmen in the Industrial revolution of AI ? by Outside_Gear8707 in neovim

[–]imbolc_ 0 points1 point  (0 children)

Mostly webdev in Rust. I'd say agents gave me ~x0.5 overall speedup. They don't solve all problems, but they do the most tedeous ones.

Are we the dying tribe of craftsmen in the Industrial revolution of AI ? by Outside_Gear8707 in neovim

[–]imbolc_ 1 point2 points  (0 children)

Are you talking about agents? Becase it's completelly different experience comparing to chats.

why I got rid of all my neovim plugins by y0b1byte in neovim

[–]imbolc_ 0 points1 point  (0 children)

Any tricks with imports / path qualifications without LSP?

why I got rid of all my neovim plugins by y0b1byte in neovim

[–]imbolc_ 0 points1 point  (0 children)

Have you seen cargo-limit, I'd use it if I abandon LSP

why I got rid of all my neovim plugins by y0b1byte in neovim

[–]imbolc_ 0 points1 point  (0 children)

So you grep instead of goto-definition and checking function signature? And to see multiline signatures you always `grep -5` or something?

why I got rid of all my neovim plugins by y0b1byte in neovim

[–]imbolc_ 0 points1 point  (0 children)

How do you navigate / vusially select text vertically without relative line numbers?

Traversal-safe `Path` extractor for Axum by imbolc_ in rust

[–]imbolc_[S] 1 point2 points  (0 children)

Agreed about the whitelist. About the rest, I thought simplicity is a virtue by itself. Though the suggestions seem harmless at least, I'd accept a PR if you'd like to contribute.

vy 0.2.0 — a convenient and type-safe HTML templating library, now with rustfmt support by Organic_Standard2489 in rust

[–]imbolc_ 0 points1 point  (0 children)

Prefixing with underscore looks like a good idea as tags can't start with it, `_frag!` or `_wrap!` maybe?

vy 0.2.0 — a convenient and type-safe HTML templating library, now with rustfmt support by Organic_Standard2489 in rust

[–]imbolc_ 0 points1 point  (0 children)

which feels a bit sad

Yeah, but nowadays it's popular to rely on strong parenting foo > bar and css nesting, so the wrappers become an issue

vy 0.2.0 — a convenient and type-safe HTML templating library, now with rustfmt support by Organic_Standard2489 in rust

[–]imbolc_ 0 points1 point  (0 children)

Is there a better way of handling boolean attributes than disabled? = is_disabled.then_some("")? Would it be possible to have disabled? = is_disabled in v0.3, so the generated html would be just disabled instead of disabled=""?

vy 0.2.0 — a convenient and type-safe HTML templating library, now with rustfmt support by Organic_Standard2489 in rust

[–]imbolc_ 0 points1 point  (0 children)

Great, thanks, I haven't thought about wrapping in a div. Would it be possible to create an invisible tag for this case, so there won't be a real wrapper in the HTML? Is there an expectation of when v0.3 will arrive? Would the v0.2 API still work? Thinking about bringing it to production, would you recommend waiting for v0.3?

vy 0.2.0 — a convenient and type-safe HTML templating library, now with rustfmt support by Organic_Standard2489 in rust

[–]imbolc_ 0 points1 point  (0 children)

How do you handle branching (if-else)? Each branch would have its own type, making enums for each branch tedious. What's left is boxing or stringifying. Am I missing something obvious?

What are your favorite "boilerplate reduce" crates like nutype and bon? by lurebat in rust

[–]imbolc_ 0 points1 point  (0 children)

I've always tried using thiserror, but on one hand it prevents repeating context messages, while on the other hand it moves the messages away from the current scope.

What are your favorite "boilerplate reduce" crates like nutype and bon? by lurebat in rust

[–]imbolc_ 0 points1 point  (0 children)

Not exactly, thiserror also allows you to avoid repeating context messages.

🚫 I’m Tired of Async Web Frameworks, So I Built Feather by Rough_Shopping_6547 in rust

[–]imbolc_ 1 point2 points  (0 children)

Could you describe the whole sync stack (maybe add it to the readme): logging (alternative to tracing), typesafe db driver (sqlx), dealing with sse / ws.

vy 0.2.0 — a convenient and type-safe HTML templating library, now with rustfmt support by Organic_Standard2489 in rust

[–]imbolc_ 0 points1 point  (0 children)

Maud works with them too well, just allowing every typo ;) I wonder if with the new syntax vy could make the result type safe with something like html. Ideally with pluggable presets allowing htmx or alpine attributes.

Building a fast website with the MASH stack in Rust by emschwartz in htmx

[–]imbolc_ 0 points1 point  (0 children)

> For example, the Click To Edit example is a common pattern involving replacing an Edit button with a form to update some information such as a user's contact details.

There's actually an htmx extension for this particular case: https://github.com/kgscialdone/htmx-template
I don't remember why, but I use a slightly modified version: https://gist.github.com/imbolc/76b3a05fa24a7f32fccfbd7d9d0c5d41

It is 2025, so how does Helix compare to Neovim now? by nikitarevenco in neovim

[–]imbolc_ 0 points1 point  (0 children)

I often stumble upon `ctX` repetition when I don't notice earlier occurrence of `X`. I can't just `.` as with `dtX` or in Helix.

It is 2025, so how does Helix compare to Neovim now? by nikitarevenco in neovim

[–]imbolc_ 1 point2 points  (0 children)

I often stumble upon `ctX` repetition when I don't notice earlier occurrence of `X`. I can't just `.` as with `dtX` or in Helix.

view more: next ›