easy to understand and use for everyone. you no longer need to spend tons of time teaching junior devs how to use git. By default mercurial also doesn't let you change history. There's no staging area or indexing before the commit. The gui and commands make total sense to the layman.
Git is definitely more powerful but causes more damage than good and wastes more time in most workplaces who are just looking for some simple version control and branching/merging features.
NetBeans was my go-to IDE until I started working with Kotlin, which more or less forced me over to IntelliJ. I’ve also tried VSCode on some pure Java/Maven projects since then, and found that it shares some of that same feel—more lightweight and direct, which I’ve always quite liked.
They're a hominid and belong to our species but are completely alien and terrify humans at a deep, genetic, evolutionary level. I love the way Watts describes Siri's involuntary reaction to the vampire, as though his fear and awareness of being viewed as little more than a potential meal are baked into his biology.
Similar to a newborn duckling that instinctively hides from shadows of a certain shape even though it has no concept of birds of prey, Siri experiences, when he interacts with the vampire, some similarly ancient, autonomic memory from the time when our ancestors were prey animals. We become little more than flighty, paranoid herd animals, jumping at the merest snap of a twig, like deer, when we find ourselves in the presence of an animal that flips the appropriate switch in our biology.
It's a wild, compelling subversion of so many sci-fi tropes and so much self-congratulatory tree-of-life bullshit and so much of our instinctual belief system regarding the way we fit into the world. It's also a completely novel (as far as I know) approach to undermining the notion of humanity's specialness, highlighting the fact that we're just animals -- and that our betters are, too, just as the invading aliens are, in a very different way.
I can later (short on time this morning), and I plan to add diagrams to the website and a video discussing it.
Basically, the rook, assuming the spaces are open and he and the rook havent moved, either moves adjacent to the king (if he isnt already adjacent) and the king moves two spaces around him.
Prior to that they had an 'economic miracle' from WW2 till then which is probably more what people refer to. The lost decades are quite easy to understand with conventional economics - they had a property and stock bubble which got everyone left with huge debts when it collapsed.
You have a point, for sure; the _whole_ previous century (couple centuries, even) of Japan economical history is one-of-a-kind (as is Argentina’s).
However, wtr. “lost decades are quite easy to understand with conventional economics”: that’s more debatable. For example, stagflation is common(ly explained), but stag-deflation (as in Japan) is more unusual and has weirder effects. The US subprime crisis was also a real estate bubble (which, here also, rippled to the financial markets), but its burst had quite different fallouts.
Anyway, thanks for adding to the discussion, and disclaimer: IANAE (I Am Not An Economist — thanks God ^^)
When the pattern `[Posn(x, y), ...]` matches a list of positions,
since `Posn(x, y)` is followed by `...` the `x` is bound to a sequence of first coordinates and `y` is bound to a sequence of second coordinates.
In the template the `Posn(y, x)` is followed by `...` so the same number of positions is produced as the common length of x and y.
Your version would expect a list of two elements, you use & to indicate that you're collecting the remainder of the list as in:
fun flip_all([Posn(x, y), & rest]):
You'd need to amend the logic of the function body to iterate or recurse over the remainder. You'd also ended up with a nested list using your version but you can use & again to splice in the result, so if you wanted a recursive version of that it would be something like (skipping the base case):
OO in Perl is lower level compared to Java or C++, so e.g. instead of having a class construct, you have to simulate a class - typically by binding (blessing) a data structure to a namespace. Then any functions in the namespace become methods that can be called via the data structure (object).
In practice, this has turned out to be a mixed blessing because of how tedious it is to do this repeatedly. So over the years there have been many libraries created to make this easier, each with different features.
There's currently work underway to modernise Perl's built in OO to address these problems.
On the other hand, this makes some things easier, e.g. Design by Contract can be added to Perl just by writing a library.
Another example, adding traits to PHP required updating PHP itself, whereas in Perl there are libraries to do that.
reply