@pemensik here's how Ladybird does it. Getting peer information is probably the least portable socket operation I've ever seen. Every unix does it slightly differently just for fun.

https://github.com/LadybirdBrowser/ladybird/blob/master/Libraries/LibCore/Socket.cpp#L482-L521

@bugaevc @bugaevc Thanks for the details! The intialization order of parent classes definitely makes it hard to do what c++ wants to do...

> So are/were you considering peel for some project? What are you trying to do?

I'm reviving my efforts to create a GTK4 UI for Ladybird. Last summer/fall I had scaffolding in place, but now I'm actually implementing the UI itself.

(Side note on that: the adoption of librsvg by gtk and the move of librsvg from C to rust caused problems for vcpkg that have taken a lot more effort than I hoped to resolve... and I still need a final review from vcpkg on that)

I was looking at the 'gotchas' in the peel documentation and ran across the constructor issue, and the 'weak ptr in lambda' issue and found them particularly unfortunate. I'm unsure how to create a 'proper GTK app' in C++, but looking at the Qt and AppKit UIs we already have, meshing our C++ ViewImplementation and C++-like UI concepts feels like there would be a lot of friction. Especially if we try to keep the UI components 'feeling' like Ladybird/Serenity C++. Adopting an entirely different style for one component is a bit of a non-goal as it would require contributors to gain extra knowledge from... somewhere in order to hack on the UI layer.

@bugaevc following up on this old post, why does peel not call object constructors?

That feels ... c++-hostile, at the very least. I saw in the README/docs and some issues that the goal of peel is to be as faithful to GTK as possible, but ... maybe I'm missing something.

Is it truly not possible to

```
auto* p = g_object_new(...)
new (p) MyClass; // call c++-generated constructor
static_cast<MyClass*>(p)->init();
```
?

The documentation I saw that suggested doing

```
void
MyClass::init()
{
new (&m_vec) std::vector<int>{};

...
}
```

feels like a bridge too far in being C-like.

I would expect a C++ library to either call my class's constructors, or enforce that all 'classes' are trivially constructible, to avoid foot-guns/awkward situations like that.

@bkardell I'm using Firefox on all platforms. I switched from Chrome when my ad block extension stopped blocking mid roll ads on video streaming sites I'm paying for, about a year ago I guess?

The ad landscape for sites and streaming is just infuriating as a user. Block the ads, hurt the provider. Don't block the ads, and the user experience is untenable. I don't understand why sites are even offering ad-supported paid tiers. Either I'm giving you money, or I'm watching ads. That's how it used to be anyway.

@gregkh Thanks for the posts on kernel releases and commit tracking!

I will note that some of the 'code' elements on this post and the diagram in the previous one don't look great/are illegible in Firefox's dark mode (likely a media query prefers-color-scheme: dark thing). The setting is here in Firefox's settings if you're not familiar: