these works are really gems, but this type code is very strange, and not useful for standard situation.
AI devs will take more "normal and useful" code for learning their products than these "noisy and hard-reading" code.
Yeah I remembered same thing. btw Futaba channel (mama 4chan) has different lifespans to drop thread on each board. (ex. img.2chan.net drops thread in 1hour). Just an idea.
As a native Japanese, I can tell you that is true. There are many types of Japanese paintings, but the most popular is ukiyo-e. And I can't think of a more famous ukiyo-e work than "Great Wave". Therefore this is considered the most famous Japanese painting.
If asked to choose one ukiyo-e as an illustration for a banknote, almost all Japanese would choose this work. (Especially considering that the back of the banknote, i.e., a landscape, is required)
Although less famous than "Great Wave", however there are still works that are comparable to it. "Yakko Edobei" by Sharaku is one of them, and it's the most famous ukiyo-e portrait work.
I more or less agree with the author that "programming paradigms are becoming practically the same as programming styles", but even so, some languages have core features that cannot be replicated by mainstream "multi-paradigm" languages, and then that I can call them as the Next Paradigm.
An example is dependent types. This is impossible in all the languages the author mentions in the article (yes, well, GHC Haskell comes close), but there is at least one "21st century general-purpose language" that uses it, called Idris.
The probe is expected to operate during lunar daylight, i.e., until 2/1. (Note the main mission of SLIM is a "pinpoint landing" and the observation by the probe is just a bonus.)
During the remaining three days, JAXA has announced that they will focus on optical observations of the surrounding environment (specifically, some rocks in the surrounding area).
So it is hard to imagine they will do this hard schedule of risky additional operations to restore the attitude.
> Now, if your product is something for which nobody needs support or consultancy, you risk having the MongoDB-Amazon issue.
...So, that is the problem isn't it?
Basically, well-written software and documentation are meant to reduce the amount of support and consulting needed by users.
Assuming your point is true, then for a company that sells support and consultants, enriching documentation, etc. would be an action in direct conflict with its own interests, wouldn't it?
The MongoDB people are very passionate and have built a great software, documentation and user community... to the point where they no longer need to sell their own support. Therefore, it is my understanding that Amazon has decided to use their "support".
(If you're saying that it doesn't matter to the users if the company lives or dies when there is already functioning software and community, that may be true)