Open owenwaller opened 1 month ago
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. or any other medium.
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 tinygo
as this is likely to determine where we direct our efforts?
But a question. As far as @bradleypeabody and myself are aware tinygo
does NOT support the Go net/http
layer when compiling for wasm
. See:
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!)
https://github.com/tinygo-org/tinygo/issues/850#issuecomment-627047525
Does your experience with using tinygo
compiling for a wasm
target differ? Specifically can you use a Go standard library net/http/Client
to make a simple GET call?
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
@gedw99
And my apologies. In my haste I forgot to say, if you wish to contribute to vugu
you would be more than welcome.
There is a V1.0 ToDo list in #260
Note to self: I need to look at this to check it's up to date.
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