Date: Mon, 11 Nov 2024 10:29:58 -0500
On 11/11/24 00:40, Tiago Freire wrote:
> This does look like an ad disguised as a discussion.
No because people in here knows me from the ages.
> There's nothing in this email chain that is actionable.
Again, maybe that's right but nonetheless what I talk about are very
important topics.
> The entire conversation can be dismissed with the simple question:
> So what?
So what? They don't teach C++ in universities anymore so I'm trying to
reverse the trend.
> Doing stuff in Python takes longer to run and consumes more power than they otherwise would in C++.
> So what?
It's bad for the economy and maintenance as well because Python is not
backwards / forward compatible which creates a disaster waiting to happen.
> I already knew that, and I assume everyone in this mailing list knows that.
> What would you expect would be the outcome of such an exchange on this mailing list?
> What do you intend to do?
> Convince python developers (in a C++ mailing list) to switch to C++?
I wanted to strengthen one's arguments here and at the same time get
your perspective in return because you guys have smart arguments in general.
> What would be the expect outcome where you would say, "yes, something was achieved here",
> Other than plug for your own business?
Again, I've been commenting for ages in these mailing lists so me and my
business are not new. I'm just trying to "un-obscure" facts that might
help debate C++ against Python developers for the greater good of our
ecosystem. If we don't talk about that then C++ will slowly die in the egg.
I also want to open source a concurrent cyclic container header I wrote
for my employer so I'm planning to contribute down the road.
> This does look like an ad disguised as a discussion.
No because people in here knows me from the ages.
> There's nothing in this email chain that is actionable.
Again, maybe that's right but nonetheless what I talk about are very
important topics.
> The entire conversation can be dismissed with the simple question:
> So what?
So what? They don't teach C++ in universities anymore so I'm trying to
reverse the trend.
> Doing stuff in Python takes longer to run and consumes more power than they otherwise would in C++.
> So what?
It's bad for the economy and maintenance as well because Python is not
backwards / forward compatible which creates a disaster waiting to happen.
> I already knew that, and I assume everyone in this mailing list knows that.
> What would you expect would be the outcome of such an exchange on this mailing list?
> What do you intend to do?
> Convince python developers (in a C++ mailing list) to switch to C++?
I wanted to strengthen one's arguments here and at the same time get
your perspective in return because you guys have smart arguments in general.
> What would be the expect outcome where you would say, "yes, something was achieved here",
> Other than plug for your own business?
Again, I've been commenting for ages in these mailing lists so me and my
business are not new. I'm just trying to "un-obscure" facts that might
help debate C++ against Python developers for the greater good of our
ecosystem. If we don't talk about that then C++ will slowly die in the egg.
I also want to open source a concurrent cyclic container header I wrote
for my employer so I'm planning to contribute down the road.
-- Fornux Logo <https://www.fornux.com/> *Phil Bouchard* LinkedIn Icon <https://www.linkedin.com/in/phil-bouchard-5723a910/> Founder & CEO T: (819) 328-4743 E: phil_at_[hidden]| www.fornux.com <http://www.fornux.com> 320-345 de la Gauchetière Ouest| Montréal (Qc), H2Z 0A2 Canada The Best Predictable C++ Memory Manager <https://static.fornux.com/c-superset/> 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 2024-11-11 15:30:00