Looks cool, trying it out now - thanks!
Looks cool, trying it out now - thanks!
Good to know!
https://programming.dev/c/linuxupskillchallenge always tempts me to learn something.
There are so few shower thoughts that are worth pondering. This is one that is.
It’s RomHacking.net.
I hope they’re also looking at providing Steam Deck support for the original game too, otherwise there are going to be a lot of disappointed potential players looking to try/revisit the original. Like me:/
Never did manage to finish it, stuck on the last boss. Pile of shame.
If Bose does I’m unaware of it. Then again I never turn that kind of function on if I am aware of it.
à bas la différence
There’s also one in the mouth under the front of the tongue. Shower thought still holds for that one too!
Champion!
Spent a lot of time poring over that. Is it firearms that caused the radical redesign in the 1500’s?
Had a look to see how easy it was to get it up and running on the stream deck. I’m a massive Fallout fan, but it was just all too hard at this stage.
This has been bothering me too. Hope you get an answer.
That is a fascinating picture!
AI could system test, I’d just rather it was a different AI to the one that did the coding. Point being if an entity can write and test code, the same shortcomings that lead to a bug being introduced make it less likely to be found if that entity is also doing the testing. Whether that’s because of a logic fault, or just a misinterpretation of the requirements.
Developers write and execute the unit test, and perhaps component test. Once you get past that to system testing it should be someone independent.
If the same entity is both writing the code and testing the code it’s not great. Even though the code in this instance is there to support testing, it’s still being crafted by an ai that may one day also be expanded to create the tests themselves. It’s that scenario I’m concerned about. It’s part of the reason we do more than just unit test.
Agreed. This project is currently about validating the test coverage/power. It’s not too much of a stretch to envisage it one day actually designing/writing the tests themselves, but this is only a first step. And if it did end up creating tests and also editing the code under test, would there not be an independence issue?
So not much of interest, at least for me. Stability, UI.
”What’s actually changed? Frankly, there’s too many individual improvements to list. But some quick highlights:
For users it should provide a more stable experience overall. There’s better error handling, more in-depth progress notifications for Decky and plugins. Along with Decky being properly usable without an internet connection. There’s also various UI styling improvements. You should also hopefully never see the boot-loop problem again with some recent changes.”