Blog post: "Roadmap for the Xilem backend in 2024" #30
Conversation
|
Quick question: Is there a way to get a link to the page generated by Zola in CI? That way I could put a "Rendered" link at the top of my PR. |
There was a problem hiding this comment.
I'm giving my comments based on how I perceive this blog will land. I realize it's pretty negative overall, but I'm not sure how else to say it.
I think the best way to fix this is to change the two molotov cocktails into "these are things I want to explore. I will prototype them because I feel there's a lot of potential, and make the case based on that."
Ultimately though it's your voice, and at some point we can just publish, I'm not going to ask for many more review cycles. If nothing else, it will get the conversation going, and there's benefit in that.
There was a problem hiding this comment.
I agree with Raph. often the post sounds a little bit too "definitive", given that Xilem is still an experimental research project (with the goal to exit this phase at some point I hope). And without providing actual data/code that proves that the ideas here are really improving the current state.
So I also would prefer more defensive "exploration" wording, that maybe at some time prove that the direction is right.
My idea/vision of Xilem would rather be to create an open ecosystem that makes extending Xilem easy in the spirit of a lot of Rust projects, like bevy, not to close it to users and burden all the heavy work onto the maintainers of Xilem.
Rewrite the part about no custom widgets. Add footnotes. Reword some stuff. Add section about inter-project relations.
|
Draft updated. I've softened the part about custom widgets a bit, though I think it's going to be controversial no matter what. |
There was a problem hiding this comment.
I think this blog post is ready to publish. It's improved a lot in iteration, thanks - before I was worried that the controversial parts would cause more heat than light, but now I'm hopeful it will spur productive discussion.
Because of the link to RFC 1, that should probably get merged first. I'll review that today also.
|
Current plan is to publish after office hours, unless someone has a last-minute objection. The RFC will remained un-merged until we figure out our approval process. |
Rendered as markdown.