2 ms·

Again, Stenberg himself seems to feel differently about what's going on than you do. From his blog post "What goes into curl?" [1]: > I’m the lead developer of

Again, Stenberg himself seems to feel differently about what's going on than you do. From his blog post "What goes into curl?" [1]: > I’m the lead developer of the curl project but I also offer commercial support and curl services to allow me to work on curl full-time. This means that paying customers can get a “priority lane” into landing new features or bug-fixes in future releases of curl. They still need to suit the project though, we don’t abandon our principles even for money. [1]: https://daniel.haxx.se/blog/2021/06/16/what-goes-into-curl/ https://daniel.haxx.se/blog/2021/06/16/what-goes-into-curl/

oscargrouch 5y ago
> Will I ever rewrite curl in rust? > I don't believe in rewrites, no matter which language. I believe in replacing code and fixing components gradually over time. That could mean that we have a curl written mostly in rust in 10 years. Or in 20 years. Or not. https://twitter.com/bagder/status/1360131939794042884 https://twitter.com/bagder/status/1360131939794042884
- geofft 5y ago
  That exactly matches the philosophy of this organization: https://www.memorysafety.org/about/ https://www.memorysafety.org/about/ > We recognize the amount of work it will take to move significant portions of the Internet’s C and C++ software infrastructure to memory safe code, but the Internet will be around for a long time. There is time for ambitious efforts to pay off. By being smart about our initial investments, focusing on the most critical components, we can start seeing significant returns within 1-2 years. > We encourage projects to replace libraries or modular functionality with memory safe libraries, rather than embark upon ground-up rewrites. This allows us to break up the work into manageable pieces and deliver value incrementally. > Since many projects will end up using the same memory safe libraries, this approach also allows us to invest and build confidence in a particular set of libraries. Investments in a library for one project will add value across multiple projects. For example - the curl project will use the Hyper and Rustls libraries. The work we do to build excellent C API wrappers and improve the integration experience will help with many projects that will use the libraries in the future.
  - oscargrouch 5y ago
    Yes exactly, it's an org that attempts to creates trojan horse implants into popular projects for gradual takeover and control of projects in the long term by the virtue of the amount of people working on it. They should be more open about it, and stop using generic words like security and memory safety for the actual corruption of those values in the form of rewriting popular stuff in Rust (apparently Apple is making followers using the safe word 'security' like politicians use 'terror' to manipulate public opinion). If it was really about security and memory safety, other memory safe languages would be among the projects and also attempts to fix memory safety issues in C and C++ would also receive grants.

oscargrouch 5y ago

> Will I ever rewrite curl in rust? > I don't believe in rewrites, no matter which language. I believe in replacing code and fixing components gradually over time. That could mean that we have a curl written mostly in rust in 10 years. Or in 20 years. Or not. https://twitter.com/bagder/status/1360131939794042884 https://twitter.com/bagder/status/1360131939794042884

geofft 5y ago
That exactly matches the philosophy of this organization: https://www.memorysafety.org/about/ https://www.memorysafety.org/about/ > We recognize the amount of work it will take to move significant portions of the Internet’s C and C++ software infrastructure to memory safe code, but the Internet will be around for a long time. There is time for ambitious efforts to pay off. By being smart about our initial investments, focusing on the most critical components, we can start seeing significant returns within 1-2 years. > We encourage projects to replace libraries or modular functionality with memory safe libraries, rather than embark upon ground-up rewrites. This allows us to break up the work into manageable pieces and deliver value incrementally. > Since many projects will end up using the same memory safe libraries, this approach also allows us to invest and build confidence in a particular set of libraries. Investments in a library for one project will add value across multiple projects. For example - the curl project will use the Hyper and Rustls libraries. The work we do to build excellent C API wrappers and improve the integration experience will help with many projects that will use the libraries in the future.
- oscargrouch 5y ago
  Yes exactly, it's an org that attempts to creates trojan horse implants into popular projects for gradual takeover and control of projects in the long term by the virtue of the amount of people working on it. They should be more open about it, and stop using generic words like security and memory safety for the actual corruption of those values in the form of rewriting popular stuff in Rust (apparently Apple is making followers using the safe word 'security' like politicians use 'terror' to manipulate public opinion). If it was really about security and memory safety, other memory safe languages would be among the projects and also attempts to fix memory safety issues in C and C++ would also receive grants.