Are you implying that this was an AI bot comment?
1,601 karma · joined January 19, 2014
Bluesky: https://bsky.app/profile/kelteseth.bsky.social
Gitlab: https://gitlab.com/kelteseth/ScreenPlay
https://www.t-online.de/nachrichten/ausland/internationale-p...
[1] https://www.dw.com/en/crime-statistics-knife-crime-drugs-lif...
Huh? I had to do zero extra work to run it on the steam deck.
> in the past 48 hours, code.qt.io has been under a persistent DDoS attack. The attackers utilize a highly distributed network of IP addresses, attempting to obstruct services and network bandwidth.
https://lists.qt-project.org/pipermail/development/2025-Nove...
So it’s true 3,300 people were arrested for posts online. What they don’t tell you are the statistics or context. The actual law for these arrests covers EVERYTHING online. These arrests include those arrested for terrorism (if the planning/act of terror includes any online communication in the UK), threats of violence, racist abuse, hate speech and unwanted communication (including sending unsolicited sexual photos to strangers). It also includes spreading false information that could cause harm or affect an ingoing investigation.
If you look at convictions, only 137 people were actually sentenced in 2024.
https://www.reddit.com/r/DebunkThis/comments/1mmux6r/comment...
This is actually a satirical piece, written as a fake credit rating report. It's mocking how Meta (Facebook's parent company) is using a complex financial structure to keep $27 billion in debt off its official books. Here's what's actually happening in plain English: The basic setup:
Meta is building a massive $28 billion data center in Louisiana Instead of borrowing the money directly (which would show up as debt on Meta's financial statements), they created a convoluted structure with multiple shell companies and a partner called Blue Owl Capital
The trick:
On paper, Blue Owl's company "Beignet" owns 80% of the project and borrows the $27 billion But Meta still guarantees all the rent payments, covers cost overruns, and promises to pay if anything goes wrong So economically, it's Meta's debt—they're on the hook for everything—but legally it's structured so it doesn't appear on Meta's balance sheet
Why the author thinks it's absurd:
Meta controls the project, uses the buildings, guarantees all payments, and bears all the real risk The only reason it's "not Meta's debt" is a technicality in accounting rules The author is essentially saying: "This is obviously Meta borrowing $27 billion with extra steps, and everyone pretends otherwise because the rules allow it"
The whole piece is written as if a rating agency is giving this deal an A+ grade while openly admitting the structure is ridiculous—it's a critique of how financial engineering and accounting rules let big companies hide their true debt levels.
1. The state of C++ is not great. Few developers, C++ footguns, complicated build systems, and generally slow progress, see my https://arewemodulesyet.org/
2. How Qt presents and licenses itself. Either you go LGPL or you have to pay big money for a commercial license, which will then infect all other apps as well. For example, when you have two Qt apps that talk to each other you must license _both_ commercially.
3. The split of Widgets and QML makes the ecosystem fragmented, because Widgets will never die. Even the Qt devs themselves are split about this. You can see this when example code for a new feature uses Widgets. QtCreator is also a nice example, where they reverted some new QML code quite a while ago and have not substantially added any new QML code since then.
4. Tooling: We use QML for everything and the tooling is not great. The language server is still super flaky and breaks, and developer tooling like the Chrome Dev Tools is virtually nonexistent.
5. Packaging is still also not great but has gotten better in the last few versions where Qt creates a deployment cmake script for you, but you still need logic for your own (vcpkg) packages.
That is an unfair comparison. Nobody uses direct compiler command line approach to compile more than a simple hello world test project.
> C++ 26 reflections have now been voted in. This would get rid of moc entirely, but I really do not see how this will become widely available in the next 5-10 Years+. This would require Qt to move to C++ 26, but only if compiler support is complete for all 3 compilers AND older Linux distros that ship these compilers. For example, MSVC still has no native C++ 23 flag (In CMake does get internally altered to C++ latest aka. C++ 26) , because they told me that they will only enable it is considered 100% stable. So I guess we need to add modules support into moc now, waiting another 10 years is not an option for me .
> No more weird forward declarations
We c++ devs just have collectively accepted that this hack is still totally ok in the year 2025, just to improve build times.