Interview with Alyssa May https://krita.org/en/item/interview-with-alyssa-may/
Yes! We've crossed 5000 euros! https://krita.org/en/fundraising-2018-campaign/
I've released my first gem!! https://github.com/mkgremillion/ByteInterpreter
And now, to get some sleep 😪
Did you install EFF's brilliant Privacy Badger or any other smart HTTP Cookie management tool? Or did you simply pick the privacy preference in your browser that ignores all third-party cookies? Did many websites you visit annoy you with permission-to-use-cookies pop-ups because of European legislation?
Guess what, it's all been useless.
@BadMinotaur Notes from when I was learning Ruby way back in the day:
- Other names for a Ruby “singleton class”: anonymous class, eigenclass, object-specific class, virtual class. Kind of a Ruby internal thing IMO: I never really used it.
- a Ruby “singleton class” (so, a Ruby internal thing) is totally different from the widespread “Singleton Pattern” that you can find in OO languages such as Java & Ruby. Classes following this design pattern are called singleton classes. Hence the confusion
@BadMinotaur People use "singleton class" and "eigenclass" to mean the same thing in Ruby. However, "singleton" is also a well-known design pattern, so probably what they mean is that a Ruby eigenclass is different from a class that implements the singleton pattern.
So, re: eigenclass. From what I understand it refers to the hidden Class instance inside the heart of every Ruby object. It is often used in place of “singleton class” but I’ve seen it said in various places that a singleton class and an eigenclass are two different things.
Anyone experienced in unofficial Ruby nomenclature want to weigh in?
Am I a minotaur that's bad, or am I someone who is bad at being a minotaur?
A Mastodon instance for Rubyists & friends