post yfw everything is now programmed in javascript

I guess we'll be reverting to the 1940s then

>>59272545
Embedded JavaScript is already around OP, get with the times.

https://bocoup.com/blog/intel-galileo-javascript-nodejs/

Honestly, I think stuff like Arduino's Process and Galileo and so on are a good thing because they lower the bar for doing DIY electronics and microcontrollers. Who doesn't do something fun with their Raspberry Pis for example.

>>59272545
dumb frogposter

File: 354deaa3770912621bb816da070346ab.jpg (12KB, 258x245px) Image search: [Google]

12KB, 258x245px

>>59272545
>mfw there are people on /g/ who are wasting their time learning Java and C#instead of the language of the future , javascript

>>59272621
>you can't learn more than one language

>>59272545

alert(((!![]+[])[!+[]+!+[]+!+[]])+(([][[]]+[])[+!+[]])+(([][[]]+[])[!+[]+!+[]])+(([][[]]+[])[+[]])+((!+[]+[])[+!+[]])+((![]+[])[!+[]+!+[]+!+[]])+((!![]+[])[!+[]+!+[]+!+[]])+((![]+[])[!+[]+!+[]])+((![]+[])[+[]]));

>>59272545

Why did it have to be Javascript? Why couldn't it have been literally any other scripting language?

At least the Java in JavaScript doesn't mean Java...

>>59272829
cause they basically didn't exist, javascript will die when webassembly comes around BUT webassembly will be awful and much more dangerous.

>>59273991

what the hell is this crap
>The wasm stack machine is designed to be encoded in a size- and load-time-efficient binary format.
Is it like a JVM or what?

File: 5781914-et-arkivsvin.jpg (2MB, 3008x2000px) Image search: [Google]

2MB, 3008x2000px

>yfw wasm will kill js and make all the leddit code artisans unemployed

>>59274015
yeah its like a bytecode level VM in a browser. You can compile target to wasm and then bytecode blob will run.

>>59272829
>Why couldn't it have been literally any other scripting language?

Polite reminder Javascript's only serious competition was VBScript. Be careful what you wish for.

>>59273991
>much more dangerous.

What are you basing this on? What do you think a wasm vm will do that js engines don't already?

>>59274068

So I suppose the idea is that you can compile various languages to wasm so we can do away with messy transcompilers.
If so, that seems like a breath of fresh air.

Javascript is actually one of the best embedded programming languages in existence. It's only real competitor is Lua. It makes sense that it's showing up everywhere. That's what it was made for.

Remember, huge amounts of money and highly skilled people are being applied to the problem of making Javascript good in every way. Forget node -- think V8. Those guys are making Javascript fast and fully featured.

Lua is a simple enough language to implement and has already got a state of the art compiler that's among the fastest dynamic language implementations ever.

Honestly if you're still shitposting about Javascript you're the real pajeet

>>59274110
javascript is already harmful as fuck but wasm won't be as easily introspectable. Also, perl.

>>59274116
Yeah, its also sort of a google counter to asm.js which turned a subset of javascript itself into an assembly interpreter you could target. Pretty fucking horrifying.

>>59274123
>think v8
>low performance JS engine on the backend
not even comparable to LuaJIT.

>>59272829
Because the best paradigm for embedded & extensible programming languages is prototypes. Javascript has objects with prototypal inheritance, Lua has tables.

That single feature is responsible for the unprecedented freedom those languages give you when it comes to extending the host system they are embedded to.

>>59274191
Javascript is a much more complex language than Lua. It makes sense that it'd be harder to implement.

>>59274191
>google counter to asm.js

wasm isn't a google project, it's cross-vendor; moreover asm.js was only ever intended (very cleverly) as a catalyst to force browser vendors to develop an optimized transpiling target language. It was designed for obsolescence from the start and its developers willingly conceded as soon as there was broad interest in WebAssembly

>>59272829
I might be wrong but I'm guessing V8 had a lot to do with the explosive adaptation of js. Would like to hear from someone that uses js extensively though.

>>59274233
its also nondeterministic as fuck, any language that would be usable and fast will be unrecognizable as javascript.

>>59274261
Right, but most of that broad interest was from google pressure/money. They were already losing in the JS engine performance race anyway.

>>59274123
>Javascript is actually one of the best embedded programming languages in existence.

unsubstantiated opinion

>It's only real competitor is Lua. It makes sense that it's showing up everywhere. That's what it was made for.

tangent

