Nonsense like this is why the #OpenLDAP Project has always discouraged using any forums other than the official OpenLDAP mailing lists. The true subject matter experts of open source projects don't use 3rd party for-profit forums. https://mastodon.social/@trisweb@m.trisweb.com/112396412105342949 We also maintain a presence on IRC but since that isn't archived or searchable, it's still an inferior choice.
Independent projects must own all of their data. Information you give to Stack Exchange, Quora, etc doesn't belong to you.
Unfortunately constructors are pretty much the safest way to do library init, especially in a threaded program. And you could do all kinds of mischief in a destructor too, running long after privilege checks were done.
@niconiconi imo a language spec should define only the language syntax. Nice-to-have libraries are no different than anybody else's code written in that language.
The only reason you ever needed to define a standard library for C (or C++) and its behavior is because companies were selling language implementations without library source code. If your syntax spec is solid and your compiler is correct, then you just need to provide library source code and everyone will get the same behavior.
@niconiconi but it's obvious there is a right and wrong in that argument. C used to be a language that could be implemented in itself, but isn't any more. It is now broken, because the spec makes it illegal to write functions like memcpy() in user code; they're only legal in the specially blessed standard library, which gets to ignore some of the braindead typing rules. When your language spec only works via special case exceptions to the rules, it's a broken spec.
@tweedge I had a similar experience a couple months ago looking for a new laundry washer & dryer - all the latest models had wifi. Why the hell would my washing machine need wifi? I bought the model from a couple years previous, with no smart features.
@jbhall56 there's a simple solution to the proliferation od commercial data brokers selling your personal information: 1) acknowledge that your personal information is your property. This is just common sense.. 2) impose an automatic mechanical royalty of not less than 70% of gross revenue for any company selling your information. 3) any entity that doesn't pay your royalty is guilty of trafficking stolen property, and liable for all the associated penalties.
@jbhall56 the 70/30 split is justifiable since the owner is the actual creator of the product. If one broker can't make sufficient profit from selling your data, some other one will. Free market at its best.
Likewise, if you want to display ads on my computer, then you must pay me for the network bandwidth, memory, and CPU time consumed in delivering and displaying your ad on my systems. You've all been using my compute resources for free, that has to end.