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
Does browserify, webpack, and other still have a purpose now than we have the module import with es6?
Beside of the coffee/typescript conversion, I mean.
Does browserify still have a purpose after es6
Of course it still has purpose.
Browserify/webpack resolves requires/imports and packages your code into a bundled file (or files). ES6 (ES2015) doesn't do anything to change that need.
Until the browser gets a native support for resolving require or import, many people will still want to package their code. Even then, bundling is still useful because you can package your code into a single http request instead of one http request per import.
Maybe after all browsers support http2 and native import, then you can start ditching the bundlers ^_^
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 5 months ago.
Improve this question
What are the open standard principles ?
I googled it but I am getting different answer from different website cant decide what to write
It's a pretty confusing concept because it is NOT the same as open source.
Open source means you can get the CODE and use it in whatever way you need (make your own changes etc).
Open standard means you can get the PROGRAM / TECHNOLOGY for free. To put it very roughly, open standard is that you can get a complied ".exe" executable (but no source code), and install the software at no cost, and open source means you can have the code, make your own changes, and then make your own ".exe" if you want.
HTML and XML are open standard technologies.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 2 years ago.
Improve this question
I would like to display a code snippet from my own public GitHub source repo in my own web site, without having to make a copy. This is for a tutorial to illustrate some programming concepts. So not to run it but to pretty print it, as it were.
I bet this is something that many people need. I am looking for a lead on how to do this.
You could use the GitHub API to accomplish this.
See the Get Contents endpoint.
Yes, you can do that either by publishing your repo on npm and then referring it as npm dependency in projects package.json.
or 2nd , you can directly refer GitHub repo as dependency in package.json.
Hope this gets you in right direction.
thanks
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
I am really thinking of how I can build a very minimal Git-like software only for my self for now!
I have gone through Git documentations and even the way git works and I have quite an understanding on it.
Is there any example for me to study as a bonus before I dive into this project?.
In addition to the Documentation/technical folder which explains the internals of Git, you can study how Git was re-implemented, as an exercice, in other languages.
See for instance:
in Go the project src-d/go-git (recent 2018),
in Javascript: danlucraft/git.js (much older),
In Javascript (more recent 2015): Gitlet.
In Java, the project eclipse/jgit (used by EGit)
In C (with a lot of bindings for other languages), LibGit2 (and its GitHub repository, apologies to Edward Thomson for not mentioning it first.)
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
It seems like the React community has heavily adopted ES6 as de facto when building applications, but I realized using ES6 with Polymer is fairly uncommon and doesn't seem to be actively encouraged. I was wondering why this is and if it's considered bad "style" to develop Polymer components using ES6 and compile them down to ES5 with Babel or something?
Polymer and the Polymer Elements don't require transpilation to use. To use ES6 would require users to add a transpilation step. Why should you require this extra overhead? When's the last time you saw react components distributed without requiring a build step?
That being said, ES6 code works well with Polymer. I use both in my projects. It will work much better when the proposed changes to the custom elements spec are available.
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
With various methods to get around the same-origin policy, such as CORS (if you have access to the server hosting the files), or by using parsing methods such as the getJSON method in jQuery, does JSONP ever now need to be used?
(I actually struggled for a long time to get my head round JSONP anyway - I don't think it helped that some sites seemed to overlook it - for example, the Google Map developer docs state that they return data as JSON, but make no mention of the Same Origin Policy - is this naïve of them for assuming most people know of the issues and can get round of it, or naïve of me for getting too bogged down with trying to understand the technical differences between JSON and JSONP?)
Yes, JSONP is obsolete now. There's absolutely no reason to offer a JSONP service anymore. Ajax with the relevant CORS headers is saner and cleaner.