In the modern era, software is commonly delivered as a service: called web apps, or software-as-a-service. The twelve-factor app is a methodology for building software-as-a-service apps.

SSE Servlet example

Aurelia is a next generation JavaScript client framework that leverages simple conventions to empower your creativity.

Der Dystopia Tracker dokumentiert, was in Literatur und Filmen für die Zukunft vorausgesagt wurde – und was davon bereits Realität geworden ist. Inhalte beisteuern können alle, die möchten.

HATEOAS (Hypermedia as the Engine of Application State) is a constraint of the REST application achitecture. A hypermedia-driven site provides information to navigate the site's REST interfaces dynamically by including hypermedia links with the responses. This capability differs from that of SOA-based systems and WSDL-driven interfaces. With SOA, servers and clients usually must access a fixed specification that might be staged somewhere else on the website, on another website, or perhaps distributed by email.

Web development has seen a huge innovative jump in the last years. Frameworks such as Ruby on Rails or node.js and several other frameworks have changed the landscape of the CGI and PHP based web considerably. New programming paradigms have emerged to make web apps managable to facilitate a clean application design. Node.js was the first to succeed in bringing the performance of asynchronous I/O to the masses. With vibe.d we are trying to bring the highest performance possible together with a programming interface that is as clean as possible. At the same time the choice of D as the programming language leads to code that provides much less potential for errors thanks to it's comprehensive static type system. Still, D's clean syntax gives you the same lean programming experience as in dynamically typed scripting languages. The combination is a very fast and practical system that provides a solid basis for many typical web applications and services, as well as non-web services. It st

ODA stands for Online DisAssembler. ODA is a general purpose machine code disassembler that supports a myriad of machine architectures. Built on the shoulders of libbfd and libopcodes (part of binutils), ODA allows you to explore an executable by dissecting its sections, strings, symbols, raw hex, and machine level instructions. You can use it for a variety of purposes such as: Malware analysis Vulnerability research Visualizing the control flow of a group of instructions Disassembling a few bytes of an exception handler that is going off into the weeds Reversing the first few bytes of a Master Boot Record (MBR) that may be corrupt Debugging an embedded systems device driver Satisying your own intellectual curiosity (Does there exist some sequence of bytes that disassembles to the same logical operation for two separate platforms?)

fuzzdb aggregates known attack patterns, predictable resource names, server response messages, and other resources like web shells into the most comprehensive Open Source database of malicious and malformed input test cases.

http://t.co/pFUPmSmF46 Battle for the planet of the APIs #rss #web

Javascript version of Clippy

And what if we got together a bunch of experts who work on large sites to create a definitive front-end performance guide?

Testing for Internet Explorer just got a little easier

Introducing modern.IE: A new set of tools to help you support modern and older versions of Internet Explorer

o demonstrate how installed web applications could work, Mozilla Labs has created some application, directory and store demonstrations.

In the architecture we propose, applications are part of the web. Directories and stores can provide ratings, reviews, approval processes, and proof-of-purchase services, but applications can also be self-published by developers.

I’ve been playing with javascript lately, and here’s the result: QWebClient, a thin client for Qt applications. This is a pure Javascript implementation which runs in any modern browser (no plugins required). QWebClient works by starting an http server in the application process, which the browser then connects to. The project currently has research quality - get the source at qt.gitorious.org

Uzbl follows the UNIX philosophy - "Write programs that do one thing and do it well. Write programs to work together. Write programs to handle text streams, because that is a universal interface."

* very minimal graphical interface. You only see what you need
* what is not browsing, is not in uzbl. Things like url changing, loading/saving of bookmarks, saving history, downloads, ... are handled through external scripts that you write
* controllable through various means such as fifo and socket files, stdin, keyboard and more
* advanced, customizable keyboard interface with support for modes, modkeys, multichars, variables (keywords) etc. (eg you can tweak the interface to be vim-like, emacs-like or any-other-program-like)
* focus on plaintext storage for your data and configs in simple, parseable formats
* Uzbl keeps it simple, and puts you in charge.

StoryTestIQ (STIQ) is a test framework used to create Automated Acceptance Tests or Story Tests.

STIQ is a mashup of Selenium and FitNesse. It is "wiki-ized" Selenium with widgets and features that make it easier to write and organize Selenium tests.

When developing web applications, it is helpful for a cross-functional team to have a definitive and executable view of the requirements for an iteration. STIQ is used to record Customer needs and acceptance criteria; the tests are a big part of the "Definition of Done". The Story Tests written at the beginning of an iteration will initially fail. It is the responsibility of the team to implement the requirements in order to make the Story Tests pass. This practice is called Story Test Driven Development and it is a natural extension of the well known Test-Driven Development and Automated Acceptance Testing practices.