It's 1 megahertz, not 1 megahert.

Sorry, there is a big mistake in the first few minutes. The BASIC that was laying around ( = Dartmouth BASIC) was adapted by Microsoft for the Commodore 64, and there was very well paid for. Back in those days 25.000 US Dollars was a huge sum of money. You could buy a house or a big luxury car for that. And besides that, Microsoft adapted BASIC for other 6502 computers before, so it must have been not to much work.

Great video mate, thank you very much 🤙

So, I have to type in A string of incomprehensible gibberish instead of 1's and 0's? Yeah, no thanks

For future videos, can you please turn off DARK MODE, as makes viewing in a mobile screen almost impossible.

More of this stuff, Please! Awsome!

popcnt had a false dependancy on skylake, fixed in sunny cove.and onwards hence xor eax,eax

This is very clear

bro it's time for me to upgrade my laptop xD

This explanation was so great. Assembly is not an easy thing to understand, and you made it very clear. Nicely done!!!

This was so fun to watch even tho I only understood 30% or so of it. This tells me how much I have yet to learn. Thanks for posting this

Dear Mark. Sans this "magnificent eight" the RISC-V will show very low performance, and will not reach the technical level of Intel/AMD/ARM. My MHP RISC architecture is far ahead, for it do not need "magnificent eight" at all.

Oh I remember learning really quickly those hex codes and could look at a row and divide it out in my mind and just type in the graphics I had drawn on the graphing paper. I never wrote my numbers out ahead of time, but I loved watching how you showed everyone the way it was done.

Maybe a follow on video of why we use pointers?

Jack really said that to Bill? He’s my hero!

05:09 The RISC-V architecture defines 32 registers named x0 to x31. x0 is always read as 0, and writes to x0 are discarded. The a0 register is actually an alias for x10. Every register has an alias name, and the aliases reflect the usage of the registers in the standard calling convention ABI. For example, the return address register is x1 and has an ABI name ra, x2 is used as the stack pointer and has the ABI name sp, and so on. The "a" registers a0-a7 (x10-x17) are used for function arguments and return values (a0-a1).

Still don't understand why ARM is efficient. It still has more instructions on average to handle right ?

I never thought about this thing that pointer takes 8 bits. It reason why addresses of variables don't follow each other (have gaps). Now I understand memory allocation better and clearly see that pointer to int takes more memory than just int. Very usefull video, many thanks!

Great vid!

awesome, it explains pointers like no other. thank you so much for making this video!

This video came a few hours too late for me. A pointer places an address in ram to be easily referenced. Realistically, I knew what a pointer was before in other words [a reference to an address on the stack]. I was picking up assembly, and it gave me the notion to redefine the meaning of a pointer.

What is a pointer? The c-array identity crisis.

this

No 64 how about the VIC 20.

In programming languages like BASIC, the $ was ALWAYS used for strings, as far as I'm aware. It just made it easier to separate the variable types. But in modern languages, the type of data a variable will hold is always declared at the start of a procedure or function, and no special symbols like $ are even needed anymore.

I am also still surprised about the Euro to String ratio on the financial markets with my damaged brain.

so, are you ready? what do you mean if I am read Y?

READY PLAYER ONE! ?OUT OF PLAYERS ERROR!

Be aware that some laptops have whitelists that prevent part upgrades or replacement parts from other brand.

I still call $ string

I'm sure is a glitch, the read y in string should've returned ?TYPE MISMATCH ERROR not ?SYNTAX ERROR and without line, it is very weird

in an instant, it's READ Y

There was a TV show called "Vega$" circa 1980, and I always read that as "Vega string", although I knew that was not the intent. I was aware that Commodore (and Atari) computers used "READY" (with or without a trailing period) as a prompt, and that their screen editors would read it as "READ Y" if <enter> was pressed on those lines, but it didn't affect my reading of "ready" in other contexts.

Read Y? Because reading is fun!

Try vic-20 BASIC.

I feel your pain. I read '$' as 'scalar' due to Perl.

I luv my C=128.

mind blown.

I wish I still had my super-fancy “databases” I wrote on my C64 in middle school, cataloguing my books with lots and lots of DATA statements. 😀

3:27 Running the DATA statements actually does nothing. There is no buffer (it would be a waste of memory to have one), and READ simply scans the actual BASIC code for DATA statements. The pointers you've been reading point directly into the code. That's why you got a syntax error at 100: READ wasn't reading any buffer, it was reading the actual line 100. The pointer increased by 3 because there are two digits and a comma. And finally, notice that in almost all code printed in magazines, DATA statements are at the end of the program, so they couldn't have possibly run before the READ statements. The RUN statements resets the pointers to the beginning of the code, so that you can read the data from the beginning when running the code from the beginning. And the obvious corollary of all of that is that executing DATA in the immediate mode does literally nothing.

Well, basically you had no chance to use meaningful variable names, because they could only be one or two characters long (not including a $ for strings or # for integers - which were useless, since everything got converted to floats internally anyway). You could use longer names, but everything after the second letter was discarded.

The C-64 designers must have put it there intentionally as an Easter egg, just to screw over with newbies

Great… so now every other c64 channel i watch will do a video on this.

Huh, I wonder if the $ usage influenced Clickteam's Fusion game engine, historically it has always had $ at the end of names that result in strings, but only by convention.

I also read the $ as "string" for many years

I was not read Y for this xD. Thx!

Try not to wear hand jewelry when working with electronics. Watch bands can snag and and rings can conduct.

The result of the JIT optimisation is not stored between the runs. It would suggest, that in this case it may not be worth calculating the final result by JIT, the JIT would need to take CPU time to calculate the result to create the final value. Potentially it is just a better overall/global strategy, to minimise the total CPU usage, to calculate the value once by not fully optimised code, instead of calculating it within JIT, just to return it from the generated code and exit. My point is that in Java byte code execution cost we need to add JIT+optimiser execution cost to the cost of the run of the generated binary. Unlike in compiled and optimised c++ binary execution where only the CPU cost of binary run matters.

For brands, I prefer Clevo due to the great experiences I've had with Linux - but I also tend to buy overpowered systems.

I still use a 10 year old T430. Replaced the keyboard (from T420), screen (from T440), maxed out the RAM, added SSD