开发者

Docker logs without the logging stack Discussion | Link

Bluesky will be getting "communities," which will function as smaller spaces where you can "go deeper and hang out with people who care about the same stuff" sometime this year, according to head of product Alex Benzer. They will be built on the decentralized AT Protocol that underpins Bluesky, with Benzer saying that "it's a […]

The Framework Laptop 13 Pro is delayed. The new 13-inch Framework flagship was set to launch in June, but shipments from the first batch are now expected in July - and there's still a chance some shipments could slip to early August. If you're not in the first batch, your Laptop 13 Pro shifts from […]

My frustration with distributing java apps didnt show up recently. I remember having implemented my first network jar downloaded back in the 2000's because i needed applet like feature support with desktop full control. Years after, the problem is the very same. Webstart didnt really took off and the only mean i had in my projects was the ugly fatjars, including the (for me) uglier spring-boot repackaging that changes the application classloading behaviour and hence giving me by time some headac

Been building EventInbox for a while — webhook delivery infrastructure for developers. Finally got the landing page live today: https://eventinbox.pro It's the layer that sits between your app and your customers' endpoints — durable delivery, automatic retries, HMAC-signed payloads, full observability, and replay. SDKs for TypeScript, Python, and Go. Still early but the API is live and signup works end to end. Would love honest feedback on the page and the product direction. submitted by /u/eventinbox [link] [留言]

C# 14: The field Keyword — Cleaner Properties, Zero Boilerplate Every C# developer has been there. You start with a clean auto-property, then requirements change and you need to add a tiny bit of validation. Suddenly that one-liner explodes into six lines of boilerplate — a private backing field, a getter that just returns it, a setter that assigns it. The logic is two words. The ceremony is everything else. C# 14 fixes this with the field keyword: a contextual keyword that refers to the compiler-synthesized backing field of a property, letting you write custom accessor logic without ever declaring an explicit field. The Problem: Boilerplate Tax on Simple Properties Auto-properties are one of C#'s best quality-of-life features. This is clean: public string Username { get ; set ; } But the moment you need to trim whitespace on assignment, that cleanness evaporates: private string _username = string . Empty ; public string Username { get => _username ; set => _username = value . Trim (); } You now have six lines — and four of them exist only to hold the shape of the pattern together. The backing field _username is not carrying any meaningful design weight. Its only job is to be a storage slot that Username uses privately. You already know the compiler creates one for auto-properties. You are just forced to make it visible so you can reference it. This is the boilerplate tax. You pay it every time you add even the smallest piece of logic to a property. Why field Exists The C# language team has discussed this friction for years. The challenge was finding syntax that is: Unambiguous — no conflict with existing identifiers Familiar — consistent with how value works in setters Scoped — only meaningful inside a property accessor The solution landed in C# 14: the contextual keyword field . Just like value refers to the incoming assignment in a setter, field refers to the hidden backing storage the compiler manages for the property. It is contextual, which means it only acts