Statement Regarding the Zen Programming Language

As a Japanese-speaking software engineer, I found that the company, connectFree, did too many suspicious acts as below:<p>- They are attempting to register &quot;ZIG&quot; [1] and &quot;SiFive&quot; [2] as trademarks in Japan. Only this is enough for me to see them as a trademark troll.<p>- Since Zen is a fork, Zen comes with Zig&#x27;s (or its derived version of) standard library, but when they copied Zig&#x27;s library source files, they removed the original copyright notice from each file header and replaced with &quot;Copyright (c) 2018-2020 kristopher tate &amp; connectFree Corporation.&quot; Sure, because it&#x27;s MIT license, you can relicense, but is replacing the original copyright notice OK? Even if it&#x27;s OK, why did they do that?<p>- I once attended a meetup where the CEO of connectFree, Kristopher, gave a presentation about Zen. He gave many reasons to use Zen, but most of them were Zig&#x27;s features. Until someone pointed out in the meeting, Kristopher didn&#x27;t mention or even imply that Zen is a fork of Zig. Many of my friends didn&#x27;t actually know until this statement was made that Zen is a fork of Zig.<p>- connectFree recently published license terms for Zen (perhaps only in Japanese), and in the license they claimed that you are required to obtain a paid license to distribute a program even in the source code form as long as the program is written in Zen. I can&#x27;t believe that you are able to force it, and it looks like Kristopher retracted the license later, but at least they tried to do that once. And you still need to buy a license to distribute a program in binary form if it&#x27;s written in Zen and compiled with connectFree&#x27;s Zen compiler.<p>[1] <a href="https:&#x2F;&#x2F;www.j-platpat.inpit.go.jp&#x2F;c1800&#x2F;TR&#x2F;JP-2020-078615&#x2F;FF75D797BF8A8562102A23936240FF60A15248A6D91AF8F8F1D741CC24A962DD&#x2F;40&#x2F;ja" rel="nofollow">https:&#x2F;&#x2F;www.j-platpat.inpit.go.jp&#x2F;c1800&#x2F;TR&#x2F;JP-2020-078615&#x2F;FF...</a> [2] <a href="https:&#x2F;&#x2F;www.j-platpat.inpit.go.jp&#x2F;c1800&#x2F;TR&#x2F;JP-2019-153075&#x2F;A707749AD6C41F384D8CED6C08A74E7898E52A3D0239F66CE1A12E89F0D927DB&#x2F;40&#x2F;ja" rel="nofollow">https:&#x2F;&#x2F;www.j-platpat.inpit.go.jp&#x2F;c1800&#x2F;TR&#x2F;JP-2019-153075&#x2F;A7...</a>

As somebody that just got into Zig and loves the language, it makes me super sad that the developers on this project have to spend their valuable time stressing about BS like this.<p>Also, the ideas the Zen people list on their website for forking Zig are terrible ideas- They were pushing to turn Zig into a hard-to-reason-about vanilla object-oriented programming language.

Probably the strangest part of this is a person trying to sell a paid version of a compiler. Did that person miss the boat by 30 years? All mainstream programming languages today are free and open source. Programming languages are platforms that thrive only when they&#x27;re widely adopted. The community that adopts it builds the libraries and ecosystem necessary for it to be viable. You can&#x27;t possibly build a new platform with a high barrier to entry if you&#x27;re competing with established platforms where the barrier to entry is next to nothing.

Something which people don&#x27;t always recognize about open source is how &quot;value-capture&quot; works for creators. FOSS eschews direct monetization (selling licenses to the core product) based on an ethical premise (it&#x27;s unfairly limiting to end-users) and&#x2F;or a business premise (the ecosystem is a key to the value prop and licenses would slow down the ecosystem growth).<p>None of that means that the creator isn&#x27;t capturing value. You capture social credibility and market awareness which you can convert in a variety of ways, including monetarily (by selling complementary products&#x2F;services, by donation models, or by getting a job that you might not have had the career-credentials to get otherwise). As an aside to elaborate on this point: a lot of the recent debate about paying FOSS maintainers has to do with projects which realized all the potential social value-capture, and left creators with an externality of maintenance.<p>Intuitively, I think people understand that forking and rebranding a project without a really strong motivation can be scummy, but I don&#x27;t think people can verbalize why. This is why: you&#x27;re attempting to steal the upside which the creator is the in the process of capturing.<p>And FWIW, anybody saying that a blogpost is weak action and you ought to be going to court is ignoring that, when the value you&#x27;re capturing is reputation, then public discourse is the tool you want to be using to manage it.

I just want to say that I really admire and support what Zig is trying to do here. It takes guts to try to launch an ecosystem from a fun hobby to something that can be used in production and hopefully sustain its contributors. They&#x27;re not there yet, but it looks like they may well be on that journey.<p>This thing looks very unpleasant, but hopefully it conveys the message that Zig is potentially valuable. Figuring out how to fund such a project and organize the community is a hard problem, and again I wish them well in finding a good path.

