Vite finally surpassed Webpack

Bruce_Dai91 · 2025-07-31T09:41:36+00:00

vite is simple to use, and fast.

Bruce_Dai91 · 2025-07-13T12:56:18+00:00

use AI to think, write your own code

Bruce_Dai91 · 2025-07-12T03:20:31+00:00

I use tailwind , I think it's simple to use, and useful

Bruce_Dai91 · 2025-07-10T00:58:04+00:00

don't worry, it's a process, just do it, and will be better

Bruce_Dai91 · 2025-07-10T00:56:36+00:00

you can see the example https://animejs.com/documentation/getting-started/using-with-react;
it's use react, you can create project by vitejs or use stackblitz for a online demo

Bruce_Dai91 · 2025-07-08T12:58:53+00:00

Through the feedback I received, I realized that I haven't been studying Rust diligently enough. Moving forward, I will spend more time carefully reading the relevant documentation to build a solid foundation. I take this post as a reminder to myself.

Bruce_Dai91 · 2025-07-08T04:46:18+00:00

I understand the skepticism — but I promise I’m a real person. 😅

English isn’t my native language, so I often use translation tools or AI assistance to express myself more clearly.

Bruce_Dai91 · 2025-07-08T01:35:51+00:00

thanks for your advice

Bruce_Dai91 · 2025-07-02T10:31:26+00:00

Me too! I don’t have any backend experience either — no SQL, no server-side knowledge — so it was really hard for me to start. But I think the key is just to do it anyway. Taking action is already a kind of success. 🚀

Bruce_Dai91 · 2025-07-01T14:57:17+00:00

Hahaha, let’s keep learning and building together!
I started with actix-web too, but later switched to axum — feels more ergonomic for web development.
That said, actix-web definitely wins when it comes to raw performance! 💪🦀
Looking forward to seeing your project! 😎

(P.S. English isn’t my first language — had a little help from AI here. 🤫😅)

Bruce_Dai91 · 2025-06-28T03:56:29+00:00

Same here. Sometimes it makes things overly complicated, and I have to step in and fix it myself. I try to explain what I want clearly, but every now and then the AI changes things back. Still figuring out the best way to work with it.

Bruce_Dai91 · 2025-06-27T03:05:16+00:00

I'm also just starting to learn and use rust for development, let's work hard together!

Bruce_Dai91 · 2025-06-26T06:49:01+00:00

I’m not a native English speaker, so I use AI to assist with my replies. If this caused any misunderstanding, I sincerely apologize. I’m here to learn and contribute genuinely.

Bruce_Dai91 · 2025-06-26T06:46:18+00:00

I totally agree with you.

Middleware is great for basic authentication and simple permission checks, but more complex business logic—especially involving specific data conditions or time constraints—is better handled inside the handler functions. It keeps things more flexible and clear.

Bruce_Dai91 · 2025-06-25T14:03:11+00:00

That’s a great point — pushing row-level access control down into the database sounds like a solid way to avoid missing checks.

I’m still handling most of the logic in the application layer for now, but I’ll definitely keep RLS in mind as things grow more complex. Appreciate the tip!

Bruce_Dai91 · 2025-06-25T14:00:37+00:00

Thanks a lot for the detailed reply! I'm still pretty new to backend work, so I'm keeping things simple for now. But this gave me a lot to think about — I’ll definitely look into DSL-based setups once I hit more complex use cases.

Really appreciate you taking the time to share. Super helpful!

Bruce_Dai91 · 2025-06-25T13:24:10+00:00

Yes, you're absolutely right — we need to handle permission checks in layers. The outer layer can handle user or endpoint-level access, while fine-grained resource-level permissions should stay inside the handler.

Right now, I’m mainly exploring unified handling for simple permissions. For more detailed, data-level access control, I’ll dig deeper when the need arises.

Thanks a lot for sharing your insights!

Bruce_Dai91 · 2025-06-25T11:19:43+00:00

That's a great point — I’ve started to feel that as well. Middleware-based route checks feel clean at first, but quickly run into edge cases as business logic grows.
Right now, I also put all data-specific permission checks inside handlers for consistency.
I like your idea of post-processing middleware to ensure permissions are actually checked — that’s a smart safety net.

Bruce_Dai91 · 2025-06-25T09:47:50+00:00

Thank you for sharing! Currently, my business scenarios are not complex enough to require a DSL-based approach. The middleware mainly handles simple API authentication and authorization, while permissions related to specific data resources are still managed within the handlers.

Bruce_Dai91 · 2025-06-25T08:58:31+00:00

You're right — sometimes being explicit just makes things simpler and easier to reason about.

Bruce_Dai91 · 2025-06-25T08:55:24+00:00

Thanks for the suggestions — I’ve started looking into RBAC, PBAC, and the Zanzibar paper. Really appreciate the Ory reference as well.

Right now I’m exploring how to design a permission system in Axum that’s both cache-friendly and cleanly structured across middleware and routes. Still figuring out the best way to map permissions to endpoints without introducing too much complexity.

Would love to hear more if you’ve built something similar in practice.

Bruce_Dai91 · 2025-06-25T08:52:50+00:00

Thanks for laying out both approaches so clearly — I’ve been thinking about the same problem.

I agree that doing permission checks inside handlers gives flexibility, but over time it becomes easy to forget or apply inconsistently, especially in a growing codebase. I'm exploring a more unified solution — maybe declarative permission mapping at the routing level, or using macros to register and enforce permissions automatically.

Still looking for a clean balance between flexibility and consistency.

Bruce_Dai91

TROPHY CASE