The ISC license is a simplification of the MIT/BSD licenses made possible by the universal adoption of the Berne Convention. Anyone who isn't doing GPL should choose the ISC license. There's also Apache 2.0 if you want to want to support FAANG in their efforts to weaken software patent holders.

What is your project? If it's possible for people to "steal" the whole thing and sell it then why do you intend to put it into the public domain? The open source code I write has less than zero economic value. If someone ever found a way to sell my work I'd be thrilled because then I could copy their tactic and convince their customers to become my customers.

"What is your project? If it's possible for people to "steal" the whole thing and sell it then why do you intend to put it into the public domain?"

It is a visual programming language bundled with an IDE.

And since code is just information, anyone can copy it and claim as theirs - like with everything immaterial. Licensed or not.

I would be just concerned, if people could legally claim ownership of it, whith public domain.

Like Blockly? Have you considered offering it as an online service? Then you don't need to publish the code and at all and there's no problem.

With public domain, the public owns it. So even though it would be kind of slimy, they would be well within their rights to claim ownership over your work, because you gave it to them. The fact that you feel this way, would make me not believe a public domain accreditation coming from you btw. In fact, maybe it isn't slimy at all. Consider classical musicians. They own their performances of Mozart. If someone takes what you've built and pull through on the execution to turn it into a profitable product, then they're basically doing the same thing. They earned the income.

So the biggest concern with using someone's work, on the path to success, is making sure that it's being used in accordance with their intentions. Since otherwise the moment you start pulling in money those people will turn around and sue or generate bad press or gossip. Licenses protect your users rights. That's why you need one. Since otherwise no one's going to use your work.

No, actually a bit more advanced than blockly (in my opinion). But something in that direction.

"Consider classical musicians. They own their performances of Mozart."

But they do not own the composition. I do not think the compiling can be viewed as performing, but I am not a lawer.

And I do want to publish the code.

I didn't say anything about compiling. What do you hope to gain by publishing the code? I'm assuming you've written GUI code? GUI code usually isn't a work of art.

Erm. How could a visual language work with only gui code? I've written all sorts of code. Compiler, database, visual framework etc.

And what do I hope to gain by publishing it and not keeping it proprietary? Well, a better world obviously. So idealistic reasons.

Well, "making the world a better place" is surely subjective. The taliban and the nazis want to make the world "better", too. And Terry Davis was a racist theocratist and had serious mental issues, so I think this is what lead to his sad ending, not that he choose the public domain for templeOS. And I think my ideals are more align to what is commonly accepted as "good".

And more details about my project I will share, once it is released. I just have to make up my mind about the licence and do a screencast.

Why is ISC better than MIT? I don’t think I’ve ever seen it used before.