Speaker 2
I believe it's just wont feel refuse to run it's goang o say not to borri. Ye, ok,
Speaker 1
com, ye, make sense. Ah, ye. They go. That's good to know. Ye. I mean, often i'm so abstracted from the physical hardware. In certain environments, the wereo, that wouldn't be i wouldn't be able to make use of that. But there's certainly some cases where i could probably use that to day. Appreciate telling me about that one. And even if you think, well, my work load is not that special, i believe in go
Speaker 2
m d 64, version three, there's an instruction that the run time garbage collector can use to quickly scan memory for four pointers, or something like that, in a way that essentially batches the work and makes it a lot faster. So you might get
Speaker 1
the run time g cs being like a few % faster, even if you don't care about no sues. So even if you're not going to make use of it, maybe the go tooling and run time and bits and pieces do very interesting. I do want to speak about one more subject before we get on to work spaces, if we can. And this is something i use a lot, and these are the templates in go. So we got text template and h m l template. And these sometimes get criticized as being too rudimentary and too low level. And but it sort of has enough of what you need as long as you mix in go code. Usually in functions that you make available to the ten plates. You cannot really do everything you need, but are we getting some new functionality in ten plates? So i added a couple here, which are pretty simple to understand.
