Also a reply so you can understand a bit how things typically work in FOSS projects.
There’s a democracy in healthy ones, but ultimately, there has to be someone at the top that has the final say. The project maintainer/main contributor. Someone who gets to be the tie breaker, or absolutely final authority on what does or doesn’t make it into a patch/version/etc.
This is extremely common, and generally healthy, in these kinds of ecosystems.
I don’t know if it’s complete devotion, but Linus has a reputation he’s earned the difficult/hard way.
If he says something, people should take it seriously and consider his words. That’s not to say he’s right all the time, but you’d better have a damn good reason for disagreeing with him.
We won’t be around, but Unix time will be.
Need to get people to bump this higher up. Great take.
Unfortunately, those of us that make games in Unreal Engine are stuck writing a lot of C++, unless we want to do everything in BPs (no thanks, they’re fine, but it’s not coding, and it’s difficult to maintain and refactor for complicated projects, they’re good for taking C++ components and building bigger components out of the base C++ functionality though).
With that said, UE’s support for C++ is decent. Which is, that as long as you tag all your fields, properties, methods, classes, etc. with some UnrealEngine attribute filter (like UCLASS or UPROPERTY), Unreal will handle the memory management of those constructs for you. Which is nice.
Unfortunately it has some other limitations to the C++ language that you can’t work around, like disallowing pure abstracts because every C++ derivative class based on any UE construct (Actor, Character, Pawn, etc.) has to be instantiatable in the editor. So no pure abstracts and such.
In general, I’d give it a 6/10.
It’s still mostly C++, but some of the things suck less.
Yeah, exactly. This would have to be a Genie using the “Brewster’s Millions” rules, not the ones in the tweet. In that case, they wouldn’t be able to own anything bought with the 100M at the end of the month.
One hundred percent this. Source, am lifelong engineer.
This is the correct answer
Const keyword means constant, a value that won’t change after the application has been compiled; this allows for certain optimizations.
Let keyword is a JavaScript variable that is safely scoped down to the method or function level.
Var keyword is generally discouraged in JavaScript, because it’s a global declaration. The value of it could be available anywhere in the application, and the app might have collisions.
So, the meme is, shifting from a constant, unchanging gender, to the middle where gender is defined and scoped to a local level, to the extreme, where gender is variable globally.
We just built and deployed a fully functional AWS app for our team entirely written in AI. From the terraform, to the backing API, to the frontend Angular. All AI. I think AI is further along here than you suspect.