...many "things" are left undefined, unspecified, implementation-defined, etc. However, that's easy to say and even to give examples of, but hard to fix. It should also be noted that it is not all that difficult to avoid most of the problems and produce portable code. ...

...r because you do not need to worry about static, final, empty constructor, etc, and it will NOT cause any bad design issue. The only downside I can think of is that it still has the name of "interface", but nothing more than that. Never-ending debate At the end, I think everyone is just quoting from...

...s some sort of normal axes instance, where I can add a title, axis labels, etc. and then do the normal savefig() like I would do for any other typical matplotlib plot. – gotgenes Jul 15 '11 at 19:19 ...

... Merkle Trees, at least within the bitcoin and ethereum communities, IPFS, etc. – Duke Apr 21 '16 at 20:50 1 ...

... with an API of >100 classes, a different formatting/parsing mechanism etc. Of course, if you do need complete representation of different chronologies (e.g. Hebrew) or wish to be able to define your own imaginary Calendar system (e.g. for a game you are writing) then perhaps JODA or JRS-310 is...

... but not create (don't know why!). A post might be able to Create and Read etc. A group of managers might have the editor role, while a user in IT, who is not in the managers group, may also have the editor role, even though the rest of his or her group does not. So while in a simple system groups...

...e history from the "origin" - meaning to delete it from GitHub, Bitbucket, etc - you'll need to delete the repo and re-push a pruned copy of the repo. But wait - there's more! - If you're really concerned about getting rid of a password or something like that you'll need to prune the backup (see bel...

...like commenting, less verbose quotes, and the ability to write expressions etc. – Steve Bennett Sep 3 at 0:14 add a comment  | 

...Pollob sometimes mistakes happens. When you write a lot of code, ifs/elses/etc. You may forget ```return next()` – Jone Polvora Jul 25 '19 at 16:45 add a comment ...

... discarded, because it's lazy. You have to use one of doseq, dorun, doall etc. to force evaluation of lazy sequences for side-effects. user=> (defn foo [] (doseq [x [:foo :bar]] (println x)) nil) #'user/foo user=> (foo) :foo :bar nil user=> (defn foo [] (dorun (map println [:foo :bar])) n...