Call me an elitist, but I think people really need to learn and use Git on the command line. It's integral to the job and visual clients hide away not just the nitty-gritty, but often basic processes. Why do I end up teaching experienced developers how to use git reset? There's some day-to-day stuff thaat I do like to do on the IDE though.
[hops off soapbox]
Ranting aside, JetBrains' visuals and organization for Git are really good. Visaual Studio loses track of commits across forks and time, but Rider can keep up, so I'm sure a standalone client will work pretty well.
It’s really interesting that Proton feels like a step forward in cross-platform gaming, but it also made it more economical to focus on Windows builds and dependencies.
Steam has a lot of power in the market and a vested interest in making things easier for developers and publishers. I wouldn’t be surprised if they picked up (more of) the slack in keeping systems backwards compatible.
Same as Microsoft, sort of. They can’t afford to have Apple’s “courage” in dropping x86 and then amd64.
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.
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.
Call me an elitist, but I think people really need to learn and use Git on the command line. It's integral to the job and visual clients hide away not just the nitty-gritty, but often basic processes. Why do I end up teaching experienced developers how to use
git reset? There's some day-to-day stuff thaat I do like to do on the IDE though.[hops off soapbox]
Ranting aside, JetBrains' visuals and organization for Git are really good. Visaual Studio loses track of commits across forks and time, but Rider can keep up, so I'm sure a standalone client will work pretty well.
So how are you liking it?