Flip is the best

Yeah, both things are impressive in their various ways, lol.

My thoughts exactly

He has a Vtuber tag tho

C'mon this is a programming channel, you think the editor hasn't learned enough in his spare time to automate this task? 😆

Ain't no way

Why not?

Sounds crazy to hint it's not

Why should i move from C++? Why don't you keep on working with Rust and stop suggesting ways of removing a language like C++ that many others like to use?

Completely agree. Keep in mind that most of the people complaining about C++ have no clue about C++, or they don't use anything after C++11@@feynman_QED

I wonder how viable it would be to use D as a build system in this case. Just have a D program generate the bindings then kick off the compilers for all 3 langs then execute the program. Cool thing there is getting D + its package manger/build system Dub + some libraries to use only takes < 10 minutes, starting from having non if it installed. Even better given some of D's other features many D programmers are use to writing code to generate code.

@@feynman_QED Why are you so defensive? I’m not telling anyone to move away from C++, you can code in whatever language you like. However, there are people that would like to take a legacy codebase and migrate over to Rust and the article showed a very promising way to possibly accomplish it.

@@Ellefsen97 First of all, i am not defensive. With one of your level? Come on. Second, you wrote that "It could also potentially make it easier to gradually move a project from C++ to Rust". It's not consistent with what you've just said. This sentence says another story. Why should i move a project from C++ to Rust? Explain that to all of C++ programmers why. They are really interested.

That's sweet and I will have to keep that in mind for my company.

@@TJackson736 details are in an article "calling c from python" in the blog "atila on code"

I hope Prime looks the same for next stream lowkey

It works on audio input. Easy task for streaming or editing software.

Probably because there is a lot of exciting C++ code out there…

D's tools libraries in general suck the big one at least last time I checked (about 1.5 years ago). The VS Code extension for example still is the state where the compiler says one thing and the extension something else.

@@floppa9415 Thanks for the feedback. That doesn't surprise me. The reason I didn't continue using the DM C++ compiler was because of the linker's limited support to OMF, requiring you to convert MS-COFF libraries to VS6 MS-COFF to then use their COFF2OMF tool, or I guess use another linker...it was limitations like that which put me off using it. Fantastic product with a lot of passion behind it, but impossible to use when you step outside the eco-system. Reading the GCC page, David Friedman is no longer the developer with the D project having been revived in 2009 by Iain Buclaw and other contributors. I wish them well but it seems D never reached the critical mass it needs to thrive.

Its not that it's inefficient its just that the responsibility of creating an efficient layout is on the programmer

@@pxolqopt3597 Yes, indeed, and you end up with structs where field order has nothing to do with code readability, which is "fun" for larger structs. Enjoy!

Optimal performance is why the padding is used. If you pack you lose performance but gain efficiency in size. Rust picks the least performant but safest way every time.

I always make sure to properly align the struct if i need it packed so it's not up to the compiler.

@@anon_y_mousse Yeah of course. I'm thinking small structs going over the wire personally. I'm just countering the ops assumption that packing means performance gain which it does not when accessing the members, the contrary in fact. Every dive i take into rust just proves the wildly inefficient choices they made.

Well, that's not something a lot of languages will even attempt to do, and in D, multiple inheritance from C++ classes won't really work, and from what I've heard your only option there is to dupe the D compiler that the class doesn't have multiple inheritance and the compiler won't have a problem during name mangling. However, multiple inheritance is usually not a good thing.

It already exists as a macro crate called "cxx". You put in some declarations about the C++ side & the Rust side and it handles all the mangling for you. AFAIR it also goes both ways between C++ Rust

All this programming language nonsense is boring. Just code everything in assembly language. Then you only need a cross-assembler to compile for different CPU architectures, which can cross-assemble itself to run on those architectures.

@robinpage2730 A few things about assembly languages and assemblers you might find informative: - Assembly language is not a single language, but a rather a type of language. There are multiple different, system-specific assembly languages. - A cross-assembler is a program that runs one type of system, but generates machine code for a target system of a different type. - Programs which take code written in one assembly language and translate that code into a different assembly language don't really exist, because there are fundamental incompatibilities between systems. To make that work, you'd have to translate the assembly code into some kind of higher-level representation - or in other words, decompile the assembly language into a programming language. There a few exceptions to this: for example, translating linux 32-bit risc-v assembly to linux 64-bit risc-v is generally quite possible, depending on the risc-v extensions supported by the target cpus.

Wow how did you find the channel then?

Oh and please don't start your coding journey with any of the languages mentioned in this video XD Maybe C++ as a flavour of C if you wanna start knowing from the very basics, but if you're not already curious about computer fundamentals, this will be harder than starting with Python/JS.

@@VivekYadav-ds8oz I googled how to code for video games. I went down the rabbit hole and ended up here. A lot of people say don’t learn c++ first but primetime can’t stress enough how important the fundamentals are so I believe I’ve made my choice. Now where to begin lol. I definitely hope to spell cast in vim one day too!

automated (hopefully)

You'd have to instantiate the templates/macros in all 3 languages. It's doable, but hard as you have to know in advance which instances you need.

Member functions

When rust was as old as zig is now it was also in alpha stage, despite having many people working on it full time with large corporate backing and zig is trying to cover a larger range of programming than simply a programming language and compiler. It's good that it takes it slow before zig is version 1.0 where backward compatiblity breaking changes cant be made. I remember when rust was in alpha and it also made breaking changes every month.

good one

Prime talking about his camera 3:47. Foreshadowing 4:20.

oh we definitely need to abuse d.

The compiler could implement a library to do that unification, aligning everything to whatever the convention is for the language in which the main() function is written: if it's in C++, then that convention is used, but if it's in Rust, then Rust's convention is used.

F O U R T H

Ban all programming languages. Everything should be coded in assembly for minimum compile time, file size, and maximum running program speed and programmer torment.

Because C++ is one of the most used languages in the world. Rust is better in many ways, but thinking it will replace C++ is delusional

​@@vercolit we will see how that statement ages. However I agree that there is a lot of code written in c++ today and that code won't vanish overnight. Meaning that there is a need to interact with this code even in case rust replaces c++. The current status quo that everything interops over c is not ideal as shown in the article.

We have something like 50 years' worth of extant C++ code that's still useful. And if you're a plugin developer for any graphics app (Adobe, Autodesk, Rhino, everything), the SDKs are all C++ and won't ever be rewritten. This interop is DESPERATELY needed.

Rust can't be a "better C++" until it adds inheritance, proper generics (including variadics), function overloading, default parameters, and exceptions, to name only a few.

@@redcrafterlppa303 " The current status quo that everything interops over c is not ideal as shown in the article." The status quo is that for a very good reason: the semantic ideas the various different languages add on top of C are generally incompatible. Doesn't Rust, for instance, feel free to move memory around unless you explicitly pin it? Trying to interop between two disparate languages without making sure they talk in the absolute lowest possible denominator is a recipe for disaster.