this post was submitted on 06 Feb 2024
104 points (94.1% liked)

Programming

16769 readers
168 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]



founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 27 points 6 months ago* (last edited 6 months ago) (1 children)

Currently the obvious tell is if they pitch Rust

I would amend that to "if they pitch any language".

The best language is almost universally "whatever we already use" or for new projects "whatever the team is most familiar with". It should occasionally be reconsidered, and definitely try out new languages, but actually switching to the new language after trying it out? That should be very very rare.

[–] [email protected] 6 points 6 months ago* (last edited 6 months ago) (1 children)

The team/organisations knowledge is a huge factor but its easy to fall into a trap where no matter what the problem is the solution is X language.

If I have an organisation that knows C# and we need to build a Web Application. I would suggest we need to learn Node.js and Typescript and not invest in a solution that turns C# into web pages.

[–] [email protected] 2 points 6 months ago

Wait, are you seriously overlooking ASP.NET and suggesting c# tes learn typescript and node to build web apps?

I get that it's a hypothetical, but typescript and node shouldn't be the first stop on the we need to build a web page train for folks already in the c# wagon.