Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

我希望有linux 32位系统的包 #2160

Open
LoveDoLove opened this issue Jan 25, 2025 · 1 comment
Open

我希望有linux 32位系统的包 #2160

LoveDoLove opened this issue Jan 25, 2025 · 1 comment

Comments

@LoveDoLove
Copy link

Is your feature request related to a problem? Please describe.
Yes, the problem is that many older systems or specific hardware configurations still rely on 32-bit Linux distributions. As software development increasingly focuses on 64-bit systems, it becomes challenging to find compatible packages for 32-bit systems. This can be frustrating for users who need to maintain or use older hardware, or who have specific requirements that necessitate a 32-bit environment.

Describe the solution you'd like
I would like to see the availability of a Linux 32-bit package for your software. This would involve compiling and distributing a version of your software that is compatible with 32-bit architectures. Ideally, this package would be maintained alongside your 64-bit versions, ensuring that users of older systems can still benefit from updates and new features.

Describe alternatives you've considered

  1. Using a 64-bit system: While this is a viable option for some, it is not feasible for users with hardware that only supports 32-bit systems.
  2. Virtualization: Running a 32-bit system within a virtual machine on a 64-bit host is possible, but it adds complexity and overhead, which may not be ideal for all users.
  3. Cross-compilation: Manually compiling the software for 32-bit architecture is an option, but it requires technical expertise and may not be practical for all users.

Additional context

  • Target Audience: Users with older hardware, embedded systems, or specific use cases that require 32-bit Linux.
  • Impact: Providing a 32-bit package would extend the reach of your software to a broader audience, including those who are unable to upgrade their hardware or systems.
  • Examples: Many open-source projects still provide 32-bit packages (e.g., Debian, Ubuntu, and some specialized software), which demonstrates the ongoing need for 32-bit support in certain contexts.
@hatsuyuki280
Copy link
Contributor

hatsuyuki280 commented Feb 14, 2025

尽管无论如何都不应该假设最终用户所拥有的硬件环境和专业知识。

但咱还是觉得应该再次讨论专门提供x86/i386架构预编译版本的必要性。

以intel为例,约20年前就已经存在x86-64架构的方案了。
这意味着在约20年前就已经存在可以运行64位系统的平台了。

关于你所提到的Additional context:

  • Target Audience: Users with older hardware, embedded systems, or specific use cases that require 32-bit Linux.
  • Impact: Providing a 32-bit package would extend the reach of your software to a broader audience, including those who are unable to upgrade their hardware or systems.
  • Examples: Many open-source projects still provide 32-bit packages (e.g., Debian, Ubuntu, and some specialized software), which demonstrates the ongoing need for 32-bit support in certain contexts.

尽管通常来说20年前的设备即便至今通电依然有可能正常工作,
但咱依然很难假设会有足够数量的人会积极选择那些仅能执行32位软件的环境。

以及,尽管CPU支持x64并不意味着一定要运行64位的系统,
但在咱看来,很难想象一个专门选择了对于2025年来说相对“小众”的设备/系统的人,
或者正在折腾嵌入式设备的人,会不具有相应的技能完成交叉编译。

对于一个选择保持不升级硬件以支持64位系统/软件的人,自然是可以假设他们确实存在一些无法使用32位系统的客观条件。
但就咱的经验来说,绝大多数情况下这几乎仅会发生在银行/金融系统/政务系统等专业机构而非个人使用环境。
暂且不讨论他们完全有能力购买“技术支持”以满足一些冷门需求。
这些企业用户通常本就存在一整个运维团队,用于解决这些技术问题

这里甚至没有讨论即便是银行/金融系统/政务系统等专业机构,这些从上古运行至今的或许还在运行COBOL的IBM巨型机上的业务系统,也仅会用于核心业务,哪怕他们的决策层的所有人对于技术都是半桶水,也不会允许一个玩具被和核心业务运行在同一个实例上。

尽管咱确实承认无论如何都不应该假设最终用户所拥有的硬件环境和专业知识。

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants