- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Tue, 17 Jan 2012 14:52:49 -0800
- To: "Marat Tanalin | tanalin.com" <mtanalin@yandex.ru>
- Cc: www-style@w3.org
2012/1/17 Marat Tanalin | tanalin.com <mtanalin@yandex.ru>: > 18.01.2012, 02:31, "Tab Atkins Jr." <jackalmage@gmail.com>: >> 2012/1/17 Marat Tanalin | tanalin.com <mtanalin@yandex.ru>: >> >>> 18.01.2012, 01:35, "Tab Atkins Jr." <jackalmage@gmail.com>: >>>> Stepping outside this problem, you shouldn't really be using @import >>>> in your stylesheets anyway. It's bad for performance, since it makes >>>> your stylesheets download one-by-one instead of in parallel. Making >>>> @import more powerful might encourage more use of this, which I'd >>>> personally prefer to avoid. It's better to either link in multiple >>>> stylesheets via multiple <link> elements (so the browser can start >>>> downloading all of them at once), or use a preprocessor to munge the >>>> sheets together into a single file so you can pull them all down with >>>> a single request. >>> As I've already said, there are different situations: internet, intRAnet, local webpages opened from CD. Delay concern is generally applicable to former one only, but current limitation is applied forcedly and harmfully to all of them. >> >> We only really care about the web, since the vast vast majority of >> pages using our tech are web pages. Making choices that are bad for >> the web but offer a minor benefit to non-web usage isn't a good >> tradeoff. > > Please don't speak/decide for all web-developers. They should have flexibility. I'm not. I'm speaking for the community *designing* the web platform. *We* care mostly about the web, and won't hurt the web in order to optimize non-web cases unless it's, like, crazy good. ~TJ
Received on Tuesday, 17 January 2012 22:53:38 UTC