kittygiraudel / sjsj Goto Github PK

http://riotjs.com/

I find that 'Design Paten' discussions tend to be framed in terms of patterns that tend to need to be shoehorned into JavaScript awkwardly. (see prototype pattern) it might be a good idea to either add some discussion of this or judiciously edit the pattern entry to remove the more java centrist patterns that aren't helpful for discussions of JavaScript in favor of JavaScript centrist ones (e.g. callbacks and promises)

Are you using this page (http://jargon.js.org) for computation?

Is it advisable to include code snippets to enrich a certain definition?

When I heard of this project, the first thing I did was look to see how you defined "Isomorphic", but then it wasn't there :)

Simple analogy here: http://stackoverflow.com/a/29826133/178058

Platform - ubuntu 14.04
chrome Version - 50.0.2661.94 (64-bit)
Issue - search icon show up as blank square.

What would be the proper way to reference another entry in this same repo? For example, in the definition of RequireJS, there should be a reference to AMD. Is it fine to link to master branch, like https://github.com/HugoGiraudel/SJSJ/blob/master/glossary/AMD.md ?

https://github.com/trailsjs/trails

Commonly used in VanillaJS and by libraries such as Inferno: it's the process or re-using JavaScript objects/DOM nodes that been pooled after use, rather than creating new objects/DOM nodes each again.

Include Sails to your list of JavaScript jargon.

Great effort and initiative, you guys.
I'm a web dev for years and i haven't seen this project.

Intuitively, i clicked on the big term name in a single term page, expecting to go back to the main index / single letter index.

The title can be made clickable, going back to the previous state. Might be more convenient than finding the same letter or going all the way to the logo

Hi!

May I translate this repo into Russian?

According to lodah's docs, currying

Creates a function that accepts arguments of func and either invokes func returning its result, if at least arity number of arguments have been provided, or returns a function that accepts the remaining func arguments, and so on.

And in Ramda

Returns a curried equivalent of the provided function. The curried function has two unusual capabilities. First, its arguments needn't be provided one at a time

And wu

Returns a new function that keeps currying until it receives expected arguments, at which point it evaluates fn with those arguments applied.

The mathematical definition (or, at least, the one on wikipedia) and the one currently in the guide is

A function that takes multiple arguments (or a tuple of arguments) into evaluating a sequence of functions, each with a single argument.

I'm not sure how it's done in other languages, but at least in all the javascript libraries a curried function can be called with multiple arguments, whereas the mathematical definition can only be called with one at a time. This type of currying might more rightly be called auto-currying, but I don't really know much about the formal definition anyway, so it might just still be currying. Seeing as how this is a javascript jargon glossary, I think it would make more sense to use the definition of currying as is commonly seen in javascript, even if it's a bit more complicated to explain.

hi Hugo, recently noticed a very large number of {hash}.final files
under the storage folder for Firefox which do not cleanup after themselves.
They are occupying a large amount of disk space unnecessarily.

They all have your name attached, for example,
../storage/default/https+++hugogiraudel.com/cache/morgue
so could you kindly explain why such files should persist?

Thanks very much.

From http://seleniumhq.github.io/selenium/docs/api/javascript/module/selenium-webdriver/lib/promise_exports_Thenable.html:

Thenable is a promise-like object with a then method which may be used to schedule callbacks on a promised value.

(Enhancement)
I have created a gh-pages branch and placed a simple search page that uses the JSON data.
Please check it here and let me know If I should create a pull request.
;)

I'm not sure if subcategories are a good idea, but here's the problem I'm thinking about:

I just submitted a pull request for CORS. inside it, I'm using a lot of terms around HTTP like headers, methods (OPTIONS specifically), resources. I think it would be good to have separate entries for these. But the word resource has different meanings in different contexts, the same goes for the word header. Should I just ad these as HTTP resource and HTTP header, or could it be useful to have a HTTP category under which these entries fall?

Example:

Ramda: a practical functional library for JavaScript programmers.
React: a library developed and used at Facebook for building user interfaces.
Redux: a predictable state container for apps.
Revealing Module Pattern: a design pattern conceptually based on the Module Pattern. The only difference is that the revealing module pattern was engineered as a way to ensure that all methods and variables are kept private until they are explicitly exposed.
RxJS: a library for asynchronous programming using observable streams.
Require.js: a browser based module loader using AMD.

=>

Ramda: a practical functional library for JavaScript programmers.
React: a library developed and used at Facebook for building user interfaces.
Redux: a predictable state container for apps.
Require.js: a browser based module loader using AMD.
Revealing Module Pattern: a design pattern conceptually based on the Module Pattern. The only difference is that the revealing module pattern was engineered as a way to ensure that all methods and variables are kept private until they are explicitly exposed.
RxJS: a library for asynchronous programming using observable streams.

For example I find

Virtual DOM: a copy of the DOM in memory that the program can modify instead of directly interfacing with the “real” DOM to help speed up interactions

to be very misleading as it implies the "real" DOM is not stored in memory,

I don't mean to pick on that specific one and I'd like to make lots of adjustments. I assume you want a PR for this, do you have any guidance however on what is/is not appropriate to edit/what level of explanation you want/the length of the summary/the length of the description?