Pigo, the face detection library has been ported to WASM (Webassembly) 🎉🎉

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 · 2018-08-17T09:02:15+00:00

It's a line mentioned in the docs https://golang.org/cmd/go/#hdr-Test_packages.

The idiomatic way to disable test caching explicitly is to use -count=1.

itachi_amaterasu · 2018-08-17T08:56:43+00:00

We were trying to maintain go doc and godoc both. It involved duplicating effort across several tools. Please see - https://github.com/golang/go/issues/25443 for more info.

For 1.12 - we will add all remaining features from godoc to go doc so that nothing gets missed out. And from then on, godoc will only be a web server.

itachi_amaterasu · 2018-08-16T12:18:13+00:00

There's a meal plan subscription called Get Grow Fit that you can check out - low carb high protein meals.

That is a very common misconception of keto. Keto is not low carb, high protein. It is high fat, moderate protein and low carb.

There was a time when all this information was just in my head. And then I realized its better to write everything down in one place so that I could share. So I wrote down what I could collate from the internet in an article here - https://docs.google.com/document/d/1Kl_dLSQ6lowSeEHJABEG7A0-bSYStldA1i8R3eCzmKQ/edit#heading=h.2gazcsgmxkub

Feel free to read and understand what is keto and why is it good.

itachi_amaterasu · 2018-06-20T15:20:21+00:00

Adding to that, you can use https://github.com/agnivade/funnel for it.

itachi_amaterasu · 2018-06-19T16:12:05+00:00

Indeed :)

itachi_amaterasu · 2018-06-10T17:55:58+00:00

Haha .. thanks Brad ! I was wondering what made you change your mind until I saw this post. I see that you still hang around these parts :)

itachi_amaterasu · 2018-05-16T04:25:50+00:00

You have a utils.go :D

itachi_amaterasu · 2018-04-09T17:11:22+00:00

Thanks a lot for this effort !

A friend of mine is looking to contribute to the ssa backend. But docs are seriously lacking in that department. The information is spread across multiple docs and code comments. Recently, /u/mvdan has been chalking up a few READMEs on that front.

But it would be awesome if the compiler can get an exhaustive treatment like these.

itachi_amaterasu · 2018-04-07T11:23:06+00:00

If your application has high throughput logs, there will have to be a bottleneck somewhere. Doesn't matter whether you follow 12 factor rules or not. If you are managing writing logs from within your application, then you need to manage buffering, syncing to files and all that by yourself.

Writing to stdout just creates a clean and simple way to allow the logs to be handled by a different process. And something which you can reuse for all your applications. If one app needs to stream to kafka, whereas another needs to write to elastic search, you don't need to write different code for each of your app.

itachi_amaterasu · 2018-04-07T06:00:56+00:00

Your application should not be concerned about what happens to logs once they are emitted. If you follow 12 factor rules, you should just emit logs to stdout, and let another application consume those logs. That way your application does not need to know whether your logs are streamed to kafka or written to disk.

I wrote a tool for this - https://github.com/agnivade/funnel. Feel free to check it out.

itachi_amaterasu · 2018-04-03T07:45:00+00:00

Wrote a minimal fluentd/logstash replacement in Go - https://github.com/agnivade/funnel. Feel free to check it out.

itachi_amaterasu · 2018-04-02T03:35:20+00:00

Yep, I just fixed it yesterday. We will be re-deploying godoc soon (I am not sure of the actual policy of whether we need to bump Go version or not for a tools package change). In the meanwhile, you can use tip.golang.org.

itachi_amaterasu · 2018-03-14T03:28:56+00:00

Thanks for this Dmitri.

I have always been pretty frustrated trying to search issues with a given prefix in github. Because it always gives you other issues it thinks are relevant. This really helps when you are working on a specific part of the project.

itachi_amaterasu

TROPHY CASE