HackerTrans
トップ新着トレンドコメント過去質問紹介求人

bdahz

no profile record

投稿

A simple personal website built with SVG

xingyu.wang
2 ポイント·投稿者 bdahz·2 年前·0 コメント

Ask HN: What kind of license is good for a rendering engine?

3 ポイント·投稿者 bdahz·2 年前·11 コメント

OpenWebF

github.com
2 ポイント·投稿者 bdahz·2 年前·0 コメント

コメント

bdahz
·昨年·議論
Is this the same guy talking about the same topic?

https://www.youtube.com/watch?v=p0lFyPuH8Zs

I need a transcript as the FOSDEM website didn't provide a one (404 not found), but youtube has.
bdahz
·昨年·議論
The free download requires account registration, which will discourage most people from trying it. Even third-party login might make it easier, but I didn't find that option.
bdahz
·2 年前·議論
I'm curious what if we replace Rust with C/C++ in those tiers. Would the results be even better or worse than Rust?
bdahz
·2 年前·議論
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?
bdahz
·2 年前·議論
How is the performance when compared to similar implementations in C/C++ or Rust?
bdahz
·2 年前·議論
How does cosmopolitan support GPU-based applications?
bdahz
·2 年前·議論
Related post discussing the rounded shapes (and squircles) in design tools:

https://blog.verygoodgraphics.com/posts/rounded-shapes/
bdahz
·2 年前·議論
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.
bdahz
·2 年前·議論
Sorry, I was just raising my question. Because in my country most app maker does not care about accessibility. Now I know.
bdahz
·2 年前·議論
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?
bdahz
·2 年前·議論
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.
bdahz
·2 年前·議論
Great advice. Thank you so much!
bdahz
·2 年前·議論
Dual licenses, or triple licenses are common in some open source software. Maybe more rules should be presented to make the dual licensing more clear?
bdahz
·2 年前·議論
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.
bdahz
·2 年前·議論
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
bdahz
·2 年前·議論
A tomato clock: https://github.com/harry75369/ESP8266_Tomato