WTF Bites
-
In Linuxland, they still believe in the dream of independent updates of apps and libraries, with all its consequences.
It is a huge advantage when it comes to fixing security vulnerabilities—patch up openssl or curl or such and all the applications get the patch. And it generally works well, too. Well, for C applications, and with huge effort Qt. The main problem is that C++, with its monomorphisation, plays very poorly with shared libraries.
I suspect it's huge part of the reason WinRT/UWP went the COM way, too. And Linux would do best going the GObjectIntrospection way or something similar.
In Windowsland, it's been a custom since 95 days to package all DLLs together with the application and treat them as inseparable whole - effectively multi-file static linking.
That's why MSVCRT gets breaking changes every season while GCC team needed a multi-year debate whether to become C++11-compliant or leave the broken implementation of std::string alone.MSVCRT always existed in at least FOUR versions in each release (the shared and static ones, and the debug versions of that), and for a while even in EIGHT (single- and multi-threaded). That makes assembling an application with third-party libraries quite the pain.
Linux stuck to one version. It has static and dynamic version, but unlike Windows, where the difference affects compilation due to the required
declspec
declarations, in Linux that decision can be postponed until linking. Thus linking third party libraries is much easier, but then the system vendors are reluctant to complicate it by adding new versions.
-
Status: Why the fuck is this recording so damn quiet?
I'm fricking re-encoding it with a +24dB volume modification....
-
This post is deleted!
-
@error I had a reminder in Outlook today for a meeting that was scheduled 22 hours from then.
(I think the meeting was moved from today to tomorrow, so probably by those 22 hours. Still not very useful.)
I think if the meeting time changes, all attendees will get a new notification/reminder.
-
@loopback0 said in WTF Bites:
Weird Outlook complaints.
Pet grammer peeve: using RSVP as a verb.
It always takes me a minute to remember the French source phrase for the acronym; I instantly think of the English that my siblings made up: respond so violently please.
-
Pet grammer peeve: using RSVP as a verb.
In English, everything is a verb!
Filed under: Verbing weirds language!
Verbing weirds language.
Verbing weird languages.
-
MSVCRT always existed in at least FOUR versions in each release (the shared and static ones, and the debug versions of that), and for a while even in EIGHT (single- and multi-threaded). That makes assembling an application with third-party libraries quite the pain.
AFAIK there was never a "DLL single-threaded" version, bringing the total to six, not eight. Which is still quite a bunch.
-
@Zecc You want to change your
d
tod2
for better$ex
?Why does
$ex
some how look like/Sex
?
And we are almost in the out of context thread waters.
-
-
-
@loopback0
FOCUS AND ASK AGAIN
-
@Luhmann DON'T BET ON IT
-
@loopback0
SO IT SHALL BE
-
@Luhmann THE STARS SAY NO
-
@loopback0 , @Luhmann INTERNATIONAL CAPS LOCK DAY was last Saturday.
-
@Zecc NO DOUBT ABOUT IT
-
@Luhmann WTF is a Beka?
-
@loopback0 said in WTF Bites:
Weird Outlook complaints.
Pet grammer peeve: using RSVP as a verb.
That's one of the things I like about English: you can take any noun and verb it.
-
-
I think my boss told me to scrap it. Probably for the better.
Wise boss.
-
@Luhmann WTF is a Beka?
- a brand of beds and matresses (context!)
- a Tanzanian singer
- a different artist (slight personal preference for this option)
- wait it's a reagea artist
- or a soccer player
- no a different soccer player
-
@MrL huh I didn't actually know it was a D20 on the inside. Guess that makes the 3D printing easier.
PHP: Hypertext Preprocessor.
-
@Gustav One day, my father suggested to me that Linux needed a Registry, because it would take N
/etc
accesses down to 1. That was the day when I realized I was an adult, as I told him how god-awfully stupid that idea was...
-
@Gribnit does this person think the Registry only loads once on boot, and saves only on shutdown or something? Because, uh, that ain’t how it works.
-
-
Yeah, but I’d prefer if the email stays in my emails where I can read it instead of having to look for it in the calendars. Fucking idiotic feature.
Just go to your deleted messages and undo it. But don't worry, the odds are high that the meeting will be modified before it happens and that email does not auto-delete even tho there's nothing for you to respond to.
-
@Tsaukpaetra said in WTF Bites:
@loopback0 said in WTF Bites:
This definitely can't be found in the calendar.
You'd be surprised how many people are shocked when I lead them to water.
I use the web version (because Ubuntu) and just have the 'My Day' widget open on the right. Shows all my upcoming meetings.
-
@BernieTheBernie said in WTF Bites:
@Zecc You want to change your
d
tod2
for better$ex
?Why does
$ex
some how look like/Sex
?Because ÿøųŕ fǒñţ $ü×
-
@Tsaukpaetra said in WTF Bites:
@loopback0 said in WTF Bites:
This definitely can't be found in the calendar.
You'd be surprised how many people are shocked when I lead them to water.
I use the web version (because Ubuntu) and just have the 'My Day' widget open on the right. Shows all my upcoming meetings.
Outlook for Mac has that too, it's handy.
-
CMake. Need I say more?
I copy/pasta'd a line wrong (one CMakeLists.txt file used
APP
, the other usedTARGET
) - I used the wrong macro in the header section in the library (I usedset(${APP}_HDR ...)
, it should have beenset(${TARGET}_HDR ...)
)Library compiled.
App using the library compiled. But couldn't link (failed to resolve class from library).I spent about 2 hours trying all sort of things (playing with namespaces, filenames, etc) before I finally found that.
-
-
Pet grammer peeve: using RSVP as a verb.
It always takes me a minute to remember the French source phrase for the acronym; I instantly think of the English that my siblings made up: respond so violently please.
When I was a kid someone told me that it was "Respond So Very Promptly" and it was a long time before I found out that was wrong.
As for using RSVP as a verb, I see nothing wrong with that. Responding to something is an action, you are doing something, and that's what verbs are for.
And Calvin is wrong. There is nothing weird about using "access" as a verb. Again, it's an action, you are doing something, and that's what verbs are for.
-
@Gern_Blaanston said in WTF Bites:
And Calvin is wrong. There is nothing weird about using "access" as a verb. Again, it's an action, you are doing something, and that's what verbs are for.
It's weirder if you use Access as a noun
-
-
@Gern_Blaanston said in WTF Bites:
Pet grammer peeve: using RSVP as a verb.
It always takes me a minute to remember the French source phrase for the acronym; I instantly think of the English that my siblings made up: respond so violently please.
When I was a kid someone told me that it was "Respond So Very Promptly" and it was a long time before I found out that was wrong.
As for using RSVP as a verb, I see nothing wrong with that. Responding to something is an action, you are doing something, and that's what verbs are for.
I respondpleased is like saying I fuckyouverymuched up. It does contain the verb that expresses what you're trying to say, but the rest of it changes the meaning to something different.
-
-
It's weirder if you use Access as a noun
The only thing I want to do with Access as a noun is
-
-
I just started learning Kotlin and so far it's been very frustrating. For example, this code compiles just fine:
class Factory(private val params: Params) : ViewModelProvider.Factory { override fun <T : ViewModel> create(modelClass: Class<T>): T { return super.create<T>(modelClass) } }
And this code compiles fine (with a warning):
class Factory(private val params: Params) : ViewModelProvider.Factory { override fun <T : ViewModel> create(modelClass: Class<T>): T { return if (modelClass == MyVM::class.java) { MyVM(params) as T } else { throw java.lang.IllegalArgumentException() } } }
But this code (the in-development version of the above) fails to compile:
class Factory(private val params: Params) : ViewModelProvider.Factory { override fun <T : ViewModel> create(modelClass: Class<T>): T { if (modelClass == MyVM::class.java) { MyVM(params) as T } else { throw java.lang.IllegalArgumentException() } return super.create<T>(modelClass) } }
There are two compile errors, pointing to the last line:
e: MyVM.kt: (28, 36): Type mismatch: inferred type is MyVM but T was expected e: MyVM.kt: (28, 36): Type mismatch: inferred type is T but MyVM was expected
Can you guess what happened? No, it's not a compiler bug, it's the intended behavior of the language.
-
I think it’s defective
edit: My very next question seems to have been bestowed the number 0
-
Can you guess what happened? No, it's not a compiler bug, it's the intended behavior of the language.
I guess something with ass-u-me-ing that if
modelClass == MyVM::class.java
thenT == MyVM
but … then it shouldn't be a type mismatch so… don't know what actually.Side note: the
MyVM(params) as T
does not seem to be actually used on the fourth line in the last snippet (it is returned from the if, but that is no longer returned and not assigned anywhere).
-
@Gern_Blaanston said in WTF Bites:
Pet grammer peeve: using RSVP as a verb.
It always takes me a minute to remember the French source phrase for the acronym; I instantly think of the English that my siblings made up: respond so violently please.
When I was a kid someone told me that it was "Respond So Very Promptly" and it was a long time before I found out that was wrong.
As for using RSVP as a verb, I see nothing wrong with that. Responding to something is an action, you are doing something, and that's what verbs are for.
I respondpleased
Is it not literally "respond if you please"? If that's what it is, then there is absolutely nothing wrong with using it as a verb, because that's grammatically what the word "respond" in there is.
Now, requesting "Please RSVP" in your letter is redundant.
And I can see the argument that saying something like "I RSVP'd" would expand weirdly. But a reasonable response would be that when using an acronym that contains a verb as a verb itself, the verb in any expansion of the verbed acronym would attract any and all verb appurtenances (and pronouns and conditionals and any other such things would switch appropriately as well).
-
@Gern_Blaanston said in WTF Bites:
And Calvin is wrong. There is nothing weird about using "access" as a verb. Again, it's an action, you are doing something, and that's what verbs are for.
It's weirder if you use Access as a noun
proper or
impro...common?
-
@Tsaukpaetra said in WTF Bites:
I doo...
Make sure you clean up after yourself! No one else wants to deal with it.
-
@Tsaukpaetra said in WTF Bites:
I doo...
Make sure you clean up after yourself! No one else wants to deal with it.
I mean.... I'm sure someone would....
-
@Tsaukpaetra said in WTF Bites:
@Tsaukpaetra said in WTF Bites:
I doo...
Make sure you clean up after yourself! No one else wants to deal with it.
I mean.... I'm sure someone would....
Well, sure, someone would, but they still (most likely) wouldn't want to.
-
Can you guess what happened? No, it's not a compiler bug, it's the intended behavior of the language.
I guess something with ass-u-me-ing that if
modelClass == MyVM::class.java
thenT == MyVM
The opposite, actually. Basically, Kotlin wanted to have sum types (tagged unions) like all the cool kids these days. But it went the Scala way of not actually having sum types and instead emulating them with class hierarchies. In Scala, there's no magic (surprisingly for that language) - you have to make explicit cast, and you can use
match
statement to make it safe. That leads to code that closely mimicsmatch
statements in languages with actual sum types. The cast variable is constrained to its scope, ie. the particularcase
inmatch
.But Kotlin wanted to be cooler than Scala. It didn't want its sum types to only work with
match
(which it renamed towhen
to emphasize how much it's not like the other languages). It wanted to make it work withif
blocks too. So its makers devised a feature called Smart Cast that's so full of compiler magic it makes me puke. It detects all the times you check the types (mostly for nulls) and automatically redeclares the variables to that type for your convenience, in all code paths where it can be proven. The compiler also understands what theClass
objects are, and applies the same code flow analysis whenever you compare them for equality.In this case, the compiler sees
throw
, and concludes the part afterelse
can only run if theif
condition is true. And so it smartly convertsmodelClass
fromClass<T>
toClass<MyVM>
because it knows for sure the two are one and the same. However, it's not smart enough to realize this also implies thatT
must beMyVM
. And so, while the first code snippet correctly passesClass<T>
tosuper.create<T>
, the third code snippet is actually trying to passClass<MyVM>
, which is a different type fromClass<T>
and the compiler emits the errors. Why two errors? Fuck if I know.Side note: the
MyVM(params) as T
does not seem to be actually used on the fourth line in the last snippet (it is returned from the if, but that is no longer returned and not assigned anywhere).Yeah, that's the real kicker. You know what happens when you put
return
there? It compiles.
-
Yeah, that's the real kicker. You know what happens when you put
return
there? It compiles.With unreachable code?
-
I've said it before, I'll say it again: Microsoft Teams is so incredibly fucking retarded!
Last week when I was in a meeting, it asked me something along the lines of
Hey, it looks like your audio driver needs to be updated. Do you want to update now?
Um, first off, I'm pretty sure that if my "audio driver" needed an update, the OS would tell me so, not some random-ass app. (Okay, macOS Ventura just came out and I'm still on Monterey, but that doesn't mean the audio driver isn't fine.) So what you really mean isn't the driver but something in your shitty app.
Second, I can hear everybody and the mic works, too. Just update whatever you need to update after I'm done with this meeting.Had it happen again today, and noted exactly when it happens: When I'm in a meeting and click the button to share the screen. Obviously, that means I absolutely do not want to click the fucking update button at that time. But then it also doesn't update, apparently until the next time it asks me right when I'm in the middle of a meeting and trying to share the screen.
Like, seriously?!
-
@Gern_Blaanston said in WTF Bites:
Pet grammer peeve: using RSVP as a verb.
It always takes me a minute to remember the French source phrase for the acronym; I instantly think of the English that my siblings made up: respond so violently please.
When I was a kid someone told me that it was "Respond So Very Promptly" and it was a long time before I found out that was wrong.
As for using RSVP as a verb, I see nothing wrong with that. Responding to something is an action, you are doing something, and that's what verbs are for.
I respondpleased
Is it not literally "respond if you please"? If that's what it is, then there is absolutely nothing wrong with using it as a verb, because that's grammatically what the word "respond" in there is.
It is, but that's no better. You literally say "news of day" in Swahili for "how's your day?", or "not-identity what" in Lao for "no worries", but using these expressions literally in English makes no sense at all. "Respond if you please" has this condition in it that we can assume is true because she wants to say she did respond so the result is about as y as
var I_please = true; if(I_please) { respond(); }
Now, requesting "Please RSVP" in your letter is redundant.
And I can see the argument that saying something like "I RSVP'd" would expand weirdly. But a reasonable response would be that when using an acronym that contains a verb as a verb itself, the verb in any expansion of the verbed acronym would attract any and all verb appurtenances (and pronouns and conditionals and any other such things would switch appropriately as well).
It sure makes sense some acronyms. "I LOL'd" is common; "at work everybody is BYODding" would be fine. "Let me just LCD this widget" would be weird though, just like "try to IIRC this" or "I hope I've been able to Q.E.D. it". All the right verbs but accompanied by nonsense.