critique of vibe.d

Wed Jul 9 17:30:43 PDT 2014

On Thursday, 10 July 2014 at 00:02:23 UTC, Sönke Ludwig wrote:
> Am 10.07.2014 01:27, schrieb luminousone:
>> On Wednesday, 9 July 2014 at 19:51:38 UTC, Sönke Ludwig wrote:
>>> Am 09.07.2014 21:21, schrieb luminousone:
>>>> On Wednesday, 9 July 2014 at 15:21:40 UTC, Sönke Ludwig 
>>>> wrote:
>>>>> Am 09.07.2014 03:54, schrieb luminousone:
>>>>>> There is lots of missing little bits here and their, 
>>>>>> password hashing
>>>>>> functions that use crypt_(C) formated hashes.
>>>>>
>>>>> I was hoping for dauth [1] to fill that gap. It doesn't use 
>>>>> the same
>>>>> format, but one with the same goal. I didn't actually try 
>>>>> it out yet,
>>>>> though.
>>>>>
>>>>>>
>>>>>> There are diet/jade template bugs still, specific major 
>>>>>> problem being
>>>>>> that use of single quotes inside of double quotes when i 
>>>>>> need to pass
>>>>>> strings to js functions inside of js events such as 
>>>>>> onclick inside a
>>>>>> html tag, seems to be broken.
>>>>>
>>>>> Do you have a concrete example where this goes wrong? I've 
>>>>> tested
>>>>> both, nesting ' inside " and vice versa. Both seemed to 
>>>>> work fine for
>>>>> <body onLoad=...>.
>>>>>
>>>>>>
>>>>>> There is not common database interface for sql 
>>>>>> databases(forgivable
>>>>>> actually), but many of the specific database libraries are
>>>>>> messy(ddb for
>>>>>> example) and they are not any where near api "stable".
>>>>>>
>>>>>> Support for mongo is... cute?!, don't get me wrong it has 
>>>>>> a place, for
>>>>>> most apps it would be fine, it is however unusable for the 
>>>>>> apps i am
>>>>>> involved in.
>>>>>
>>>>> Yeah, I kind of like it for its flexibility, but it's 
>>>>> definitely not
>>>>> the right choice for million user web services. I'm 
>>>>> currently looking
>>>>> at NouDB as another potential SQL based target.
>>>>>
>>>>> [1]: http://code.dlang.org/packages/dauth
>>>>
>>>>
>>>> hopefully, these posts are simply read as text, if not I can
>>>> figure out something else.
>>>>
>>>> a.menu_item(href='#', onclick='load("invoice");') New Invoice
>>>> a.menu_item(href='#', onclick="load('invoice');") New Invoice
>>>>
>>>> will always generate the following output,
>>>>
>>>> <a href="#" onclick="load("a");" 
>>>> class="menu_item">New
>>>> Invoice</a>
>>>> <a href="#" onclick="load('invoice');"
>>>> class="menu_item">New Invoice</a>
>>>
>>> That's right, but as far as I understand, it *should* work 
>>> like that,
>>> because HTML character entity replacement should happen 
>>> before parsing
>>> the JavaScript code, even if it's a little more verbose than 
>>> it should
>>> be.
>>
>> It breaks the js. And the character entity replacement only
>> effects text between tags, with the exception of the script tag
>> which also does not get characters replaced, the existing
>> "script." tag in diet templates works correctly. Text inside of
>> attributes is not ran through the character entity replacement.
>
> This is not true. See 
> http://www.w3.org/html/wg/drafts/html/master/syntax.html#attributes-0
> On which browser does it break the JS for you? It works for me, 
> at least in Opera and Firefox.

Chrome, When the links are clicked they simply don't do anything,
the load function is not called. And it doesn't seem to throw any
errors in chromes developer tools, which does seem odd.

Your link is for the html 5.1 draft spec, might this be different
dependent on the version of html being used?