Dealer

英ジャガー4千人削減か従業員の1割

dmenu_business ｜ 2026-09-07 21:43 | id : 152949

VSPT.SN - Reuters

reuters_business ｜ 2026-09-07 21:43 | id : 151814

VSPT.SN  Reuters

米特使会談「小さな一歩」露報道官

dmenu_world ｜ 2026-09-07 21:19 | id : 152760

9月の値上げで消費者悲鳴　店も限界

dmenu_business ｜ 2026-09-07 21:14 | id : 152762

Palestinian parents fear for children's lives at school as settler attacks grow

bbc_world ｜ 2026-09-07 21:12 | id : 152809

A headteacher in the occupied West Bank has installed new barbed wire fencing after three pupils were killed this year.

ZATRANO: A Go Application Platform Built Around a Small Kernel and an Opt-In Package Ecosystem

golangbridge ｜ 2026-09-07 21:03 | id : 160995

Hi Gophers, I’d like to introduce ZATRANO, an open-source Go application platform for building production-grade software. The current v2 architecture is a significant redesign rather than a simple version upgrade. The main idea is simple: Go provides the language. ZATRANO provides the application platform. Instead of putting every application capability into one framework core, ZATRANO separates the runtime foundation from the application ecosystem. The Architecture ZATRANO is split into two independently maintained Go modules: the framework module and the packages module. The framework repository contains: a small runtime kernel dependency-neutral contracts application bootstrap CLI HTTP primitives routing middleware configuration dependency container lifecycle management core infrastructure The packages repository contains optional application capabilities such as: authentication sessions validation database ORM queues notifications scheduler cache localization AI RAG agents OAuth WebAuthn billing OpenAPI GraphQL and other application services The important part is that the kernel does not depend on the packages ecosystem. The dependency direction is intentionally one-way: Application → Framework → Contracts & Kernel Application → Selected Packages This keeps the runtime foundation small while allowing the application layer to grow independently. Why Build It This Way? One problem I wanted to explore is the growing gap between “a Go HTTP framework” and “a complete production application platform.” Go gives developers excellent primitives, but a production application still requires decisions and integrations around authentication, sessions, database access, queues, caching, notifications, AI, security, configuration, lifecycle management, and many other concerns. ZATRANO attempts to provide those capabilities without turning the kernel into a dependency-heavy monolith. Another important principle is explicit enablement. An application only enables the packages it actually needs. The goal is: Small kernel Stable contracts Strongly typed developer APIs Opt-in capabilities Explicit application boundaries rather than one enormous framework core. A New Application A ZATRANO application can be created with: zatrano new myapp cd myapp go run ./cmd/app serve Packages can then be explicitly enabled as needed: go run ./cmd/app package:enable auth The platform also provides a kernel-only minimal mode for applications that want to start with an even smaller surface. One Architectural Detail I’m Particularly Interested In ZATRANO uses a dependency-neutral contracts layer as the public ABI of the kernel. The intention is to keep the stable application boundary independent from implementation packages. Conceptually: contracts → stable dependency-neutral ABI kernel/* → strongly typed implementation From(app) → typed developer API This lets the ABI remain small while keeping the actual developer experience strongly typed. Repository Framework: GitHub - zatrano/framework: A Go application platform for building production-grade software. · GitHub Packages: GitHub - zatrano/packages: Official ZATRANO packages · GitHub Feedback I’m Looking For I’m interested in feedback from experienced Go developers, particularly around: Is this separation between runtime/kernel and application capabilities useful in Go? Where should the boundary between a framework kernel and an application package be? Does a dependency-neutral contracts/ABI layer provide meaningful long-term value? What would you expect from a production-grade Go application platform that existing frameworks don’t provide? I’d particularly appreciate architectural criticism rather than just feature requests. Thanks. 1 post - 1 participant Read full topic

イラン中間選挙控える米政権を挑発

dmenu_world ｜ 2026-09-07 20:59 | id : 152761

露と北朝鮮を結ぶ初の自動車橋開通

dmenu_world ｜ 2026-09-07 20:37 | id : 152730

中電会長浜岡巡る相次ぐ不正を陳謝

dmenu_business ｜ 2026-09-07 20:28 | id : 152735

QLYS.O - Reuters

reuters_business ｜ 2026-09-07 20:11 | id : 153086

QLYS.O  Reuters

デング熱が急拡大　バングラデシュ

dmenu_world ｜ 2026-09-07 20:02 | id : 152731

経団連会長法人税増税に賛成できぬ