Andreas Kurz

Just a noob asking stupid questions.

[Andreas Kurz @AndreasKurz]

@valigo i just took my ssd with windows from my old pc and put it inside my new pc (complete different system).

It worked, but I had not internet connection even with cable. Had to download drivers on an other device and put get it to it, but except that it was kinda easy.

[Andreas Kurz @AndreasKurz]

@rfleury @atomicptr I just build the master branch and it is working now. Nice work.

But there was an issue that the older version of the debugger created a .rsi file already and I had to delete that one or the debugger would ignore all the breakpoints (not find them or whatever).

[Andreas Kurz @AndreasKurz]

@Tisani01 @TejaMainHu92 @i_am_prabesh @GameOnSwagOn his point is that ronaldo does the exact same thing when he has the ball…

[Andreas Kurz @AndreasKurz]

@ElsonMgaya28881 @ThePrimeagen lower cost, double price

[Mario Nawfal @MarioNawfal]

The CEO of Take-Two, the company behind GTA, just said something the entire AI industry doesn't want to hear.

And he said it without being anti-AI.

Strauss Zelnick's argument is precise. AI is built on datasets. Datasets are backward-looking. Creativity is forward-looking. A model trained on everything that already exists cannot, by definition, produce something genuinely unexpected. And all hits, by their very nature, are unexpected.

Asset creation and hit creation are not the same thing. AI is getting very good at the first one. The second one is what actually makes money, builds franchises, and changes culture. Nobody has shown AI can do that yet.

The derivative property problem is real. You can clone GTA with existing technology. You could do it before AI. It would take 3 years and look identical. It still wouldn't sell. Because it isn't GTA. It's a clone of GTA.

And consumers, despite what the industry occasionally pretends, can feel the difference between something genuinely new and something assembled from the residue of things that already worked.

Thousands of mobile games ship every year. 0 to 5 hits get made. The same studios make them every time. The technology to make more games has been commoditized for years. It didn't democratize hit creation. It just flooded the market with more forgettable product.

The Silicon Valley thesis that AI unlocks game creation for everyone is true in the same way that cheap cameras unlocked filmmaking for everyone. They did. And the same 5 studios still make the movies everyone watches.

What Zelnick is saying, without quite saying it, is that the thing AI cannot replicate is taste. The instinct for what hasn't been done yet. The cultural antenna that detects the gap in the market before the data can see it.

Data tells you what people wanted. Hits tell people what they want next.

Those are different jobs.

[Ryan Fleury @rfleury]

I'd like programmers to retire the "isn't this just reinventing <thing>?" responses. Nobody has read every Wikipedia article. Nobody agrees on every piece of terminology. Reinvention is a good & necessary thing, because it renews, updates, and clarifies ideas. It's also admirable, because it means that someone discovered something important without it being told to them already. That is a much more valuable trait than memorizing terminology and facts.

[Andreas Kurz @AndreasKurz]

@pixelprayer This has to be minecraft.

[Тsфdiиg @tsoding]

It's been almost 5 years. I'm still waiting for the copyright laundering scheme to somehow magically cure cancer.

[Andreas Kurz @AndreasKurz]

@TheGingerBill Oh wow, that is good to know. With this i can clean up alot of my code.

[Andreas Kurz @AndreasKurz]

@TheGingerBill Very clean. Did not know you could do that. When writing „return true“ with named return types it sets ok=true before returning?

[Andreas Kurz @AndreasKurz]

@NyxXeres @TheGingerBill I am not saying that defer is bad. I love that feature. I am just pointing out that the code is not doing the same thing.

[Andreas Kurz @AndreasKurz]

@Its_Nova1012 delete your account

[Valentin Ignatev @valigo]

In reality, both X11 and Wayland are a lost cause. Real winner on Linux desktop is win32, because all games target in. I think Mesa should just standardize Wine platform GPU context and make DirectX drivers, and Wine should ship a real desktop instead of being a layer on top of Wayland/X11.

X11 had 40 years, Wayland had 20 years. I think it's time to take an L and focus on destroying Microsoft on its own playing field.

