chuckadams

The process node size in William the Conqueror's time was really off the charts.

plus the fact that the kernel doesn't know anything about PATH (it's only your shell that does)

glibc is what deals with PATH, not the shell. On Linux, it's execvp(3) in libc which is implemented in terms of execve(2) in the kernel, but POSIX doesn't make a distinction between syscalls and library functions, so a kernel could implement either or none directly.

Lots of software licenses have “non-compete” clauses that forbid you from using it to develop a competing product. Wouldn’t surprise me if there was a compiler or two out there with that restriction, most likely niche languages.

I would agree that turing-complete config is more trouble than it's worth when the config is something you might need to reason over, such as a build definition in Gradle. But for something like a window manager config where everyone's config is a snowflake, it's kind of ideal. Horses for courses and all that.

I wouldn't say text/template is terribly weird per se, and it's quite reminiscent of Jinja. But what is awful is using a text templating language to generate yaml with the correct level of indentation, and that's where 75% of Helm's problems lie; the other 25% is putting too much logic in templates while working with the clumsy workarounds to text/template having no capability of defining custom functions.

Gotta say, I like most of the effects except for the wiggly "membrane" on inputs and buttons: I'd prefer to see the the whole thing jiggle when clicked or focused, rather than a small circle, and to turn off the effect entirely for typing. I suppose it's trivial enough to go into the source, but if there's a cheap and easy way to expose customization knobs like that, perhaps take it as a suggestion.

SQLite famously doesn't accept PRs either, and it's public domain.

If you don’t know what OpenCode is, imagine a boot stamping on a human face forever. The boot is made of TypeScript and the face is everything we have learned about security and systems software since the invention of the electronic computer in the 1940s.

I nominate this for a Bulwer-Lytton prize in the Tortured Metaphor category.

Gehenna was well-known in the oral tradition of Jews and Muslims long before the 1600s. The whole "lake of fire" thing appears in the Book of Revelation, is very unambiguously referred to as such in the Greek text, and that's what most conceptions of hell come from. Dante's Inferno is literally frozen over at the bottom, which is not the standard Biblical version of Hell most people think of.

The overwhelming majority of people who came to the site wanted the site to be something that it was fundamentally not trying to be

Message received I guess, seeing as how the overwhelming majority left.

And this kind of superior attitude over the unwashed masses is precisely what kept me away.

Taking personal offense to someone insulting your question is something you should learn to get over.

I did get over it when I stopped bothering with SO. Sorry, but a community whose ethos is "you need a thick skin to belong" is not one most people even want to belong to.

One thing that might have helped SO is if they actually embedded the supposed duplicate, and its answer, in the question, then had a checkbox for "was this the same as your question?" SO was never in the habit of listening to suggestions unless it was to nitpick them to death on meta, and there were plenty of other self-inflicted wounds with no technical quick fix.

They created TypeScript, and maintain it now. It's not exactly a business for them, no one is buying "TypeScript Enterprise" subscriptions. It's all under the Apache License 2.0 and certainly big enough that if they started pulling anything untoward, it would see a fork. Sometimes Microsoft produces an unalloyed good, they're not a monolith.

Reddit has many different subs that suffer from its problems in different degrees, so there's still islands of relative calm and sanity, usually in low-traffic subs. To some extent this was also true of different sites in the overall StackExchange network, but SO itself always dominated the network, it was designed and run as a monoculture, and that culture was, well ... gestures vaguely in SO's direction

StackOverflow management alienated those users, too, by shoving AI down their throats in every facet of the site.

Actually, I thought they outright forbade AI answers? I don't know where else AI might have come in -- having an AI look for related answers instead of making users use the primitive search (for which almost everyone always used google instead) might have been a good idea. Probably wouldn't have been enough though once google started answering the questions before showing SO links.

Isn't that "O Brother Where Art Thou"? Probably my favorite Coen brothers movie.

Yikes. I initially saw a different photo that looked a lot more like it could have been waving, but yeah, that's just blatant.

