dustismo
Joined 15 years ago
Joined 15 years ago
Making thinking was something like:
pros:
1. json has lots of tooling and is generally easy to work with 2. if I put up a ui/webapp around hfd, then json will work well for that. 3. if I want a custom DSL, I can always have the grammar convert to json as the underlying representation.
CONS: 1. the json ends up being deeply nested and hard to work with 2. lack of multiline strings and comments (I went ahead added comment support though :))
HFD is meant to make it easier to create designs which are parameterized (i.e. one design where you could easily change the width, height, thickness, ect). And make it simpler to split and layout designs across multiple pieces of material.
Anyhow, is a step in the right direction to have small hackable eink displays.
> 5. Is your bus factor greater than n/2, where n is the number of engineers?
Sounds interesting, would like to know a bit more. Looks like I have to find out for myself if I want answers
yes :)