[Andreas Kurz @AndreasKurz]

@Its_Nova1012 Delete your account.

[Nic Barker @nicbarkeragain]

To be a little less vague, I suspect that we're likely (not certain, but likely) to be entering into a period of unprecedented software degradation, and we're going to be seeing an increasing frequency of outages like this across many high profile products.

But IMO the cause is actually not just the-one-thing-that-everyone-is-always-talking-about, it's a number of things that have all been bubbling away at just below critical levels for a long time. Some of the things off the top of my head:

- Poorly designed / optimised software has been getting a free ride on hardware improvements pretty much since the invention of the computer. That chapter is now coming to an end, and will only be worsened by the enormous industry-wide pivot to producing & innovating on AI specific hardware, rather than general purpose CPUs etc.
- The ZIRP era created a temporary suspension of reality in our industry, and now that it's ended we need to deal with the hangover. Companies that spent years making no profit, paying extravagant compensation to employees / shareholders and giving away server time for free are now pivoting into extraction mode, which is putting further pressure on their low quality software. QA is being laid off, hardware budgets are being reduced, timelines for shipping features are becoming more aggressive, etc.
- The enormous amount of free money incentivised too many new people to join the industry too quickly. This has led to an abundance of poor quality education programs (bootcamps, uncertified colleges etc) and an influx of people into the industry who frankly aren't interested in programming. If you compared the average person in the industry now to 20 years ago, I suspect the difference in motivations would be stark. I'm not saying it's these people's fault necessarily, it's simply an inevitable result of the absurd compensation / performance expectations ratio that our industry has enjoyed for the last 15+ years. Working for a tech company has also become socially prestigious, which further adds to the problem.
- Because computer programming was once an incredibly niche area of interest, many of our fundamental systems are built on trust. We're now starting to see that if systems like open source, public supply chain, discussion spaces, education etc become flooded with bad actors, we have no real mechanisms to deal with them.
- Our hiring / recruitment pipeline has totally misaligned incentives. Even before the AI resume / AI HR-filtering arms race disaster that we're experiencing now, the widespread adoption of the leetcode style interviews IMO selected for a very narrow personality type, and filtered candidates that would have made great contributions to the industry long term.
- The pivot from purchasing long term stable releases of software, to paying a subscription for constantly updating software has done huge damage to software quality as a whole. Companies have lost their incentive to get their software "right" because they can just "fix it later", and for the consumer - you can't just go back to the version of github that still works because the new one has problems.

This was all happening well before AI entered the picture. I won't belabor the point because there has been endless discussion about it. But to me personally, there are two additional and deeply worrying problems with AI code generation.
- It's undeniable at this point that it negatively affects the people who use it. It stops juniors from getting better, and it burns seniors out and makes them hate their jobs. Like it or not, humans are still the core of this industry, and I don't see this ending well.
- It's completely unfit for purpose in the most important, high-stakes situations. One of the reasons that we excuse all the small errors it makes, is because it's low effort to type "do it again and fix this bug". That kind of thing doesn't fly when you only get one attempt because a mistake results in data loss or an outage. The damage is done.

All the above has led to a silent exodus of many of our most experienced and impactful people. There are so many amazing programmers who made enough through stock options / compensation that they didn't need to work anymore, and were only doing it because they enjoyed it. Many of these people have just quit the industry and switched to doing hobby projects in the last 5 years. These are the types of people who have the experience and foresight to prevent the types of outages that we're seeing at github today.

It's very easy to assume that the proverbial straw that broke the camel's back is entirely to blame here. But I think it's a reckoning that has been on the horizon for a very long time.

[FFmpeg @FFmpeg]

FFmpeg is moving to Rust 🦀

Our use of C and Assembly in FFmpeg has been an unacceptable violation of safety.

FFmpeg will be running 10x slower - but we're doing it for your safety.

All your videos will appear green - safety first, working software later.

[Andreas Kurz @AndreasKurz]

@HeatherIsUnsane 27+48 = 20+55 = 75

[Andreas Kurz @AndreasKurz]

@vkrajacic Do you plan on or is there already a way to add network disks? Like SMB served files?