A startup fresh out of private beta offers a three-way intersection between machine learning, the API economy, and open source developers' need to monetize their creations.
Algorithmia, which launched privately last year, allows users to build algorithms, make them available as a Web service, and monetize them.
The service can be used in two basic ways: either by calling algorithms available in the system via its REST API (with examples provided), or by writing and submitting the algorithms to be used. Each algorithm has its own interactive console page, so they can be tried out directly on the Web without needing to write and implement code. Many of the algorithms are original creations; others are implementations of existing software, such as a tokenizer based on Apache OpenNLP.
Last week I talked a bit about how best to protect against the vagaries of human error, happenstance, and Murphy’s Law in regard to remote devices. Most of that includes trying to anticipate every possible circumstance that may occur and provide some kind of protection against them, such as remote-controlled power distribution devices that can automatically power-cycle a device if network connectivity is lost or scripts that run on remote devices that can make sure that some form of remote access, such Dropbear SSH, is running and available.
Last week, 60 kernel developers signed off on a small patch called the Code of Conflict that provides guidelines for discourse in the kernel community and outlines a path for mediation if someone feels abused or threatened. The code was written by kernel maintainer Greg K-H, supported by many of the most prolific maintainers and developers of the kernel community and accepted into the kernel by Linus Torvalds himself.
Release 7.9 of GDB, the GNU Debugger, is now available via anonymous
FTP. GDB is a source-level debugger for Ada, C, C++, Objective-C,
Pascal and many other languages. GDB can target (i.e., debug programs
running on) more than a dozen different processor architectures, and GDB
itself can run on most popular GNU/Linux, Unix and Microsoft Windows
In this post, we have introduced the FrameGraph and the node types that compose it. We then went on to discuss a few examples to illustrate the Framegraph building rules and how the Qt3D engine uses the Framegraph behind the scenes. By now you should have a pretty good overview of the FrameGraph and how it can be used (perhaps to add an early z-fill pass to a forward renderer). Also you should always keep in mind that the FrameGraph is a tool for you to use so that you are not tied down to the provided renderer and materials that Qt3D provides out of the box.
It is hard to believe that the Raspberry Pi has been around for three years already. Launched back in 2012, the credit card-sized PC attracted quite a bit of attention due to its $35 price and potential ability to encourage programming with children. Today, it was revealed that over 5 million units of Raspberry Pi have been sold to date.
From the corporate world I frequently hear how hard it is to predict and track what upstream developers do. On the other side, developers that work part or full time upstream frequently underestimate the need for communicating what they do in a way that enable others (or themselves) to provide deadlines and effort estimations. Upstream and product "time lines" and cultures often differ too much to be compatible under the same environment.