>To all others: Relax, nothing has been checked in! It is just an
>enhancement bug in bugzilla :).
Is this funny? Andreas, can you get T to behave and stop the argumentation. I
assume this is not the core team's opinion. We would appreciate a more
professional attitude! Thanks!
>From the message it is clear to a person who can read that there is more to
>read in the bugzilla. The clarification is unnecessary. The game of words has
>no sense!
>The new version is even more questionable than the first, as Json maps
>are silently stripped off of all their keys, and the resulting Json only
>contains the array of map values! This is a tremendous loss of
>information, particularly as the order in which the values are placed in
>the array is non-deterministic. The consumer of the resulting Json has
>to get by with it.
First of all, there are nothing stripped off silently.
Second, for a developer who can read code, can see what it does.
Yes, T! It is a tremendous loss off information and that is what is wanted! One
example:
If you have a json array of 250 rows with each 3 key-value pairs, you save the
space (in our case 66%)
T, the keys are repeated 3 x 250 times without sense!
So why key labels then? The same reason as you gave, readability in the
working, non-compressed, version of the file, cause the values could also be
the same.
Example, if you load 250 lines in a selectbox we save 40% of the time to load
it. That is a way forward else our users would get very irritated.
>I cannot imagine anybody wanting to use this. If you didn't want maps,
>you would use arrays in the first place. No wonder you save space when
>you throw out information. Semantics not changed, huh?!
Give us test results instead, supporting your "theories" and imagination, with
the above given facts.
If you do not want to convert the maps to arrays then you still can save space
by compression (in our case about 33%)
T, your rethorics is full of holes and is inconsequent.
Are databases compressed in any way to save space? yes, they are and the
reasons are obvious
Do we compile code to execute applications? yes, we do and the reasons are
obvious
Does qooxdoo use compression? yes, it does and it is obvious why
I can not read compressed and changed qooxdoo javascript! The biggest loss of
information and distortion of javascript semantics are generated by the
generator.
Javascript was not intended to be compressed, but qooxdoo is. We know the
reasons.
In our case we have static json files of about 6 MBytes and by this addon
feature we can remove 4 MBytes and get a faster application!
Stefan
------------------------------------------------------------------------------
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
