Happily running the MC1 #FPGA computer @ 120 MHz, after patching my broken DE0-CV board with a new oscillator via GPIO pins (off screen, wires to the right).
https://t.co/BfExWMPWSB
#MRISC32#CPU#VHDL#opensource
Created another tool: Remote V4L recording (for Linux).
I needed to capture a video stream from my PS3, but the laptop that I could connect to the HDMI was too weak, so I had to stream the raw video+audio data over LAN to a more powerful computer.
https://t.co/THkDHPtgHs
@cr88192 Then I got that beat ;-) I was born in the 1970's. The C64 was great for learning computers. Advanced enough to seem like magic to a kid, but simple & approachable enough that you could peek through all memory and learn almost everything about it, much of it by heart.
@cr88192 I started on the Commodore 64 in the 1980s, Basic. Discovered 6502 machine code somewhere around 1985 or so. Then Amiga and 68k assembler. Got into C in the mid 1990s, and moved to higher level languages from there. Never was much of a Windows guy.
Why not change the Unix epoch to the big bang?
The number of seconds since the big bang fits comfortably in an unsigned 64-bit integer (only 59 bits are required, so far).
Caveat: All we have to do is to define the age of the universe with sub-second accuracy. 🤔
@codeslubber@lemire Interesting. No, still trying to figure you out.
You clearly couldn't care less about low level computer internals and like high level programming and AI. That's a perfectly valid position.
Yet you're deeply offended if someone hints that you're not a computer internals expert?
@codeslubber@lemire I fully agree.
However, that has nothing to do with how a computer works.
We're not comparing generic merits. I'm trying to explain what the word "computer" means (and you put up formidable resistance).
@codeslubber@lemire You may recall: the subject that got you into the argument swinging and namecalling was that you disagreed with:
"Haters [of C] usually do not know how computers work"
I kind of though that was the subject? Maybe you got bored and moved on to screaming about other things?
@codeslubber@lemire Please, just this once: Explain exactly where in a computer design does that Bayesian classifier fit? Why do you keep bringing that up?
@codeslubber@lemire > you have no idea how they work or how to make one
Well, I literally did make a computer pretty much from scratch. I know EXACTLY how it works. What are you even talking about?
Oh, rather than facing the embarrassment you went into full blown troll mode...
@codeslubber@lemire Seriously? You can't see it? 🤣
You're literally defending my argument, furiously. In fact you're the living embodiment of it.
✅ Hates C
✅ Convinced that only losers care about how a computer works
A very lengthy read about the state of memory safety in C/C++, but also very balanced and interesting, by John Viega:
#c#cplusplus#rust#memorysafety
https://t.co/tc5lwaEoqQ
@codeslubber@lemire Showing deep dislike for C.
Dated & faulty view of how machine instructions work and repeatedly claiming that knowledge about internal workings of a computer (CPU+memory) is useless.
It's almost as if...
(my work here is done)
@codeslubber@lemire As impressive as they are, Bayesian classifiers have no part in how a computer works. They are functions that run on a computer.
By definition:
computer = CPU + memory (nothing else)
https://t.co/sPBPF5bkJf
@codeslubber@lemire It's the exact same argument all along. You just need to listen. And you have the logic backwards. Knowing the language does not necessarily make you hate it less, esp. not if you're forced to use it without knowing what it's good for. Use it when it solves your problem.