I personally think he really is a fascist, but I still don't think he was deliberately throwing out a Nazi salute. Just naive about waving to a crowd in front of a camera, which is very on-brand for him.

Given the continued downward trend, it may be the buyers may just be disagreeing on how fast it drops, not necessarily taking a long term buy and hold position. I don't know much about option pricing, but aren't put options basically betting on the spread?

That's my take on it too. The DOM itself is full of issues from its naive inheritance-happy OO design, and could use a refresh into something with better separation between data and presentation, but it's what we have right now in the real world. There's always going to be footguns, we can't put safeties on all of them. I have to wonder if it's something in the design of WebKit that makes inheritance particularly difficult to implement.

As for potential property collisions, I think the common wisdom is to just ensure the property name contains a dash, since the html5 spec goes out of its way to avoid using them. Doesn't solve brittle inheritance hierarchies in general, but it does at least stay out of the way of built-in behavior.

K8s uses watchers on etcd, not polling, so if there's no changes, there should be no activity. But just collecting metrics like CPU usage is probably a watcher on constantly changing data, like every second or so. So your control nodes are likely to stay warm most of the time, but there's also things like MicroK8s, which is made so you can stop the control plane and the worker containers keep running.

Which is a bit tricky on a Playstation. Sure you can scrounge up some Jellyfin-ish sort of thing, but most people buy on the console platform because they specifically don't want to jump through hoops.

Fair enough, I'd call it "homage" perhaps.

I reject your joyless reality and substitute my own.

Kubernetes is built around a JSON API: those yaml files are just an encoding of the objects that it manipulates with fairly vanilla REST commands. You could actually use JSON in your manifests instead, it's a proper subset and all, though it's not going to help the verbosity. For that you need a better abstraction like Pulumi, cdk8s, Yoke, or even just good old Terraform/OpenTofu. Or just write your own, there's an openapi spec and clients in every language out there.

I'm hardly trying to pretend like I'm a hyperscaler: I usually run k3s on a single node, and most of the time I admin it "clickops" style with k9s, something I find much easier than most other management tools.

Yes, and Kubernetes came around as another player in that ecosystem and became popular for a reason, largely so we didn't have to manage clusters with imperative non-idempotent scripts with no runtime introspection or self-healing. I've done light devops (lab scale, not enterprise) off and on since cfengine was a thing, and while I'm no fan of the explosion of YAML (there's a special place in hell for helm in particular for using text/template to generate yaml), I'll take the controller loop design any day over most of the alternatives. Just having a sane API alone is a godsend: you ever try scripting vSphere?

Lots. Firebird and DuckDB come immediately to mind. Wikipedia lists several more, though not all of them are relational: https://en.wikipedia.org/wiki/Embedded_database

The only browser Apple is blocking it on is Safari: other browsers implement it just fine, and the standard passed over Apple's objections. The rationale was architectural, arguing that extending built-in components would lead either to brittle components that would break when new properties were added or causing the specification of builtin components to freeze forever to avoid such breakage. I'm not sure I buy the arguments 100%, but for sure it's not evil/incompetent board executives twirling their mustaches as they deliberately break the web: https://github.com/WICG/webcomponents/issues/509#issuecommen...

Anything doing server-side work is going to have to be at least somewhat custom. The main problem is there isn't a standard "combobox" at all to speak of: we're still mostly stuck with the same carved-in-stone widget set from Mosaic, whereas native toolkits were more inventive even in the late 80s. Where's Athena's 2d panner widget, for example?

I didn't read any satire in the article at all, it just laid out all the built-in behaviors that a proper button has, and how much work it is to reimplement all of them. Something declarative and CSS-like would have been ideal for customizing elements, but instead we got the half-assed Custom Elements API and the completely different DX atrocity that is Web Components.

I can't really fault Custom Elements too much though, it's an imperfect API for an imperfect DOM and it's better than waiting forever for perfection. But I don't extend the same generosity to the Web Components spec.