You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With #50 the source data are now parsed from StrictYAML format and dumped again as JSON for future parsing since JSON turns out to be much faster. It feels a little stupid though, so I should think about a better solution. It's not a pressing issue as the current solution works well and is fast enough. It's just technically not ideal.
StrictYAML offers type checking and subjectively easier editing than JSON but at the same time it's much much slower.
Action items:
Can I live without type checking? (then check plain YAML's speed)
Can I live with editing JSON? (then check speed of JSON parsing with validation)
Can I live with both of the above? (then use plain JSON?)
Is there any other (better) option?
The text was updated successfully, but these errors were encountered:
With #50 the source data are now parsed from StrictYAML format and dumped again as JSON for future parsing since JSON turns out to be much faster. It feels a little stupid though, so I should think about a better solution. It's not a pressing issue as the current solution works well and is fast enough. It's just technically not ideal.
StrictYAML offers type checking and subjectively easier editing than JSON but at the same time it's much much slower.
Action items:
The text was updated successfully, but these errors were encountered: