I've been using Turbo Pascal and Turbo Assembler on real vintage hardware in my attempt to do the Roguelike Tutorial. I'm still getting to the point of finishing part 1 because I decided to go hard mode and use the…
Yeah, there's no visible flicker at 70Hz or higher.
No, I mean the screen noticeably flickers when displaying a static image at 60Hz progressive.
You don't want to simulate the god-awful flicker my CRT has at 60Hz.
A project I've just started is to follow the Roguelikedev tutorial on a 32-year-old PC, using the period dev tools. I'm going to have to write everything myself, and I'm currently researching how to poke the graphics…
Yup, definitely the Rust users who are toxic. Totally not the people going into every thread about Rust to tell everyone about how toxic Rust users are. Nope.
Complete and utter nonsense. Every Windows tool I remember using has handled LF-only endings perfectly fine, meanwhile Linux tools regularly fail to handle CRLF endings.
The only times I can remember having line-ending issues is using GNU's tools on Linux. Every Windows tool I can remember using accepts both CRLF and LF.
Microsoft's PowerToys did add that in (I think) the last version. Alt + Left click moves, alt + right click resizes.
That's not really that surprising when you think about it. Standard library-provided things are implemented on a basis of working OK for as many scenarios as possible, not on one of being the best possible…
Hilariously, I had the exact opposite. I use Fira Code, which I eliminated in the first round.
> It's as if someone asked you how many 1s there are in the binary representation of this text. I'm actually kinda pleased with how close I guessed! I estimated 4 set bits per character, which with 491 characters in…
Memory allocations in Rust are also always done explicitly, but Rust's library types don't have APIs that allow you to get it wrong.
And, by default, panicking in Rust also doesn't crash, it begins a stack unwind which can be caught on any layer above it with catch_unwind.
Back in 2015 when the Rust project first had to disable use of LLVM's `noalias` they found that performance dropped by up to 5% (depending on the program). The big caveat here is that it was miscompiling, so some of…
For Rust vs C++, I'd say it'll be much easier to have a complete understanding of Rust. C++ is an immensely complex language, with a lot of feature interactions. C# is actually fairly complex. I'm not sure if it's quite…
So in Rust an unsafe block and an unsafe function mean two different things. An unsafe block allows you to do things that are unsafe, such as dereference raw pointers, access union fields, calling unsafe functions, etc.…
Only if that memory page is unmapped, and only if the optimizer doesn't detect that it's a null pointer and start deleting verification code because derefing null is UB, and UB is assumed to never happen.
There are also limits to what the borrow checker is capable of verifying. There will always be programs which are valid under the rules the borrow checker is enforcing, but the borrow checker rejects. It's kinda…
That support could be Microsoft driven. Parts of Windows 11 are written in Rust, and having that platform in Tier 1 makes their lives easier.
There's no push to add Debian's officially supported platforms to Rust because Rust already supports those platforms.
Based on this, and many other similar threads, it's the anti-Rust zealots insulting Rust users.
Zig only does bounds checking by default in Debug and ReleaseSafe builds. If you build with ReleaseFast or ReleaseSmall it will happily do an out of bounds read: https://godbolt.org/z/733PxPEPY
Not even close. Borrow checking takes less time than type checking.
A few years ago I did some testing with a quick Arduino-based setup I cobbled together and got some interesting results. The first test was the simple one-light-one-button test. I found that I had reaction time…
I've been using Turbo Pascal and Turbo Assembler on real vintage hardware in my attempt to do the Roguelike Tutorial. I'm still getting to the point of finishing part 1 because I decided to go hard mode and use the…
Yeah, there's no visible flicker at 70Hz or higher.
No, I mean the screen noticeably flickers when displaying a static image at 60Hz progressive.
You don't want to simulate the god-awful flicker my CRT has at 60Hz.
A project I've just started is to follow the Roguelikedev tutorial on a 32-year-old PC, using the period dev tools. I'm going to have to write everything myself, and I'm currently researching how to poke the graphics…
Yup, definitely the Rust users who are toxic. Totally not the people going into every thread about Rust to tell everyone about how toxic Rust users are. Nope.
Complete and utter nonsense. Every Windows tool I remember using has handled LF-only endings perfectly fine, meanwhile Linux tools regularly fail to handle CRLF endings.
The only times I can remember having line-ending issues is using GNU's tools on Linux. Every Windows tool I can remember using accepts both CRLF and LF.
Microsoft's PowerToys did add that in (I think) the last version. Alt + Left click moves, alt + right click resizes.
That's not really that surprising when you think about it. Standard library-provided things are implemented on a basis of working OK for as many scenarios as possible, not on one of being the best possible…
Hilariously, I had the exact opposite. I use Fira Code, which I eliminated in the first round.
> It's as if someone asked you how many 1s there are in the binary representation of this text. I'm actually kinda pleased with how close I guessed! I estimated 4 set bits per character, which with 491 characters in…
Memory allocations in Rust are also always done explicitly, but Rust's library types don't have APIs that allow you to get it wrong.
And, by default, panicking in Rust also doesn't crash, it begins a stack unwind which can be caught on any layer above it with catch_unwind.
Back in 2015 when the Rust project first had to disable use of LLVM's `noalias` they found that performance dropped by up to 5% (depending on the program). The big caveat here is that it was miscompiling, so some of…
For Rust vs C++, I'd say it'll be much easier to have a complete understanding of Rust. C++ is an immensely complex language, with a lot of feature interactions. C# is actually fairly complex. I'm not sure if it's quite…
So in Rust an unsafe block and an unsafe function mean two different things. An unsafe block allows you to do things that are unsafe, such as dereference raw pointers, access union fields, calling unsafe functions, etc.…
Only if that memory page is unmapped, and only if the optimizer doesn't detect that it's a null pointer and start deleting verification code because derefing null is UB, and UB is assumed to never happen.
There are also limits to what the borrow checker is capable of verifying. There will always be programs which are valid under the rules the borrow checker is enforcing, but the borrow checker rejects. It's kinda…
That support could be Microsoft driven. Parts of Windows 11 are written in Rust, and having that platform in Tier 1 makes their lives easier.
There's no push to add Debian's officially supported platforms to Rust because Rust already supports those platforms.
Based on this, and many other similar threads, it's the anti-Rust zealots insulting Rust users.
Zig only does bounds checking by default in Debug and ReleaseSafe builds. If you build with ReleaseFast or ReleaseSmall it will happily do an out of bounds read: https://godbolt.org/z/733PxPEPY
Not even close. Borrow checking takes less time than type checking.
A few years ago I did some testing with a quick Arduino-based setup I cobbled together and got some interesting results. The first test was the simple one-light-one-button test. I found that I had reaction time…