user门户

常见问题解答

中小企业如何把握机遇？

对于中小企业而言，建议从以下几个方面入手：To put all this in the right context, let’s zoom in on the copyright's actual perimeters: the law says you must not copy “protected expressions”. In the case of the software, a protected expression is the code as it is, with the same structure, variables, functions, exact mechanics of how specific things are done, unless they are known algorithms (standard quicksort or a binary search can be implemented in a very similar way and they will not be a violation). The problem is when the business logic of the programs matches perfectly, almost line by line, the original implementation. Otherwise, the copy is lawful and must not obey the original license, as long as it is pretty clear that the code is doing something similar but with code that is not cut & pasted or mechanically translated to some other language, or aesthetically modified just to look a bit different (look: this is exactly the kind of bad-faith maneuver a court will try to identify). I have the feeling that every competent programmer reading this post perfectly knows what a *reimplementation* is and how it looks. There will be inevitable similarities, but the code will be clearly not copied. If this is the legal setup, why do people care about clean room implementations? Well, the reality is: it is just an optimization in case of litigation, it makes it simpler to win in court, but being exposed to the original source code of some program, if the exposition is only used to gain knowledge about the ideas and behavior, is fine. Besides, we are all happy to have Linux today, and the GNU user space, together with many other open source projects that followed a similar path. I believe rules must be applied both when we agree with their ends, and when we don’t.

技术成熟度如何评估？

根据技术成熟度曲线分析，2025年7月生效的《企业管治守则》（联交所《上市规则》附属章节）修订版，在以下关键领域提出了更为严格的要求：提升董事会效能、强化董事会独立性、推动多元化、加强风险管理与内部监控。这些修订的方向无疑是正确的，但它们更多是“制度设计”层面的完善，而非“责任落实”层面的突破。独立董事在“承担责任”与“成为逃兵”之间的两难困境，从根本上仍未得到解决。