If you can't be bothered to set a reminder, subscribe to the RSS feed, create an ifttt trigger or anything like that... I don't know what to tell you. There's lots of solutions to this predicament. This one's on you.
Re:The internals of PostgreSQL
by mickronome on Thursday January 26, 2017 @05:25AM
(#13490187)
I don't think a clearly expressed opinion does warrant the kind of response you gave here. There is little of substance in your comment except questioning the posters character by implying he/she is either lazy or to stupid.
A tip on how to use IFTTT quickly and easily for this particular task would probably be a more constructive response. I for one don't know how to use IFTTT to reliably detect changes in any webpage, I thougt it was mostly for different api services and the like, as those are the only use-cases I've heard about.
Re:The internals of PostgreSQL
by hordeallergy on Thursday January 26, 2017 @04:30AM
(#13489948)
As far as not having to read things twice, draft and final, I'd have to lean towards @sqldba's position.
There is also an interesting middleground named Evolving Publication where the author publishes section by section, and the RSS feed informs you whenever a new section/chapter is added to the article:
https://martinfowler.com/bliki/EvolvingPublication.html
So the RSS feed is not per article, but per article part.
That is interesting, ta, although more work for the author.
Re:The internals of PostgreSQL
by icebraining on Thursday January 26, 2017 @04:41AM
(#13489994)
I, OTOH, would rather know about it and start to take advantage of what's already available, rather than wait for the finish, if and when it ever comes.
I always see these things posted while they're still being written and then I never go back to see them when they're completed. And nobody posts when it's completed.
I'd prefer the posting not be done until it's finished, or, that there be an "email me when it's finished" button.