Python and the Real-time Web
mrjoes.github.io
Python and the Real-time Web
1–10 of 18 posts
Re: Python and the Real-time Web
#2I was really confused about the word "polyfill," which the author used without explanation. Since I've written code to render filled polygons before (concavity is a fun corner case), I assumed this was what it was referring to, and I was really confused about how that's even remotely relevant. Wikipedia finally straightened me out [1].
Re: Python and the Real-time Web
#3I like the blog post format better than a Google Hangout. When there's a conversation, unless (or perhaps even if) it's heavily moderated, things get lost in the noise. I was really confused about the word "polyfill," which the author used without explanation. Since I've written code to render filled polygons before (concavity is a fun corner case), I assumed this was what it was referring to, and I was really confus…
Re: Python and the Real-time Web
#4Re: Python and the Real-time Web
#5I haven't read the whole post yet, but is the author saying that a WSGI+Gevent is better at real-time than Tornado alone?
'I prefer out-of-process approach, where separate set of processes/servers are responsible for realtime portion.'
and
'Tornado is the framework I stopped on.'
and
'Greenlets make everything "easy" at cost of possible issues and allow implicit context switching.'
Re: Python and the Real-time Web
#6I haven't read the whole post yet, but is the author saying that a WSGI+Gevent is better at real-time than Tornado alone?
Re: Python and the Real-time Web
#7I like the blog post format better than a Google Hangout. When there's a conversation, unless (or perhaps even if) it's heavily moderated, things get lost in the noise. I was really confused about the word "polyfill," which the author used without explanation. Since I've written code to render filled polygons before (concavity is a fun corner case), I assumed this was what it was referring to, and I was really confus…
Re: Python and the Real-time Web
#8I like the blog post format better than a Google Hangout. When there's a conversation, unless (or perhaps even if) it's heavily moderated, things get lost in the noise. I was really confused about the word "polyfill," which the author used without explanation. Since I've written code to render filled polygons before (concavity is a fun corner case), I assumed this was what it was referring to, and I was really confus…
When did "polyfill" replace "shim," I wonder?
Re: Python and the Real-time Web
#9I like the blog post format better than a Google Hangout. When there's a conversation, unless (or perhaps even if) it's heavily moderated, things get lost in the noise. I was really confused about the word "polyfill," which the author used without explanation. Since I've written code to render filled polygons before (concavity is a fun corner case), I assumed this was what it was referring to, and I was really confus…
When did "polyfill" replace "shim," I wonder?
"Shim, to me, meant a piece of code that you could add that would fix some functionality, but it would most often have it’s own API. I wanted something you could drop in and it would silently work (remember the old shim.gif? that required you actually inserted the image to fix empty td cells – I wanted something that did that for me automatically).
I knew what I was after wasn’t progressive enhancement because the baseline that I was working to required JavaScript and the latest technology. So that existing term didn’t work for me."