LeFrog

as a fellow Python user, I fucking hate significant whitespace. Also YAML. WTF they where thinking

Maybe even worse than von Papen, because von Papen did not know about any such previous case. Merz on the other hand, seems to either actively ignore it or even endorse it.

Yet, we believe that an LLM is a good-enough measure of semantic ambiguity for our needs.

AI and believers, name a more iconic duo

wait, is this real?

if glass.empty?
  make_sad_noise
else
  homi.hydrate(glass.qty)
end

Let me introduce: Association of German National Jews

(Spoiler: they got their faces eaten in 1935)

Dude, this is a false dichotomy. Both are not mutually exclusive.

Be safe out there and use xcancel.com instead

Ah yes, the good old ROT26 encryption. Some say its unbreakable

Good point. My laptop is dualbooting Windows and Linux (Ubuntu 22) and its faster to:
start Linux, login, start quemu, start Windows VM in quemu, login in windows in the VM, shutdown windows in the VM gracefully, exit quemu, shutdown Linux gracefully
than
boot windows natively, login and wait till it is responsive enough to do anything with it.

In Germany there is a saying that goes like

Seagate, oder Seagate nicht

where “Seagate” sounds like “sie geht” (“she works”; the word “hard drive disk” is femininum in German).

So it translates to “She works, or she does not work.” or “Sometimes they work, sometimes they do not work”

Just curious, what is your use case for ESPhome/ESP32? I am still not sure what people do with it.

This is basically one of the core ideas of Ruby: that you can read it like a story. Once you are used to reading it as “do X unless Y”, you will miss it in other languages. Note that I wrote Y, not Y is true. Because often Y is a statement that has meaning in itself.

Example:

# imagine that given_name is some text from user input

# this is of course valid:
user.name = given_name if !user.is_locked

# but this reads more fluently:
user.name = given_name unless user.is_locked

Ruby also allows using ? as last character in method names, which is a convention for methods that return either true or false.

Same goes for ! (the bang operator), that is commonly used to tell developers that there exists a non-bang version of the same method as well. The bang method is often the more strict version (e.g. raises an error instead of returning nil; or having side effects compared to the non-bang version).

So the above example may be more commonly written like this:

user.name = given_name unless user.locked?

and the question mark makes you automatically adding is or has while reading: Set the user’s name to the given_name unless the user is locked

Of course this is all by convention and you may also do it different. But that’s how most Ruby code is written.

To stay consistent, lots of projects use RuboCop, which warns you on inconsistency based on your project’s settings.

Ruby has it as well:

a ||= b

# which means
a = a || b
# wich is the same as
a = b if !a
# which rubyists like to write as
a = b unless a
# or as ternary
a = a ? a : b

Honest question: what else can they do anyway? They cannot fight this war alone.

Little bit disappointed that its not

::: spoiler Arch :::

TL;DR do not use ==

Not sure about the situation in Norway, but Switzerland has a quite right-conservative government and is also expanding their surveillance , e.g. Proton freezes Swiss investment over surveillance fears

This noob even forgot zero

Even the bugged release version from 2077 was better than reality