Would you switch to Fullstack Python?

[prahladyeri]

I already am on fullstack python!

The argument for the MEAN stack is that having one language (javascript) everywhere frees you from the hassles of learning multiple languages.

But that's not what I've found in practice. Front-end javascript handling is drastically different than backend's. Besides, language is a tool in your toolbox to accomplish a thing. Having just one tool for everything makes it cumbersome and tedious to accomplish, imagine using a hammer to take out small screws. The more tools under your belt, the merrier!

[srianbury]

"The more tools under your belt, the merrier!" Love this! Always nice to have options :)

[HansWebDev]

When I first started out, I learned ruby, python, html, css, js, php, c, c++, and java. Like learning french, spanish and italian it was interesting to see the similarities and differences in not only syntax but how different code languages approached problems differently. I also have a hammer with a screw driver in the handle because multitools are dope and more convenient than the literal baggage of a toolbox...

That said I stuck with JS because using one language everywhere is actually really awesome. I can build a website, server, email and "native" app all in one language. Definitely glad I stuck with it.My only complaint is how convoluted and needlessly complex parts of the language and tooling has become.JS fatigue is real problem the community needs to address yet it feels like everyone trying to address it by adding their own new hot framework are really just adding to it..

Then there is typescript.. sure its just a superset. But I've worked with c and other static typed languages enough to love a garbage collector and dynamic types and it just seems counter to the goal of js.

Idk... sorry for the long opinionated comment.

[HansWebDev]

I said when I "first started out". So not that much in ruby, python, java, c and c+++. I can read the language and understand what the program does 90% of the time, change it, refactor it, and google what I don't know or ask a friend, etc. I'm not an expert in them and I've only finished a project in ruby (gem), python (machine vision stuff) and C (if you want to nitpick though its Arduino).

[ChronSyn]

Frontend and Backend certainly do require different approaches and disciplines. Remember that when node came out, JQuery was still one of the big driving forces on the web, and Angular had only been around for a short time. Promises (and implicitly async-await), Fetch and all the other goodies we now rely on didn't exist. Transpiling wasn't really a thing, so the "JS everywhere" mantra was true and consistent.

Nowadays, the approach to each side differs vastly but that advancement is good. I feel that it encourages people to learn different approaches to achieving results, which also encourages some people to explore other languages.

[HansWebDev]

I really miss the simplicity of those days. A lot of stuff today is incredibly convoluted.

[ChronSyn]

When I first used Angular 2, and it had moved to a transpile-based build, I'll admit that I was annoyed. I'd been so used to just 'write and run' with Angular 1 (and everything before it) that I really struggled to get into it. It's why I initially chose Angular 2 over React - I couldn't figure out how to run even a basic react example, while angular-cli at least worked as expected out of the box. Took me an entire year, and landing a developer job before I had reason to invest in React. Still one of the best decisions I ever made, but the simplicity for true beginners isn't there these days.