Tyk.io REST was NEVER about CRUD

https://tyk.io/blog/rest-never-crud/

A popular myth is that REST-based APIs must be CRUD-based – that couldn’t be further from the truth. It is simply one pattern in our API design toolbox.

This article outlines a variety of additional patterns available for REST-based APIs. The intent isn’t to be fully exhaustive, but to open the options for API designers uncertain about how to apply designs beyond CRUD to REST-based APIs.

lya Grigorik : Don't "Push" Your Pull Requests

https://www.igvita.com/2011/12/19/dont-push-your-pull-requests/

There is nothing more frustrating than to read the threads, or even worse, be on the receiving end of this experience gone wrong. The contributor is wounded because they are not recognized, and the maintainer is caught in a dilemma: they want to build and foster their community, but they have to dig-in against their biggest fans. There is no winner here and neither side is to blame.
Next time, before you dive into the editor, open a discussion, outline your problem and solution, and offer to do the work - don't "push" the pull request, and don't work in the dark.

InfoQ: Getting to Know Graal, the New Java JIT Compiler

https://www.infoq.com/articles/Graal-Java-JIT-Compiler
Oracle recently announced the first release of GraalVM, a research project that may in time lead to a replacement for HotSpot in its entirety.
For Java developers, Graal can be thought of as several separate but connected projects - it is a new JIT compiler for HotSpot, and also a new polyglot virtual machine. We will refer to the JIT compiler as Graal and the new VM as GraalVM.
The overall aim of the Graal effort is a rethinking of how compilation works for Java (and in the case of GraalVM for other languages as well).

Web: Single Page Application Is Not a Silver Bullet

Seva Zaikov - Single Page Application Is Not a Silver Bullet:



Single-page applications are everywhere. Even blogs, simple html pages (in the beginning something like https://danluu.com/), have turned into big fat monsters – for example, jlongster’s blog has 1206 stars at the moment of writing, and not because of the content (people usually subscribe to blogs rather than star the source): the only reason is that once he implemented it using React & Redux. What is the problem, though? He wants, he makes it, no questions here. The problem is that it is considered normalto make blogs for reading so bloated – of course, there are some people who complain, but the general response is utterly positive. But who cares about blogs – the problem is that nowadays pretty often question is not “to SPA or not to SPA”, rather “which client-side framework should we use for our SPA”.



'via Blog this'

Choosing an HTTP Status Code — Stop Making It Hard – Racksburg

Choosing an HTTP Status Code — Stop Making It Hard – Racksburg:



'via Blog this'

Why Raspberry Pi isn't vulnerable to Spectre or Meltdown - Raspberry Pi

Why Raspberry Pi isn't vulnerable to Spectre or Meltdown - Raspberry Pi: "Over the last couple of days, there has been a lot of discussion about a pair of security vulnerabilities nicknamed Spectre and Meltdown. These affect all modern Intel processors, and (in the case of Spectre) many AMD processors and ARM cores. Spectre allows an attacker to bypass software checks to read data from arbitrary locations in the current address space; Meltdown allows an attacker to read data from arbitrary locations in the operating system kernel’s address space (which should normally be inaccessible to user programs).

Both vulnerabilities exploit performance features (caching and speculative execution) common to many modern processors to leak data via a so-called side-channel attack. Happily, the Raspberry Pi isn’t susceptible to these vulnerabilities, because of the particular ARM cores that we use.

To help us understand why, here’s a little primer on some concepts in modern processor design. We’ll illustrate these concepts using simple programs in Python syntax like this one..."



'via Blog this'