All the knowledge about every language in existence.

Just imagine never having your questions downvoted on SO because you never have to ask questions anymore <3

Also getting a really good Dev job because you know the language very well. You might have too much info in your brain but the genie probably accounted for that

@Sony-wf-1000xm3 If you formulate the wish well enough, yes.

That would mean you know java, php and JS.
St that point you would be better off dead.

@mundo03 I already know PHP (it's my fav language) and JS (I work in EmberJS pretty much daily).

Now with Java... yes... Though C# and Python can also go die in a fire :^)

@FinlayDaG33k
You better not say anything about ruby.

But man, 2 out of 3 lame languages, you must take antidepressants.

These days, or infact since long, knowing a language isn't sufficient.
Knowing some libraries is more of a skill that is sought. Easily getting up speed to a language imo should be your basic skill set as a dev.

@mundo03 I used to work in Ruby quite a bit (cus well... RoR) but it fell out of favour to me because PHP is just a lot more popular and easier to find stuff for :p

@A4Abhiraj correct but if I already know a language very well, it should make using those libraries (and patching up shortcomings and what not) a whole lot easier :p

@FinlayDaG33k how dare you say that.
RoR has grat docs you don't need anything else, you can't find shit because not a lot of people are asking, because good docs.

On a serious note, I used RoR v3, moved to Sinatra whenever I need to do anything with a backend.
But I have read there have been huge changes and improvement after that.

I also do python for automation (because they won't let me use ruby) and JS to get angry at how much you need to write to achieve simple things.
I still think JS has nothing to do on the back and Vanilla JS with no node is enough for everything front end, anything complicated should be webassembly, not Js and node bullshit.
:D

@mundo03 I mean library wise :p

Back then a lot of stuff required me to make stuff from the ground up that I didn't yet fully understand (cryptography related, which isn't something you want to implement if you don't understand how it works) while PHP just had those libraries as simple modules.

The landscape may have changed since then as it was about 9 years ago already.

I only use Python for demo stuff (like, I built a demonstration of how mining works on a more technical perspective - like how the hash is *actually* made - a while ago) but that's it...

Though nowadays I do tend to lean towards Julia for that because it's less messy to understand for non-devs imo.

(1/2)

For JS you do sometimes need to write *too* much yes.

But EmberJS does a lot for me.

My dashboard (https://gitlab.com/finlaydag33k/...) is made with it).

For back-end JS (like Yuuki, my little monitor/personal assistant thing) I use Deno, not NodeJS because I prefer TypeScript and to not have to bother with 1337666 modules and dependency hell all the time...

just slam the module in my file as a link and be done with it, let Deno figure it out.

Also means that I don't accidentally break my app if I use version 1.x of one library in one part but *need* 2.x in another part.

Or if said library has a dependency that would conflict with a version that I need elsewhere.

Deno, imo, is what NodeJS *should* have been.

(2/2)