This probably doesn’t work for everybody, but I love it.~
This probably doesn’t work for everybody, but I love it.~
This probably doesn’t work for everybody, but I love it.~
This probably doesn’t work for everybody, but I love it.~
I really think (this time) that I won’t add many more features. 😅 At the moment, the program is very “generic” and basically only does some pattern matching: If it sees a
mov instruction followed by some 8 bit register and then some 8 bit number, then it encodes it as a 0xB0 byte using a certain mechanism (e.g., the register number might get added to 0xB0 and then the 8 bit number might just follow verbatim). That’s what the long list in the screenshot shows. “A cmp followed by two arguments of a certain type gets encoded as …” They’re all handled exactly the same.Adding support for more instructions *mostly* just means adding more entries to that table.
If I were to add “optimizations”, I *guess* complexity would skyrocket. 😅
I really think (this time) that I won’t add many more features. 😅 At the moment, the program is very “generic” and basically only does some pattern matching: If it sees a
mov instruction followed by some 8 bit register and then some 8 bit number, then it encodes it as a 0xB0 byte using a certain mechanism (e.g., the register number might get added to 0xB0 and then the 8 bit number might just follow verbatim). That’s what the long list in the screenshot shows. “A cmp followed by two arguments of a certain type gets encoded as …” They’re all handled exactly the same.Adding support for more instructions *mostly* just means adding more entries to that table.
If I were to add “optimizations”, I *guess* complexity would skyrocket. 😅
I really think (this time) that I won’t add many more features. 😅 At the moment, the program is very “generic” and basically only does some pattern matching: If it sees a
mov instruction followed by some 8 bit register and then some 8 bit number, then it encodes it as a 0xB0 byte using a certain mechanism (e.g., the register number might get added to 0xB0 and then the 8 bit number might just follow verbatim). That’s what the long list in the screenshot shows. “A cmp followed by two arguments of a certain type gets encoded as …” They’re all handled exactly the same.Adding support for more instructions *mostly* just means adding more entries to that table.
If I were to add “optimizations”, I *guess* complexity would skyrocket. 😅
I really think (this time) that I won’t add many more features. 😅 At the moment, the program is very “generic” and basically only does some pattern matching: If it sees a
mov instruction followed by some 8 bit register and then some 8 bit number, then it encodes it as a 0xB0 byte using a certain mechanism (e.g., the register number might get added to 0xB0 and then the 8 bit number might just follow verbatim). That’s what the long list in the screenshot shows. “A cmp followed by two arguments of a certain type gets encoded as …” They’re all handled exactly the same.Adding support for more instructions *mostly* just means adding more entries to that table.
If I were to add “optimizations”, I *guess* complexity would skyrocket. 😅
And as I've forseen the other day, we have to deliver yet another workaround hotfix, once the other team eventually gets their stuff integrated that we should rely on. Good riddance it's the weekend now!
Haha, eleven bytes, how mean is that!? :-D But I already see you working on that as well at some point in the near future. :-)
#catsoftwtxt
#catsoftwtxt
/https://baldo.cat/media/photos/IMG_3425.jpeg) #catsoftwtxt
#catsoftwtxt
/https://duque-terron.cat/media/photos/IMG_3429.jpeg) #catsoftwtxt
#catsoftwtxt
The paperback edition Otherland Volume Three: Mountain of Black Glass, from Tad Williams
The paperback edition Otherland Volume Three: Mountain of Black Glass, from Tad Williams
@nick@domain support by doing a webfinger lookup to get the URL.
@nick@domain support by doing a webfinger lookup to get the URL.
The idea would be that you'd login with your Yarn.social account on some pod you control/operate or share with a nice person 🤣 -- For those unfamiliar, this is called IndieAuth or IndieLogin. ALL Yarn.social pods are in fact valid (_have been for years now_) IndieAuth Providers. So I can just ust that. This also technically means you _could_ login with your own domain too (_more on that later..._)
The idea would be that you'd login with your Yarn.social account on some pod you control/operate or share with a nice person 🤣 -- For those unfamiliar, this is called IndieAuth or IndieLogin. ALL Yarn.social pods are in fact valid (_have been for years now_) IndieAuth Providers. So I can just ust that. This also technically means you _could_ login with your own domain too (_more on that later..._)
> The author recounts their experience with a “no calls” policy in enterprise sales, finding it surprisingly effective. They attribute this success to addressing common reasons for calls—lack of understanding, onboarding issues, pricing uncertainty, and trust concerns—through clear messaging, self-serve onboarding, transparent pricing, and robust security documentation. While acknowledging potential limitations, the author advocates for a #nocalls approach, emphasizing the benefits of efficiency and alignment with their values.
> The author recounts their experience with a “no calls” policy in enterprise sales, finding it surprisingly effective. They attribute this success to addressing common reasons for calls—lack of understanding, onboarding issues, pricing uncertainty, and trust concerns—through clear messaging, self-serve onboarding, transparent pricing, and robust security documentation. While acknowledging potential limitations, the author advocates for a #nocalls approach, emphasizing the benefits of efficiency and alignment with their values.
So, is that a standard lubuntu or a special version for that laptop? Any driver issues so far?
So, is that a standard lubuntu or a special version for that laptop? Any driver issues so far?
So, is that a standard lubuntu or a special version for that laptop? Any driver issues so far?
So, is that a standard lubuntu or a special version for that laptop? Any driver issues so far?
I added more instructions, made it portable (so it runs on my own OS as well as Linux/DOS/whatever), and the assembler is now good enough to be used in the build process to compile the bootloader:
That is pretty cool. 😎
It’s still a “naive” assembler. There are zero optimizations and it can’t do macros (so I had to resort to using
cpp). Since nothing is optimized, it uses longer opcodes than NASM and that makes the bootloader 11 bytes too large. 🥴 I avoided that for now by removing some cosmetic output from the bootloader.
I added more instructions, made it portable (so it runs on my own OS as well as Linux/DOS/whatever), and the assembler is now good enough to be used in the build process to compile the bootloader:
That is pretty cool. 😎
It’s still a “naive” assembler. There are zero optimizations and it can’t do macros (so I had to resort to using
cpp). Since nothing is optimized, it uses longer opcodes than NASM and that makes the bootloader 11 bytes too large. 🥴 I avoided that for now by removing some cosmetic output from the bootloader.
I added more instructions, made it portable (so it runs on my own OS as well as Linux/DOS/whatever), and the assembler is now good enough to be used in the build process to compile the bootloader:
That is pretty cool. 😎
It’s still a “naive” assembler. There are zero optimizations and it can’t do macros (so I had to resort to using
cpp). Since nothing is optimized, it uses longer opcodes than NASM and that makes the bootloader 11 bytes too large. 🥴 I avoided that for now by removing some cosmetic output from the bootloader.
I added more instructions, made it portable (so it runs on my own OS as well as Linux/DOS/whatever), and the assembler is now good enough to be used in the build process to compile the bootloader:
That is pretty cool. 😎
It’s still a “naive” assembler. There are zero optimizations and it can’t do macros (so I had to resort to using
cpp). Since nothing is optimized, it uses longer opcodes than NASM and that makes the bootloader 11 bytes too large. 🥴 I avoided that for now by removing some cosmetic output from the bootloader.
https://pt.wikipedia.org/wiki/Rui_Lu%C3%ADs_Br%C3%A1s
https://pt.wikipedia.org/wiki/Rui_Lu%C3%ADs_Br%C3%A1s
https://pt.wikipedia.org/wiki/Rui_Lu%C3%ADs_Br%C3%A1s
https://www.youtube.com/watch?v=D6JV63UbN9k&list=PLyVWviOmesDPB_T6lyMUU1j31hfONqkxL&index=80
https://www.youtube.com/watch?v=D6JV63UbN9k&list=PLyVWviOmesDPB_T6lyMUU1j31hfONqkxL&index=80
https://www.youtube.com/watch?v=D6JV63UbN9k&list=PLyVWviOmesDPB_T6lyMUU1j31hfONqkxL&index=80
easy miles
#running #treadmill
easy miles
#running #treadmill
easy miles
#running #treadmill