Gist of Go: Concurrency is out!
Learn Go concurrency from the ground up with 50 auto-tested exercises and tons of interactive examples.
It's a full course + book in one.
https://t.co/aBlt4BLEq1
🪣 RustFS: high-performance, distributed object storage system built in Rust
- offers full S3 compatibility, is completely open-source, and is optimized for data lakes, AI, and big data workloads
https://t.co/AqM1s2VTYf
google/wire is now archived (https://t.co/lQ1MUurYo3) because it’s considered complete, not because it’s deprecated.
Still, it’s best to avoid DI frameworks and wire dependencies by hand.
Constructors and small packages make dependencies obvious, with fewer surprises. They also encourage you to actively think more about design.
If a project is already built around a DI framework, or the business requirements are too complex for hand wiring, adopting one is fine. The preferred choice should be google/wire rather than uber/dig or fx, as dynamic wiring is discouraged; explicit, compile-time wiring is always better.
templ v0.3.920 released today. Main new feature is support for template fragments (https://t.co/oah5ZuLAmQ) to reduce bandwidth and support LoB.
Docs at https://t.co/bozIicQcMD
Nuxt 4.0 is here at last … and it's all about DX ✨
🗂️ app/ directory for better organisation
🔄 smarter data fetching
⚡️ a faster CLI with socket communication
🔧 improved TypeScript integration
... and a smooth upgrade experience. 💚
https://t.co/Jvf5DOGzE9
Go 1.25 is coming soon, and the official release notes are pretty dry.
So I prepared an interactive version with lots of examples.
https://t.co/cc8qH7SDWt
Go is the ultimate backend language.
Its loosely coupled packages make modular development a breeze, enforcing single responsibility for cleaner code.
Strict typing catches errors early, while unmatched performance and flexibility power everything from APIs to microservices or even in a loosely coupled monolith.
Go gets it right.
Graceful shutdown in Go is really nuanced and requires care to avoid corruption and poor user experience. This is the only guide you need to master it: https://t.co/ZsR66O4hmB
If your code requires a database to be up and running, or a service to be available, or to have a specific set of permissions on some system, verify these conditions as the process boots up, making sure that any trivial setup issue causes an immediate failure.
This way, any crash due to a trivial setup issue will happen immediately, not after minutes or hours of processing. A late crash caused by something easily fixable is extremely frustrating and a waste of time.
When your code fails after running for a while, it should fail due to some legit, unavoidable exceptions, not due to simple, fixable setup issues.
I have followed this since my very first job, and it has saved me countless hours :)
Want to get to grips with building web applications in #golang?
Let's Go is a clear and concise guide which packs in all you need to know about best practices, project structure and practical code patterns – incl. dependency management, authentication, databases, testing & more.