Group items matching

in title, tags, annotations or url

The River's EdgeParty House

javascript.options.showInConsole = true. Logs errors in chrome files to the Error Console. nglayout.debug.disable_xul_cache = true. Disables the XUL cache so that changes to windows and dialogs do not require a restart. This assumes you're using directories rather than JARs. Changes to XUL overlays will still require reloading of the document overlaid. browser.dom.window.dump.enabled = true. Enables the use of the dump() statement to print to the standard console. See window.dump for more info. You can also use nsIConsoleService from privileged script. javascript.options.strict = true. Enables strict JavaScript warnings in the Error Console. Note that since many people have this setting turned off when developing, you will see lots of warnings for problems with their code in addition to warnings for your own extension. You can filter those with Console2. extensions.logging.enabled = true. This will send more detailed information about installation and update problems to the Error Console.

The biggest question left unanswered in my mind is the role state will play in software of the future.

The biggest question left unanswered in my mind is the role state will play in software of the future. That seems like an absurd statement, or a naïve one at the very least.  State is everywhere: The values held in memory. Data locally on disk. Data in-flight that is being sent over a network. Data stored in the cloud, including on a database, remote filesystem, etc. Certainly all of these kinds of state will continue to exist far into the future.  Data is king, and is one major factor that will drive the shift to parallel computing.  The question then is how will concurrent programs interact with this state, read and mutate it, and what isolation and synchronization mechanisms are necessary to do so?

Many programs have ample gratuitous dependencies, simply because of the habits we’ve grown accustomed to over 30 odd years of imperative programming.  Our education, mental models, books, best-of-breed algorithms, libraries, and languages all push us in this direction.  We like to scribble intermediary state into shared variables because it’s simple to do so and because it maps to our von Neumann model of how the computer works.

many of the fighters carried nuclear tipped air-to-air missiles, so it would have been a bit of a turkey shoot. Until, that is, all of the EMP from the exploding missiles and bombs rendered SAGE unusable.

The web browser is a good example, on a pc it may make sense to ask a user to find, click, type, and browse the web or look for a service. In a mobile, converged product, you need to help the user be present with the service even or especially when they are driving or have the product in a pocket or handbag, and requiring them to constantly select 'yes' or to type in forms etc. are real headaches for a consumer.

We will not provide a store front, but will help the community create multiple online stores from which they can generate revenue for themselves and the developer.

At the other end of the spectrum, you see hoards of teenagers in the U.S., Europe and Asia happily texting one handed, using predictive text.

there is a little bit of hand-waving involved in calling JavaScript a functional language. JavaScript is not a side-effect free language, nor is it an expression-based language (i.e., it is not value-oriented, but rather variable-oriented). There is no tail call optimization in any of the current implementations, so recursion must be kept shallow. And the list goes on. Truth be told, JavaScript is really one of the first hybrid imperative-functional languages.

Higher-order functions allow us to do functional composition,

Since JavaScript does not have "overloaded" functions, this type of functionality is usually simulated using manipulation of the function's arguments. Currying comes in handy because it allows you to do this manipulation in a much cleaner and more modular way.