Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Forma – An efficient vector-graphics renderer

github.com

Post reply on HN
Print view View original

31–40 of 64 posts

Re: Show HN: Forma – An efficient vector-graphics renderer

#31

Post by afandian »

cmrdporcupine wrote: post #25
afandian wrote: post #18

Earlier quoted context omitted.

When you leave employment at Google do you typically retain your github account and contribution rights to the repo?

Most people I think just use their personal github but join the Google org. And then you get booted from it when you quit. Commit rights, I'm actually not clear on, but by default I think you'd lose rights. I believe there's likely a process for keeping them,, but I don't recall what it is. The one repo I contributed to that followed this process was essentially abandoned long before I left Google.

Thanks, that's interesting. Is any production Google code written this way, or is it only Google-adjacent open source?

Re: Show HN: Forma – An efficient vector-graphics renderer

#32

Post by 323 »

tayistay wrote: post #29

> Line segments are transformed into pixel segments by intersecting them with the pixel grid. We developed a simple method that performs this computation in O(1) and which is run in parallel. What's a pixel segment exactly? Just a list of pixel coordinates that intersect?

I don't know for sure, but I suspect a list of consecutive horizontal pixels (no diagonal).

Re: Show HN: Forma – An efficient vector-graphics renderer

#33

Post by Zaskoda »

I hope this makes its way into web browser rendering. I've been working on a "game engine" using SVG in the browser. When I started, everything I read said don't - because performance. However, manipulating an SVG using a reactive framework (I use Vue) makes for very readable code. Our game client is meant to be a "reference" client so readability is more important than performance, which just needs to be "good enough." However, a significant boost in SVG rendering performance would be amazing.

edit: although, as I look more deeply, I may be misunderstanding and this may not be something that would benefit existing SVG browser rendering in any way...

Re: Show HN: Forma – An efficient vector-graphics renderer

#34

Post by wmf »

cmrdporcupine wrote: post #17
TheRealPomax wrote: post #16

Slightly curious why it's on the google github account, if it's not an official google project, or even endorsed by google? Surely this should live over on github.com/dragostis/forma then?

If you're a Google employee, there's a few different paths to 'legally' open sourcing stuff without violating your employment contract. The simplest and fastest one is just to assign copyright to Google, use an approved license (basically anything non-copyleft) and stick it under the google/ github org. It being there doesn't mean Google sponsored or authored it, just that a Googler worked/works on it. And the "not o…

Putting "not official Google products" under github.com/google is the dumbest policy. I wonder why they don't realize/care about this.

Re: Show HN: Forma – An efficient vector-graphics renderer

#35

Post by cmrdporcupine »

afandian wrote: post #31
cmrdporcupine wrote: post #25

Earlier quoted context omitted.

Most people I think just use their personal github but join the Google org. And then you get booted from it when you quit. Commit rights, I'm actually not clear on, but by default I think you'd lose rights. I believe there's likely a process for keeping them,, but I don't recall what it is. The one repo I contributed to that followed this process was essentially abandoned long before I left Google.

Thanks, that's interesting. Is any production Google code written this way, or is it only Google-adjacent open source?

There are definitely things under the google github org that are used in production, though they are typically mirrored from Google3 in some way. But not sure what, if any, has its origins in a personal open source projects.

Re: Show HN: Forma – An efficient vector-graphics renderer

#36

Post by cmrdporcupine »

wmf wrote: post #34
cmrdporcupine wrote: post #17

Earlier quoted context omitted.

If you're a Google employee, there's a few different paths to 'legally' open sourcing stuff without violating your employment contract. The simplest and fastest one is just to assign copyright to Google, use an approved license (basically anything non-copyleft) and stick it under the google/ github org. It being there doesn't mean Google sponsored or authored it, just that a Googler worked/works on it. And the "not o…

Putting "not official Google products" under github.com/google is the dumbest policy. I wonder why they don't realize/care about this.

Yeah, I suppose they could create a separate org, "Google Open Source" and put it there, but probably they'd like to reserve the right to own and then change the "not official" to "official" whenever they please.

There are many lawyers and such at Google who think about these things more intensely than you and I do. I'm sure they have looked at all angles.

EDIT: I do find it amusing to watch HN and other forums whenever something new and interesting is dumped under the /google org and people need to be convinced it's not some radical new direction Google is taking. But I've also been wrong before. I dismissed Fuchsia as a personal hobby project that grew out of control, until it grew out of control enough that it rm -r'd everything I'd been working on for 2+ years.

Re: Show HN: Forma – An efficient vector-graphics renderer

#37

Post by zem »

afandian wrote: post #31
cmrdporcupine wrote: post #25

Earlier quoted context omitted.

Most people I think just use their personal github but join the Google org. And then you get booted from it when you quit. Commit rights, I'm actually not clear on, but by default I think you'd lose rights. I believe there's likely a process for keeping them,, but I don't recall what it is. The one repo I contributed to that followed this process was essentially abandoned long before I left Google.

Thanks, that's interesting. Is any production Google code written this way, or is it only Google-adjacent open source?

i work on https://github.com/google/pytype which is largely developed internally and then pushed to github every few days. the github commits are associated with the team's personal github accounts. pytype is not an "official google product" insofar as the open source version is presented as is without official google support, but it is "production code" in the sense that it is very much used extensively within google.

Re: Show HN: Forma – An efficient vector-graphics renderer

#38

Post by mkl »

nerpderp82 wrote: post #26
dragostis wrote: post #7

Earlier quoted context omitted.

Thank you for the endorsement. Looking forward to collaborating more with you on 2D graphics.

How does this compare to https://github.com/RazrFalcon/resvg ?

That's a different kind of thing, I think. It renders using tiny-skia, so probably comparing to tiny-skia would be more appropriate? It also sounds like resvg's renderer can be swapped out, so it may be possible to have it render with Forma.

Re: Show HN: Forma – An efficient vector-graphics renderer

#39

Post by nerpderp82 »

mkl wrote: post #38
nerpderp82 wrote: post #26

Earlier quoted context omitted.

How does this compare to https://github.com/RazrFalcon/resvg ?

That's a different kind of thing, I think. It renders using tiny-skia, so probably comparing to tiny-skia would be more appropriate? It also sounds like resvg's renderer can be swapped out, so it may be possible to have it render with Forma.

That sounds neat.

Re: Show HN: Forma – An efficient vector-graphics renderer

#40

Post by dragostis »

tayistay wrote: post #29

> Line segments are transformed into pixel segments by intersecting them with the pixel grid. We developed a simple method that performs this computation in O(1) and which is run in parallel. What's a pixel segment exactly? Just a list of pixel coordinates that intersect?

A pixel segment is a line segment that fits inside of a pixel's square box. It can start and end anywhere inside of this 1x1 square box and it has a 64bit compact representation.
Post reply on HN