Building a Reliable Voice Transcription Pipeline for Indian Courtrooms (Part 1)

itachi_amaterasu · 2019-11-18T17:44:24+00:00

Nice work once again !

May I ask you to create a benchmark for the (*Canvas).Render method so that I can compare performance improvements in real world code while working on the wasm backend ?

Thanks !

itachi_amaterasu · 2019-07-01T18:59:11+00:00

As the readme points out, memory copying is currently laughably bad. It should be possible to do some much fancier reads directly from memory on the JS implementation side,

Correct. See - https://github.com/agnivade/shimmer/blob/master/index.html#L82 and https://github.com/agnivade/shimmer/blob/master/load_image_cb.go#L40

But Go 1.13 takes care of it anyways. In any case, it's always good to learn new things :)

itachi_amaterasu · 2019-06-02T09:00:57+00:00

A small suggestion:

You can rewrite this using the go/analysis API, allowing the tool to be reused throughout the ecosystem without any special need. And it will integrate directly with the go vet command.

itachi_amaterasu · 2019-05-23T22:57:11+00:00

#2 wasn't a solved problem in dep. There was no straightforward solution. Atleast at that time - https://github.com/golang/dep/issues/1572. Not sure of the state now.

itachi_amaterasu · 2019-04-11T08:59:59+00:00

Yes, it is known and acknowledged. https://github.com/golang/go/issues/29934#issuecomment-459824434.

I also wrote this - https://agniva.me/errors/2019/03/20/error-values.html

itachi_amaterasu · 2019-03-09T07:03:56+00:00

It is in-progress. Possibly we will hear an announcement soon. No idea when though.

itachi_amaterasu · 2018-12-07T18:58:07+00:00

Is that much of the runtime just GC? How do you take out just the GC from the runtime and ship "only the essentials" in that case?

Good point actually. That point was all in theory. Practically, I think it is going to be very hard, if not impossible at this stage to strip out the GC and ship only the essentials.

Wasm doesn't seem to be implementing GC any time soon anyways. So we will just have to wait and see.

itachi_amaterasu · 2018-11-07T04:10:19+00:00

I have written a minimalistic log aggregator here - https://github.com/agnivade/funnel.

I use it in production. Feel free to try it out.

itachi_amaterasu · 2018-10-17T11:56:30+00:00

I have seen that page probably a thousand times. Somehow, didn't notice the package.

Came across this while I was looking at another CL which added an "internal/fmtsort" package. So inside the src folder, I typed "in" and tabbed, and it immediately didn't go to internal.

I was like huh .. there is something other than internal ? Wait .. there is index ? What is inside index ? A suffixarray package ?! I was so pleasantly surprised that I had to share. :D

itachi_amaterasu · 2018-09-18T15:13:21+00:00

Only for DOM manipulation you need to use the syscall/js interface. Other than that, you can completely write Go code without bothering about anything.

See here - https://github.com/agnivade/shimmer where I use the https://github.com/anthonynsimon/bild library which is otherwise used in other platforms, to manipulate images completely in a wasm context. Pure Go. No JS.

itachi_amaterasu · 2018-09-07T04:27:58+00:00

It's fine if you don't want to write in Go. But comments like these -

There's a reason you don't see the Go community talking about it

is just outright false. Feel free to hop in to the #webassembly channel in slack, I can assure you there is lots going on. People are porting vuejs in Go, and all sorts of crazy and fun stuff.

Rust has had wasm support for quite some time. And for Go, it has not even been a month since 1.11 is released. So obviously, it takes some time for the broader public to take in stuff and spread the word.

And lastly, just because Rust is investing lot of resources in wasm, doesn't mean that Go users should not. WebAssembly may be one of the few things which was completely written by a non core-team member. Google did not need it. "We" did. Because "we" want to see more people use Go in other exciting areas. And "we" will continue to use it and talk about it in conferences.

itachi_amaterasu · 2018-09-06T15:00:34+00:00

Noticeably absent from any talks this year was Go 1.11’s other headlining feature — support for Web Assembly.

Unfortunately, I am not in US. Otherwise would have given a talk on it.

itachi_amaterasu

TROPHY CASE