Goldon Marks

@0xK1K3 @neogoose_btw @skydotcs I actually worked with an intern who didn't even familiar with the keyboard layout😂😂😂 no offensive, was typing like having a brain trauma

@harshildesigner @figma Figma

Built this Light/Dark Dashboard in @figma for Payroll System using Variables for different breakpoints. 🔥 Giving away the Figma file + Tutorial (with all variables set up). Comment 'Figma' & I will DM you the link (Must be follow so I can DM) #figma #Process #uidesign

@the_moisrex if it is not complicated, it is not a feature of C++. This is common sense😂😂

Did utf-8 need to be this complicated in C++?!

@lefticus No matter what, will use .h only, or C++ should stop be compatible with C

Is your header file meant for use by a C compiler? No? THEN STOP USING .H If I see .h I have to literally go and read the code to see what language it's in, I have no other choice. If I see something like .hpp, I know it's a C++ header file!

@Sosowski And they call this modern😂😂😂

After 29 years, C++23 finally has a "print" function.

@krisjusiak GCC has become the python interpreter of C++. Maybe with a little modification, it could turn C++ into a static typed scripting language😂

[#cpp26 (reflection)* vs #cpp20] design by introspection godbolt.org/z/9x9b45YP5

@FredrikMalmer @SebAaltonen Completely agree!!! The more I use C++ the more I feel they never code. Nobody can name a C++ project that Bjarne had made, but the books he sells.

@SebAaltonen I always get the feeling the the C++ standards body never ever used any other programming language and just add things they heard about but have no idea of how it could be implemented in a user friendly way.

C++ auto keyword issues again found in the code base. Function returns reference. Local variable with auto type used to get the return value. Deep copies the returned array. Use auto& for capturing references, otherwise you will get copies. Auto doesn't respect ref return.

@marcba What movie is this, so funny!!! LOL🤣

People refusing to use TypeScript

@ale_sp_brazil Rust is a tool that is ahead of C++ in every way, that is the reason C++ is being phased out. Further more, people don't need grammar books to understand Rust, that is a big win.

People say everyone should use Rust instead of C/C++ because Rust is memory safe while C/C++ wouldn't be, but that's not true (not even close). The main problem with C/C++ is that many developers do not care about security while programming and do not use various available features to avoid memory safety issues. Additionally, different features are available in compilers and sanitizers to help us eliminate such issues. C/C++ is a really mature language, its syntax is much better (by far) and the features are completely amazing. C/C++ and Rust are great, and we should choose one or the other motivated by the project being developed, and not for out-of-contextual reasons. #cpp #c #programming #rust

@lefticus why can't the compilers figure the constexpr out themselves, it's not funny to type specifiers anymore.

At my C++ meetup's social hour. Me: <looks up> 4 people looking at me. Me: umm... Them: this new guy just asked what the point of constexpr is

@hankadusikova @lefticus a compiler flag to try everything as constexpr first, so I don't need to type constexpr anymore.

@seanbax no border bill no fund bill😂

The senate struck a bipartisan plan to fund Ukraine's defense and the new speaker is killing it. I can't understand why the Republican party is being run out of the Kremlin.

@the_moisrex A great pic to demonstrate how shitty designed C++ is. C++ is created for selling grammar books.

C++ Iceberg fouronnes.github.io/cppiceberg/

@rustoftheday This is so bad that you create a new Vec for iteration, never do this in production code.

🦀 #daily #Rust 74: The .zip() function for iterators in Rust allows transforming two vecs into a single vec of tuples. However, the syntax is not as convenient as #Python's version. But this issue can be nicely addressed using #generics:

@farre_x @seanbax because they need to abstract away the implementation details, this is a typical style of OOP.

@seanbax I never understood why the standard library in C++ (which basically amounts to "idiomatic C++") is written in such a horrible, awful way. Standard library implementations would be a great example on how to write decent/good C++ & it's obfuscated to hell. To me it's bizarre.

C++'s reference story is a mess. Aliasing makes it difficult to correctly write code that resizes buffers. std::vector's push_back/insert has to copy the incoming value, because it might be a reference into the current vector, and you don't want a use-after-free UB.

@m_adduci @hankadusikova I sincerely doubt that most of the committee members don't even code or code in C++😂😂😂, It's not so, why they're making C++ so hard to use

@seanbax It seems like a nice solution, but in this way the safety is not fully guaranteed, and It may take forever to apply this feature in a big project. If there's a tool that can convert the codebase into using the memory safety grammar, it would be great.

@GoldonMarks It would absolutely be very different. Your project stays in one language and one toolchain, and you can migrate little bits at a time and your project remains deployable all the way through.

Frustrated that nobody in C++ world cares one jot about the memory safety issue. Another C++ mailing dropped without even lip service in that direction. There are a hundred degrees of freedom to nail down and there's no one to even bounce ideas off.

@lefticus I don't think whoever designed the exception have ever written code😂

Why do you think C++ Exceptions are slow?

@mdrizwanalam72 drop me one pls.

JavaScript practice book. (Interview/University exam edition) ✅ 70+ Theoretical Questions. ✅ 50+ JavaScript Exercises. Grab it for FREE, if you have not get it yet. - Drop a 😃 in the comment - like/Retweet Make sure you follow me, So that am able to DM You.