What programing language to pick?

diegoromero24 said:

Programming can be defined as the art of problem solving through code, AS LONG as you know how to solve problems through code, you’ll be a good programmer.

Some languages provide different tools and have their own quirks, yes. But there’s absolutely NOTHING stopping you from learning CS concepts outside of any particular language, which is what a GOOD programmer does. Just because a language is popular doesn’t make it the only choice or THE BEST CHOICE FOR ALL, it all depends on which tasks you want to accomplish.

And yes, as “ridiculous” as you might think it sounds, a professional programmer is usually required to work with new frameworks and even new languages a lot of the times. Or maybe me and all my peers are the only “geniuses” that can switch languages when best suited for certain tasks.

(Source: I program in JS, Ruby, Python and C++)

Click to expand...

jake lionar said:

create web app front end and backend web developement
create mobile app
and desktop app
i already knew some basics of c c++ c# python php, but right now i want to advance or master one language that will allow me to do all the things listed above

Click to expand...

splishsplash said:

For data science and task automation you'd absolutely want Python.

Unfortunately there's a LOT of bad advice out there and it can be very hard to make a decision. I've been a dev since the 90's btw, so I was writing code while a lot of guys here were still learning to crawl.

Ultimately you have to make your own decision, but the thing you need to be careful of in this industry is fanaticism. Ever since the early days it's been rampant. emacs vs vi, linux vs freebsd, freebsd vs openbsd etc. You'll find a lot of die-hard javascript fanatics that will convince you that it's the best thing since sliced bread, but I can tell you that out of all the main stream languages Python is one of the cleanest languages in terms of the actual syntax and how to write code. You can read any code in Python and you'll understand it. Other languages have a lot of quirks and special ways of doing things which that you need to learn the style of the programmer rather than the fundamental style of the language.

Python is strongly-typed. Javascript is weakly typed.

There's no procedural programming in javascript. It's just a big mix of everything. You aren't going to learn about interfaces, polymorphism or multiple inheritance. These things in javascript are more like "hacks". You use prototypes to achieve polymoprhism. I don't think you can implement interfaces, and javascript doesn't support multiple inheritance. There's a hacky way to do it with ES6, but again, do you really want to be learning "hacky ways", or learning the fundamentals in a clean way?

Python is imperative, procedural, OO and functional.

Python was designed to be what it is. Javascript is just a big evolution of addons, hacks and glues to do things. It's very powerful, but this is not the type of language you want to learn to be a software engineer in. It's a power tool for getting stuff done when you're already a strong developer.

Python has way more libs than js.

Most people and articles out there are just full of crap, then you have the die-hards in a language that will convince you it's the most amazing thing ever, but they're lacking the broader perspective to compare because they're so entrenched in their own daily programming practices and way of solving things.


You see this below. This is an example. His response is just "You truly have no idea what you're talking about". Notice how he added "truly" to give it more emphasis. The notion that a js programmer can "switch between languages" in a matter of weeks is beyond ridiculous. See if this guy really understands mutable vs immutable data. I doubt he's even heard of these terms let alone the ability to actually understand the difference.



In fact here's one for you.

Can you make a mutable data type in javascript immutable? If so, how? And tell me if using const on an object will prevent that object from being modified. If not, why.

Click to expand...

fruits = ["apple", "banana", "cherry"]
for x in fruits:
  print(x)

for x in range(6):
  print(x)

for(let i = 0; i < myArray.length; i++){
    console.log(myArray[i].name);
}

for (let part of myArray) {
    console.log(part.name)
}

myArray.forEach(function(item){
  console.log(item)
})

var obj = {a: 1, b: 2, c: 3};

for (const prop in obj) {
  console.log(`obj.${prop} = ${obj[prop]}`);
}

splishsplash said:

What about my question?


Can you make a mutable data type in javascript immutable? If so, how? And tell me if using const on an object will prevent that object from being modified. If not, why.


Answer this. If you can't answer this you have no place giving advice here.

Your entire reply contains vague non-technical language like

"different tools" -- What tools? Programming languages don't have "tools".

"CS concepts"? You've gone even broader now. That could be anything in the whole field of computer science.

Putting "GOOD" in caps doesn't help your argument.

"tasks to accomplish" -- Again, this is not the kind of language a high end dev is going to use.

Neither "professional programmer". Any idiot can be a "professional programmer".

And no, in the field of software engineering a dev is not required to work in new frameworks and definitely not new languages even some of the time, never mind "a lot of the time". Superficial knowledge of multiple languages doesn't mean you're going to be using multiple languages. A dev will generally master 2-3 languages, and that's the top guys. Not many are master level in 5-10+ languages. Just because you can read/write code in a language doesn't mean you're going to be using it on a daily basis in projects.

You don't even appear to me to be an intermediate level dev let alone anywhere near "genius".

