Instead of entire new programming languages, maybe existing languages can have alternate localizations (done at the IDE level). The same source code would display in a different language from a user with their IDE in Spanish vs the user with their IDE in English.
Edit: Food for thought regarding reserved keywords...
I recently discovered Chrome had MIDI as well while looking for a music sight-reading app. Unfortunately, Chrome for iOS does not support it even though Android does.
Or in my case, I feel the need to learn these technologies so I implement them to some extent, maybe that way I'm more employable. Then again, I love tinkering with new tools and my side projects don't make me any money yet.
I remember that, they recommended a workaround last minute for it. Our snake depended on simulations so we just spun up a beefy GCP instance for a short period at the expense of a few cents.
The level of humour I experience from spoken Spanish (especially on day-to-day conversation) is on another level compared to English. This is solely based on some words/phrases sounding way more funny in Spanish than in English. Can't think of any examples, but generally a quick 2-3 word phrase in Spanish will carry some (intended) funny-ness to it, whereas in English, the joke is on the meaning of the words rather than the sound and expression of it.
My English comprehension level is comparable to native speakers, so it's not because I'm missing any jokes. This is not to say I don't enjoy comedy in English, in fact, I seem to enjoy it as much as anyone else.
I think removing unnecessary code and generalizing redundant parts should be a given. On the other hand, early optimizations such as caching or in-lining should be avoided unless needed.
Slow humans is not as much a bottleneck in Dota as it is in Starcraft. It's easier to "brute force" Starcraft by sheer APM, which is easy for AI to do.
Very possibly. But that would be easily reproducible with layers as well.
Look how there is no perspective change on the rising blocks and the shadow underneath. Blocks just move straight up and down and shadow just increases/decreases in size.
You can probably do this with simple tools. It's all about the layers; If you observe closely, you can see all the objects in the frame have very simple movements.
The 3D effect is just an optical illusion coming from all these simple movements in 2D space.
I read these two as well. Computer Organization and Design and Computer Architecture on my 2nd and 3rd-level computer architecture courses respectively. Glad to hear Hennessy and Patterson getting the Touring award, always had a good hunch about Computer Architecture despite not knowing as much back then.
That's a very black and white point of view. There's lots of grey areas and varying urgencies for problems. I'm sure most respectable programmers would take care of matters as fast as they could, even if it isn't that urgent.
If it takes me an hour to take systems back up after things go bad during the after-hours, it's not because I was purposely not doing my work. It's because that's literally what took me to fix the problem.
Programmers aren't magicians and we certainly aren't out there to get you and waste your time on purpose.