To give you some perspective on what I was doing back then: I couldn't even use built in fonts. A friend of mine drew them, and I copied the image of each letter on the screen to show text.
Back then, I didn't have a choice because the only way to get the performance needed was to code in assembler. Learning higher level languages, and the libraries that came with them, was a huge relief. So nowadays, I prefer to write code in higher level languages (mostly Java).
I have heard about Rust. Looks interesting. Each language has its own characteristics and nuances, and may be better suited to accomplish what you want in certain contexts. And sometimes the effect of I/O on performance is way stronger than smart algorithm design. That's why it is helpful to find the bottlenecks, when you’re optimizing performance.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hi Anton.
To give you some perspective on what I was doing back then: I couldn't even use built in fonts. A friend of mine drew them, and I copied the image of each letter on the screen to show text.
Back then, I didn't have a choice because the only way to get the performance needed was to code in assembler. Learning higher level languages, and the libraries that came with them, was a huge relief. So nowadays, I prefer to write code in higher level languages (mostly Java).
I have heard about Rust. Looks interesting. Each language has its own characteristics and nuances, and may be better suited to accomplish what you want in certain contexts. And sometimes the effect of I/O on performance is way stronger than smart algorithm design. That's why it is helpful to find the bottlenecks, when you’re optimizing performance.