>Remember, huge amounts of money and highly skilled people are being applied to the problem of making Javascript good in every way. Forget node -- think V8. Those guys are making Javascript fast and fully featured.

appeal to popularity and authority

>Lua is a simple enough language to implement and has already got a state of the art compiler that's among the fastest dynamic language implementations ever.

tangent

>Honestly if you're still shitposting about Javascript you're the real pajeet

old meme

Feels good. Programming a tool, not some philosophical exercise. Being able to work in one language for everything makes shit just werk.

>>59272545
>npm/node.js
lmao, man, just like everything, it will be done it shit tier NPM or other then moved to C

>>59274310
Chrome has a majority marketshare, there aren't many other places money and interest are going to come from within the space of browser vendors, though incidentally those other entities were on board, too.

It sounds like you're posing this as google's nefarious pet project when in the long-term it was largely foisted on everyone by Mozilla and no one happened to be less than enthusiastic about it anyhow.

Battery technology does not go along with Moore's law. This is the bottleneck now for things like embedded JS/Ruby/Python to be relevant. You simply cannot afford losing 1 hour of runtime because of running a shitty VM as backbone of your application.

>>59274411
Nah, it was always inevitable. It's a shame that nowadays nothing can progress without google's help though.

>>59272545

let fuckyou = {};
best freaking OOP outthere

first O in OOP means Object, not Class

>>59272545
JavaScript is pure degeneracy. See >>59272664
It's like one of those esoteric programming languages except it is used in "production" environments.

Just because hardware is getting faster we don't need to compensate for that with a slow as hell scripting language.

File: 1488508804898.png (337KB, 1144x888px) Image search: [Google]

337KB, 1144x888px

Daily reminder: If you refuse to use a certain programming language you're a shitty programmer.

File: rustled.png (191KB, 534x306px) Image search: [Google]

191KB, 534x306px

>>59272545
>yfw once WASM has DOM access and GC support and completely destroys JS

>>59274437

RAM performance also has not been improving as fast as CPUs have. Many applications may be bottlenecked by an inability to properly use cache because of being written in JavaScript.

>>59274998

I will refuse to use COBOL, and will not take any jobs that involve COBOL programming.

>>59272621
>he thinks i couldn't learn JavaScript in 20 minutes

>>59277567
You could learn enough javascript to be harmful, but not enough to get hired. Buzzword frameworks need to be relearned every few months anyway.

>>59273991
this

File: 1470235957260.png (274KB, 564x600px) Image search: [Google]

274KB, 564x600px

>>59274315
>someone makes a huge industry
>the city its in prospers and attracts people
>hey guys its a good idea to go there and see what it's all about
>I mean that's where the money and people are

>LOL YOU SURE CONVINCED ME WITH THOSE HOT OPINIONS
>TANGENTS TANGENTS TANGENTS
>LOL APPEAL TO POPULARITY YOU'RE BETTER OFF STAYING IN <irrelevant city> WHO EVEN CARES ABOUT THAT INDUSTRY
>LOL APPEAL TO AUTHORITY WHO CARES ABOUT THE HIGHLY SKILLED PEOPLE WORKING THERE

File: 1483541723000.png (394KB, 700x915px) Image search: [Google]

394KB, 700x915px

>>59272545

>>59274602
Agree

>>59273001
Yeah, that would be really disrespectful towards Java

>>59276978
>missing out on all that money and guaranteed employment at absurdly comfy institutions

Pajeet

>>59281783
You're the cancer that's making present day software more and more restrictive. Kill yourself.

File: spooky_wtf.jpg (26KB, 195x235px) Image search: [Google]

26KB, 195x235px

>>59273991
>>59274015
Basically. Unlike JVM the bytecode was designed to be easily verifyable, but that isn't a trivial thing to do.
I expect a couple of hotfixes, similar how Silverlight got a couple of holes fixed.

The other downside is of course that debugging and inspecting the source will be less practical, but thanks to minified js that was a moot point before.

>>59272545
It's not about hardware getting better. It's about programmers getting shittier and that utter clusterfuck we call the Web being what draws most new ones into the field.

I'm old enough to remember late 90's when JS was a new thing. Literally _everyone_ with any kind of programming experience (and these were pre """webdev""" days) was treating JS like typographers treat Comic Sans: as a retarded redhead stepchild. Two decades later an 95% of "programmers" are webdev fucking artisans trying to convince you JS is cool and hip and "actually LISP with C syntax" (even though they've never used either). I guess once you put in the effort to learn all of JS's pitfalls, inconsistencies, and bad design decisions, you have a hard time accepting it shouldn't (and wasn't meant to) be used for anything other than simple DOM manipulation.

>>59281889
the various minifyings and packings and other less useful obfuscations were always around but it was all done clientside, you could modify the DOM API itself to make it easy for debugging.

>>59281845
>javascript
>objects are literal key-value store
>can annotate random objects with your own data
>most extensible language ever
>will eventually gain rich metaprogramming capabilities
>free spec, open standards, free software implementations

>LOL YOU CANCER STOP RESTRICTING US WITH YOURE JAVASCRIPT KILL YOURSELF

File: 1480700535021.jpg (5KB, 259x194px) Image search: [Google]

5KB, 259x194px

>>59272545

>java

File: 26266c83d2b1bc7a5a863fa4ed8d02d873811b7f_hq.jpg (67KB, 750x788px) Image search: [Google]

67KB, 750x788px

Javascript is an absolute trainwreck, have fun with all those () and {} bracket clusterfucks

>>59282549
>language syntax identical to any other
>this is the reason javascript is bad
No.

File: misato.jpg (11KB, 399x259px) Image search: [Google]

11KB, 399x259px

>>59281889
>not using non-minified js for debugging during development

>>59282598

      });
    });
  });
});

>>59282787

>reading js library code

js is like radiation exposure, you definitely do not want to go into the reactor to "see why it isn't working".

limit your yearly exposure

>>59282827
This. Complete clusterfuck. Requires looking at some python for eye bleach.

>>59282827
>what is async/await

>>59282953
Part of the latest spec.
It took years for JS to fix itself.

>>59282888

what about muh lisp

File: 1484205098169.jpg (55KB, 957x621px) Image search: [Google]

55KB, 957x621px

I don't mind JS

>>59282787
You can have sourcemaps for WebASM sources, too.

Also >>59282837

>>59282968
Yes, but it's better now.

js syntax really disgusting

>>59272598
>Who doesn't do something fun with their Raspberry Pis for example.

90% of /g/ who bought one and gave up on their projects

>>59282968
That is not an argument.

>>59283537
>Better now
>IE6 still a release target
Legacy will never let that be true.

>>59284049
It is when half the running browsers still don't implement said feature.
Even node only took it off harmony last year.

>>59284132
That's on the browsers and implementations, not on javascript.

>>59284073
>supporting IE6

Certainly not me. I'm submissive in bed but I'm not that much of a cuck

>>59281783
>trying to counter after getting destroyed this hard
You lost this one, sorry senpai

File: 1486125510385.jpg (18KB, 340x340px) Image search: [Google]

18KB, 340x340px

>>59274032

>>59286425
>LOL BTFO I WIN ANON I'M SO SORRY DON'T BE SALTY NOW

>>59282598
>language syntax identical to any other
u wot m8

>>59287955

javascript syntax ultimately descends from C, all C-like languages have he same obsession with brackets and braces

>>59274602
Except Classes are inherently objects.
You can have an empty class, it doesn't mean it's not an object.

>>59288023
>Rust and Python have the same syntax because they're ultimately based on C design principles
Do you realize how retarded you sound right now?

>>59288047

>python
You mean the language which is most notable for ditching braces and using whitespace instead?
Thanks for demonstrating your autistic retardation.

>>59274110
VBScript would have been better

Nobody would ever have liked it so it would be used sparingly.

>>59272545
Do people actually think javascript is good?

Is this just a joke that's gone too far?

Maybe it's some form of masochism?

Personally I do use javascript regularly. It's just so easy and fun to write, even though I know it's terrible and messy. I have some cognitive dissonance but it feels so good. Kind of like fucking a fat chick.

>>59274123
What is spark? Ada?

>>59281827
That sounds exactly like what a pajeet would like tho

>>59272545
Can't be used for real time applications, regardless of how powerful your hardware is.

>>59282350
Sounds like crippled Lisp to me.

>>59288047
Neither Python nor Ruby belong to "C-like" family of languages (which includes C++, Objective-C, C#, D, Perl, PHP, Java, JavaScript and at least a dozen lesser known ones). Python was actually designed as a successor to ABC laguage, from which it took meaningful whitespace. In the case of JavaScript, it was Netscape's deliberate "marketing" decision to make the syntax Java-like (and give it its stupid fucking name later on) because Java was considered the shit back in 95.

>>59283808
t. pajeet