5 ms·
While I was reading this post, the page automatically reloaded to something that said "oops, this page can't be found", and then a few seconds later loaded back
by lambda 13y ago
While I was reading this post, the page automatically reloaded to something that said "oops, this page can't be found", and then a few seconds later loaded back to the original. This is while I was simply reading the text, not interacting with the page at all.
Somehow, through the magic of JavaScript and Websockets, they managed break passively reading static content.
- orclev 13y agoI had to accept cookies from the site before it would even show me anything but a blank page.
- acqq 13y agoIt's not static and it's not readable HTML when accessed without JavaScript. If I understand, that's the feature of the framework that is being praised.
- 1qaz2wsx3edc 13y agoI don't think that's completely fair. Meteor to me, is more cased for building realtime applications. Should a blog be a realtime application? Probably not, can it? Sure. Not only that but, but the page compensated. It's also kind of neat, that the author has indeed written a realtime blog. For fun: they could magically fix typos while you're reading.
- joshowens 13y agoPerhaps I should write a quick event to highlight words as they get fixed in realtime :)
- RockyMcNuts 13y agoOr users could legitmataly highlight typos and they could get fixed in real time.
- joshowens 13y agoGreat idea!
- rywalker 13y agosorry that was a deploy to fix the "oops, this page can't be found" that was flashing before the page loads. When we deploy Meteor, it hot fixes the client (i.e. restarts the app in your browser)
- lambda 13y agoMy skepticism here is due to the use of an "app in my browser" to display a static blog post. A blog post is fairly simple static content. My browser is an app that does fine at displaying it. By making the page an app that dynamically updates upon server changes, you actually substantially damaged my experience, as I was interrupted in the middle of reading the page. I'm not opposed to apps which dynamically update data in real time from the server, when that's appropriate. A static blog post does not appear to be such a case. The irony here is that this was on an article titled "Why Meteor will kill Ruby on Rails", an overstated claim describing how a framework build around updates from the ground up is so much stronger than one based on delivering static content. The actual behavior of the page seemed to speak more loudly than the content.
- oliversong 13y agoTo be fair, this is something that you can easily change if you prefer to take the site down while deploying. Hot code pushes are a feature. It's difficult to implement the same functionality with Rails, where the default is to be down while deploying.