gerrit

Sat in that same course. Nice to see Bremen people here

It’s a German company and “flix” is local slang for quick

Yes please

Or simply flushing out the <head> of a html document before the body is generated so the browser can start pre-fetching resources. That's the main use case that motivated Rails to implement streaming.

I've been using hogan.js to compile mustache templates to JavaScript functions on the server-side and write them to a js file that is then served to the browser:

  Templates={}
  Templates['templatename']=function(){/*compiled template*/}

They can then be referenced quite easily in your backbone render methods.

I guess the problem for a lot of people is, sometimes the samwers clone the execution too. In some cases even down to typos in the HTML source

Most German banks have been providing HBCI for over a decade, so that doesn't really narrow it down.

It's the account of Junio C Hamano who is the main maintainer of git

Japanese computer systems are often not using Unicode but are based on other encodings like shift-jis.

Even if it wasn't for historical characters that aren't part of Unicode, this will probably stay that way because of the inefficiencies of encoding Asian text in e.g. UTF8.

That's part of the reason the ruby programming language didn't have proper Unicode support for a long time (and now supports arbitrary encodings for its strings, not just Unicode ones)

The user experience when viewing webpages is improved by actually showing a lower-resolution image while the crisp high-resolution image is being downloaded (however slowly), similar to progressive JPEGs.

Depending on the data contract, the user experience when viewing their mobile phone bills might be affected negatively though.