Atwood’s Law states that any application that can be written in JavaScript, will eventually be written in JavaScript. Winamp2-js is yet another example supporting this law. It is a re-implementation of Winamp 2.9, a classic Windows MP3 player from decades ago, done in HTML5 and JavaScript.
The source code is on GitHub and a live demo is available here.
“A Practical Introduction to Container Terminology” is at the same time two things for me:
Strongly recommended.
Here are some very exciting news from the Nginx front lines: HTTP/2 Server Push is now available in the latest and greatest Nginx 1.13.9, which was released yesterday!
Server Push was one of the most exciting features for me in all of the HTTP/2 specification. But I wasn’t quite sure how it will be implemented, and, most importantly, how it can be made easily available to the web developers, who are often few levels removed from the web server configuration. I think Nginx solves the problem quite elegantly.
On the configuration level, “location” directives are often available to the web developers withing the virtual host / server. But for those who can’t use those or don’t want to mess around with the configuration files, an even easier option is available – Link HTTP header.
I’m sure this will soon be widely supported in all the major libraries and frameworks, much like HTTP cookies are.  Great times ahead!
A while back I blogged about TreeSheets, which is a flexible free form data organizer. If you tried that but felt that you need something slightly different, then check out TreeProjects – a personal database software for home and business.
TreeProjects provides an unlimited, freeform, ordered hierarchical organization of your information items (in a tree), single-file compressed data storage, instant single-click item viewing and editing, multi-tab interface for concurrent editing of several items, powerful search capabilities, and many other features.
Collaborative editing is a very challenging subject, technically speaking. The old days of users editing a file, sending it to another user, and back are long gone. Version control tools like git helped with tracking changes and resolving conflicts. But the newer generation of tools – Google Docs for example – push the bar even higher. Now many users expect real-time, transparent collaborative tools, which allow multiple users to work on the same document at the same time and without any additional technical complexity.
Automerge is one project that helps the developers to build such collaborative tools, by providing a library of JSON-like data structures, which can be edited in parallel and then merged back together.
Automerge […] supports automatic syncing and merging:
- You can have a copy of the application state locally on several devices (which may belong to the same user, or to different users). Each user can independently update the application state on their local device, even while offline, and save the state to local disk.(Similar to git, which allows you to edit files and commit changes offline.)
- When a network connection is available, Automerge figures out which changes need to be synced from one device to another, and brings them into the same state.(Similar to git, which lets you push your own changes, and pull changes from other developers, when you are online.)
- If the state was concurrently changed on different devices, Automerge automatically merges the changes together cleanly, so that everybody ends up in the same state, and no changes are lost.(Different from git:Â no merge conflicts to resolve!)