|
Yes, TypeScript helps, but only for JavaScript. I find that the hardest thing, because the BS of duck-typed languages causes code breakage at runtime, not compile-time, and the Intellisense sucks no matter what editor you use.
This should really have been included in the options from which to choose when answering this, actually interesting, question.
|
|
|
|
|
It's how to do things, or where to find them.
Like when you switch from C# to Node.js.
Suddenly, your files need to go into specific folders and you need to require them.
You could write one huge file that does everything, but that's not best practice and will come back to bite you later.
Also, learning the framework or libraries.
Like what's the equivalent of System.IO.File.ReadAllText("myfile.txt") (just to name an easy and trivial example)?
In the case of Node.js, you'll probably find x npm packages, but which one is preferred?
It's these things that make a project race past the deadline or even fail completely, not syntax.
|
|
|
|
|
Totally agree with you. The new language usually isn't the problem, but all of the "stuff" that comes with it:
- 1400 npm packages, but most are not what I need. How do I know what I need?
- When do I jump in with JavaScript when there's a new framework every 12 seconds?
- Whitespace matters here, but not here.
- This feature behaves differently because there's 50 years of history (even though the language isn't 50 years old... or 5).
Truth be told, it's the nuance that both frustrates and makes things fun. 
|
|
|
|
|
This poll question sucks. Beyond the syntax, and how you terminate a statement (if you even have to), all languages are generally the same. Google resolves the "it's hard to change languages" problem, because everything is on the internet.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
In my current role I am doing a mix of C# and Python. I did join the company for the challenge of learning something new.
But the biggest feature missing from python is a case statement, there is no such thing. There are hacks many hacks such as dictionaries but the are not clean
Every day, thousands of innocent plants are killed by vegetarians.
Help end the violence EAT BACON
|
|
|
|
|
I don't find the syntax subtleties so puzzling (except maybe some extreme stuff like Lisp or, back in my days, APL), it's mainly a matter of challenging your comfort zone for a while.
It's more the way things must be thought trough the language : predicate languages (Prolog anyone ?), declarations, variables scope, mix of markup/code, object oriented or not, value vs reference arguments, available libraries...
And then the constraints on the development stack (Arduino IDE anyone ?)
|
|
|
|
|
Separating the code (rather markup extensions) from the markup, as in XAML, especially knowing the keywords used in the extensions part of the markup.
|
|
|
|
|
... finding the new way to do old things.
Exception up = new Exception("Something is really wrong.");
throw up;
|
|
|
|
|
I can't select any of those, but it insists that I do.
Edit: Not truly related to the question, more of an issue when switching between languages, even languages you use daily... the use of quotes or apostrophes or backticks for strings or characters, etc.
modified 6-Oct-21 16:54pm.
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
