TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Native context menus in macOS was requested 22 YEARS ago. Its released today

9 点作者 subbu将近 4 年前

1 comment

webmobdev将近 4 年前
<i>It&#x27;s open source ... there are many eyes on the code ... somebody or the other quickly identifies &#x2F; fixes the bug ... code quality of open source software is above par ...</i> etc. etc. have become something of a trope in our industry.<p>I am a big supporter and advocate of opensource software. But after so many years of both using and contributing to the opensource movement, I&#x27;ve realised that the popularity of an opensource software isn&#x27;t really a reflection of its code quality. Minix 3 and FreeBSD are better than Linux. TextPattern is &#x2F; was better coded than Wordpress. OpenSSL was insecure for so many years till its fork LibreSSL.<p>Inexperience of the early founder(s) of the project is one factor for poor code quality (that often does improve as the founder becomes more experienced and &#x2F; or other experienced devlopers contribute to the project). Documentation and testing is another.<p>But another factor is money which dictates the design of the open source software.<p>Mozilla is a good example of this - despite the millions of dollars they have received, they deliberately avoid modularising their software. Gecko, the web engine, should be available as a stand alone piece of software that anybody should be able to use to create another browser or some other application with it. But there is no easy way to do this because Gecko has been tighty coupled to the browser code. And this is very intentional - Mozilla makes it money from browsers, and hence despite working on an open source project, their code is deliberately convulated to make it harder for others to create another browser from it to compete with their product. (Yes, you can fork their existing mess, but it&#x27;s a sub-par product because of the way it is coded - you would have a really tough time creating a native UI for it, for example - and so you just end up with an imitation of their browser).<p>(And it is not as if they can&#x27;t do it - as they realised they were losing the browser wars on mobile, they&#x27;ve finally released the Gecko engine for Android - <a href="https:&#x2F;&#x2F;mozilla.github.io&#x2F;geckoview&#x2F;" rel="nofollow">https:&#x2F;&#x2F;mozilla.github.io&#x2F;geckoview&#x2F;</a> - hoping others would be motivated to create Gecko mobile browsers and they continue to remain relevant on the mobile platform).<p>SQLite is another example where the code is opensource, with the most liberal source license, but the testing code is closed and unavailable. Again a deliberate choice made to hurt any competing product created with their code, i.e. a choice dictated by commercial interests.<p>Both the above examples highlight how the open source spirit is somewhat crippled and sacrificed when a lot of money comes into the picture.