fuzzy2

No need to green-wash what is already green. You could label it "hippie propaganda" or something the like though.

I think TFA just reiterates that we can no longer build complex stuff within a reasonable timeframe and budget. Nuclear reactors just happen to be super complex. Nothing nefarious going on.

A server machine with multiple busy databases has 24.6 TiB written in 1349 hours. That’s on ZFS. As such, I’d say your usage patterns appear rather non-average.

Started using it a while back. Works rather well, even though some minor UX quirks exist. Self-hosting is easy, too, with Docker Compose. If you're in the market for a web-accessible bookmark manager, maybe give it a go!

This article leaves me confused. The “wide event” example presented is a mishmash of all the different concerns involved with a business operation: HTTP request, SQL query, business objects, caches, …. How is this any better than collecting most of this information as separate events on a technical level (with minimal, if any, code changes: interceptors, middleware etc) and then aggregating afterwards?

From my perspective, this is just structured logging. It doesn’t cover tracing and metrics, at all.

> This process requires no code changes—metric are derived directly from the raw event data through queries, eliminating the need for pre-aggregation or prior instrumentation.

“requires no code changes”? Well certainly, because by the time you send events like that your code has already bent over backwards to enable them.

Surely I must be missing something.

Just now, because Vodafone is running Wi-Fi hotspots on their customers' routers. (It's opt-out.)

An appliance wouldn't be able to use that, of course.

So then what do you use or recommend instead?

The idea is that you do not install packages, at all. Instead, you would use Flatpak and the like, plus mutable containers (Distrobox or whatever) if needed.

It’s not really about the manifest. It’s about the APIs available to extension programmers. Chrome has made the "webRequestBlocking" API unavailable and that’s what’s affecting adblockers. Chrome will eventually remove the code supporting this API, and it is not feasible for downstream to make it available anyway.

I agree that voice control is great, but I feel we’re at an “uncanny valley” moment. You can talk to a machine fluently in natural language, until you suddenly can’t and it makes the dumbest misunderstanding, either from recognition or from parsing.

You still get the best results by talking like a robot.

> Oops, turns out I was given a /64.

Is that really the case though? I very much doubt it.

I get a /56. Dynamic configuration mechanisms exist. I literally do not have to anything except flip a switch. My router even supports Prefix Delegation, so a downstream router/access point can do its thing.

Windows Filtering Platform does it. Windows Firewall barely taps WFP's potential and definitely does not do the whole "ZoneAlarm" style allow/deny thing.

Oh, but that is not a minus. That’s a hyphen-minus. A proper minus (−) is almost the same width as an en dash.

The title on HN got mangled. It’s ~$40B (APPROXIMATELY $40B), not minus.

Interesting stuff! Though I don’t get why b00lin would have to prove that they weren’t cheating. This is not a criminal case, but still. Activision was denying access to a service that was paid for.

I hate GitHub Actions, and I hate Azure Pipelines, which are basically the same. I especially hate that GitHub Actions has the worst documentation.

However, I’ve come full circle on this topic. My current position is that you must go all-in with a given CI platform, or forego the benefits it offers. So all my pipelines use all features, to offer a great experience for devs relying on them: Fast, reproducible, steps that are easy to reason about, useful parameters for runs, ...

It's almost like Sheep.exe, but not quite there yet!

That was never ANT+ anyway.

Typescript-the-compiler has exactly zero dependencies. But maybe that's now what you were referring to…?

That's somewhat arbitrary, don't you think? I think of "programming" as just writing code, "engineering" is coming up with what to code.

Rather, this is about capitalism. You want more freedom in going about your business. You cannot have that in a profit-oriented company. (Rare exceptions apply.) We're so focused on delivering, what we deliver becomes less of a concern, even though it should be the number 1 concern. The rest follows.

As a counterpoint: I often see technology-specific gitignore files, created from a template, that attempt to cover all commonly used tools. Can't really tell what is actually used from that.

I still love technology. It's only getting more amazing all the time. If you view just that, we're not just living in the future, but way beyond.

The application though, both by others and what I do at work? Meh.

So am I pessimistic about technology now? I think that's a valid way to put it. And yet I also feel "out of place in the tech world" with my viewpoint. Sure there's others with similar positions, but I feel this is not a majority.

Mechanical keyboards aren't automatically great or durable. I've had various die on me. One from sitting in a drawer, probably corrosion. And it's not even always the keys/switches, electronics can degrade too and firmware can be horrendously buggy.

I'm eager to try this. Seems like it could revive the genre after Semantic Merge died.

WebAssembly cannot access the DOM. So, not a full replacement.

I don't entirely get what you mean by "layout engine". A WYSIWYG editor perhaps? Or maybe a canvas like Microsoft OneNote, where you can draw and put text boxes? Or a word processor? Why isn't the usual Markdown (or the like) approach enough?

My gut feeling is that you cannot (fully) abstract away HTML/CSS if you want the result to feel like an actual website.

With Astro, MkDocs or docfx, I do not have to touch HTML, except maybe for creating the master layout and/or transformation rules, if needed.

Sounds like you might be looking for a Static Site Generator. Astro was already mentioned. There's plenty of others, mostly geared towards blogs. I also had success with docfx and MkDocs, both for project documentation.

With "maybe later" prompting to enable every few minutes, of course only "accidentally". :-)

I'll just answer here, but this isn't about this post in particular. It's about all of them. I've been struggling with a team of junior devs for the past months. How would I describe the experience? It's easy: just take any of these posts, replace "AI" with "junior dev", done.

Except of course AI at least can do spelling. (Or at least I haven't encountered a problem in that regard.)

I'm highly skeptical regarding LLM-assisted development. But I must admit: it works. If paired with an experienced senior developer. IMHO it must not be used otherwise.

I mean, yes, VS Code certainly is great and all, but…

> It's probably 70% of what VS on Windows is

no. From my perspective, it doesn’t even have 50% of VS features, and that’s probably a generous estimation. VS has lots and lots of features. Granted, many of them are irrelevant for most users most of the time.

Even Rider is lacking in comparison. It is very limited regarding debugging targets for example.

In a past project, we used Units.NET. It worked pretty well as far as I could tell. (I was not involved with the gritty domain details.) My colleagues even extended the library where units were missing.