Finite element method Updated 2025-07-16
TODO understand, give intuition, justification of bounds and JavaScript demo.
KIPP Updated 2025-07-16
Magic: The Gathering is too expensive Updated 2025-07-16
Ciro thinks this is idiotic, and that Wizards should sell all cards individually with unlimited supply and all with the same prices, especially online where there are no printing costs. But because Wizards made the silly promise never to reprint certain cards with the reserved list in 1994, they can't even correct this mistake legally! (TODO maybe, see further discussion at: www.mtggoldfish.com/articles/contract-from-below-promissory-estoppel-and-the-reserved-list). There is however one simple solution: create and promote a new no reserve list format, and let reserve list formats rot away:
One interesting outcome of this would be to have card cost limited formats. Penny Dreadful puts a super low limit, on individual cards, but it would be cool to have a max cost per deck version of it.
A cool thing is when they printed Garth One-Eye, which allows you to make imaginary copies of some of those restricted list cards during play. This is the type of "flirting with the rules", that Ciro Santilli admires. The introduction of online-only cards such as XXX has pushed that even further as of 2021.
This was especially insane when Ciro was young and the Internet was not very widely available in Brazil yet, and Ciro did not know how to check the values of cards on online markets, and would trade cards with older much more knowledgable teenagers, based solely on his appraisal of a card's strength! Can you imagine how many young Timmys got ripped off in this manner, trading useless one million mana spells for ultra expensive black lotuses?
There is however one good solution to Magic's insane cost: watch people who have nothing better to do in their lives play on YouTube.
And as Internet formats dominate more and more, if they have any brains at will they will migrate to a subscription model where you pay to play for a given period of time, and have immediate access to all cards. It could even be a tiered access, with older formats being more expensive (more bugs to fix on different cards), but you must get access to all cards of a format at once.
Video 1.
The Tarmogoyf Scandal by Nikachu MTG (2021)
Source.
Markdown Updated 2025-07-16
The questions are: who is this Mark, and why does he have to go down?
Division Updated 2025-07-16
Fatty acid Updated 2025-07-16
Horrors of open source Updated 2025-07-16
Not everything is perfect.
One big problem of many big open source projects is that they are contributed to by separate selfish organizations, that have private information. Then what happens is that:
  • people implement the same thing twice, or one change makes the other completely unmergeable
  • you get bugs but can't share your closed source test cases, and then you can't automate tests for them, or clearly demonstrate the problem
  • other contributors don't see your full semi secret important motivation, and may either nitpick too much or take too long to review your stuff
Another common difficulty is that open source maintainers may simply not care enough about their own project (maybe they did in the past but lost interest) to review external patches by people they don't know.
This is understandable: a new patch, is a new risk of things breaking.
Therefore, if you ever submit patches and they get ignore, don't be too sad. It just comes down to a question of maintenance cost, and means that you will waste some extra time on the next rebase. You just have to decide your goals and be cold about it:
  • are you doing the right thing and going for a specific goal backward design? Then just fork, run as fast as possible towards a minimum viable product, and if you start to feel that rebase is costing you a lot, or feel you could get some open source fame for cheap, open reviews and see what upstream says. If they ignore you, politely tell yourself in your mind silently "fuck them", and carry on with the MVP
  • otherwise, e.g. you just want to randomly help out, you have to ask them before doing anything big "how can I be of help". If I propose a patch for this issue, do you promise to review it?
Writing documentation in an open source project in which you don't have immediate push rights is another major pain due to code reviews. Code code reviews tend to be much less subjective, because if you do something wrong, stuff crashes, runs slower, or you need more lines of code to reach the same goal. There are tradeoffs, but in a limited number. Documentation code reviews on the other hand, are an open invitation to infinite bike-shedding, since you can't "run" documentation through a standardized brain model. Much better is for one good documenter person to just make one cohesive Stack Overflow post, and ping others with more knowledge to review details or add any missing pieces :-)

There are unlisted articles, also show them or only show them.