The U.S. Web Design Standards is the U.S. government’s very own set of common UI components and visual styles for websites. It’s a resource designed to make things easier for government designers and developers, while raising the bar on what the American people can expect from their digital experiences.

Source: 18F: Digital service delivery | Introducing the U.S. Web Design Standards

The fix. Make sure you backup your system first!!!

  1. Start Services via Control Panel>Admin Tools (also with Ctrl+R and services.msc)
  2. Look for Apache and mySQL services. Look at the patch indicated in the description (right click on service then click on properties). Chances are that you have Apache listed twice, one from your correct install and one from a previous install. Even if you only see one, look at the path, chances are its from a previous install and causing your install not to work. In either case, you need to delete those incorrect services.

    a. Got to command prompt (run as administrator): Start > all programs > Accessories > right click on Command Prompt > Select ‘run as administrator’

    b. on command prompt type sc delete service, where service is the service you’re wanting to delete, such as apache2.1 (or sc delete Apache2.4). It should be exactly as it appears in your services. If the service has spaces such as apache 2.1 then enter it in quotes, i.e. sc delete “apache 2.1”

    c. press enter. Now refresh or close/open your services window and you’ll see its gone.

DO THIS for all services that XAMPP finds as running with incorrect path.

Once you do this, go head and restart the XAMPP control panel (as administrator) and viola!!! all works. No conflicts

Source: XAMPP on Windows – Apache not starting – Stack Overflow

The JXCore Project

Recently, a project named JXCore announced that it will now be open source under the liberal MIT license. One of the key features in the recent release was the ability to run Node.js applications on mobile, both Android and iOS, while leveraging the full Node.js ecosystem on npm.

One of the ways the project achieves this is by supporting a multiengine architecture that allows developers to select which JavaScript engine to use, SpiderMonkey or V8, depending on the platform. The main advantage of the SpiderMonkey engine, in this case, is that it can be executed in Interpreter mode, which is accepted on both iOS and Windows platforms. The net result is that it allows Node.js developers to build a Node application for the server using the V8 engine in JIT mode while also moving part or all of their business logic to the mobile application using SpiderMonkey.

While the project’s creator, Nubisa, says that the current version is still “in development,” it is currently available on GitHub.


Source: Build Mobile Apps with JavaScript and the Node.js Ecosystem | Huffington Post