924 karma · joined December 13, 2022
The advantage is that one can go in and modify any aspect of build process easily, provided one takes care to remove cruft so that the Makefile does not become huge. This is very important for embedded projects. For me, the advantages have surpassed the drawbacks (which I admit are quite a few).
You could, in theory, abstract much of this common functionality away in a library (whether for Make or any other software), however properly encapsulating the functionality is additional work, and Make does not have great built-in support for modularization.
In this sense I would not say Make is overly complex but rather the opposite, too simple. Imagine how it would be if in C global variables were visible across translation units. So, in a way, the "Makefile effect" is in part due to the nature of the problem being solved and part due to limitations in Make.
The matter is that this "freeloading" is subjective as the GPL license does not really place any contribution requirements. Matt says it is about trademarks but the court stated TMs were not violated either. Dura lex sed lex, he will have to deal with it.
I feel that there are already too many other things to fix to be wasting time in creating new potential bugs.
> In March 1988, the 'Electronic Café' was opened near Hongik University in Seoul.
> In July 1991, the SFnet Coffeehouse Network was opened in San Francisco.
> The concept of a café with full Internet access (and the name Cybercafé) was invented in early 1994 by Ivan Pope. [...] Over the weekend of March 12–13 in the theatre at the ICA, Pope ran a Cybercafé
> In June 1994, The Binary Café, Canada's first Internet café, opened in Toronto,
> Internet café called Cyberia opened on September 1, 1994, in London, England.
def or(a, b): r = a() if not r: r = b() return r
What I see is that the bot was badly programmed and it did not ignore quoted text, so the first automated report triggered another bot response which quoted the swear word which triggered the bot a third time.
I don't think it is good idea to merrily write 10s of import statements and end up with loads of dependencies.
I tried getting into C++ coroutines in the past and I was put off because of the complexity and the lack of an I/O system that was understandable by a human being.
The main problem is that v4 has not yet been retired and that means many times you have to support both.