This is going to be one my next projects for experimenting with the Web Serial API. I got an old Ioline plotter that refuses to die. Any advise or tips for where to start with the SVG to Gcode conversion?
I used svg2polylines to load the SVG into line segments, interpolating any splines into something easier to use for a plotter. Feel free to take a look at the core/project/import.rs in the project I linked. You might also want to look at the core/post.rs which does the gcode generation.
A hiring manager asked me a question like those. I said: "sorry I'm not prepared, I don't remember from the top of my head." Right before that interview I was a solo founder. He said something like: "ok, so you just focus on the work?" "Yes." I got the job.
I should go back to this (like some of the other comments suggest) - I think there is potential in suggesting multiple lines, and I would have really loved it to work, but it is clear that their ux testing was poor.
CSS Modules are a simpler solution to cascading problems. They create unique class names, so your classes don't clash [1]. And they don't have the two main downsides of TW, which are readability [2] and tooling. Tooling for debugging and experimenting interactively with Chrome and FireFox DevTools.
Don't most modern CSS tools create unique class names? I know styled-components did.
Recently I've been using linaria which is a drop-in replacement for styled-components (exact same API) but its zero runtime. All the CSS is compiled during build (similar to vanilla extract, panda CSS, etc).
I really prefer things like styled-components or Linaria or CSS Modules where you can just write straight up CSS. If you ever decide to switch your tool you should always be able to just copy-paste your CSS away. You don't get that with Tailwind or "styles-as-objects" stuff (StyleX)
Thanks for your work on Yak. When I was evaluating the alternatives to styled-components, I went with Linaria over next-yak because it is zero runtime. Any plans for Yak to support this as well?
Yeah they are not supporting server components. That's why I said I used Linaria which is a drop-in replacement. Exact same API so any team can simply run a codemod tool to change the import rule from styled-components to linaria
We've for a while determined that unique class names are a dark pattern. Having to match unique and unreadable names with the actual src is a productivity killer.
https://www.kb.cert.org/vuls/id/319816
reply