Doubling PRs isn't necessarily unbelievable. AI reduces ceremony around PRs, makes the small shitty changes that you never had time to do possible and the larger cleanups at least doable.
Double the PRs doesn't mean double the output.
521 karma · joined December 20, 2025
Double the PRs doesn't mean double the output.
"Airplanes that get shot in the wing always survive" logic. People _do not get diagnosed and die_ because the US healthcare system is inaccessible to close to 50% of your population. A diagnosis easily reaches a few hundred dollars for the best cases (and several thousand if you need multiple tests/blood tests/operations like colonoscopies). And when you do get diagnosed, then you've just entered a world of having to pay hundreds of thousands of dollars.
>we get those numbers in part by diagnosing earlier and that our outcomes are broadly similar
lmao no you simply don't diagnose people and they just "die of natural conditions" early because they couldn't afford the treatment even if they were diagnosed.
I don't see you complaining that the US military has a low operating margin, so maybe we can just agree that some things are just normal expenses for a population. Which therefore leads to step 2: nationalize every single hospital.
>cutting salaries for doctors/nurses/etc
Considering that over 50% of the money that goes into healthcare is just siphoned off by middlemen, no, just getting rid of these means that your health workers do not have a worse salary.
>But, we're actually in a primary care shortage.
Because people do not even go see their GP since there's a chance it leads to life ruining expenses.
> fewer residents are going into family medicine.
Because they're going where money is. Remove that from the equation, and all you have is a public service with public servants.
>a lot of people in the industry believe that Medicare has a large amount of undetected fraud.
Aside from the fact that "people in the industry" have a financial interest in making you believe Medicare is a net negative, there's a great thing that comes from making healthcare a public service: there's no longer any fraud. And those "fraudulent" expenses you used to have that were costing you millions anyways have just had their costs cut in half.
>Healthcare reform is hard.
It's the easiest thing in the world when you have the amount of money the US does. Healthcare reform isn't a financial or infrastructure problem, it's a political one. Cuba has a working healthcare system despite being under US embargo. Botswana has a working healthcare system. Rwanda has a working healthcare system. Azerbaijan, Sri Lanka, Turkey, Serbia, and the list goes on.
Once you grow the balls to nationalize everything, even a first year economy student could make a plan that works.
yeah sure everyone has 100€ to spend on friends, at least once a month.
What kind of reality does he live in ?
>> What's moving the goalposts? I am very much amazed at what Opus 4.8 can do. I push its code straight to prod.
>>> What's moving the goalposts? I am very much amazed at what Opus 4.6 can do. I push its code straight to prod.
>>>> What's moving the goalposts? I am very much amazed at what GPT5 can do. I push its code straight to prod.
>>>>>> What's moving the goalposts? I am very much amazed at what Opus 3.5 can do. I push its code straight to prod.
Or we do what we've always done to war profiteers and hang them after taking their supplies, because hoarding food and expecting to be paid for it while people are dying is immoral and tends to get people a little bit pissed.
There's no fucking bet to be made that people will need to eat tomorrow, or have a house, or have water. Those are basic needs.
Normal countries also have media silence for the day or two before the votes.
Restricting the reach of politicians is an absolute good.
Additionally, anyone who has seen how Swift evolved should be wary of Lattner saying "the language is mostly stable", or even "the language is released".
cuba has a longer life expectancy than the US despite all of that btw
Watch out, you're almost sounding like the "not real communism" boys.
>Both have their issues, but nothing compared to communism.
Some would say leaving a few million people die of thirst and hunger every year because it's "not profitable to fix it", or having a population of dozens of millions in your own country suffering of mental health problems, inability to get basic healthcare or even living conditions for the past 50 years might be a sign that your favorite system is fundamentally immoral, but hey.
And before any "uuuuh this can't work uuuh people want to get rich uuuh", you are literally talking about the community that has made open source software, the most commie thing imaginable on earth.
Terrible news for you, people work on dogshit dells given by their company and netbooks, not high end laptops. Macbook Pros, high end laptops, etc are exceedingly rare. (And can also deal with the high memory usage by virtue of having more memory).
>you want a background picture which fills the entire window
Which you rarely do, and also you don't develop for either, you're going to have a 1080p image at best, and then a bug report from that one client saying "background is blurry" in your backlog for the next 5 years.
>I have mainly used pangocairo, which is based around CPU rendering text to a pixel buffer.
Then you're using it wrong/using the wrong tool. Re-paying text layout at every render is already painful and it should be cached, your font rendering should absolutely be in a texture atlas.
>If DWM has only one buffer which all windows share
Slightly inaccurate in my answer there, but DWM only keeps one final composition buffer, which it handles itself from the various windows (that do have their own buffer, but only for their size and are only kept active if the window is visible.)
* Not every app is full screen (especially not a weather widget.)
* Very few people actually have a 4K display. 1080p and 1440p cover over 75% of users already.
* You do not allocate a separate buffer for the main content and the parallax, applying a different transform does not need a dedicated buffer, just something the size of your asset. It can be a 640x480 upscaled asset for all you care.
* You also don't allocate a dedicated buffer for text rendering/hinting. Your text rendering engine keeps a texture atlas in a buffer which is eventually maaaaaybe reach a 4k texture if you display a TON of various glyphs, realistically they won't. DirectWrite will also share this atlas with other executables unless you explicitly ask for isolation.
* On windows, you write to DWM, which keeps a single buffet for all your windows. Every window does not pay that memory price. I'm pretty sure most compositors do something similar.
Default uneducated behavior to respond to anything USSR related with "BUT STALIN GULAGS" (when gulags are both from the time of Lenin and heavily ran by Trotskyists, who, if you've heard anything about them, weren't exactly Stalin's best friends.). Bringing in nazis is just the cherry on top.
Shit knowledge and reading of history doesn't make an argument.
Conditions in gulags were fucking dreadful, the same way conditions post any revolution when it came to repressing those who would put down a revolution would be: american prisons post reovlution weren't better, french prisons post revolution weren't better, etc: every single revolution has pretty much ended with a period of terror, and Lenin's wasn't different.
As it remains, the subject isn't gulags (which are, undeniably, work camps, though not death camps), but regular prisons. which existed. Which were the same damn thing as american prisons, except you would come out of it and probably have a house at least.
Instead, you got a nice paycheck, and made sure to make the world actively worse for everyone. Good job.
Whenever I feel like I'm bad at software development, I look at Atlassian and I feel good.
Which is now being fixed by the Styles API (https://developer.android.com/develop/ui/compose/styles) which are easily reusable.
sharedUserIds cannot be applied blindly, they need the app to be signed with the same key, both need to declare their sharedUserId to be the same, etc.
- An app without the INTERNET permission will crash the moment you try to access the internet. It's like a rite of passage of every android developer with every new project, you forgot the permission.
- Launching an Intent is EXTREMELY visible. It opens a full on browser. It's limited to a GET with a dedicated URL, so what are they going to do, stuff your data in query params ?
- Even in the case of another app being installed that would silently receive this intent and not pop an activity, you need a different app. It cannot be an activity added by the same package.
- Loading a Chrome Custom Tab opens a whole ass browser in front of you, think you're going to miss it ?
- Shared user IDs also require two different app installations and you cannot declare multiple. You also cannot have sharedUserId if you do not sign the apps with the same key. you cannot sharedUserId with Facebook, you need once again a dedicated app installation.
- A ContentProvider needs a dedicated permission on the writing app AND on the reading app, which is once again very visible.
I'll add more to your list: an app can request to write a file inside your downloads folder, and another one can show a popup asking you to open it! And if someone shows up with a hammer at your door, he can also hit your fingers really hard to make you tell him the data.
Android apps are, by default, very well isolated. INTERNET is a permission like any other, just not surfaced as a dangerous one (like permanent access to your background location would be), or a runtime one (like access to your current location while the app is in foreground)
Which is equally terrible and has earned them every single rendering engineer in the world taking the piss out of them when they proudly announced it was as complicated as rendering a video game.