4 ms·
That easy to write part is something, I am not so sure about. It took me ages to understand why my first try at writing a blender plugin didn't work. It was be
by SunlitCat 2y ago
That easy to write part is something, I am not so sure about. It took me ages to understand why my first try at writing a blender plugin didn't work.
It was because of white spaces not lining up. I was like, really? Using white spaces as a way to denote the body of a function? Really?
- nottorp 2y agoI'm curious... what rock have you been living under in the past 33 years since python was launched?
- SunlitCat 2y agoLet's see, I was living under the: - Amiga E - Assembler (on Amiga) - perl - tcl/tk - javascript - vbscript - java - vba - c - c++ - python rock. Granted at some of those rocks, I just took a quick peek (more like a glance), but a rock with whitespaces being important was, at that moment, new to me!
- nottorp 2y agoOh cmon, I can still write some z80 assembly from memory and remember the zx spectrum memory layout somewhat, but I check new programming languages now and then :)
- SunlitCat 2y ago:) I just meant that for someone coming from a language(s) where different kinds of delimiters are used to denote function bodies, a language that puts such a huge emphasis on whitespace was kinda throwing me off to get an error message slapped at me even though I was replicating the example letter by letter (although, obviously, I missed the importance of whitespace).
- nottorp 2y agoIt's all fuzzy, but I'm sure I knew about the importance of whitespace in python long before I actually tried python. Even Raymond's article which was one of the first whined about it [1]. I definitely remember reading that one and thinking I have to check out that language later. [1] https://www.linuxjournal.com/article/3882 https://www.linuxjournal.com/article/3882