This month in Linebender, November 2024 edition! #80
Conversation
waywardmonkeys
changed the title
waywardmonkeys
force-pushed
the
blog/tmil-11
branch
from
b28f8cf to
2db08af
Compare
There was a problem hiding this comment.
We have generally tried to scope these quite tightly to "what happened in the previous month", whereas this update seems quite focused on "we have big plans for December".
I'm inclined to be cautious about making big release announcements before we do them; I think I'm really taking umbrage with the "we will" phrasing, when in my mind there's a decent (~45%?) chance that "we will" in fact not.
| Linebender, among other things, believes in helping build solid foundations for people building user interfaces and working in graphics, in the Rust programming language (and on GPUs). | ||
| Upon seeing a problem, we prefer to produce a focused crate that solves that problem and that can be used by others within the Rust ecosystem. | ||
| Color is one such area. | ||
| It is much harder than it may appear at first, with many complicating factors like what should be done by a basic color struct, what color spaces to support, and whether or not to support color formats used in print (like CMYK). | ||
|
|
||
| We looked around at a wide variety of crates in various stages of maintenance and development, their feature sets, the "weight" of those crates, and how closely they fit in with what we would need in Vello, tiny-skia, resvg, svgtypes, Masonry, and Xilem. | ||
| We decided to do a crate based on the [CSS Color Module Level 4] draft specification, with support for a limited number of additional color spaces. |
There was a problem hiding this comment.
My initial thought on this is that these paragraphs don't seem to contain very much information.
If I were writing this, I'd probably say something along the lines of:
The [CSS Color Module Level 4] draft specification provides an excellent scoped set of Color operations for 2d graphics rendering.
We have chosen to base our long-desired improvements in color support on it.
Several existing crates exist in the ecosystem for color, but we found that none of them met our requirements of maintenance and development, feature sets and "weight".
But equally, this post isn't in my voice.
There was a problem hiding this comment.
Thanks for putting in the effort to write this, much appreciated!
I agree with Daniel that the scope of these posts should be fairly strict on what happened in the specific month. We've previously even skipped talking about things that have already happened before writing the post, but in the new month. Thus, talking about plans seems even more out of scope. Plans can also change, and often do.
What's more, higher signal to noise ratio is a good thing. So focusing on talking about what actually happened can help with that as plans always have less precise language than descriptions of things that already happened. Also, most definitely skip talking about our lack of plans for any task.
The exceptions I can see making here are some future ideas for Color, as it is indeed the first time we've released anything for it and having some idea of its future is very valuable. Mentioning the Piet Zulip thread is also fine I guess. I'd cut the rest of the future plan talk though.
Co-authored-by: Kaur Kuut <[email protected]> Co-authored-by: Daniel McNab <[email protected]>
This reverts commit c6cff92.
Co-authored-by: Kaur Kuut <[email protected]>
Co-authored-by: Tom Churchman <[email protected]> Co-authored-by: Kaur Kuut <[email protected]>
|
|
||
| Work on Xilem web has been continuing well: | ||
|
|
||
| * [xilem#731][], [xilem#734][]: Added a example using our SVG support for drawing, called `svgdraw`. |
There was a problem hiding this comment.
| * [xilem#731][], [xilem#734][]: Added a example using our SVG support for drawing, called `svgdraw`. | |
| * [xilem#731][], [xilem#734][]: Added an example using our SVG support for drawing, called `svgdraw`. |
No description provided.