On Mon, Aug 12, 2024 at 1:36 PM John Coggeshall <j...@coggeshall.org> wrote:

> lol. Listen friend, I've been involved in PHP internals on and off for
> over 20 years -- and so has Pierre. You'd do well to respond with a little
> more consideration instead of flying off the handle calling us ignorant
> rust developers lol.
>
> The idea of enhancing support for C++ makes no sense. It's a waste of time
> and energy. The entire industry is actively trying to to move AWAY from
> C/C++ in general, not to mention someone has to maintain it after you get
> bored insulting people here and move on. This is doubly true when the
> benefit is a handful of people who want to might write some extension in
> C++.
>
> On Aug 12 2024, at 2:59 pm, Lanre <lnearw...@gmail.com> wrote:
>
>
> I didn’t realize this was an open mic for Rust devs to flaunt their
> ignorance, but since you’ve decided to chime in, let me spell it out for
> you. Rust has absolutely nothing to do with this discussion, so try to stay
> on topic. Nowhere did I mention a move to C++; perhaps reading
> comprehension isn’t your strong suit.
>
>
> PHP already supports C++ for extensions, as evidenced by the intl
> extension. The current support is painfully basic, which forces developers
> to waste time on redundant wrappers or use third-party libraries like
> PHP-CPP. What I’m proposing is a way to improve this support so C++ devs
> don’t have to keep doing the same menial work over and over again.
>
> All of this will be wrapped in macros, so C compilers won’t even notice
> the compatibility layer and will compile as usual. It’s a simple, elegant
> solution—something you might not be familiar with, given your affinity for
> Rust’s convoluted approach to everything.
>
> Cheers,
> Lanre.
>
>
It’s impressive that you’ve been involved with PHP internals, but it’s
clear you haven’t a clue about what I’m proposing and are contributing
nothing of value. You’d have to be seriously naive to believe that “the
entire industry is actively trying to move AWAY from C/C++.”

The fact is, C is still the backbone of nearly everything. If you’re
building anything that interacts with an OS or embedded device, you’re
either writing in C/C++ (C++ for Windows) or working with some C wrapper.
Rust’s approach to low-level implementation is laughable unless you’re
prepared to abuse unsafe or use Cranelift. Even simple things like JIT
optimizations are considered unsafe in Rust.

Swift, which is heavily used in macOS, is essentially an LLVM
wrapper—meaning it relies on C++. The recent advancements in Swift’s
interop with C++ highlight just how crucial C++ remains. Then there's Adobe
apps, Microsoft products, browsers, and virtually every game and game
engine that are all implemented in C++.

So, unless you’re living in a fantasy world where everyone is abandoning
proven technology for glorified scripting languages,  I suggest you step
back and recognize the reality of the situation.

I'm sure the idea of enhancing C++ makes no sense to you, and would be a
waste of your time and energy, but not everyone is that stupid/incompetent
so even if i do get bored of maintaining it, literally any C++ dev can pick
it up, it really is that simple.

Cheers,

Lanre.

Reply via email to