Date: Tue, 27 Sep 2022 11:17:00 -0400
On 9/27/22 10:58, Jason McKesson via Std-Proposals wrote:
> On Tue, Sep 27, 2022 at 10:49 AM Phil Bouchard via Std-Proposals
> <std-proposals_at_[hidden]> wrote:
>> Greetings,
>>
>> Apparently Rust is gaining traction very quickly, even Linus Torvalds will use it for his Linux kernel:
>>
>> https://www.zdnet.com/article/programming-languages-its-time-to-stop-using-c-and-c-for-new-projects-says-microsoft-azure-cto/
>>
>> Apparently as well Rust will not fix everything:
>>
>> "Bob Rudis, a cybersecurity researcher for GreyNoise Intelligence, who was formerly with Rapid7, noted developers can carry across the same bad security habits to Rust."
>>
>> I'm looking into waiving the patented Fornux C++ Superset to integrate it into free open source projects as well so that should fix a huge part of the problem:
>>
>> https://fornux.com/superset/
>>
>> What are your thoughts?
> My thoughts are that your post seems almost entirely off-topic and is
> borderline spam.
Well I disagree because it's a major architectural addition to the
standards I am proposing; not just a minor technical addition.
>
> Are you considering proposing this "Fornux C++ Superset" for
> standardization? If so, then your post should probably explain what it
> does, what problems it solves, and so forth. Most importantly of all,
> the fact that this "Fornux C++ Superset" is under patent *really*
> needs to be addressed if it's going to have any hope of
> standardization.
>
> And if you're not considering proposing it... then what is this post
> doing on the "std-proposals" mailing list? This list is for looking at
> proposed changes to the standard. If that's not what's going on, then
> it doesn't need to be here.
I already proposed a new "framework" that will allow the integration of
such memory manager, and even standard backtraces, standard profilers
and so on into that ISO standards:
https://groups.google.com/g/scc-wg21/c/0QDx9wjIwmE
But they immediately suggested I waive the memory manager even if my
point was the framework to integrate them.
>
> Rust, or any other non-C++ language, is useful as a topic to this
> forum only to the extent that specific practices in other languages
> might be useful for adoption into C++. Beyond that, discussions of who
> might want to adopt language X and so forth are all off-topic.
My point here is that Rust forces to fix the bad memory management
burden the C/C++ family has that represents 70% of the cybersecurity
problems.
> On Tue, Sep 27, 2022 at 10:49 AM Phil Bouchard via Std-Proposals
> <std-proposals_at_[hidden]> wrote:
>> Greetings,
>>
>> Apparently Rust is gaining traction very quickly, even Linus Torvalds will use it for his Linux kernel:
>>
>> https://www.zdnet.com/article/programming-languages-its-time-to-stop-using-c-and-c-for-new-projects-says-microsoft-azure-cto/
>>
>> Apparently as well Rust will not fix everything:
>>
>> "Bob Rudis, a cybersecurity researcher for GreyNoise Intelligence, who was formerly with Rapid7, noted developers can carry across the same bad security habits to Rust."
>>
>> I'm looking into waiving the patented Fornux C++ Superset to integrate it into free open source projects as well so that should fix a huge part of the problem:
>>
>> https://fornux.com/superset/
>>
>> What are your thoughts?
> My thoughts are that your post seems almost entirely off-topic and is
> borderline spam.
Well I disagree because it's a major architectural addition to the
standards I am proposing; not just a minor technical addition.
>
> Are you considering proposing this "Fornux C++ Superset" for
> standardization? If so, then your post should probably explain what it
> does, what problems it solves, and so forth. Most importantly of all,
> the fact that this "Fornux C++ Superset" is under patent *really*
> needs to be addressed if it's going to have any hope of
> standardization.
>
> And if you're not considering proposing it... then what is this post
> doing on the "std-proposals" mailing list? This list is for looking at
> proposed changes to the standard. If that's not what's going on, then
> it doesn't need to be here.
I already proposed a new "framework" that will allow the integration of
such memory manager, and even standard backtraces, standard profilers
and so on into that ISO standards:
https://groups.google.com/g/scc-wg21/c/0QDx9wjIwmE
But they immediately suggested I waive the memory manager even if my
point was the framework to integrate them.
>
> Rust, or any other non-C++ language, is useful as a topic to this
> forum only to the extent that specific practices in other languages
> might be useful for adoption into C++. Beyond that, discussions of who
> might want to adopt language X and so forth are all off-topic.
My point here is that Rust forces to fix the bad memory management
burden the C/C++ family has that represents 70% of the cybersecurity
problems.
-- Email Signature Logo <https://www.fornux.com/> *Phil Bouchard* facebook icon <https://www.linkedin.com/in/phil-bouchard-5723a910/> CTO T: (819) 328-4743 E: phil_at_[hidden]| www.fornux.com <http://www.fornux.com> 1188 rue Saint-Louis| Gatineau (Qc), J8T 2L8 Canada Banner <https://goglobalawards.org/> Le message ci-dessus, ainsi que les documents l'accompagnant, sont destinés uniquement aux personnes identifiées et peuvent contenir des informations privilégiées, confidentielles ou ne pouvant être divulguées. Si vous avez reçu ce message par erreur, veuillez le détruire. This communication (and/or the attachments) is intended for named recipients only and may contain privileged or confidential information which is not to be disclosed. If you received this communication by mistake please destroy all copies.
Received on 2022-09-27 15:17:03