u/nicebyte

A lot of the newer features of C++ language and standard library are things that don't solve useful problems, or solve problems in a convoluted, ill-conceived way. see: concepts, modules, chrono, random, ranges, etc.

In addition to that, the overt reliance on templates, and pathological desire to put stuff into stdlib instead of just adding a new keyword leads to inflated compile times, which is a real and very serious problem for larger projects.

If i had to sum it up in a short paragraph, i'd just say that c++ as a whole has no direction whatsoever. It's a result of the collective effort of a bunch of smart people, backed by institutional power of a few companies, who each have their own ideas.

Because of this, each and every new feature should be treated with extreme caution until it's proven that it is 1) correctly specified and 2) actually implemented well by the compilers you care about. In practice this means that one should wait for like 5-8 years to see a new feature actually prove itself. For example, rvalue references and lambdas have proved themselves, whereas modules haves so far failed. That's the reason people are distrustful of "modern" c++ by default.

Ok, if we're doing this, could we get rid of the monorail too? Exact same story, kid climbed the monorail trying to do graffiti and got killed by the train.
https://komonews.com/news/local/seattle-monorail-14-year-old-killed-fatal-police-department-belltown-neighborhood-graffiti-rooftop-king-county-violence-mother-parent-website-accident-denny-way-intersection

Nice colors but why the Dutch angle?

the legendary Chinese Girlfriend

вау тектоник в 2026

On linux, syscall conventions are not treated as implementation details. They're considered a "public API" surface, any userland code is allowed to invoke them at will, and libc is not special in that regard. On windows, syscall conventions are implementation details. A program doing those directly is _not_ behaving in an expected manner. Whereas for a linux userland program making direct syscalls is not something abnormal, even if the majority of programs do go through libc.

Nope, i understood it perfectly. They're just incorrect. Specifically, this:

> the principle of "please go through the official library to get to the kernel" is the same.

is wrong. The linux kernel _does not care_. It establishes a stable/well-known ABI for syscalls (per platform) and never breaks it. Whether applications use it via libraries or directly does not concern the kernel - it does not treat the syscall conventions as an implementation detail!

"C standard library" is literally application code. It's not special.

From linux PoV, it does not matter whether syscalls come from some program directly or via libc.

In fact, if you write your application _without_ relying on the c standard library and using only syscalls, it will be _more_ portable, because different versions of glibc can be incompatible and it matters which one your application assumes.

No, you can't. I own those two minutes now :-)

it didn't even occur to me that something like that might appear odd to western audiences.

> Is being inexperienced and unqualified appealing?

This is what i keep asking all the trump voters.

(voted for harell btw).

this applies to more than just vulkan: it's an iterative process, like with many things. you won't "get" everything on your first go-around, and the most effective way to learn is to keep doing practical projects that gradually expand in scope.

crucially, don't "follow along" with some tutorial or video - set your own goals and do your own thing. this will force you to actually think/reason within your domain of interest. it's fine to refer to videos or tutorials, but you should be asking "what can i learn from this that applies to my current problem?" rather than trying to just copy the whole thing.

feeling like you know what you're doing can take a long time, especially if this is your initial introduction to the world of realtime graphics.

having prior experience with other apis helps immensely because, at a minimum, you'd be able to quickly move past "trivial" things that map easily to similar concepts in the api that you know, and instead focus on new, vulkan-specific concepts. stuff like synchronization, resource binding model, memory management is in and of itself complicated and trips up even experienced programmers regularly. that's why it is very hard to recommend vulkan as a "first" graphics api. if you're set on learning it, i can offer no better advice than just push through and keep writing things of ever increasing complexity until you start to "get" it.

a pervasive problem with most of the tutorials and samples out there is that they will very often take various shortcuts and make simplifying assumptions about things. this gives a general idea of what a particular aspect of the api does, and i guess that's the whole point of a "sample", but it doesn't quite answer the question, "how do i use it in a real renderer?", which is often what you're actually after.

for example, synchronization is one such thing: many samples will manually emit barriers where needed. that can be tenable (if a bit annoying) in a small codebase, but when the scale of your project gets large enough it starts to become a real problem, and few tutorials get to solving it. this is typically where you start digging into what real software written by practitioners in the field did to address it, but you'll rarely find clear-cut easily digestible answers that you can copy-paste. instead, you'll piece together a general understanding of the problem itself, existing approaches, make a reasonable assessment of what will work in your case and try implementing that. this is actually what a lot of "real" work in this field is like.

i _hate_ the new icons.

not to be negative, but can someone explain to me what is supposed to be amusing about this - is it supposed to be amusing at all? i'm familiar with both calvin and hobbes and dune but i seem to be missing some piece of context here.

hey, thought the quad was closed

ten gamers were slaughtered in tomato town, and you're laughing.

blursed video

Might be from the Russian orthodox church in cap hill

i... always thought the "french" pronunciantion was the correct one...

Yes, systemic change like enforcing the law for example.

what is this case?

thanks, i hate it

is this an original song or a parody?

i fail to see how "object orientation" matters whatsoever. any imperative language with mutability makes memory management by static analysis an insurmountable task.

predatory behavior in the biological sense is defined by killing and consuming another organism. afaik it's not specified that the killer has to also be the consumer. by that definition, humans fit the description.