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.
Related
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 4 years ago.
Improve this question
I've been looking at ways to improve perfomance of my website. I've seen many people mentioning that it is good to minify files in production, which would improve speed as the amount of data that needs to be transferred would reduce. To my understanding, most modern browsers cache HTML, CSS and JS files. If that is the case, is there any additional benefit of minifying these files?
"To my understanding, most modern browsers cache HTML, CSS and JS files"
True, but cached resources are available only after the first visit. The first visit to your website will result in the client downloading all of these resources, and only then caching them, which could result in high response times for large files.
Resource file minification has no other real benifit besides reducing loading time.
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 was thinking of learning Angular 2, but can you actually learn it without any JavaScript or TypeScript experience ?
Angular 2 today works with either Javascript, Typescript or Dart.
It relies heavily on knowledge of one of the languages in order to use it.
You can refer to their Quickstart tutorial as a way to see how an Angular 2 Web App looks like with Javascript or Typescript.
But the bottom line is you will need to have at least basic knowledge of one of the languages to get started with Angular 2
It's also worth noting Typescript is a super-set of Javascript so it supports everything Javascript supports but sometimes the syntax is a bit different and you should approach Typescript after you already have some Javascript knowledge
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.
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.
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.