New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is anyone making use of the tinygo
support?
#268
Comments
I would !! the binary size is why I would use tinygo. I have used tinygo for other WASM stuff. |
I have been using MakeFiles and task Files to make local and CI builds identical. its a good idea what your doing. Github actions suck due to not being able to run locally |
you guys are welcome to grab me on Telegram and we can do a group chat of something. the main thing with vugu for me is binary size |
@gedw99 So far you are a 1 of N sample...and yours is a I would like to not I am :) Anyone else using But a question. As far as @bradleypeabody and myself are aware https://github.com/tinygo-org/tinygo/issues?q=is%3Aissue+is%3Aopen+wasm+net%2Fhttp+ and @bradleypeabody's original suggestion here (form 4 years ago!) tinygo-org/tinygo#850 (comment) Does your experience with using If you can't make that call using the standard library then that will also influence where we expend effort. Could you let us know, either way? Thanks |
If anyone is making use of the
tinygo
support invugu
can you please make yourself known?So if you are building your
vugu
project with thevugugen -tinygo
switch enabled @bradleypeabody and @owenwaller would really like to hear from you.@bradleypeabody and I are considering changing the build process for building
vugu
itself. This will typically only impact you if you are a contributor or maintainer ofvugu
itself. Our goal is to make the build experience as near identical locally as it is when running the Github Action CI/CD build. This will also hopefully simplify the build process for contributors.Everyone else will still use
vugugen
in their projects as normal.Just to make this clear we have not made any decision on this yet. @bradleypeabody and myself are simply trying out alternative approaches at this stage.
See the related PR #267
Thanks
Owen
The text was updated successfully, but these errors were encountered: