why so many languages that compile to JS [closed] - javascript

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
There is a huge list of languages that compile to JS
https://github.com/jashkenas/coffeescript/wiki/List-of-languages-that-compile-to-JS
the question is: why? for what purpose?
just to avoid programming in pure JavaScript

Because there are javascript interpreters on nearly every consumer device/computer/browser out there. If you make a new language, you normally have to compile it to machine code or ensure that users have your language runtime installed.
Compile-to-JS languages sidestep this by compiling down to a language that already has the capability of running on billions of machines. This means that day-one someone can code in your language, and have it runnable almost anywhere.

Related

Do you guys minify node.js while deploying? [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 3 years ago.
Improve this question
I got a weird question while I'm about to deploy my node.js code. like we create a build version for angular, do i need to generate build version before deploying?(minifying js etc.,). First time deploying node.js, please help! Thanks in advance!
No, you don’t need that
Minifying is used to decrease the amount of traffic, served to users. You don’t need this for a server-side code.
As an analogy, you can ask yourself "Do you minify your php or ruby code?"

Do AMD apps load faster than CommonJS apps in the browser? [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
I have read quite a lot on those two subjects, but they still confuse me. From what I understand, AMD is generally a better choice for front-end applications, since it handles asynchronicity better. Does that mean that AMD applications are faster? Why are AMD modules better suited for browsers?
According to #Mike C, an application using AMD modules will load faster than an application using CommonJS modules, but the difference is in micro-milliseconds.

Has anyone attempted to run node.js or raw v8 engine in embedded environment? [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
Node.js seems opened up a lot of possibilities on event driven paradigm. I'm curious if there's any effort on porting node.js to embedded o/s such as uc/os? JavaScript syntax would be much more expressive than c when it comes to event driven programming, and I wonder if this actually justify the performance difference?
Any opposing thoughts are welcome too.
At least we have a nodejs package in Buildroot (http://www.buildroot.org), which means that people have been running it in embedded environments.

Why is javascript not preferred for server side scripting? [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
we all know that javascript can be used for server side scripting also.but till now I have not seen any practical example or a project based solely on javascript for server side.
Node.js qualifies but Node.js is a software platform that is used to
build scalable network (especially server-side) applications.
My question is why javascript is not preferred for server side scripting? Does it have any drawbacks?

Are modules a good idea in typescript? Or are they just added complexity? [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I come from the Java/C# world where namespaces are absolutely necessary. However, comments like these make me think that modules are of no utility in typescript (and javascript). For large typescript/javascript programs (probably several hundred .ts/.js files by the time we're done), are modules a good practice or do they just get in the way?
ps - I know that opinion questions are not allowed here. But, IMO, this is more a "please explain how javascript works" question.
Having a deep namespace hierarchy is mostly an overkill. Having a single top level namespace is definitely a good idea though.
e.g.
module appName{
class Foo{}
}
instead of
class Foo{}
But not so if you are using already using external modules (commonjs / requirejs) as they isolate code for each file.

Categories