@pvblivs Never used that feature. Basically every “read later” variant I ever used ended up being read never rather than later.
1
@markusvoelter Accompany it with a significantly alcoholic beverage of your choice?
1
@roidrage Agreed! I think my colleagues @rstrangh and @mrreynolds did an excellent job of that for our site, too: innoq.com/de/articles/2013/0…
1
“Reader mode” is my favorite Safari feature by far. There are so many websites I just can’t stand in their ridiculous original layout.
2
5
3
@coreload As STL is definitely not object-oriented, it seems to me to be entirely logical that its creator would think so.
2
@dancres From personal anecdotal evidence, I agree it’s completely gone for public APIs. Still quite often used internally, but decreasing.
@dancres I would like to believe WS-* lost because of RESTful HTTP’s architectural benefits, but suspect it was the former’s complexity
1
@hichaelmart For purely aesthetic reasons, I’m unhappy with “content-type” and can’t make Node/Express send Content-type instead
1
@bastiankrol Custom headers I set work fine, ‘Content-type’ doesn’t work for me. It’s probably somewhere inside Express.
So there really is no way to make Node.js add and send HTTP header names in their mixed case form, as God intended them to be sent?
4
1
Very slightly indeed RT @trondhr: @stilkov Or the slightly more sinister Apocalyptica :-) youtube.com/K6WCZqd9TXw”