- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
I unironically love this. Of course it isn’t practical in the least, but I love it.
“Lousy Smarch Weather”
‘Do Not Touch -Willie’
“Hey, good advice!”
I love the month of Jay
My wife and I always wanted a joctober baby…
Genuine Question:
if you could split the month names into 3, how would you split them to maximise their choice overlap?
- “em” is a good overlap for nov/sept/dec
- “uar” is good for jan/febr
I assume the post is the maximum. I wonder if there is an algorithm for that
hierarchical letter clustering would be my guess, or graph-based clustering using ngrams of 2-4 as nodes and maximising for connections.
Or using an optimized Regex and printing out the DFA?
Edit: Quick N-gram analysis (min=3, max=num letters in that month)
R-code
library(ngram) tmonths = c("january", "february", "march", "april", "may", "june", "july", "august", "september", "october", "november", "december") zzz = lapply(tmonths, function(mon){ ng = ngram::ngram_asweka(paste(unlist(strsplit(mon, split="")), collapse=" "), min=3, max=nchar(mon)) return(gsub(" ", "", ng)) }) res = sort(table(unlist(zzz))) res[res > 1]
This gives the following 9 ngram frequencies greater than 1:
ary uar uary emb embe ember mbe mber ber 2 2 2 3 3 3 3 3 4
As you can see two longest most common motifs are “em-ber” and “uar-y”
Using this I propose the following graph
Mermaid
stateDiagram direction LR sept --> em nov --> em dec --> em em --> ber oc --> to to --> ber feb --> uar uar --> y jan --> uar ju --> ne ju --> l l --> y ma --> r ma --> y r --> ch a --> p p --> r r --> il a --> u u --> gust
Thanks for saving me time, my head was already spinning on the previous comment but you made it stop.
I’m really disappointed by June, April and August. Without these months, everything would be so neat and orderly
Interestingly
- Aprch
- Maril
are the only two hallucinations, everything else is always a legit month
Managust, the manliest of months.
Febranber. Those who know, remember.
We can clearly see that this design is silly, because it allows for so many invalid states. Yet when we represent some type, let’s say in Java, were so often forced to do this exact same thing. Have variables in a container of which only a certain combination is valid. And then have at most a comment saying “this number is only valid if X is also set” or “if the validity boolean is true”. Luckily Java finally has some ability for the so-called sum types now, just like Haskell’s data types or Rust’s enum types. Imo any language should have this.
Having data dependent on each other in a type means that either you have redundant data (so one of the fields should be computed) or that your container tries to be too generic (you should in this case prefer an ‘Apple’ class over a ‘Fruit’ class with an enum field ‘Type’)
Wake me up when Septempril ends
Sounds like a medicine I shouldn’t take before asking my doctor if it’s right for me.
I use febr a rch btw
You know about neo-pronouns, get ready for neo-months
at least no bot will solve this
I understand that bad ui is a fun meme and all, but how did this one even cross their mind as an idea for a bad UI? This is a new level of convoluted I would not have even considered.
My guess: someone messed up trying to split an array and split a string from it and hilarity ensued.
It’s too unregular and too good to be a coincidence. Unless they threw an algorithm on it that was intended for whatever
To be clear, I don’t think the choices are a coincidence; I think the general idea is one.
Might be a decent way to sort out bots, actually.
j’october
Tu as october
Il elle on a october
october
j’octobe
tu octobes
il/elle/on octobe
nous octobons
vous octobez
ils/elles octobent