Looking into the future of Linux

Looking into the future of Linux

by Tom Adelstein


Advances in desktop Linux are developing along two trend lines -- one for adoption and the other for innovation. The rate of adoption for Linux shows steady growth at a constant rate. However, technological advances can have an unpredictable impact on adoption -- and cause exponential growth.

Analysts agree on the current rate of adoption within the enterprise and among consumers and predict a minor dent in market share. Some analysts forecast that now that Linux has surpassed Apple's market share, it will take a six percent share over the next two years. Given conventional wisdom, those predictions seem reasonable.

(Click for larger view of the screenshot)

The disruptive nature of technological innovation throws these estimates out the window. While analysts can reliably make predictions from trade shows and vendor presentations, they are merely reporting proprietary trends in a closed environment. Taking into account open development projects bourne out of IBM, HP, Sun and the community, the world of open source quickly can take on a different hue.

Among the many innovations currently evolving in the GNU/Linux space, significant advances in interoperability among platforms such a single logon to Active Directory and even applications as mail and calendaring applications such as Lotus Notes and Microsoft Exchange interoperate with Linux. File managers can now visually detect Windows and UNIX hosts on a network. Device management to enhance hardware driver support, too, allows Linux to become a more supportive hardware platform than rivals.

Another key area of advancement in open source is visual. As digital convergence comes to fruition, the move toward an open environment for entertainment took a major leap when Sun Microsystems released Project Looking Glass under the GPL. The Santa Clara-based company's three-dimensional desktop environment has received great praise and attention for modernizing the look of the desktop.

In just a few short weeks, Project Looking Glass (lg3d) went from a fascinating trade show demo to something developers could bring to mass consumption.

Today, the open source project runs on Fedora, Red Hat, SuSE and Sun's Java Desktop System. It works in 64 bit and 32 bit environments. Time to market is on a fast track as new developers have migrated to the project.

One of the major contributors and proponents of Project Looking Glass, Ricardo Wagemaker of GCCLinux.com, supports its use in manufacturing, medicine and biometrics, however his world revolves around entertainment. His goal is to make Linux the quintessential entertainment platform from gaming to advanced viewing.

Tom Adelstein caught up with Ricardo to discuss his views, and news about the project . . .

  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
Code inspection, also known as code review, is the process of reviewing source code to identify potential errors, bugs, security vulnerabilities, or other issues. Here are the steps involved in a typical code inspection: 1. Planning: The first step is to plan the code inspection. This involves identifying the objectives of the inspection, selecting the reviewers, and scheduling a time for the inspection. 2. Preparation: The next step is to prepare for the inspection. This involves sending the source code to the reviewers ahead of time, along with any documentation or specifications that may be needed. 3. Review: During the review, the reviewers examine the code line by line, looking for errors, bugs, security vulnerabilities, or other issues. They may use tools such as debuggers, syntax checkers, and code analysis software to help them identify problems. 4. Discussion: After the review is complete, the reviewers discuss their findings with the developer or development team. They may ask questions, seek clarification, or suggest ways to improve the code. 5. Correction: Once the issues have been identified and discussed, the developer makes the necessary corrections to the code. This may involve fixing bugs, optimizing performance, or improving security. 6. Verification: After the corrections have been made, the code is re-inspected to ensure that all issues have been resolved. 7. Documentation: Finally, the results of the inspection are documented for future reference. This may include a summary of the issues found and corrected, as well as any recommendations for improving the development process. Overall, code inspection is a critical component of software development that helps to ensure that code is high-quality, secure, and free from errors and bugs.

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值