HN user

bdahz

21 karma
Posts3
Comments23
View on HN

For the simplicity of implementation and code clarity, I need to know how much I need to pay for it.

If the Haskell implementation is 3x slower than C/C++/Rust implementation, it would be acceptable.

If it's 30x slower, I would rather choose C/C++/Rust even the implementation won't be simple.

If it is even possible to be 3x faster than C/C++/Rust, then why not the mainstream programmers adopt Haskell everywhere?

Thanks for your advice. I've reverted the license back to 1.0, adjusted the royalty rate, and made the royalty disclaimer more apparent in case someone says it contains a HIDDEN royalty :)

As a small team, we don't expect to make great money just by the royalty. We choose to open source this project for many good reasons. But the only reason of adding royalty is that we want to protect our work from being stolen by some other random guy.

The reasons to escape Flash are the performance and power-consumption issues, rather than accessibility.

If you take browser as a document viewer then accessibility is critical. However if you take browser as a universal application platform, then accessibility is not necessary, right?

If there is a VGG-native browser then accessibility is not so hard to implement. The awkward problem is that current VeryGoodGraphics is just a canvas node in HTML (using WebAssembly + WebGL). So adding accessibility support will be a nightmare technically.

My concern is, are GPL-family licenses good enough to let contributors involve with this project? Because I heard that GPL licenses are like viruses and someone hates them.

Or maybe dual licenses are good enough if one of them is Apache License (for personal use only)? This is what VGG License 2.0 does.

Does anyone have the idea of escaping from HTML/CSS? As these specs are too complicated and not friendly for web developers as well. Maybe we could re-invent a browser engine without conforming to HTML/CSS specs?

An (early) alternative spec/engine would be a Figma-compatible vector graphics spec[2] and its rendering engine[3]. It is called VeryGoodGraphics[1].

[1] https://verygoodgraphics.com/, the website is built with its own technology (wasm version).

[2] https://docs.verygoodgraphics.com/specs/overview

[3] https://github.com/verygoodgraphics/vgg_runtime

Me and SVG 9 years ago

VPaint[1] is a research vector graphics editor (from SIGGRAPH 2015) that has higher-level semantics of vector graphics editting. And it claimed more efficiency to create vector graphics. May it be the hope to fix problems of SVG you guys mentioned?

[1] http://www.vpaint.org/

This is a tasteless chicken. No one would take the effort to use it in real-life business, since there are always better BI software available (Tableau, PowerBI, etc.), with much better user experience (no need to write SQL) and richer and finer plotting features.

I don't see any point in "reinventing" this.