Depends on how “separate” the plugins are.

Single config file eases configuration of a service you consider one, and extend with plugins.

If the plugins reach a certain size, or are so distinct or separate, it may be preferable have separate configs.

Julia was my scripting and util programming language of choice for a while. But it couldn’t keep me. I’m not too confident in the reasons anymore, it’s been quite a while ago. I think the dynamic, unsafe aspect was a part of it, but also how it felt overall, or with code structuring?

Maybe I’ve been pulled away by better alternatives. (Using C# also for smaller util projects.) Recently, I’ve been using Nushell for scripting, which is new syntax to learn, but I’ve been enjoying functionality-wise.

I’m surprised and disappointed they didn’t mention Windows.

They publish macOS and now Linux releases. The issue tracker has many/multiple Windows tickets and a windows label. So it seems it’s not published as a release yet, but potentially usable as self-compiled, with efforts to reach stability. I assume anyway. There’s no obvious, clear indication or documentation that I can find (docs, readme tickets, project, milestone).

Exists: Dev Docs has Windows setup instructions.

Slogan: “Code at the speed of thought”

How does it speed up my typing? /s

“We value your privacy”

yeah, no, very obviously you don’t

I promise I won’t go more into the tech bits meant for developers 😅

Checks if they’re still on/coming from programming.dev

You’re saying wrong solution but point to the right solution in the same standard?

• Description: Zapier uses two custom HTTP header fields named X- API-Deprecation-Date and X-API-Deprecation-Info

Is your issue with the field name only? Why do you say wrong solution then?

It makes sense to include so it’s obvious in the readable HTTP request response. We use readable URLs and header names for the same purpose: So it is inspectable and understandable from that text format. You may leave deprecation information out, but then you’re missing part of the resource description that you’re addressing with the URL/URI.

Given a defined header it also allows you to add tooling and automation. There’s no need for manual reading.

You didn’t even describe how it’s on the website.

I would use the webbrowser/Firefox save page functionality.

Or open the webbrowser dev tools and document.querySelectorAll('img') and get the URLs from it and use those.

Or Page info media tab.

Or dev tools network tab. To identify and use the image web requests.

Or use Nushell with query module enabled, and http get query html.

Or my own C# until.

But I suspect there’s Auth in play, so the only easy access is within the browser session?

Earlier this week for a character range.

/edit: Now I remember. For setting up a new entry in Jenkins CI build failure analysis - identifying the build failure cause in the log.

Seemed verbose, overengineered, unnecessary framework introducing complexity. I didn’t see a strong use case for it, maybe for a lack of an obvious one or my understanding of it.

It also didn’t leave a strong impression. I had to look at the site and goal/description to remember.

Maybe some niche data handlers and implementors have use for it. But a Wikimedia project seems overblown for that.

I have not used it though. I’m open to being shown and corrected.

What conclusion did you come to?

He’s gonna live a long life. Until we know pi.

I really like Calendar Versioning CalVer.

Gives so much more meaning to version numbers. Immediately obvious how old, and from when.

Nobody knows when Firefox 97 released. If it were 22.2 you’d know it’s from February 2022.

It doesn’t conflict with semver either. You can use y.M.<release>. (I would prefer using yy.MM. but leading 0 is not semver.)

In my Firefox I get a NS_BINDING_ABORTED error on the Google Fonts font request.

And they didn’t specify a font fallback, only their external web font. It would have worked if they had added monospace as a fallback.

Ignoring secondary email addresses, what was my primary [onlineaccount] E-Mail address has changed four times.

Nested CSS obscures complexity

An interesting point. Something I will take with me for observation and consideration.

Maybe sometimes it’s worth despite it and other times not.

extending the list

• You don’t need JavaScript to build web pages
• You don’t need JavaScript to publish web pages

Seems like a valid formalization.

I think a or a few counter-examples would go a long way though.

The “rectangle” probably isn’t supposed to be this messy?