Interesting, that definitely makes sense!
Software developer and artist.
Interesting, that definitely makes sense!
Actually, I like encapsulating global state in a structured and documented construct. But I guess I could see Java developers going overboard with abstraction in an imperative language.
I’ve recently come to appreciate the “refactor the code while you write it” and “keep possible future changes in mind” ideas more and more. I think it really increases the probability that the system can live on instead of becoming obsolete.
Actually one of the few languages you can learn in its completeness in less than a day, so I wouldn’t really say it’s “hard to understand”. More like hard to read and understands programs written in it.
Interesting viewpoint, but I think the applications aren’t at fault: The operating system should ensure that the user has control of the computer at all times. I think you need to do three things to achieve that:
If it ain’t broke, don’t fix it.
If you know it will break, try to see how to reduce the damages.
A little bit of Go when I’m not too frustrated from loosing the last game (don’t know why this happens only with Go, but I can’t help it) and Netrunner.
Props for actually answering the question, and with a reasonable language too. Although Forth hasn’t clicked for me personally, and I doubt it’s a better choice for OP, it’s still a unique language design and worth studying.
The whole list:
Some highlights:
I just noticed…
Saboteur II (2-12) is a lot of fun. You could say it’s social deduction, but the expansion makes knowing the roles much easier and less important.
I doubt TCP/UDP or basic HTTP requests will change much, but I guess it depends on how high-level the API is.