This triggers the Jow Forumstard

this triggers the Jow Forumstard

Attached: file.png (480x286, 16K)

this triggers the high level language tard

Attached: file.png (920x650, 21K)

Dumb neetcoder.

whats a virtual table i dont think my compiler supports than bro :s
based poster

dumb webdev

triggered kek

samefag

This is from that /dpt/ thread isn't it?

This triggers the Jow Forumstards and, let me say, for a fucking good reason!

Attached: uselsssmeme.png (1024x570, 45K)

Honestly, OOP has been one of the dumbest ideas to come about in Computer Science and programming in general.

Attached: 1549907264744.png (1066x1367, 854K)

This triggers everyone.

Attached: LISP.png (626x366, 26K)

every cache miss these monsters cause is another day the dev doesn't deserve to live

Not my fault CPU architecture is garbage.

>repeating yourself that much
>having to use factories to deal with all the bullshit taxonomy you have introduced for no reason
OOPtards have never had a job in their lives!

someone post it

It's not that horrible. lisp atoms are small and fixed-sized, thus different allocation strategies can be used.

>vtable pointer embedded in the object itself
horrible design only Java people could invent and only C++ people could adopt

>this triggers the CPU to load new cache lines
ftfy

So if tomorrow a compiler solves the problem of data contiguity for linked lists you have no reason left to complain?

not really, vtables are staticand controlled by compiler. they ought to be close together, usually multiple on one mempage.
linked list of small arrays

static_assert(!std::is_polymorphic::value, "oops no vtables allowed in this codebase :^)");

>whats a virtual table
>t. code monkey

I love this. but it's only for that one type, not codebase-wide

I don't understand, why should anything posted so far trigger me?

Attached: 418964_1.jpg (125x128, 5K)