@borrowck_novel@HSVSphere@typememetics I think they cannot comprehend that good engineers precisely describing well-designed systems don’t want to pay the cost of compilation-based memory safety guarantees because it just doesn’t add much value in this context.
Correctness is a design problem, not a language problem.
If a system is incorrect by design, it’s incorrect by design.
This is another way, of course, of saying that safety is an emergent property of “the system as a whole”.
Cf. Fallacy of composition
https://t.co/xPyfOQLVDL
@Azanium_@strwpien_0x@valigo If you want to precisely and efficiently solve a problem in C++ then you absolutely have to think about these things. Otherwise you may as well just use Go or some shit.
@Azanium_@strwpien_0x@valigo Yes we all know that. But there are things baked in that you can’t solve by abstaining from features. And newer features that are better reasoned are crippled by backwards compatibility. Any prolonged exposure makes this obvious, denying it is Stockholm syndrome or inexperience.
What I think is important is to continue caring about the things you love despite anything. The storm will pass. The chaff will be blown away. Good work will continue standing.
@Azanium_@strwpien_0x@valigo You’re just using the complexity to try to flex. I have used C++ professionally for many years and all the most experienced programmers I know agree that it’s a badly designed mess in the same way. The reason it’s popular is because of network effects not because it’s good.
@AgileJebrim@jorandirkgreef I’ve too found retries and acks to be counterproductive in certain situations, have you or are you aware of anything written about this kind of system design more concretely? It feels like we talking along the lines of “Residuality Theory”
@nafonsopt Yep. It doesn’t matter how good Apple hardware is anymore because MacOS and iOS no longer “just work” and are clearly getting worse every release.
Hey, happy to announce that the RAD Debugger is now available for Linux (in alpha). It is early and preliminary! Expect random weirdnesses *for sure*, but it is ready to be played with!
https://t.co/XLpdRIMcUm
@cachecrab@usr_bin_roygbiv Kind of. Im pretty sure the term could predate software, certainly it predates CI. I don’t know wtf codex is trying to do. Term is also used a lot in manual testing in games industry before considerable time gets sinker into testing a naff build that happened to pass auto-checks.
@cachecrab@usr_bin_roygbiv Different thing. Smoke tests are cheap tests that catch failures quickly before spending effort on more in-depth testing. Bear in mind integration tests should be extensive and may not always be cheap to run.