Maybe I'm too old or my family was weird. We called it "le carwash" with a beautifully French "carouache" pronunciation. But yeah, "lave-auto" sounds more familiar.
Honestly, If anyone asked me "T'as fait quoi?" I'd blurt out "J'ai amené ma voiture chez le lavage". Background: I stopped speaking french when I was ten and my family isn't native, but it feels more conversational than "station de lavage".
It feels more like a question on english linguistic conventions than logic.
If someone asked me the same question and I wanted to give a smartass reply, I'd tell them "You want to wash your car, good to know. Now, about your question, unless you tell me where you wanna go I can't really help you".
It's the least convincing excuse used to circle around GDPR and similar laws. "I swear, it's for security! (please ignore the part in our ToS that says we can resell your HW configuration profile and installed software stats to our commercial partners)".
> The updates are over https. The default certificates are 10year expiry.
I wish I knew this last week while trying to restore a 2010 21" iMac.
Apart from this, I encountered another annoyance mid-way; the official download urls for Sierra and High Sierra were nowhere to be found. I somewhat remember being able to download the official dmg/disk image from some official repository, probably some App store public url?
can look for macos downloader scripts in github. I noticed the readme here shares some URLs though I'm not sure if they still work https://github.com/Comp-Labs/Download-macOS
Many of the decompiled console games of the '90s were originally written in C89 using an ad-hoc compiler from Metrowerks or some off-branch release of gcc-2.95 plus console specific assemblers.
I willing to bet that the decompiled output is gonna be more readable than the original source code.
Not related to what I was saying. Compilation is a many-to-one transformation & although you can try to guess an inverse there is no way to guarantee you will recover the original source b/c at the assembly level you don't have any types & structs.
In the music industry they have a saying about sampling and IP clearance which easily applies here too: "The lawfulness of your actions is directly related to your law firm fees compared to the other part".
Are Dolphin and emulation in general going to be legal in the future? Easy, if Nintendo chooses to go with Morrison & Foerster or Fish & Richardson for a lawsuit I'm going with "no".
A safer assumption would be that our body influences our behavior and tastes, and in turn they are directly affected by changes in our body, like an organ transplant.
A more interesting question regarding the case above would be "what's in our hearth and lungs that affects our perception of capsaicin?".
Hopefully this will help decompilation projects into generating better pseudocode. Some sort of "generate code -> build and execute -> test against existing executable if it behaves like the original -> change code again" loop.
CSS Zen Garden is quite the opposite of a good example of your point. Even small changes to the original page layout would completely break most of the provided styles.
If I removed the .page-wrapper class it would be also nearly impossible for a different developer to reverse-engineer the issue from the existing Template and CSS files.
The point isn't simply "class removal affects cascading", but "anything upstream is capable of placing the original content in an unrecoverable state".
Where "anything" could be your framework, your CMS, you or your coworkers a few years after the original CSS has been written and you can't fully remember what ".format-header__nav-wrapper:not(:last-child) .model-header__nav-wrapper:not(:last-child)" is doing.
And yes, that's a real CSS selector from a refactoring job I'm doing right now.
reply