That's because it's very hard to fund development of something as complex as a web browser in 2019 with nothing to fund the development other than donations.
> but they don't really mean anything in relation to the program: they're just a procedure to get the job done.
Actually, I don't think till now I've got recursion. I only see it used in bunch of places and I've understood it enough to see how it works. Not quite sure, how it should click for me?
> A typical ELK deployment has logstash and kibana as well.
Now that we have tools like docker-compose, would it not be possible to spin up all the dependency apps in a single command, so as to preserve the character of a monolithic app?
I think the simplest way to understand recursion is as a for loop where you use the stack as the counter.
Recursion is basically implementing the operations of a repetitive loop but the loop controls are not explicit like in a for loop, instead you use the stack as the counter of the loop.
Once you think of recursion as just another way to do for loops, it immediately is demystified.
> XML and especially XML schema are hugely complex and almost laughably difficult to bind
I'm not very well versed in XML schema but if it were needlessly complex, it's probably not a good idea to throw baby out with the bathwater?
XML seems more type safe, easier to fold larger XML documents than JSON or YAML and it seems safer to edit.
Looks like, we're now reinventing all the XML advantages with a new config language, one at a time.
First, JSON came because it looks simple at first sight, but looks hard as soon as the JSON is huge, no different or better than XML, in fact, probably worse.
Then YAML appeared because, now it even allows you to add comments to config files, but it's a nightmare to edit, one wrong indentation and the YAML will blow up at runtime.
And looks like, we're now coming up with other languages to add in the missing functionality that XML already provided.
It's an interesting thing that with the emergence of cloud computing, we get so many open source library and tooling almost for free but all of this came at the cost of killing the market for professional desktop software.
The installers from 90s and 2000s in windows that people used, were really good at extracting config questions from the users in a very user friendly way. The cloud services today are basically hiding the installation wizard but at the cost of rent seeking as opposed to running unfettered software on your own hardware.
I never really understood this. This seems to be an oft repeated truism from mid 2000s with little backing it up.
The only awesome thing that JSON did, was lose type information as well. In fact, the only thing that I can see that JSON brought to the table was easier editing by those who didn't have IDEs, at the expense of losing type information.