nebeker

Good article, thanks for the link! In the context of this conversation, I can agree that being exposed to different ways of solving problems will make you better and faster at doing just that.

Common criticisms here would be that these endeavors stifle creativity and show the adoption of modern solutions. That said, I find conducting “code archeology” to figure out the idiomatic way of doing something in an old project very rewarding. Because computer programs exist in people’s mind’s, doing that with the support of original developers or subject matter experts is some of the most effective knowledge transfer I’ve ever witnessed.

My take on a summary: like C/C++, Rust can be relevant in a variety of use-cases and one could conceivably build a long-term career on it, while adjusting to market/technology interests.

Seems like a reasonable prediction?

That totally threw me off. “Literally unplayable,” as they say.

I adore Rider for work, but have found myself preferring VS Code for personal contributions, myself because it’s lighter.

I’m curious about your opinion though: why would you only use them in a corporate environment, assuming the scope of projects is equivalent?

That makes sense. I’m also involved in localization efforts. In niche cases, it’s paid off to work with the clients directly on that. You get you a good balance between correctness and day-to-day usefulness.

Since ladder is mostly diagram-based it almost doesn’t need to be localized and isn’t jarring when you use non-English variable and function names with English keywords.

Apart from being strictly left-to-right.

If he worked in Germany, did he use English or German mnemonics?

If he worked in Germany, did he use English or German mnemonics?

Industrial controls equipment made by German companies can be programmed in English or German. You can also switch languages (German/English) at any time and the IDE switches over all the keywords.

Semicolon!

Shared with my favorite blind iOS dev. Should be a good laugh!