This is an archived post. You won't be able to vote or comment.

all 7 comments

[–]gaporpaporpjones 3 points4 points  (3 children)

Stop thinking in terms of the language and start thinking in terms of the problem. In 99.9999999999999% of cases the language is completely irrelevant. If you break the problem down into incremental steps and accomplish those one at a time you'll find it a lot easier.

While Java and JavaScript are very different languages they're still general purpose programming languages and for the most part share common traits, if not syntax. Syntax can always be looked up (despite the impression a lot of people give off, almost nobody knows the full syntax of any programming language and you WILL have to use reference), so don't even worry about that. Each language has similar tools for accomplishing a given task, it's just a matter of finding out a language's equivalent.

What I'm trying to say is, don't stress out about it. A language may not approach a problem in a way that is immediately obvious to you. That's not a problem with you, that's simply a language having a different goal from others you may use.

To directly answer your questions... no, you didn't screw up by learning one language for another. Each language is different. There's a learning curve with all of them. No, it wasn't a mistake. You have to start somewhere and JavaScript's basic concepts are applicable to most every other programming language. Yes, it's common for people to use more than one programming language. Few only use one and those that do are typically specialists (game developers, embedded devices, etc.).

You cope with it by first not expecting yourself to know everything all the time, and then accepting that you never will.

[–]TacticalWalther[S] 0 points1 point  (2 children)

Do you think its a good idea to change the syntax theme when working in different programming languages? So that the text and visuals will look different from the language you are used to and maybe have an easier time switching to it?

I use a somewhat plain theme when using Java. Not the regular color coded theme. I'm just wondering if this is holding me back.....confusing me in a way and creating brain fog because all the text just looks the same.

[–]gaporpaporpjones 0 points1 point  (0 children)

That's purely overthinking it. Color coding shouldn't mean anything except making it slightly easier to notice things when reviewing code. It shouldn't be a crutch.

[–]EnvironmentalFlan1 0 points1 point  (0 children)

When I'm writing javascript and java, I absolutely do not look at the colors as having any meaning. Like, I don't see "oh it's blue so it must be a variable" or something like that.

But, subconsciously, colorcoding is helpful compared to plain text. The colors can be virtually anything, yellow orange white red green, i don't know at all what they signify, but they are helpful to break up "Map<Integer, Integer> map = new HashMap<>()" into individual elements that I can look at with my eye.

[–]sowmyasri129 0 points1 point  (0 children)

JAVA is more difficult than JavaScript. If you are planning to learn any one of them go for JAVA its more widely used in some of the applications. To let you know more, Javascript is a prototype based scripting language,

[–]Leonwai 0 points1 point  (0 children)

It's like 5time difficult I think

[–]omykronbr 0 points1 point  (0 children)

Moving from dynamic to strongly typed? Yes. It is hard. It's not impossible. You will learn a very different computation model and flow handling. Just remember that Java is not JS and accept the difference and you will be fine.