@@letoan285 Thats the plan.

try this : github.com/semicolon-10/assets/blob/main/code_share_io_template.rs

Thanks for the feedback! Yes, by definition, you're correct. However, when following patterns, there isn't always a one-size-fits-all approach. The best method is whatever works best for your specific situation. While introducing mappers and DTOs adheres to clean architecture principles, it also comes with additional maintenance costs. For straightforward use cases like this one, where the models are simple and relational fetching is minimal, it might be more practical to use domain objects directly.

Surely, I will create a video on the job market. As far as frameworks go, Axum, Actix, and Rocket are all easy and straightforward to use. Each has its strengths that i will discuss in an upcoming video.

Thanks for the feedback, Actually, there is no definitive right or wrong way when it comes to models in Domain-Driven Design (DDD). My approach is as follows: Use domain objects directly for GET requests when they match your data needs, as this simplifies your design and maintains consistency across your application. This approach is particularly effective for read-heavy operations, where performance benefits from avoiding unnecessary transformations and keeping the codebase straightforward.

@@Semicolon10 of course, thank you

Are you blocked still?

​@@Semicolon10 Thank You very much for your attention and attitude. Regarding Logging Tutorial - yes, it is in a same state - I plan to check is it on my Linux machine soon.

@@TheHellishFrog Sorry i missed out on your comment earlier. Ideally it should work as it is on a windows machine too. But did you try passing the env variable from CLI instead?

@@TheHellishFrog Also do give this solution a try github.com/rust-lang/log/issues/39

@@xosnrdev RustRover, SignUp for Community Edition and Enjoy for free

@@asdasdaa7063 Yes on my todo already.

RustRover

github.com/semicolon-10/opentelemtry-rust-setup

This is just a introductory video, Majorly covering the token generation part. I will add a separate on for token management & expiry

Yes, I have a video on that too kzbin.info/www/bejne/i2nPkKl9i9h8aMU

Sure : github.com/semicolon-10/tauri-rust

@@riigel Surely, Thats already on my todo!

thanks man!

Sure : github.com/semicolon-10/grpc-stream-rust

@@Semicolon10 ❤

Здравствуйте, Да, многие крупные компании начали использовать Rust, и тенденция к принятию новых языков часто начинается с этих крупных организаций. Десять лет назад .NET был популярным выбором для бэкенд-разработки, но сейчас индустрия сместилась в сторону Go и Kotlin. С 2022 года наблюдается растущий интерес к Rust. У него теперь одна из самых больших сообществ на Reddit и поддержка практически для всего. Так что, да, спрос на Rust высок, и в ближайшие год-два вы, вероятно, увидите больше вакансий для разработчиков Rust. Поэтому сейчас идеальное время для изучения Rust. Если у вас нет опыта в программировании, Rust может показаться немного сложным для начала, но все равно стоит попробовать. Он похож на такие языки, как C++, с которых вы могли начать изучение основ. Так что лучше начните с Rust. Удачи!

github.com/semicolon-10/grpc_rust

@@Semicolon10 Thank You!

Choose tracing for advanced, structured logging with spans and events, and env_logger for simple and quick logging needs with configuration via environment variables. (Sorry for late response, I missed your comment)

You only need Arc Mutex If you want to share objects across threads.

Thanks for your feedback but i don't get your query. If you mean why tokio? Tokio is just a util dependency to work with futures. If not tokio then probably some other dependency. I use tokio because its very popular among rust community and easy to understand and use. Most rust programming in industry is done using Tokio for async. Hence i prefer so audience learn what is the best. Also its pretty straightforward hence you feel i paint it in same way. But it gets the job done and everyone understands it. But i will definitely look into using other similar deps in future vids. Thanks

Its essential for installing the development files for musl, which are required for compiling Rust programs that depend on musl. In this context, it ensures that the necessary libraries and headers are available for the Rust compiler to build the project successfully.

i just Learned About Musl yesterday using chatgpt... And got to know that musl is way better than regular glibc .... Gpt result. -> Static Linking vs. Dynamic Linking: musl: Supports static linking, which means all dependencies can be included in the final binary. This makes the binary self-contained and ensures it runs on any Linux system without needing external shared libraries. glibc: Typically used with dynamic linking, meaning the binary depends on shared libraries that must be present on the target system. This can lead to compatibility issues if the target system has different versions of these libraries. Binary Size: musl: Produces smaller binaries due to its lightweight nature. This is advantageous for embedded systems and containerized environments where minimizing resource usage is important. glibc: Binaries can be larger and may include additional overhead from shared libraries. Compatibility: musl: Ensures compatibility by including all necessary libraries in the binary. This is especially useful for deploying binaries to different Linux distributions. glibc: Compatibility can be an issue if the target system has a different version of glibc, leading to potential runtime errors. Performance: musl: Designed for efficiency and simplicity, which can result in performance benefits for certain applications. glibc: Known for comprehensive support of Linux features and wide compatibility but may introduce more overhead. Why Use musl? Portability: A statically linked musl binary is self-contained and can run on any Linux system regardless of the glibc version or the presence of other shared libraries. This is crucial for distributing binaries in a consistent manner across diverse environments. Simplicity: With musl, you avoid dependency hell and the complexities associated with dynamic linking and shared library versions. This leads to more predictable and reliable deployments. Security: Static linking with musl reduces the attack surface since there are no external shared libraries that can be replaced or modified. This can be beneficial for security-sensitive applications. Size and Performance: Musl's lightweight nature can result in smaller and faster binaries, which is advantageous for resource-constrained environments like embedded systems and containers.

Surely

Your amazing keep up the great work

May I ask where are you from.

Singapore

I just made a video of using diesel with MySQL with migrations and diesel cli.

@@Semicolon10 perfect, but using testcontainers?

@@os365 Surely added on my Todo.. Will soon release one.

Thanks 🙏🏻, If you are using VsCode or anyother Ide you can install rust analyzer plugin. If you need free rust dev with Jetbrains toolkit you can install rust rover Ide and signup for community version everything comes default setup in that ide including auto imports and you don't have to pay a cent (Highly Recommended). If you are using Intellij you need to buy rust plugin as in latest Intellij Rust plugin is paid and installing it will set auto import by default. If all this doesn't work then you can go in Intellij Setting and search for auto imports and check it. Hope this helps..!

github.com/semicolon-10?tab=repositories

@@Semicolon10 much appreciated buddy.