text stringlengths 0 1.49k |
|---|
**Dmitri Shuralyov:** Yeah, I'd like to cover that, so... Just upfront, I will say that I have deleted the very last gist, I believe in 2015. |
**Brian Ketelsen:** \[laughs\] That's awesome! |
**Dmitri Shuralyov:** From that point forward, the only gists that still exist are people's old code; maybe they've copied it, or forked it, or vendored it, or whatever, and so on. So none of my code has gists anymore, but yes, I did that... And again, that was an experiment that I ran, so when I was doing it, I was ki... |
What actually made it work was that I had a widget in Conception that I can just press a button, and whatever I'd paste into a box would automatically become a gist, it will put it into my GOPATH... It would do everything in one button press. So that is the reason why it was kind of efficient to create a lot of code fo... |
\[16:08\] Over time, I saw that it's great for the initial prototyping, it is not good for maintenance; it's bad that the gists have numbers, that's the package name... So it is not a good practice, and over time I refactored all the code that I needed, to have really idiomatic, nice package names, and be the kind of c... |
So yes, they did exist then, they no longer do exist, and if you see them, please delete them... |
**Brian Ketelsen:** I think you should wear it with pride. Why not...? |
**Dmitri Shuralyov:** I do, yeah. |
**Carlisia Thompson:** I wanna now take a moment and discuss if it's gist \[djist\] or gist \[gist\]? No, I'm kidding... \[laughter\] |
**Erik St. Martin:** Then we have to stop talking about gif \[gif\] or gif \[djif\]... |
**Dmitri Shuralyov:** Yeah, yeah, it's the same question. \[laughter\] |
**Carlisia Thompson:** But you know, I say gif \[gif\] and gist \[djist\], so it cannot be the same... |
**Erik St. Martin:** Yeah, I do, too. |
**Carlisia Thompson:** Right? |
**Dmitri Shuralyov:** Yeah, it doesn't make any sense. |
**Carlisia Thompson:** See? Let's not go there... \[laughter\] I do wanna talk about though -- because to me it seems like such a big deal what you're doing, taking time off to work on your preferred open source projects, the ones that you really wanna make sure happen, and there's so many projects you're involved with... |
**Dmitri Shuralyov:** Sure, sure. So I don't think I have a nice disconnect between the different projects; a lot of them are interconnected in some ways, and a lot of them are kind of these umbrella projects where there's maybe something higher level, and lower level. But let me say that right now I think that we're i... |
In my opinion, this is a really awesome and kind of important point in time, because it means that hopefully soon more and more people can start to see that there's now the choice of what language to use inside the browser, what kind of technologies you use to develop your front-end stuff, and I really wanna see Go pla... |
I find that it's great even for doing front-end stuff, and I've been testing that theory for the last two years, I think, and I'm still very happy with it, so I'm continuing to push in that direction. |
But because of that, I think WebAssembly and Go are important, so that is kind of what I'm thinking about, and one of my top priorities - I wanna make that as much of reality as possible over the next few years. |
**Erik St. Martin:** Now, is there anything currently that's compiling or transpiling to WebAssembly from Go? Does [gopher.js](https://github.com/gopherjs/gopherjs) do that? |
**Dmitri Shuralyov:** \[20:06\] So the situation right now is that if you want to write your front-end code in Go, you have a really good option, and that is Gopher.js, but Gopher.js goes directly from Go code to JavaScript. It has nothing to do with WebAssembly, and the thing about WebAssembly is that it's a very, ver... |
If you were to try to add WebAssembly support to Gopher.js, you're basically starting from scratch. There's nothing really in it that helps you accomplish that job. So the way that I think this will happen is that hopefully maybe the official Go compiler will sometime in the future be able to target it, or maybe somebo... |
**Erik St. Martin:** So basically everything you work on is kind of like these bleeding edge kind of thoughts and concepts... Because you've also been working on [GraphQL](https://graphql.org/) stuff for a long time, too... |
**Dmitri Shuralyov:** Yeah, GraphQL is something that I've somewhat dabbled in recently, and I'm mostly done with that effort. What I saw - this happened about four months ago, three months ago... At that time, GitHub announced that their next version of the API (version 4) is going to use GraphQL. For anyone who hasn'... |
When GitHub announced that their next API is using this, that's when I saw that like this is actually a technology that's now picking up steam, and it's kind of more useful to have support for it, and I saw that in Go. There were a couple packages that implemented the GraphQL server-side, so you could have your GraphQL... |
I've done a little bit of research and I tried a few things, and I saw that "Okay, if I spend maybe a couple weeks, I could have a working client." I saw that there was quite a bit of work, but I saw that I could do this in that amount of time, and I thought it was worthwhile to make it so that there'd be a Go client f... |
It has some to-do's, but it's mostly done in the to-do's that can be completed over time. The basic functionality works, and anyone can use it. |
**Carlisia Thompson:** That is very cool. GraphQL is pretty cool. |
**Erik St. Martin:** Yeah, it's one of those technologies that always seems really fascinating, and I was always looking for the nail for that hammer... |
**Dmitri Shuralyov:** \[23:50\] Yeah. So I was somewhat fortunate in that very recently - maybe just two weeks ago - I actually had the chance to use it for real in a project. Up until that point, I've only been testing it. I've written programs that would just do various things for testing purposes, never really using... |
One of the things about it, one of the properties of GraphQL is that it's very type-safe, and I really enjoy that property of Go. It was really nice to see it here, as well. So you have really great, strong type safety, and it makes things like autocomplete help you a lot more, and the code that you write, you can see ... |
**Carlisia Thompson:** I know there is at least one episode on the Changelog that talks about GraphQL, and I listened to it, and whenever I listen to somebody talking about it, or I read about it, I wanna use it immediately... But then I go back to good ol' REST. \[laughs\] |
**Dmitri Shuralyov:** I really think that GraphQL is a great technology, it has a lot of strengths, but it also has some weaknesses that will take time for everybody to find ways to deal with. Nobody's gonna jump and switch to it right away this year; it's gonna take many years I think, and people will gradually switch... |
**Carlisia Thompson:** And talking about front-end stuff, because you know so much about this space... Sometimes, some applications need to be a back-end that interfaces with the database, and it needs a reporting layout on top of it. Is there any Go package that would do that? |
**Dmitri Shuralyov:** When you say 'reporting', do you mean like kind of just render some front-end components that visualize whatever data is on the back-end, that's being served? |
**Carlisia Thompson:** Yeah, something like the equivalent of an Excel front-end. |
**Dmitri Shuralyov:** Oh, like an Excel front-end, I see. |
**Carlisia Thompson:** Yeah. Not an Excel exactly, but you know... You choose fields and then you get a table, output of data |
**Dmitri Shuralyov:** Well, I can't think of an existing project off the top of my head that's exactly like that; if you're really talking about like a database editing/table editing component, or... |
**Carlisia Thompson:** No, just output. |
**Dmitri Shuralyov:** Oh, just like visualizing it... |
**Carlisia Thompson:** Exactly, yes. |
**Dmitri Shuralyov:** Do you have some database output that you wanna visualize this way and you'd wanna use it? |
**Carlisia Thompson:** Yeah, and I might wanna filter by fields. |
**Dmitri Shuralyov:** I see. I don't know of an existing solution. I think you would have to maybe look for it or maybe just create it yourself, but the thing that does exist right now - or continues to be developed - is a project called [Vecty](https://github.com/gopherjs/vecty), and I think this has already come up o... |
So Vecty tries to do things in a very Go-centered way, and you could totally use Vecty then to create some sort of front-end. You would still have to build it from the individual HTML tags and so on, to visualize all the things you want... But it will let you not worry about having to re-render some parts of the page a... |
\[28:12\] One of the disadvantages of trying to use Go on the front-end is that unless somebody else has created it, you probably have to do it yourself, and sometimes you have to really make this path that no one has traveled yet before. But that can also be a lot of fun, so it's kind of great if you're looking for th... |
**Carlisia Thompson:** Yeah, because the other languages that are more mature, they have a bunch of packages that would do things like that. |
**Dmitri Shuralyov:** Yeah, actually I saw an example of that very recently. There's an npm package you can download, and it's basically a component that visualizes diffs, or patch files, and I was like "Well, you can just npm install that, and it already exists, and it has all these properties that you can configure h... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.