doken

10 posts

doken

doken

@doken_r

España Katılım Nisan 2024
80 Takip Edilen8 Takipçiler
Promakos
Promakos@PROMAKOS_·
Lo dice en francés, no en árabe. El propio Vaticano confirmó que en Argelia hablaría francés, idioma colonial y oficial de facto. Y aunque lo hubiera dicho en árabe no tendría nada de raro, el árabe es lengua litúrgica de millones de cristianos desde antes del islam. Hay 20 millones de cristianos arabófonos, coptos en Egipto, maronitas en Líbano, melquitas, siríacos, asirios, caldeos, católicos de rito oriental... El árabe cristiano es anterior a Mahoma, no es lengua del islam, es lengua semítica que también usa la cristiandad oriental desde el siglo IV. Asociar árabe con islam de forma exclusiva es de una ignorancia insultante.
Progresismo Out Of Context@OOCprogresismo2

🇻🇦🇩🇿 El Papa León XIV canta el Padre Nuestro en árabe en Argelia.

Español
35
738
7.4K
250.4K
doken
doken@doken_r·
@BonesMoses @valigo You definitely can have constructors, destructors and methods in structs. They are literally the same thing as classes. Only difference is that in a struct everything is public by default and in classes everything is private by default.
English
1
0
3
168
Shaun Thomas
Shaun Thomas@BonesMoses·
@valigo Naked structs don't have constructors, destructors, or functions. They really are a separate thing. Maybe I'm just missing an April 1st joke though.
English
6
0
12
3.4K
Valentin Ignatev
Valentin Ignatev@valigo·
Maybe hot take idk, but C++ shouldn't have had "class" keyword. It's just a marketing syntax sugar over "struct" that prefixes everything with "private" unless you tell it otherwise. This is pure example of bloat. Might've been a canon event that set C++ on the wrong path.
English
63
9
569
44.9K
lalathalala
lalathalala@lalathalala_·
@Holianum @ChShersh the way i was taught is to first learn the C way then slowly introduce the features, while learning how everything works not just how to use them e.g. making functor classes before using lambdas and then i had to explain how lambdas work under the hood if i wanted to use it
English
2
0
2
158
Dmitrii Kovanikov
Dmitrii Kovanikov@ChShersh·
All highly-skilled C++ devs I know constantly learn and use new things. Including Modern C++
Łukasz | Wookash Podcast@wookash_podcast

Every now and then, comments like this appear under live coding sessions, and I don't know how to respond. My view on that matter is: - all highly skilled people I know are avoiding modern C++ - some use C, some use C++, but those who use C++, they take a tiny subset of features - like operator overloading, or destructors to have "cleanup" mechanics - none of those people use std::views, std::ranges, std::pair, or even std::unordered_map or std::vector. If they do, they know they make a concession, "I shouldn't do that, compile times and runtime will suffer, I'm doing this cause it's a prototype, not a *real* thing" What I conclude from these observations is: - modern C++ is more about fashion than any real gains - new, competing languages have features like "map, filter, reduce" or string slices and C++ committee generally wants to add features, not remove them - the implementation of these features in compilers (MSVC, Clang, gcc) is nasty, not because compiler engineers suck, quite contrary, but because those compilers need to care about decades of existing features, syntax expressions, and weird historical constructs - quick example, for everybody liking lambdas in other languages, will absolutely freak out trying to understand all the possibilities of capture monstrosity with const & reference & pointer and [=] and [*] and move semantics, and damn const reference to a smart pointer which will not update refcount, how far have we strayed from the path. So my stance is: - if I invite somebody who loves modern C++ we will talk about how cool things can be expressed, but it will come at the cost of build time and runtime. If you think this worldview lacks nuance, and should be explored more in depth - reach out or recommend a person who would be a good fit for such a discussion. We can make a live session geared towards exploring these topics, or organize a small debate (but avoiding drama, a civilized debate!)

English
13
7
241
25.4K
doken
doken@doken_r·
@wookash_podcast Genuine question: why using std::vector is a concession in runtime?
English
0
0
1
248
Łukasz | Wookash Podcast
Łukasz | Wookash Podcast@wookash_podcast·
Every now and then, comments like this appear under live coding sessions, and I don't know how to respond. My view on that matter is: - all highly skilled people I know are avoiding modern C++ - some use C, some use C++, but those who use C++, they take a tiny subset of features - like operator overloading, or destructors to have "cleanup" mechanics - none of those people use std::views, std::ranges, std::pair, or even std::unordered_map or std::vector. If they do, they know they make a concession, "I shouldn't do that, compile times and runtime will suffer, I'm doing this cause it's a prototype, not a *real* thing" What I conclude from these observations is: - modern C++ is more about fashion than any real gains - new, competing languages have features like "map, filter, reduce" or string slices and C++ committee generally wants to add features, not remove them - the implementation of these features in compilers (MSVC, Clang, gcc) is nasty, not because compiler engineers suck, quite contrary, but because those compilers need to care about decades of existing features, syntax expressions, and weird historical constructs - quick example, for everybody liking lambdas in other languages, will absolutely freak out trying to understand all the possibilities of capture monstrosity with const & reference & pointer and [=] and [*] and move semantics, and damn const reference to a smart pointer which will not update refcount, how far have we strayed from the path. So my stance is: - if I invite somebody who loves modern C++ we will talk about how cool things can be expressed, but it will come at the cost of build time and runtime. If you think this worldview lacks nuance, and should be explored more in depth - reach out or recommend a person who would be a good fit for such a discussion. We can make a live session geared towards exploring these topics, or organize a small debate (but avoiding drama, a civilized debate!)
Łukasz | Wookash Podcast tweet media
English
98
18
625
80.4K
DJ Molehill
DJ Molehill@DjMolehill·
@valigo fr, empty structs being 1 byte is wild
English
2
0
6
1.3K
Valentin Ignatev
Valentin Ignatev@valigo·
BREAKING: In an attempt to make C even more compatible with C++, C27 will have empty structs be size of 1 byte instead of 0. Our redaction contacted ISO/IEC JTC 1/SC 22/WG 14 but so far received no response. We will keep closely monitoring the situation.
English
19
1
214
24.4K
Arumba
Arumba@Arumba07·
Working on my last EU4 beginner guide before EU5 launches. It’ll be my capstone to a game I’ve been teaching since 2013. After that, it’s all eyes on EU5.
English
14
3
286
5.6K
doken
doken@doken_r·
@MovistareSports Está hablando de la gente que metió GTA San Andreas en 32MB de RAM.
Español
0
0
9
749
Movistar eSports
Movistar eSports@MovistareSports·
🟣 Xokas comenta el tráiler de GTA 6: "Hoy en día, que un juego te pegue picos de menos de menos de 30 fps es para devolverlo". "La distancia de visión no va a ser esta, es imposible".
Español
82
36
1.8K
377.8K
doken
doken@doken_r·
@PoissonProcess @the_yamiteru @jondot For example if you are iterating over structs that contain 5 bools each, same logic applies. It can very possibly destroy your cache efficiency if not packing the booleans together in the same byte results in the struct not fitting in the same cache line anymore.
English
0
0
0
38
jondot
jondot@jondot·
Don't you love #Rust?
jondot tweet media
English
76
17
416
353.9K