Assembly is the lowest I've personally gone in terms of "close to the hardware". But there are a lot of fun things you can do when you actually talk to the cpu (basically writing out the program directly, instead of using an assembler. There are a lot of hidden/duplicate (with different encodings) instructions you can abuse to make a disassembler give up.
Depends on how high level. IMO f# (and ML-likes in general) are really pleasant to read and write.
He also treated Kris Tyson with kid-gloves, and flipped more shit about Mr. Beast being a fraud than he and his buddy grooming minors.
Isn't that the language Chris Sawyer used to write Rollercoaster Tycoon? I don't know jackshit about programming.
Yes, but he's fucking autistic for doing so. He's not normal.
Are you implying that's a bad thing? It still holds up 25 years later.
The very first problem when you teach someone who has 0 knowledge on programming, is to have them think about how a computer does things at a high level, if you jump into the fire fully at the starting line, you'll overwhelm a person.
Assembly isn't really one language. But rather a label for a specific level of abstraction (not a lot of abstraction) where most instructions map effectively 1:1 to actual cpu instructions. And yes, it's what sawyer used.
And if you use typescript, avoid "any" like the plague. Thats one of the very few strict pieces of advice I can give in relation to programming.
IME functional languages lend themselves the most to learning programming. Mutation is HARD to really wrap your head around.
I've only touched a little bit of SML and Ocaml long ago, and I think I agree with you on the "computer science level" but disagree on the "engineering level" if that makes sense. If you start asking questions like, "how does this look on the assembly level" and "what's the layout in memory" and so on, these languages are "hard to read". Also, language features like overloading, inheritance and generics can make the code hard to read because, say, a "+" operator might not be what it seems. I don't think being able to type your program in fewer characters is a readibility feature, but a writability feature.
It was what he had experience with. He had been writing in assembly since the 80s and found modest success because he was able to write more efficient code than other languages which made a world of difference when you were working with hardware Of the day. Before going back to making his own games he ended up doing a lot of ports of arcade games to PC that were much more accurate to the original than competitors could come up with.
When RollerCoaster Tycoon was developed writing assembly by hand wasn't that rare. Especially for someone like Sawyer who started in 80s.
Most probably should not ask those questions, as they are not that straightforward to answer nowadays. Also there is programming thread for those who want to discuss it further. Maybe not shit up Maldy's.
I don't quite agree with you there. Sure, inheritance definitely tends to be more of a detriment than positive, but overloading and generics make the code easier to read, because you can have one function to iterate over any kind of list and do stuff with the element (the humble map). But obviously you can use those features to write absolutely unreadable code as well. Just IME, with functional languages you use the standard constructs most of the time (map, flatmap, filter, fold, etc) instead of relying on bespoke functions that are simpler to understand in isolation, but which are harder to understand in the big picture sense.
Which makes list iteration, map iteration, tree iteration, etc look the same. That's why I agree on the "computer science level" (you have an abstract container and want to go through its contents) and disagree on the "engineering level" (wtf why are you trying to make 3 totally different things look the same). I like that old John Carmack quote about him preferring to be constantly aware of the full horror of what he's doing
Nearly all console games up to 16 bit were written in assembly. They just had some more cool instructions specific to the hardware.
Or you can just use your favourite language for all of those things.
Just make sure to glaze it.
TypeScript and React bloatware? what?
Avoid all JavaScript frameworks when learning. They serve a purpose for getting work done faster, but will give you horrid habits.
Genuinely off-topic, I know, but I have to clarify: at what point does PHP come into this flow you're outlining considering it still seems fairly prevalent today?