On 2015-01-17 19:23, Andrei Alexandrescu wrote:
> On 1/17/15 10:01 AM, Sebastiaan Koppe wrote:
>> And lets be honest here, why the hell do we even use apache+php and not
>> D+vibe.d? I just rewrote my companies corporate website in under 4
>> hours. Granted, it is a simple one. But this community should be able to
>> rewrite this site in D in under a week, right?
>
> I wish.

Was that honest? I got the impression that you and Walter was satisfied with using Ddoc for the website.

-- 
/Jacob Carlborg

On 1/18/15 1:01 AM, Sebastiaan Koppe wrote:
> On Sunday, 18 January 2015 at 07:42:10 UTC, Andrei Alexandrescu wrote:
>> On 1/17/15 11:23 PM, Sebastiaan Koppe wrote:
>>> On Saturday, 17 January 2015 at 20:52:28 UTC, Andrei Alexandrescu
>>> wrote:
>>>>
>>>> Our webmaster got back. He said compression is more CPU work and on a
>>>> fat pipe (which we do have) that may make things actually worse. Also,
>>>> how would this work if we switch to vibe.d? -- Andrei
>>>
>>> If you do not have spare horsepower for compression, how will you
>>> handle twice the load?
>>
>> Not quite getting the logic there. -- Andrei
> It is unrelated to my point about compression. The reasoning is as
> follows: if you are maxed out on resources

We're not maxed out on resources. The question was whether compression adds a net benefit. -- Andrei

On 1/18/15 1:01 AM, Sebastiaan Koppe wrote:
>
> Btw. I build the dlang.org site on my computer but the <script> links
> have an %0 in the src attribute. Then 5 min later I saw the same on
> dlang.org

Urgh, typo. https://github.com/D-Programming-Language/dlang.org/commit/807d471e602c1d8e6eff671ab1fe94b20b2e5cf1

Andrei

On 1/18/15 1:01 AM, Sebastiaan Koppe wrote:
>
> Btw. I build the dlang.org site on my computer but the <script> links
> have an %0 in the src attribute. Then 5 min later I saw the same on
> dlang.org
>
> Funny thing is, all stuff is still functioning. Affirming my hunch that
> you can remove a lot of the js stuff.
>
> The site now loads in 124kb. Whoever put that %0 there, you just cut
> down the site from 300kb to 124kb. Nice Job!

Much of that was to enable running D code in the browser, which has been disabled as of late. No problem! I'll ask one of our many lieutenants to look into it :o).

Andrei

On Saturday, 17 January 2015 at 18:00:01 UTC, Andrei Alexandrescu wrote:
> Would be a nice tools/ thing. Wanna do it/ --- Andrei

First try:

https://github.com/schuetzm/shrinkcss/blob/master/shrinkcss.d

Reads from stdin, writes to stdout. Removes comments, superfluous whitespace, and the closing ";" before "}".

WARNING: This is mostly untested, the lexer is probably missing a few corner cases.

On 1/18/15 9:41 AM, "Marc =?UTF-8?B?U2Now7x0eiI=?= <schuetzm@gmx.net>" wrote:
> On Saturday, 17 January 2015 at 18:00:01 UTC, Andrei Alexandrescu wrote:
>> Would be a nice tools/ thing. Wanna do it/ --- Andrei
>
> First try:
>
> https://github.com/schuetzm/shrinkcss/blob/master/shrinkcss.d
>
> Reads from stdin, writes to stdout. Removes comments, superfluous
> whitespace, and the closing ";" before "}".
>
> WARNING: This is mostly untested, the lexer is probably missing a few
> corner cases.

Noice. Would be interesting to see how much Brian's lexer generator would help. If it reduces size considerably or makes it a lot easier to do things, that would be a good proof of utility. -- Andrei

On Sunday, 18 January 2015 at 17:46:52 UTC, Andrei Alexandrescu wrote:
> On 1/18/15 9:41 AM, "Marc =?UTF-8?B?U2Now7x0eiI=?= <schuetzm@gmx.net>" wrote:
>> On Saturday, 17 January 2015 at 18:00:01 UTC, Andrei Alexandrescu wrote:
>>> Would be a nice tools/ thing. Wanna do it/ --- Andrei
>>
>> First try:
>>
>> https://github.com/schuetzm/shrinkcss/blob/master/shrinkcss.d
>>
>> Reads from stdin, writes to stdout. Removes comments, superfluous
>> whitespace, and the closing ";" before "}".
>>
>> WARNING: This is mostly untested, the lexer is probably missing a few
>> corner cases.
>
> Noice. Would be interesting to see how much Brian's lexer generator would help. If it reduces size considerably or makes it a lot easier to do things, that would be a good proof of utility. -- Andrei

It might help, maybe I'll try it out (not today, though). One improvement I'd like to have would be to avoid the duplication of the `case`s of `lex()` in the `readXXX()` functions.