Can you answer my question above?

Can you tell me the difference between interface polymorphism and inheritance polymorphism? You won't be able to easily google that answer.

Can you explain what byte code is?

Can you explain how a typo from a very large variable name might cause bugs in a language like JavaScript compared with C# and why?

Click to expand...

Deleted member 923340 said:

Man some good and some terrible advice in this thread.

Are you in a hurry to make web apps? Javascript (NodeJs, React)

Are you in a hurry to do scraping and web automation? Python

If you are not in a hurry and want to learn the fundamentals? You should pick a solid OOP language. For that id personally rechommend Java or C#. (Python works too. But it is not a pure OOP language)

My foundation was Java (not javascript). I can pick up virtually any programming language with the foundation i had. And i can build lot of things if you give me enough time.

Click to expand...

Matheus Moreira said:

OP is probably more confused than before after reading this thread

Click to expand...

diegoromero24 said:

- Depends on what you’re trying to do, if you need an object to be immutable, what you could do is use Object.assign(newObj, list, of, sources), then work on that reference, we often use this when working with React apps.
If you use const on an object you’re storing the reference to the object, not the object itself, so yes, you can still manipulate said object.
Those are like entry-level questions.

- Tools = built-in methods or even frameworks.
- Yep, I was trying to be as vague as I could.
- Don’t really care at this point.
- Never said I was a “high-end dev”. Wtf do you even mean? Senior level? SWA?
- Ok, that’s disrespectful to any swe, so see ya.

Click to expand...

//Using immutable

const { Map } = require('immutable');

const foo = Map({ a: 1, b: 2, c: 3 } ) ;
const bar = foo.set('b', 50);

console.log("foo.b is " + foo.get('b') + " and bar.b is " + bar.get('b'));


// Prints foo.b is 2 and bar.b is 50


// Nothing

const foo2 = { a: 1, b: 2, c: 3 };

foo2.b = 50;

console.log("foo2.b is " + foo2.b) ;

foo2.b = 2 ;

// Object.freeze

Object.freeze(foo2);

foo2.b = 50;

console.log("foo2.b is " + foo2.b) ;


// Using your Object.assign method.

foo3 = { a: 1, b: 2, c: 3 } ;

foo4 = Object.assign( {}, foo3 ) ;

foo3.b = 50 ;
foo4.b = 50 ;

console.log("foot3.b is " + foo3.b + " and foo4.b is " + foo4.b) ;

Deleted member 923340 said:

I've built a ton of shits

Click to expand...

VSYNC said:

OP obviously the next step for you is Haskell. It's the future mate.

Click to expand...

thebotmaker said:

Take this guy's advice.

Click to expand...

VSYNC said:

I think it's going to be more popular than python and js combined in the future because of it's easy-to-use syntax and huge range of applications.

Click to expand...

Deleted member 923340 said:

why stop at Haskell. why not brainfuck?

Click to expand...

splishsplash said:

Yeah, you're completely wrong. Using Object.assign doesn't make anything immutable. Not even close.

What you've googled there is preventing object mutation by using Object.assign and Objecet.assign with an empty object is the same as Object.spread btw.

This has nothing to do with making an object immutable. You're very confused, which happens when you try to pretend you know what you're talking about by googling things in an attempt to sound smart.

Code:

//Using immutable

const { Map } = require('immutable');

const foo = Map({ a: 1, b: 2, c: 3 } ) ;
const bar = foo.set('b', 50);

console.log("foo.b is " + foo.get('b') + " and bar.b is " + bar.get('b'));


// Prints foo.b is 2 and bar.b is 50


// Nothing

const foo2 = { a: 1, b: 2, c: 3 };

foo2.b = 50;

console.log("foo2.b is " + foo2.b) ;

foo2.b = 2 ;

// Object.freeze

Object.freeze(foo2);

foo2.b = 50;

console.log("foo2.b is " + foo2.b) ;


// Using your Object.assign method.

foo3 = { a: 1, b: 2, c: 3 } ;

foo4 = Object.assign( {}, foo3 ) ;

foo3.b = 50 ;
foo4.b = 50 ;

console.log("foot3.b is " + foo3.b + " and foo4.b is " + foo4.b) ;

So you're just plain wrong with that one, but um, nice try.

And you didn't answer any of my other questions, which were harder. I deliberately worded them in a way that makes it hard to google an answer. You TRIED to google an answer to the first but instead you've just embarrassed yourself.

Click to expand...

diegoromero24 said:

HAHAHA. You’re funny.
First link when you Google “object immutability” talks about Object.freeze(), I literally said it depends on what you need to do. I gave you one method us React devs use when working with components and their states.

You should take a chill pill and take yourself a bit less seriously. Anyways, won’t be responding to you anymore, hopefully OP has already made a decision and ignores our back-and-forth.

Click to expand...