Interesting observation. But also:

50€ worth of gas

!anythingbutmetric!anythingbutmetric@discuss.tchncs.de

I would like to go back to the times when I could easily tell a joke from reality. To go, please.

I dare you knock on your neighbor’s door and ask them what chromium is. If they come back to you within the week and answer “a browser”, you give them a cookie.

can you elaborate on type=“datetime-local” not existing?

Oh goddamn, I hate web standards sometimes.

There used to be a proposal for datetime-local, but it was dropped, even though some browsers already supported it. That’s what I meant.

However, some years later the W3C added it to the standard again.

More info: https://webmasters.stackexchange.com/a/59541 https://stackoverflow.com/a/22654498/

They do provide a *.deb.

So 1993?

What is wrong with the simple type=“datetime-local”

The problem with that is that it doesn’t exist.

Nitpicking aside, the problem with native browser widgets, in my opinion, are:

• tiny hit areas for desktop users
• no way to highlight certain dates (e.g., holidays) or mark dates ineligible for selection (e.g., future dates)
• no way to indicate the week of year (not an issue for most use cases)
• users don’t know how to un-select a date (you’d think the ‘clear’ button would give that away and you’d be wrong)
• the widget lets you enter invalid dates without telling the user (or the programmer, for that matter), e.g., 31 Sep.

Widgets where you need to click 3 times for a simple selection, as you mentioned, have one of two origin stories:

• They were designed ‘mobile first’ with screen sizes of 320×200px in mind and therefore put a premium on screen real estate.
• The “seeing many things is confusing” camp of designers got hold of them. The fact that my users fail to recognize the ‘clear’ button in the datepicker widget seems to agree with them, but it’s still annoying for people without ADHD.

See https://sopuli.xyz/comment/21686277

Let’s consult Wikipedia (emphasis mine) [1].

Works of encyclopedic scope aim to convey the important accumulated knowledge for their subject domain, such as an encyclopedia of medicine, philosophy or law. Works vary in the breadth of material and the depth of discussion, depending on the target audience.

[1] https://en.wikipedia.org/wiki/Encyclopedia#Four_major_elements

Simple English is for people who would like a simpler language. I’m advocating for reduced scope – or at least better organization of detail. Move stuff that’s irrelevant in the great scheme of things to subpages or pages with narrower scope, instead of writing one single compendium on a topic.

I feel like the English Wikipedia is already better at this. In the German, on the other hand, the first sentence sometimes contains multiple lines of etymological derivations of the article’s title before it even mentions what it’s about (as soon as I stumble upon one of these monstrosities again, I’ll report the example here).

Which isn’t a bad thing. Wikipedia has for the last 25 years aimed at providing you with every bit of knowledge there is on a topic. That simply is not what people want when they look for information. No-one wants to read a full library’s worth of text when they want to figure out what happened in WWII. But Wikipedia lists all the minutae of every battle on every part of land, sea and air, including all the acting people from generals down to the lowliest private.

Fall-through in switch/case. The perpetual anti-personnel mine.

Commas are a premium feature now.

I wish you better luck the next time you try to read.

I wish there were a free database of words to answer that question. :(

You store your code in the fridge? Does that keeps the bugs out?

I don’t think believe using GPL will achieve anything. I am a professional developer. If I’m looking for a library for a problem and find one that’s GPL, then I will simply not consider using it. What are the options here?

I could search for a different library with an MIT license. Let’s, for the sake of argument, assume that there are none.

I could ask my boss if I can release all our source code to the public. Yeah, sure. That’s going to happen.

I could ask my boss if I can have a bit of budget to haggle out a license with the library author. That’s a waste of time and money. Hammering out a license agreement across language boundaries and jurisdictions will involve a lot of lawyering and waiting that’s just not worth it. The additional fees would likely even outweigh the agreed payment to the author.

So what’s left? I don’t use a library and program the thing myself. It might take a while, but I’m way cheaper than lawyers. So in the end, GPL won’t do a thing to force a business to support FOSS, but will annoy developers.

That’s why, if I ever am in a position to meaningfully add to FOSS, it will be under the MIT license.

I feel like it would be more appropriate is regular running wore button and running as administrator was a dude casually strolling down the pavement in sweat pants.

:(){:|: &};:
:(){:|: &};:

The intention was to provide a longer version for the first step of the ladder.