Otherwise I am pretty happy with Java, I cannot imagine writting microservices with C++.

`(anjuta:19791): Gtk-WARNING **: Theme parsing error: <data>:2:30: The style property GtkWidget:focus-line-width is deprecated and shouldn't be used anymore. It will be removed in a future version`

Yeah, it was my impression that the code is messy.

Fucking hell, even't the Gnome/GTK+ IDE has bugs.

You'd think the developers would bother to notice and fix it.

At the end of the day, code quality is directly correlated to the effort necessary to write it.

GLib does a lot of convenient things, specially when dealing with OS-specific stuff. But still, the smaller, trivial tasks, is a lot of work, because it's still C.

Back to Stroustrup, that talk is interesting because he offers his perspective in teaching C++; not to veteran programmers that need to learn the new, hotest version. But to people that are new, malleable. How he's been teaching it to people that just want to get the damn task done, they don't care about `<type_traits>` or `std::enable_if` wizardry.

He also made an interesting point in that talk; in the Annotated Reference Manual, the document that would later be the basis for the ISO standard, Stroustrup made sure to write down everything twice. So in case he made a mistake writing what he intended, people would catch him. But in standard documents, it's like the goal is to write everything exactly once. So people find something that looks weird, or wrong, they never know if it's intended or not.

There has been cases in the standard of this, where they later had to clarify things with footnotes, examples, sometimes rewrite phrases entirely.

This reminded of the US Constitution, how people were uncertain about how to interpret things like the 2A, right away. "Can we have canons?" "Yes, that's the whole fucking purpose of the 2A, you can have everything the government can."

It's elegant to have a precise but terse document, but the person writing it might not be perfect enough. The "write it twice, in different ways" seems better indeed.

C++ should just be called C-- because it’s just C, but worse

Go back to saying "oof", to reduce the stupidity you spew.

@Deleted User got a problem with objects?

@scout_t286 nope, I just got a problem with cunts

The Java crowd is thataway -points-

Oof

Ever heard of the language c+=?

https://github.com/ErisBlastar/cplusequality

@scout_t286 yep

funny shit

A loop can be what ever kind of loop it wants to be

lol

I forgot how ridcious that was

We should probably clone that before github shuts it down and bans the user for hate speech.

```cpp
/*
* The concept of 'sorting' things has long been a cornerstone of
* patriarchal discrimination against women and PoC. To 'sort' objects
* according to some percieved 'value' is morally wrong and oppressive.
* Therefore a truly feminist algorithm cannot be based upon comparing
* values of 'objects'. Feminist sorting algorithms have to take various
* things into consideration: gender, race, the program's feelings and
* the current make-up of the objects to be sorted. To implement this,
* we use a progressive stack with added affirmative action.
*/```

I think it was down for a bit

https://www.youtube.com/watch?v=_QdPW8JrYzQ

Concerning that talk... https://www.youtube.com/watch?v=Vuw_GUvL-sE

meh

wasn't posting it to implore you to go on a stupid fucking journey

was just fun to see shit being thrown back at scammers

Paulie No-nose *is* a bum though

@Legiondude lmao that fucking podcast 😂

What’s so funny about it @Durtle02 ?

You got a problem shithead?

Git gud at js before you start shit talking, durtle

Learn to be a decent human before you go talking, douchebag.