I think this is the important question. I've been searching, but all I found were deprecated and incomplete projects. If anyone knows some actual current development, even incomplete ones, let us know.
I want the same. The problem is that this kind of tool is outside the T&C of the platforms, and if they catch you using it, you would probably be banned or suspended. There will be always a small risk of that.
Ok, I'll see it later but please use the 'Release' feature of GitHub. It is the easiest way to tell for your customers that a new release is out. Even GH can send notifications. Thanks.
Summary: "Across 16 experiments with over 27,000 participants, we show that people tend to evaluate creative writing
less favorably when they believe it was written by artificial intelligence (AI), because they see it as less
authentic than if a human author had produced the exact same work without AI. This bias is persistent and
difficult to reduce, even when using techniques that mitigate aversion to AI in other contexts."
In a move that reminiscent of the change of Redis, they removed all the functionality of the UI of the community version and pointed to the paid version.
"Deprecated support of accounts & policies management, this can be managed by using mc admin commands.
Deprecated support of bucket management, this can be managed by using mc commands.
Deprecated support of configuration management, this can be managed by using mc admin config commands. Please refer to the MinIO Client for more information.Deprecated support of accounts & policies management, this can be managed by using mc admin commands.
Deprecated support of bucket management, this can be managed by using mc commands.
Deprecated support of configuration management, this can be managed by using mc admin config commands. "
The advantage of the original approach is that later, when you need it, you can just add more methods to a class that are private to them. In your approach, if you need a new function, you add it at the global level, which can totally be fine for one or two functions, but with any more you end up with a bunch of functions all at the same level that is no longer obvious the dependency between them.
... This is particularly idiomatic for higher order functions, but I think it can be useful for other things if used with restraint.
But if you have functions that only need to be called from one calling function then I why not just inline the code and eschew having a function at all. Long function bodies for the win!
Yes, perhaps I wasn’t clear — I’m advocating for just the inlined version, not the nested function in the general case.
The nested function is, I think, fine when it’s so tiny it’s not worth unit testing (like, it-could-have-been-a-lambda small) or when bar is returned by foo (ie foo is higher order), in which case you can test the return value. Apart from that… restraint!
reply