はてなブックマーク

One of the hot features that came with HTTP/2 was PUSH frames. The main idea is that if the server can predict what requests a client might want to make, the server can preemptively send request/response pairs to the client and warm its cache. This is a feature I’ve been very interested in for a long time. I feel that it can be incredibly useful for APIs to invalidate & warm caches, remove the nee

February 27, 2020 Curveball - A typescript microframework Since mid-2018 we’ve been working on a new micro-framework, written in typescript. The framework competes with Express, and takes heavy inspiration from Koa. It’s called Curveball. If you only ever worked with Express, I feel that for most people this project will feel like a drastic step up. Express was really written in an earlier time of

January 02, 2020 Performance testing HTTP/1.1 vs HTTP/2 vs HTTP/2 + Server Push for REST APIs When building web services, a common wisdom is to try to reduce the number of HTTP requests to improve performance. There are a variety of benefits to this, including less total bytes being sent, but the predominant reason is that traditionally browsers will only make 6 HTTP requests in parallel for a sin

gHacks recently reported that Mozilla plans to remove support for RSS & Atom related features. Specifically Live Bookmarks and their feed reader. The reasons cited are the lack of usage. This doesn’t completely surprise me. Both of the features don’t fit that well with modern workflows. There’s not a lot of people using bookmarks actively except through auto-complete, and the reader interface neve

I think PHP sucks, but not for the obvious reasons. Today I got into a mild discussion on twitter, sparked by the following tweet: Every time someone says "PHP sucks" an elephpant laughs and keeps counting their money earned from getting things done — (((Chris Hartjes))) (@grmpyprogrammer) June 15, 2016 It’s a nice sentiment, and worth analyzing a bit, but first… a little bit of context: My backgr

The PHP-FIG is currently going through some growing pains. I recently resigned as a voting rep, and after some juvenile controversy Lavarel, Doctrine and Propel have as well. Since its inception 8 years ago, the groups greatest problem has been to properly organize itself. From having followed the mailing lists for that time, I believe that the amount of emails entailing “the process, bylaws, voti

March 23, 2016 Npm package author revokes his packages, breaking tons of builds I just came across an interesting post via Hacker News, from an author of several hundred NPM packages (some of which quite popular) that just removed all of his packages from NPM. Tons of other projects around the world depending on his packages broke as a result of this. The NPM project responded by un-un-publishing

March 04, 2015 PSR-7 is imminent, and here's my issues with it. PSR-7 is pretty close to completion. PSR-7 is a new ‘PHP standard recommendation’, put out by the PHP-FIG group, of which I’m a member of. It describes how to create PHP representations of a HTTP Request and a HTTP response. I think the potential impact of PSR-7 can be quite large. If large PHP framework authors are on board (and at l

March 02, 2015 Dropbox starts using POST, and why this is poor API design. Today Dropbox announced in a blogpost titled “Limitations of the GET method in HTTP” that it will start allowing POST requests for APIs that would otherwise only be accessible using GET. It’s an interesting post, and addresses a common limitation people run into when developing RESTful webservices. How do you deal with comp

When you ask a developer, what is a “link”, they may quickly answer “a URL” or “a URI”, but this is not the whole truth. A URL is only an address that you can find to build a resource. A “link” connects one resource to another. My goal is to create a PHP interface that describes the abstract data-model behind a link. To do this job correctly, I felt I had to dig through all the relevant hypermedia

The IETF just published several new RFCs that update HTTP/1.1: RFC 7230: Message Syntax and Routing RFC 7231: Semantics and Content RFC 7232: Conditional Requests RFC 7233: Range Request RFC 7234: Caching RFC 7235: Authentication RFC 7236: Authentication Scheme Registrations RFC 7237: Method Registrations RFC 7238: the 308 status code RFC 7239: Forwarded HTTP extension These documents make the ori