How will fixing only C part work with the "do not break user space" policy?
How will fixing only C part work with the "do not break user space" policy?
Posted Jun 25, 2024 8:42 UTC (Tue) by b7j0c (subscriber, #27559)In reply to: How will fixing only C part work with the "do not break user space" policy? by pbonzini
Parent article: Rust for filesystems
treating the migration to Rust as inevitable feels like magical thinking, same as Mozilla experienced with Servo
Posted Jun 25, 2024 10:42 UTC (Tue)
by pbonzini (subscriber, #60935)
[Link] (5 responses)
Posted Jun 25, 2024 11:57 UTC (Tue)
by pizza (subscriber, #46)
[Link] (2 responses)
In other words, "The inevitability of Rust becoming a requirement to build a usable/useful kernel."
...All it takes is one driver (not even subsystem), and *BAM* you're now a Rust system with a (substantial) pile of C.
(Or rather, "kernel-Rust" with a pile of "kernel-C")
Posted Jun 25, 2024 12:13 UTC (Tue)
by Wol (subscriber, #4433)
[Link] (1 responses)
> In other words, "The inevitability of Rust becoming a requirement to build a usable/useful kernel."
Which, if the claims of the speed with which good solid drivers can be written in Rust are true, is inevitable sooner rather than later ...
I remember reading somewhere, that the speed at which a good programmer could produce good code was measured in LoC, REGARDLESS OF THE LANGUAGE USED. In other words, measured in terms an end user could understand - what a system could do - the choice of language has a major impact on productivity.
Cheers,
Posted Jun 25, 2024 17:20 UTC (Tue)
by NYKevin (subscriber, #129325)
[Link]
This is less surprising than it sounds. It basically amounts to "higher level languages allow programmers to write code that does more elaborate things in the same amount of development time," which had darned well better be true considering all of the performance cost of e.g. Python. If Python didn't give you a development speed advantage, there would be no (or at least much less) reason to use it for serious purposes (outside of the classroom).
Posted Jun 25, 2024 15:23 UTC (Tue)
by b7j0c (subscriber, #27559)
[Link] (1 responses)
open source projects are different...volunteers can just move on if they are unhappy, and if you don't have suitable replacement volunteers, things stop happening
Posted Jul 4, 2024 2:13 UTC (Thu)
by mrugiero (guest, #153040)
[Link]
How will fixing only C part work with the "do not break user space" policy?
How will fixing only C part work with the "do not break user space" policy?
How will fixing only C part work with the "do not break user space" policy?
Wol
How will fixing only C part work with the "do not break user space" policy?
How will fixing only C part work with the "do not break user space" policy?
How will fixing only C part work with the "do not break user space" policy?