@slimsag@JohanBrandhorst@bradfitz@PerkeepOrg@aviau_ Fair point. Go having to embed a runtime will always cause some bloat for sure. I guess I was just betting on being able to make it small enough for most practical use - and at least be competitive with other bloated JS libs ๐
@JohanBrandhorst@bradfitz@PerkeepOrg@aviau_@slimsag It might be worth even considering if there is crossover between Vugu and Vecty. Although it would probably require a lot of sorting out different design ideas, the core idea of wasm rendering from Go code is the same. Iโd be open to discuss the matter further (on Slack?)
@JohanBrandhorst@bradfitz@PerkeepOrg@aviau_@slimsag In terms of architecture, one of the primary goals was to write (HTML-like) markup as the primary interface for page layout. This is definitely a deliberate decision and I still like the idea, although it has drawbacks. Iโd like the two step generate then compile to become 1 step
@JohanBrandhorst@bradfitz@PerkeepOrg@aviau_@slimsag Vugu dev has been slow but itโs definitely still alive as a project. I plan on giving it some more love soon and organizing the additional maintenance it needs to eventually hit v1.0.0
@CompSciDrew@matryer Not if you round in the right places (in math and str conv). But keep in mind not all money is just 2 decimals. Discounts, items sold in pieces, bulk quantities with very small prices (try buying 12,000 capacitors on Digikey), BTC etc. If you donโt round, pitfalls abound.
@_rsc I think it only makes sense when either A enough target environments natively support it or B enough applications benefit from having it native vs a lib (after all is this not the rationale for int64?). Otherwise why bother. I think weโre getting closer but not quite there yet.
Who dat?! It's @bradliusgp crushin' his tutorial set for "Go is Not Just on Your Server, it's in Your Browser: The Story of and Introduction to Vugu (Go+WebAssembly UI library)" at #GoVirCon on November 12th. Check out the full description at https://t.co/xHJ7GWvhxb #Golang
@catmcgee BASIC, and no, I donโt think I could bring myself to write more of it. Maybe if I were stranded alone on a desert island with nothing but a bunch of Doritos and a Commodore 64... maybe...
@matryer Debuggers can be useful but log statements can be used in more environments (e.g. production). Log statements can also be used to summarize info and record what happened at a specific instant for later reference. Debuggers generally do not do those things well.
@Skarlso@davecheney โutilโ adds very little if any description, so instead of punting it is best to just find a descriptive name and decide the logical boundary of the package. For me some things like errors, setup/tear down code, text processing each could have been a pkg but ended up in a โmiscโ
@ryan_sb@rsyvarth Maybe but maybe not. Translating a v1 to v6 is easy and the binary format should generally be compatible. One of the goals of the spec is to keep the changes needed minimal for apps trying to adapt.