The absolutely worst two things which happened to Blogger during the last few years are, IMO:
1. What I percieve to be excessive use of JS. You can't even load a blog post there (well, at least, couldn't last time I visited a dot-blogspot site) without an on-page spinner and a bunch of stuff apparently happening in the background.
2. The tld-redirect crap. Admitedly, I had actually thought a similar mechanism to be benefitial prior to seeing an actual implementation of it but I mean, come on, does this not annoy others? What's the advantage of that anyway? Google is capable of geographical load balancing with IP addresses alone just fine, what's the deal?
Disclaimer: These are my end-user reactions. I have never operated at the scale Blogger does so there may be reasons I am not aware of.
Exactly. Blogs are mostly text sites and one would expect such to open at rapid speeds. That's one of the things I like about Svbtle, they load the blog as one single request/response with all the text, styles, JS(barely noticeable) inline making for very rapid load times
I wouldn't say excessive use of JS was the problem. JS provides the foundations to tons of extremely fast websites and should (in most cases) assist with improving performance. I'd blame the overall implementation / design which led to scaling and performance issues.
What I hated about blogger was that for a "group" blog (say, the reddit blog, where different admins might post), any images added to the post get shown from the poster's google account (somehow). Which means if someone leaves the group, the images get hosed.
>I managed to write the whole library without a single #ifdef! Generates Linux .so, OS X .dylib, and Windows DLLs. Amazing!
Could you expand on how you are doing this? You're still using a Makefile or a similar tool with some kind of platform detection for the build itself, right?
Not sure whether the parent does it like this, but you can use cmake to describe the build, and then (for instance) run cmake --build to build the project in a 'cross-platform' way using the platform's native compiler toolchain, it works the same on Windows, OSX and Linux. I think what the parent meant with 'no #ifdefs' is that the C++11 std lib comes with more modules that make a lot of platform-specific code-paths unnecessary (for instance std::thread, std::atomic for threading, and std::chrono for high-resolution time-measuring).
Yup, you nailed it. cmake for handling the builds, and the C++11 stdlib covers every platform-specific thing I needed. The only platform-specific thing I needed to do was point the CMakeLists.txt at the correct libusb (libusb.so, libusb.dylib, libusb.dll). Absolutely beautiful.
Edit: to elaborate a little more about cmake... You can use cmake to generate both Makefiles and Visual Studio build files.
On Windows:
mkdir build; cd build; cmake .. -G "Visual Studio 12 2013"; cmake --build .
Your link mentions CPython (the reference/official Python interpreter), not Cython (optimizing static compiler and extension of the Python language) so I'm not sure it answers the question raised by parent.
You're right. The parent didn't provide enough information on the use of Cython. And frankly, there's no better way to find out whether PyPy supports a particular C extension than to try it.
1. What I percieve to be excessive use of JS. You can't even load a blog post there (well, at least, couldn't last time I visited a dot-blogspot site) without an on-page spinner and a bunch of stuff apparently happening in the background.
2. The tld-redirect crap. Admitedly, I had actually thought a similar mechanism to be benefitial prior to seeing an actual implementation of it but I mean, come on, does this not annoy others? What's the advantage of that anyway? Google is capable of geographical load balancing with IP addresses alone just fine, what's the deal?
Disclaimer: These are my end-user reactions. I have never operated at the scale Blogger does so there may be reasons I am not aware of.