This is why you always use GPL

Kristopher Tate - he wrote a photo hosting competitor to Flickr way back during the Techcrunch heydays called ZOOOOMMER.

I wonder why they decided to go with the MIT license rather than GPL or something similar. Choosing GPL would protect the project from situations like this, attract more contributors, and have no impact on commercial usage of the language itself.

MIT license allows it, so where&#x27;s the problem. It&#x27;s like people who support freedom of speech, and then cry anytime someone used it to say something they don&#x27;t like.<p>Some of the wording there sounds petty. &quot;whose founder uses flawed technical arguments&quot; rubs me the wrong way. Like &quot;The science on this is settled and everyone who ever disagreed should be personally discredited&quot; kind of thing.<p>Having said that, I don&#x27;t know why would anyone sane tie their codebase to a closed source language owned by some random company. I don&#x27;t understand why Zig Foundation even bothers with this - seems like it is just giving publicity to something that has little to none chance of gaining market traction anyway.

Relevant: <a href="https:&#x2F;&#x2F;github.com&#x2F;ziglang&#x2F;zig&#x2F;commit&#x2F;3ca4925709ac6369391eb40616de33051e0bb1f1" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;ziglang&#x2F;zig&#x2F;commit&#x2F;3ca4925709ac6369391eb4...</a>

Massive Streisand effect here. The Zig project should just completely ignore this. There is no way this Zen thing is going to go anywhere. Nobody in their right mind would pay for anything of the sort in the year 2020.<p>Come on, &quot;a licensing model for the Zen compiler that requires software developers to buy a yearly subscription to distribute compiled releases of their code&quot;. That has to be a joke?

All this drama reminds me of the business culture of Japan, building walls around their gardens, growing stuff with seeds from public parks while having unethical work policies for gardeners.<p>The entire problem of Japan is that they specialized in perfecting what others invent, which can only take you so far.<p>If companies want to fork Zig and distribute it commercially in such an early stage, then Zig is doing something right.

Seems like legit? <a href="https:&#x2F;&#x2F;zen-lang.org&#x2F;zig&#x2F;" rel="nofollow">https:&#x2F;&#x2F;zen-lang.org&#x2F;zig&#x2F;</a>

I&#x27;m sad to hear that the Zig community is burdened by this. I&#x27;ve filed a couple proposals there, and hope to use it post 1.0.<p>But what a PR opportunity! Here&#x27;s an outfit selling Zig (because it&#x27;s good enough already), which won&#x27;t even hit 1.0 for &quot;two years&quot; \o&#x2F;<p>(&quot;Two years&quot; is from Andrew on a recent podcast.)

Can someone please explain why Zen&#x2F;Zip is focused on Japan? I feel I might be missing some context.

This looks like a complete mess.<p>Are there examples in today&#x27;s market where a business can depend on a new programming language? I&#x27;m curious because I&#x27;m writing a programming language, and I&#x27;d love to turn it into a business.<p>edit: add &quot;new&quot; to programming language

Qn. Why do you think providing a compiler&#x2F;support for a totally unproven language (for embedded) is a good business model?!

for great justice. take off every zig

I don&#x27;t understand why the Zig developers are getting so stressed over this. So a company forked your open source project. If you are worried about closed source forks use GPL. If you are worried that people will confuse Zig with Zen just post a warning. Honestly, I don&#x27;t understand why they are comparing source code and dragging three people into it.

Hello HN and sorry for this bizarre drama!<p>Although we have a page documenting some outlandish comments that the founder of Zig has made about Zen[0], we find it well inside of our rights to fork the MIT Licensed Zig and make a better product with commercial support.<p>We had initial plans to support Zig in Japan, but efforts to localize Zig were not accepted and we could not take the risk of not having some sort of formal role.<p>Regarding commercializing compilers: our main market is in embedded and as others have pointed out, charging for compilers and support is not uncommon.<p>One of our big main differences between Zig is that Zen natively supports vtables and traits that we call interfaces[1].<p>Although our core market is in Japan, we are preparing our English website and hope to have it out soon.<p>On a more personal note, I am happy that Zig is growing and that they got the foundation together. At the peak before the fork, I was the 5th largest contributor to Zig, so I am very happy to hear when people say that they are enjoying the language.<p>It&#x27;s midnight in Japan, but I will try to field questions if any.<p>[0] <a href="https:&#x2F;&#x2F;zen-lang.org&#x2F;zig&#x2F;" rel="nofollow">https:&#x2F;&#x2F;zen-lang.org&#x2F;zig&#x2F;</a> [1] <a href="https:&#x2F;&#x2F;www.zen-lang.org&#x2F;ja-JP&#x2F;docs&#x2F;ch06-interface&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.zen-lang.org&#x2F;ja-JP&#x2F;docs&#x2F;ch06-interface&#x2F;</a>