สำเนาบทสนทนา 🔗
WEBVTT
00:00:01.241 --> 00:00:04.631
Hello everyone and welcome to another episode of Code and the Coding Coders who Code it.
00:00:04.631 --> 00:00:12.730
I'm joined today by Vladimir Dementyev, also known as Vova, and would you please do two things for me.
00:00:12.730 --> 00:00:23.952
One introduce yourself and then also explain for people like me who do not understand how Vladimir turns into Vova, because when I found out, I was very interested.
00:00:23.952 --> 00:00:24.614
Hey everyone, the good question.
00:00:24.614 --> 00:00:24.894
So my name is.
00:00:24.914 --> 00:00:25.937
Vova because when I found out I was very interested.
00:00:25.937 --> 00:00:26.679
Hey everyone, the good question.
00:00:26.679 --> 00:00:32.911
So my name is Vova, that's a short version of Vladimir, and I actually don't know why.
00:00:32.911 --> 00:00:40.954
I know it's common in the States, in American names, many names like Robert and Bob.
00:00:40.954 --> 00:00:46.112
They have some similar letters but it's not truly the same word.
00:00:46.112 --> 00:00:52.173
It's the same mystery for us again, for foreigners, to understand why Bob is becoming Robert and vice versa.
00:00:52.173 --> 00:01:02.887
And it's actually closer because if you write Bob and Volvo in Russian it's going to be the same letters because V like V, the sound V in Russian is looking like B.
00:01:02.887 --> 00:01:06.147
So maybe there is something here.
00:01:06.147 --> 00:01:06.590
I don't know.
00:01:06.590 --> 00:01:12.572
But yeah, we usually have many names and many Slavic Russian names.
00:01:12.572 --> 00:01:19.549
They have two or three or four variations, so you're free to choose one you prefer.
00:01:19.549 --> 00:01:25.727
So in mine preferred name is Vlava and Vladimir is an official name.
00:01:26.581 --> 00:01:35.212
And for the record, it is not shortened to Vlad, which is what I learned today, Because in my head it was always oh, Vladimir, Vlad, because I've heard Vlad is like a Russian name.
00:01:35.820 --> 00:01:38.028
Yeah, that's what happens to Vladimir.
00:01:38.028 --> 00:01:46.974
All Vladimirs that come to the States, they want to be, you know, more accessible in terms of like naming things.
00:01:46.974 --> 00:01:53.108
So they shortened themselves to Vlad because it's easy, but in Russia that's a different word name.
00:01:53.108 --> 00:01:57.210
So Vlad is a short version for Vladislav and that's not me.
00:01:57.210 --> 00:01:59.584
So I did that mistake.
00:01:59.825 --> 00:02:09.402
Actually, at my first RailsConf I presented myself as Vlad, just to, you know, be closer to the audience, easier to remember, whatever.
00:02:09.402 --> 00:02:11.187
Because, oh, vlad, whatever, what is it?
00:02:11.187 --> 00:02:19.271
So then, after I moved to the States, I realized that, oh, actually, people here don't care about assimilating names.
00:02:19.271 --> 00:02:28.866
Let's say, everyone's using their names, most people, and you have to learn how to pronounce names in different languages, especially when I live in New York.
00:02:28.866 --> 00:02:32.409
So we're the community's most diverse, I think in the States.
00:02:32.409 --> 00:02:37.551
So, and I found out, oh, I should not call myself by a different name, I should use my name.
00:02:37.551 --> 00:02:48.205
So that's when I started slowly, like gradually, teaching I would say my friends that, oh, okay, actually I'm Bova, so it's yeah, it's harder to say.
00:02:48.205 --> 00:02:54.125
I understand that, but so that's why I'm fine with Vladimir and even Vlad is fine, I don't worry about that.
00:02:54.926 --> 00:03:08.384
I was always curious whenever Irina would like talk about you to me or like whatever, she would use Vova and it's one of those like we call Richard Dick at times and I'm like wait, I know there's a story there, I just don't know what it is.
00:03:08.384 --> 00:03:13.592
So, and now I learned, today I learned, and hopefully audience someone out there also learned.
00:03:13.891 --> 00:03:19.211
Yeah, and actually for the record, we don't call Irina Irina, we called her Ira.
00:03:19.211 --> 00:03:28.474
So the thing I'm learning, see I'm doing terribly- and I'm actually encouraging her to use this name when she's presenting somewhere.
00:03:28.474 --> 00:03:33.467
So not Irina, ira, just people going to learn that at some point.
00:03:33.487 --> 00:03:33.889
Yeah, yeah.
00:03:33.889 --> 00:03:37.889
Well, some of us are dumb and take a minute to learn things, but we will eventually learn them.
00:03:37.889 --> 00:03:38.812
So, ira, yeah.
00:03:38.812 --> 00:03:42.701
Okay, so anytime she no good stuff, but okay.
00:03:42.701 --> 00:03:48.866
So, vova, please introduce yourself to anyone in the audience who is not familiar with you or your work.
00:03:49.266 --> 00:03:54.909
So I'm working as a principal engineer, evil Martians consultancy.
00:03:54.909 --> 00:04:01.653
Nowadays we're focusing on dev tools, startups and all cool stuff around us.
00:04:01.653 --> 00:04:06.518
We do a lot of stuff in the Rails world, frontend world or whatever.
00:04:06.518 --> 00:04:17.446
Personally, I'm responsible for the backend team, so I'm not doing anything useful for clients directly.
00:04:17.446 --> 00:04:19.850
I'm just mostly doing research work, marketing work.
00:04:19.850 --> 00:04:29.507
Sometimes I join clients just to brainstorm ideas, but these days I'm focusing on conferences too, in particular.
00:04:29.507 --> 00:04:44.807
So RailsConf is just in a month and we have three Martian speakers there and I'm including and I'm preparing a talk on Rails, on Basm Not a new version, but a new kind of projection of Basm.
00:04:44.807 --> 00:05:04.307
Not a new version, but a new kind of a projection of Basmification of Rails, because this time we're trying to put the Rails tutorial, the whole tutorial, into the browser so you can try and build something with Rails to get an idea of what Rails is, without leaving your browser from databases, web
Load full transcript
servers, tests, everything.
00:05:04.307 --> 00:05:22.920
So just in your window, and I think that's an important step for making framework more, again, I would say, accessible to people who are not familiar with Ruby and Rails, who don't want to deal with oh, rbn and Stone doesn't work, or what's wrong with my Ruby version on Mac OS or whatever.
00:05:22.920 --> 00:05:32.331
So we have every server-side language has these problems and we want to eliminate this steep learning curve.
00:05:32.331 --> 00:05:37.286
It's the entry curve, I would say, and that's what we're working on, and I want to present that at RailsConf.
00:05:37.286 --> 00:05:41.891
So that's one of my primary tasks today.
00:05:41.891 --> 00:05:44.608
And another one is also related to conference.
00:05:44.608 --> 00:05:47.149
We just announced San Francisco Ruby Conference.
00:05:47.149 --> 00:05:57.629
So it's kind of the evolution of San Francisco Ruby Meetup, which we've been holding for more than a year and every month in San Francisco.
00:05:57.629 --> 00:06:00.249
It just actually happened yesterday or two days ago.
00:06:00.249 --> 00:06:11.769
And this November we decided, okay, we should go with a conference Two day, probably single, two track, we don't know yet, but that's going to be the whole feature conference.
00:06:11.769 --> 00:06:14.661
We preparing for that.
00:06:14.661 --> 00:06:17.747
I'm personally responsible for technical stuff as well.
00:06:17.747 --> 00:06:25.992
So we just built a CFP application from scratch for the conference because, well, there are a lot of reasons we can talk about it later.
00:06:25.992 --> 00:06:29.428
So, yeah, that's what I'm doing now.
00:06:29.428 --> 00:06:35.192
And, of course, another field of interest in my continuous work is AnyCable.
00:06:35.192 --> 00:06:43.014
So this project that's actually turning nine years in a month.
00:06:43.014 --> 00:06:47.672
Yeah, like from the day that the name came out right.
00:06:47.672 --> 00:06:52.230
I came out with the name, it was right after I joined Evil Martians.
00:06:52.230 --> 00:06:57.324
So it's nine years since I joined Evil Martians and that was my first open source project.
00:06:57.324 --> 00:07:07.142
I decided to build within the company and, yeah, that's like one of the primary projects and products right now for us, so it's real time server.
00:07:07.142 --> 00:07:21.648
If you don't know, performer is powering WebSockets for Rails apps and not only Rails, because this week we announced our initial Laravel integration and we are looking to make any table.
00:07:21.939 --> 00:07:23.757
Jason Tromp will be so excited about that.
00:07:24.000 --> 00:07:30.485
Well, yeah, like Laravel, is underwriter of many Ruby and Rails developers for many years.
00:07:30.485 --> 00:07:44.283
We know that Chris Oliver, for example, got inspiration for his PayJam from Laravel PayJam version I don't remember how they call it, but it's something they had built in into ecosystem for a
long time.
00:07:44.283 --> 00:07:46.545
So they had a lot of great ideas.
00:07:46.545 --> 00:07:50.367
They've been like a Rails descendant in some sense.
00:07:50.367 --> 00:07:57.492
They actually chose Datapath and we can learn back from them and we do that sometimes.
00:07:57.492 --> 00:08:04.557
And then Cable decided okay, we can actually now again bring something from Rails to Reliable like a powerful WebSocket server.
00:08:04.557 --> 00:08:08.562
It's going to work easily with their existing tooling.
00:08:09.002 --> 00:08:24.187
So, yeah, that's how I kind of scared some people on Twitter last week when I showed some screenshots of me doing Laravel and I got some replies oh no, what are you doing?
00:08:24.187 --> 00:08:26.526
Are you going to abandon Rails?
00:08:26.526 --> 00:08:26.987
What?
00:08:26.987 --> 00:08:28.846
No, I'm not going to do that.
00:08:28.846 --> 00:08:50.408
We wanted to share what we built for Rails community with others, and one of the goals is actually to make the tool we build in AnyCable and everything around it better, because the more use cases you have, the more ecosystem you try to integrate your software, the better it becomes, and we want this any part of AnyCable.
00:08:50.408 --> 00:08:55.952
So that's kind of philosophy which is in the name, is to be truly any and many directions.
00:08:55.952 --> 00:09:00.299
So it's like for any backend, any framework, whatever, any protocol.
00:09:00.299 --> 00:09:15.807
So that's just fits our vision for this open source tool and we just try to make it better and help others building better cool things with it.
00:09:16.067 --> 00:09:16.649
That's awesome.
00:09:16.649 --> 00:09:18.974
You are a man of many projects.
00:09:18.974 --> 00:09:28.751
People also might know you from your book Laird on Rails applications, and you have a newish version.
00:09:28.751 --> 00:09:30.914
Let's say it's in the works.
00:09:30.914 --> 00:09:32.361
We'll go within the works.
00:09:32.763 --> 00:09:51.727
Yeah, I haven't mentioned that as my project because, well, something I try to put at the end of the backlog every day, but I promised to myself actually to start writing, updating existing chapters, writing new chapters this weekend, like just tomorrow.
00:09:51.727 --> 00:10:02.644
I don't know if it's going to be like that, but because we want to get it out around Rails world, I'm not coming this year, but maybe someone will make an announcement, I don't know.
00:10:02.644 --> 00:10:07.913
So, yeah, the second edition this year, but maybe someone will make an announcement, I don't know.
00:10:07.913 --> 00:10:08.716
So, yeah, the second edition.
00:10:08.716 --> 00:10:10.339
It seems like, oh, it's just an upgrade.
00:10:10.339 --> 00:10:15.484
You already have the content, so it should be much simpler, but it's not so.
00:10:15.504 --> 00:10:18.386
When dealing with the book, it's just some state of mind.
00:10:18.386 --> 00:10:35.991
You just need to find yourself, to find the right I don't know mood or whatever to get into writing a book, to getting back into loading all the context back into your brain, which is not as large as LLMs of today.
00:10:35.991 --> 00:10:42.229
I can't just load the whole book into my brain, because it's not just a book, what's written, and that's okay.
00:10:42.229 --> 00:10:47.163
We're switching topics, I'm talking about LLMs and that's just an idea that came into my mind.
00:10:47.163 --> 00:10:54.846
It's not enough to load the text content of the book into the context of whatever brain, llm, whatever.
00:10:54.846 --> 00:11:10.009
To get an idea of what's going on, you need to actually load into your brain's context everything that happened when you were thinking about the book you were writing it, and the amount of that data is enormous.
00:11:10.009 --> 00:11:14.488
It's not reading right, it's not set in stone, it's just something.
00:11:14.488 --> 00:11:24.067
It's more like feelings, something like that, it's like inspiration, and it's not something you can just digitalize right and put into a neural network.
00:11:24.067 --> 00:11:26.908
So that's the hardest part of it.
00:11:27.759 --> 00:11:52.611
That's another project of mine today writing a book and one of the reasons for that is you know that you remember that a couple months ago at Sin City Ruby, we had an auction to support Jason Sweat with his initiative to having this amazing conference and sweat with his initiative to having this amazing conference, and my lot was a copy of my book with the draft of the new chapter, like before the release.
00:11:52.611 --> 00:11:57.249
So I can't just waste that.
00:11:57.249 --> 00:11:58.673
I have to do that.
00:11:58.673 --> 00:12:00.988
That's my responsibility.
00:12:00.988 --> 00:12:11.225
So I hope in a week Jasper will receive this copy and the draft of the chapter, because I already have this chapter in my mind.
00:12:11.225 --> 00:12:12.450
It's going to be cool, I think.
00:12:12.450 --> 00:12:13.081
I hope so.
00:12:13.081 --> 00:12:13.602
I like it.
00:12:13.602 --> 00:12:16.951
That's something I originally wanted to include in the first edition.
00:12:16.951 --> 00:12:19.423
But yeah, well, we'll see.
00:12:19.423 --> 00:12:25.693
So a lot of things going on so we can talk whatever you want.
00:12:25.693 --> 00:12:27.687
What's on your plate?
00:12:27.687 --> 00:12:31.265
Do we have any intersection here?
00:12:31.265 --> 00:12:33.730
Sure, yeah, are you writing Laravel?
00:12:34.893 --> 00:12:36.245
Yes, I am not writing Laravel.
00:12:36.245 --> 00:12:47.865
Laravel has always been one of those because it's so adjacent to Rails, it's like a descendant, it's so influenced, and then it went a step further with everything else it has going on.
00:12:47.865 --> 00:12:50.245
Laravel's always been one of those.
00:12:50.245 --> 00:12:52.841
Like man, if I couldn't write Rails anymore, what would I do?
00:12:52.841 --> 00:12:59.283
And I still think I'd pick a
Ruby-based framework, but I would definitely give Laravel a try.
00:12:59.283 --> 00:13:05.950
It seems so cool, it seems so fun and it seems like it has a pretty great ecosystem and community like rails.
00:13:05.950 --> 00:13:08.144
So yeah, it's on the list.
00:13:08.144 --> 00:13:08.845
I haven't, though.
00:13:08.845 --> 00:13:14.903
Php is just daunting to me because ruby has ruined me for other languages.
00:13:14.903 --> 00:13:18.972
Like I look at other languages and like I don't know if I can, just I don't know.
00:13:20.182 --> 00:13:32.879
But the way that the show normally works for anyone who's listening for the first time is normally what would happen is I would ask vovo what he's working on, what kind of blockers he has and what's something cool, new or interesting that he's recently learned or discovered.
00:13:32.879 --> 00:13:42.835
I'm pretty sure his intro covered the what are you working on question, which is the too long didn't listen version is a lot.
00:13:42.835 --> 00:13:47.903
Long didn't listen version is a lot.
00:13:47.903 --> 00:13:48.525
You've got a RailsConf talk.
00:13:48.525 --> 00:13:58.980
You've got a San Francisco Rubyist meetup group that you help run, and the conference coming up that you're building tools for, and you're working on the AnyCable to Laravel stuff and you've got the update to your book coming up.
00:13:58.980 --> 00:14:00.785
So there's a lot.
00:14:00.785 --> 00:14:02.750
Is there anything I missed on the?
00:14:02.750 --> 00:14:03.251
What are you working on?
00:14:03.251 --> 00:14:05.557
Actually, I have an everyday work, so there's a lot Is there anything I missed on the?
00:14:05.577 --> 00:14:06.980
what are you working on, Actually?
00:14:06.980 --> 00:14:08.322
I have an everyday work.
00:14:08.361 --> 00:14:10.384
On top of everything else, you have a day job.
00:14:10.384 --> 00:14:10.904
Got it.
00:14:11.725 --> 00:14:15.009
Meetings, calls, whatever, explorations.
00:14:15.009 --> 00:14:16.451
That's the boring part.
00:14:16.451 --> 00:14:26.943
It becomes less boring when I write about it, so in a book or give a talk and something like that, but in the moment it's usually boring stuff.
00:14:26.943 --> 00:14:31.557
I try to finish as soon as possible so I can have some time for all the cool stuff.
00:14:31.557 --> 00:14:36.345
Yeah, so that's actually my blocker, if you ask me what's my blocker.
00:14:36.365 --> 00:14:38.365
There you go, we're moving right along here.
00:14:38.365 --> 00:14:39.740
You've got plenty of work.
00:14:39.740 --> 00:14:42.203
You're working on and your blocker is your fucking day job.
00:14:42.203 --> 00:14:42.624
Oh right, it's Friday.
00:14:42.624 --> 00:14:43.725
I working on and your blocker is your fucking day job.
00:14:43.725 --> 00:14:44.566
Oh right, it's Friday.
00:14:44.566 --> 00:14:46.028
I'm in a mood, it's fine.
00:14:46.628 --> 00:14:49.150
I don't know that you can find a better word to explain it.
00:14:49.150 --> 00:14:53.196
Well, I like my job, but sometimes we have too many calls.
00:14:53.196 --> 00:15:08.528
They are all important because, well, my work on conference talks or even book doesn't help the company I work for and so that's kind of a bargain.
00:15:08.528 --> 00:15:19.301
Yeah, sure, I had tons of calls and they allowed me to write the book, you know the open source work, there you go, that's a fair trade, in my opinion.
00:15:20.121 --> 00:15:30.716
So I'm currently in because, as of recording, right now it is Friday, june 6th, which means we are rapidly approaching one month away from RailsConf.
00:15:30.716 --> 00:15:37.249
So I'm starting to get pumped for everybody to come to Philly and have a cheesesteak and talk about Ruby and Rails and all that jazz.
00:15:37.249 --> 00:15:40.902
And your talk is on Ruby on Rails in the browser with Wasm, which is super cool.
00:15:40.902 --> 00:15:56.229
Ruby on Rails in the browser with Wasm, which is super cool, and you're building basically the Rails tutorial interactively because of Wasm, not just like hey, read and look at this example, but read, look at this example and then interact with it.
00:15:56.229 --> 00:16:05.894
Can you tell us a little bit about some of the challenges on getting Rails into the browser, the state of Ruby, wasm, things like that?
00:17:27.444 --> 00:17:44.094
Yeah, so we started exploring this idea of putting Rails on WASM about a year ago Actually I think it was the very first South Ruby meetup.
00:17:44.094 --> 00:17:51.410
I presented the first talk when I managed okay, I can run a Rails application like very minimal Rails application, almost like Rails new, with some database interactions in the browser.
00:17:51.410 --> 00:17:55.096
It kind of worked enough to present a meetup.
00:17:55.096 --> 00:18:02.595
But it actually was just a very proof of concept and we started exploring this idea.
00:18:02.595 --> 00:18:07.767
And well, we started facing challenges and we started to explore this idea.
00:18:07.767 --> 00:18:14.173
And well, we started facing challenges Because Ruby is not truly a fully solved problem like a fully solved task.
00:18:14.173 --> 00:18:21.684
We have an official VASM support in Ruby which means it's possible to compile Ruby C code, like MRI code, into VASM.
00:18:21.684 --> 00:18:24.700
There are some C macros and ifdef whatever stuff over on the code base to make it compilable into VASM.
00:18:24.700 --> 00:18:30.695
There are some C macros and if-dev whatever stuff over on the code base to make it compilable into VASM.
00:18:30.695 --> 00:18:40.916
And that means you can run Ruby VM within VASM runtime browser or not only browser and that's cool.
00:18:40.916 --> 00:19:05.274
But there are some limitations like no networking, no other stuff and so on, and when it comes to like everything in Ruby world, you kind of measure the applicability of some new idea, some new tool, some language addition by the matter, if it's possible to run Rails on that.
00:19:05.274 --> 00:19:12.977
For example, we had Rectors right, rectors has been around for five years already, something like that.
00:19:12.977 --> 00:19:20.658
But the true measure of whether Ruby is Rector-ready is whether we can run Rails on Rectors.
00:19:20.658 --> 00:19:23.840
And the answer is not, not yet and maybe never.
00:19:23.840 --> 00:19:28.675
And the same could be applied to any new stuff that comes out.
00:19:28.675 --> 00:19:38.682
Actually, because Ruby heavily depends on Rails as its primary driver for attracting developers, engineers and so on.
00:19:38.682 --> 00:19:42.661
So we can just avoid this fact, right?
00:19:42.661 --> 00:19:47.902
We're not going to talk about whether it's good or not being like single framework-centric language.
00:19:47.902 --> 00:19:51.519
That's just the fact and we should live with it.
00:19:51.519 --> 00:19:53.596
So the same could go with VASM.
00:19:53.596 --> 00:20:02.156
So, okay, we have Ruby on VASM and actually Ruby VASp has much more application than just Rails being a Rails playground.
00:20:02.156 --> 00:20:05.442
But I asked myself the question okay, can I run Rails on Wasp?
00:20:05.442 --> 00:20:09.037
And it turned out that there were a lot of cool stuff.
00:20:09.037 --> 00:20:13.754
That's when you feel yourself like a pilgrim software engineer.
00:20:13.754 --> 00:20:17.052
You experience something for the first time that no one ever experienced that.
00:20:17.052 --> 00:20:21.941
Because who's crazy enough to try running on VASP why?
00:20:21.941 --> 00:20:24.492
A lot of people are trying to ask the question why?
00:20:24.492 --> 00:20:25.475
Why do you need this?
00:20:25.475 --> 00:20:27.179
Why to run Ruby on VASP?
00:20:27.179 --> 00:20:28.643
A lot of people don't understand.
00:20:28.643 --> 00:20:32.253
But I think those people also don't understand that.
00:20:32.253 --> 00:20:33.735
Because why not?
00:20:33.735 --> 00:20:34.656
That's the answer.
00:20:34.656 --> 00:20:37.459
That's how my mind works.
00:20:38.019 --> 00:20:44.447
I like the phrase coined at Rails World or RailsConf by Xavier Noria once.
00:20:44.447 --> 00:20:51.721
He also was talking about something like that and he stated that it's just a joy of problem solving.
00:20:51.721 --> 00:21:02.355
It's something like he explained that because of mathematics, mathematician roots, and I am a mathematician as well, so I love abstract stuff and all that and I just love solving problems.
00:21:02.355 --> 00:21:20.465
So it doesn't matter if there is a practical outcome of the solution right, I believe it's kind of academical kind of stuff right, it doesn't matter if you prove the theorem or whatever or some theory and it doesn't make sense today.
00:21:20.465 --> 00:21:24.355
One day some people discover it and they build something cool out of it.
00:21:24.355 --> 00:21:26.276
You never know how it's going to be used.
00:21:26.276 --> 00:21:43.682
That's where the combination of this and the joy of problem solving brought me to this Rails on VASM, and I was like a kid in a candy store because there were a lot of problems I didn't know how to solve and that's where there were a lot of blockers.
00:21:44.150 --> 00:21:53.554
But the good thing is that we're still dealing with Ruby and I believe that in Ruby, everything is possible, whatever you can imagine.
00:21:53.554 --> 00:21:59.602
You can do that Just because the language, the ecosystem, the language itself is flexible.
00:21:59.602 --> 00:22:06.620
It's an open language, which means that, oh, if something doesn't work, you just put a patch, a hack it or something to find a way out.
00:22:06.620 --> 00:22:07.915
It doesn't matter what is it.
00:22:07.915 --> 00:22:25.180
Oh, you don't have socket support in the browser or, like Nakagiri, let it just add a tab class with pure Ruby implementation, or just block it and make it look like it works, and it's probably going to work and it's enough for running something in the browser.
00:22:25.180 --> 00:22:27.096
And we have a lot of that stuff.
00:22:27.470 --> 00:22:33.900
And we were just trying to solve all the problems one by one, because Rails is not just Ruby.
00:22:33.900 --> 00:22:38.244
So you have extensions, you have databases, you have web server and you need somehow to put all of that into the browser.
00:22:38.244 --> 00:22:38.644
It's not just Ruby.
00:22:38.644 --> 00:22:45.009
So you have extensions, you have databases, you have web server and you need somehow to put all of that into the browser.
00:22:45.009 --> 00:22:48.601
And every component of Rails requires just some special attention.
00:22:48.601 --> 00:23:17.077
And at the first step, by the end of the previous year 2024, we managed to solve the problem, I think, of putting production application into the browser, but what I mean is that you can just pack your application to a VASM module, add some JavaScript scripting that we made generic enough to run any Rails application and just put it in the browser, and it's going to work up to some point.
00:23:17.077 --> 00:23:20.024
We already have databases in the browser, so it's not a big deal.
00:23:20.024 --> 00:23:41.774
And the fact that Ruby is open language and Rails is a kind of modular framework and with a lot of stuff abstracted out the Rails concepts, most of them at least, abstracted out from the implementation, so we can just swap them and replace, like, for example, sqlite database, for example, a SQLite database regular database, which is just a file.
00:23:41.774 --> 00:23:54.476
You can replace it with a JavaScript external interface and still use the same ActiveRecord connection class and most of it to build queries and do all the stuff, and it's just going to work because Rails allows us to do that.
00:23:54.476 --> 00:24:05.817
And the same goes about any Rails component, and we managed to build adapters and wrappers for running Rails in the browser.
00:24:06.781 --> 00:24:11.553
Again, the question
still holds why do you need to run Rails in the browser?
00:24:11.553 --> 00:24:20.082
And after giving this idea some time just to age, well, we found that okay.
00:24:20.082 --> 00:24:24.927
Actually, how do others use in-browser technologies?
00:24:24.927 --> 00:24:41.490
For example, we have JavaScript and while it's natural for them to run a lot of stuff in the browser because that's their runtime, but actually more than JavaScript, it's not just a browser right, it's like full stack nextjs and all that stuff and serverless stuff.
00:24:41.490 --> 00:24:59.860
They still need some kind of server and in JavaScript world they kind of solved it by putting notjs into the browser, also by the means of Basm and the project one of actually our EvoMotions clients that's why we know about that is called StackBlades.
00:24:59.860 --> 00:25:12.079
It's an online IDE that fully runs in the browser so you can run almost any JavaScript project with server and client right in your browser, with previews, hot reloads or whatever.
00:25:12.079 --> 00:25:15.679
It just works and it doesn't require any servers, containers, whatever.
00:25:15.679 --> 00:25:21.596
It's not like Cotspaces or something like that where you have a real server, right, it's really in your browser.
00:25:22.130 --> 00:25:26.157
And we were thinking like, okay, why can't we have the same for Ruby?
00:25:26.157 --> 00:25:28.817
Right, because we found it very useful.
00:25:28.817 --> 00:25:36.561
You can trash issues for open source projects or share some working examples, how to do stuff.
00:25:36.561 --> 00:25:46.330
So, oh, it's not just copy-pasting text, you just send a link where you have a reproduction and people can try it with both server and client.
00:25:46.330 --> 00:25:56.863
And we found that, okay, probably this aspect of basmification, educational aspect today is most valuable.
00:25:56.863 --> 00:26:09.862
So that's where we can get benefit right away just by making Ruby and Rails browser ready so people can try with it, can share some snippets, whatever.
00:26:09.862 --> 00:26:13.018
And that's where we started working in that direction.
00:26:14.131 --> 00:26:15.416
And Rails getting started tutorial is a good starting point.
00:26:15.416 --> 00:26:18.086
That's like a milestone If we can't put Rails getting started tutorial is a good kind of starting point.
00:26:18.086 --> 00:26:32.081
That's like a milestone If we can't put Rails getting started into the browser so people can just run Rails, new Rails like tb, migrate Rails, test, whatever, everything right in their browser without dealing with installations or whatever.
00:26:32.081 --> 00:26:37.633
We can identify all the problems we find along the way and later on.
00:26:37.692 --> 00:26:50.875
So that's our plan we can actually make this framework for building tutorials for Ruby projects generic enough so we can use it for your library, for your framework not only Rails and so on.
00:26:50.875 --> 00:27:02.779
So we're using Rails as a playground and we plan to go further from there, and that's what we're going to talk about at RailsConf.
00:27:02.779 --> 00:27:18.420
We already have half of it running in the browser, so I'm teasing some snippets every week on Twitter and they're actually lagging like a couple weeks of work, so we're closer to the end than it seems.
00:27:18.420 --> 00:27:32.863
So, yeah, and I'm pretty excited about it because, let me be honest, when we proposed this talk so I'm doing this talk with my colleague who's actually working on StackBlade's project and we had nothing, we just had an idea.
00:27:32.863 --> 00:27:35.158
So it's a typical, I guess, like a conference.
00:27:35.158 --> 00:27:44.596
Well, I had this idea years ago and I started playing with it, actually for Action Policy Jam, because I wanted.
00:27:45.051 --> 00:27:53.613
Well, it's pure Ruby Jam, so it's much easier to put into the browser and create an interactive tutorial on how to write policies and so on.
00:27:53.613 --> 00:27:57.029
And I kind of knew, well, it should be doable.
00:27:57.029 --> 00:28:01.041
And then we got accepted to RailsConf and like, ok, let's start working.
00:28:01.041 --> 00:28:02.737
So that's why I'm doing that.
00:28:02.930 --> 00:28:04.637
Now we actually have to build this thing.
00:28:05.029 --> 00:28:05.552
Yeah, yeah.
00:28:05.552 --> 00:28:07.800
So that's conference driven development.
00:28:07.800 --> 00:28:08.531
It's really cool.
00:28:08.531 --> 00:28:15.836
I don't think it works for everyone, but for me it's the best way, kind of promise driven development.
00:28:15.836 --> 00:28:32.163
Right, I'm writing the book because I promised to write a new chapter right, and I'm writing this Rails on Buzz because probably the Laravel stuff I mentioned is the only thing that came kind of from the inside because I wanted that for myself.
00:28:32.163 --> 00:28:34.256
I don't promise that to anyone.
00:28:34.256 --> 00:28:42.419
I just wanted to distract myself actually from this Rails stuff and the book, so put myself into something new.
00:28:43.252 --> 00:28:44.356
Yeah, what's the old saying?
00:28:44.356 --> 00:28:50.538
It's amazing what a developer can build when they're working on something other than what they're supposed to be working on.
00:28:50.538 --> 00:28:53.759
Laravel benefits from you having a lot on your plate.
00:28:53.759 --> 00:28:55.073
You need a distraction.
00:28:55.073 --> 00:28:57.980
You build something for them.
00:28:57.980 --> 00:29:01.812
That's awesome.
00:29:01.812 --> 00:29:02.594
I'm super excited for your talk.
00:29:02.594 --> 00:29:08.522
It was definitely very highly ranked when we were talking about it in the programming committee of like.
00:29:08.522 --> 00:29:14.317
This fits so perfectly with the future side, because that was the goal for RailsConf.
00:29:14.356 --> 00:29:24.884
Let's talk about the past, present and future of Rails at the last RailsConf, and what a great topic for
the future of Rails is like.
00:29:24.884 --> 00:29:27.352
Oh yeah, by the way, rails in the browser is a thing.
00:29:27.352 --> 00:29:40.111
Look here you can do interactive tutorials and who knows what else and we probably can't even begin to imagine what someone's going to eventually be able to do with Rails in the browser.
00:29:40.111 --> 00:29:50.715
It's such a new concept that we're limited by our imaginations right now, and someone's imagination is going to be like I wonder if I could do, and the answer is going to be yes, and it's going to be super cool.
00:29:50.715 --> 00:29:55.392
So, yeah, I'm excited for that one Amongst others at RailsConf.
00:29:55.412 --> 00:29:58.782
Railsconf has such a great schedule and program.
00:29:58.782 --> 00:30:14.716
Normally I'm a hallway track kind of guy, and this is probably going to be more talks than I've attended since my very first one, just because there's so many good ones that I want to see and I know I probably won't end up watching them on YouTube Not all of them at least.
00:30:14.716 --> 00:30:26.822
In addition to speaking at Rails railsconf, you help with the san francisco ruby meetup, which, from what I hear, is a mini conference in and of itself.
00:30:26.822 --> 00:30:33.671
You guys have multiple hundreds of attendees for each meetup, let alone now you're also doing a conference in november.
00:30:34.413 --> 00:30:37.379
Yeah, the meetup we just said.
00:30:37.379 --> 00:30:41.198
It's a huge success and we have a lot of attendees.
00:30:41.198 --> 00:30:44.402
It's not always hundreds, I think Sometimes it's a hundred.
00:30:44.402 --> 00:31:00.747
It really depends on location, I can be honest, because we have rotating locations, so actually a lot of companies in San Francisco want to host the meetup, so our popular locations would be like GitHub headquarters, I think that's where we get it.
00:31:00.767 --> 00:31:01.109
No, shock there.
00:31:01.129 --> 00:31:11.735
yeah, yeah, that's where we started and that's the first meetup had like probably a couple of hundreds of people and I usually get a lot and we have Chime.
00:31:11.735 --> 00:31:25.541
I only attended GitHub and Chime, I don't know about others, I know actually but I know that the next one in july is happening at figma and we expect it to be packed as well.
00:31:25.541 --> 00:31:31.902
We've been in talks with them for a long time to host this meetup and finally we got the date because it's san francisco.
00:31:31.902 --> 00:31:38.824
Companies have schedule planned for the whole year and like like, oh, you want to meet up at GitHub?
00:31:38.824 --> 00:31:42.380
Okay, we have something for 2026 March.
00:31:42.380 --> 00:31:45.238
We don't even know if it's going to be a meetup.
00:31:45.771 --> 00:31:55.019
Well, luckily, a lot of options and even if the plan has changed for some company and they're busy with something else on that day, we can find a backup.
00:31:55.019 --> 00:32:12.163
So, given that the meetup got a lot of attention and positive feedback, we decided that we should go with a conference, and one of the reasons for doing it this year is actually the fact that they're not going to be RubyConf this fall.
00:32:12.163 --> 00:32:15.700
So we found that, okay, there is a huge gap.
00:32:15.700 --> 00:32:21.319
No Ruby conferences this fall in the States, I think.
00:32:21.319 --> 00:32:23.999
Rocky Mountain announced also their conference.
00:32:24.992 --> 00:32:25.936
Yeah, that's in October.
00:32:27.812 --> 00:32:29.711
So we're going to be in November.
00:32:29.711 --> 00:32:35.278
So we want Ruby conferences to be spread across the year kind of evenly.
00:32:35.278 --> 00:32:37.680
So we have RailsCon this summer and no RubyConf.
00:32:37.680 --> 00:32:38.718
So we said RailsCon this summer and now RubyConf.
00:32:38.718 --> 00:32:42.657
So we said, okay, there is a sit available, why not fill in it?
00:32:42.657 --> 00:32:44.156
And we'll see what's going on next year.
00:32:44.156 --> 00:32:48.057
But I think it's going to be not just a one-time thing.
00:32:48.057 --> 00:32:50.037
Well, we don't want it to be a one-time thing.
00:32:50.037 --> 00:32:52.336
So we're really excited about it.
00:32:52.336 --> 00:32:53.300
It's a lot of work.
00:32:53.300 --> 00:32:54.977
We never did anything like that.
00:32:54.977 --> 00:32:59.497
We'll see.
00:32:59.497 --> 00:33:00.486
So far, I would say it's good.
00:33:00.486 --> 00:33:02.276
We expect a lot of cool speakers.
00:33:02.276 --> 00:33:25.142
We try to make it not just a Ruby conference but a themed Ruby conference around San Francisco and their values, right, startups, ruby builders we want to see people who build with Rails especially new companies and not only new, like major companies as well how they use Ruby, why they chose Ruby and so on.
00:33:25.142 --> 00:33:34.911
So it's more about highlighting Ruby as a cool productive tool for your business than just talking about Ruby itself.
00:33:34.911 --> 00:33:37.817
So that's our goal.
00:33:37.817 --> 00:33:39.321
So so we'll see.
00:33:39.321 --> 00:33:40.903
I'm kind of excited about it.
00:33:41.750 --> 00:33:53.036
We just announced it and it's usually for bigger conferences you need a lot of time for preparation, so we have a very short, I would say, like runway for the conference.
00:33:53.036 --> 00:33:56.061
So we just announced CFP.
00:33:56.061 --> 00:34:07.919
Cfp is open at cfpsfrubycom and that's something I've been working on recently because we decided to go with a custom application for CFP.
00:34:07.919 --> 00:34:09.416
So we built it from scratch.
00:34:09.416 --> 00:34:11.096
That was fun.
00:34:11.096 --> 00:34:16.682
It was fun and stress, stress and fun literally the day of announcement.
00:34:16.682 --> 00:34:21.514
We only had functionality ok, we can accept applications, we don't have anything yet.
00:34:21.514 --> 00:34:25.159
We don't have functionality for reviewing applications and all that
stuff.
00:34:25.159 --> 00:34:37.411
I already started working on that, but that's cool and we want to actually open source the application eventually, probably after the CFP ends, to share it with the communities.
00:34:37.552 --> 00:34:47.771
Maybe someone else will decide to pick it up and deploy somewhere instead of paying CFP services tons of money for I don't know what, why.
00:34:47.771 --> 00:34:58.675
So I remember RailsConf used to use this Ruby CFP app that's still in use, I think by RubyKaigi, maybe some other conferences.
00:34:58.675 --> 00:35:04.920
So it's like an old Rails application and RailsConf and RubyConf used to use them and it was cool.
00:35:04.920 --> 00:35:08.518
Well, it was like old school UI, whatever.
00:35:08.518 --> 00:35:23.838
Yeah, yeah, just HTML driven, but it was much easier to work with than everything that happened next, like sessionize, paperclip they're all so bad, right, and you know like conferences tend to use them.
00:35:23.838 --> 00:35:36.462
So we want to release our open source projects and make it kind of once like thing, right, so you can just grab it, deploy like update styling text and go and build a new version every year.
00:35:38.272 --> 00:35:51.455
I want it to be intentional because I don't want people to just copy all the services aggregator services, that you have a list of your proposals and when another conference announced CFP, you can say, oh, I want to pick these proposals and send it to this conference.
00:35:51.455 --> 00:35:52.954
I think it's just.
00:35:52.954 --> 00:35:54.058
I don't want that.
00:35:54.058 --> 00:36:10.357
I want people to craft a new proposal, at least copy-paste it manually, because as a reviewer, I recently took part at Yuruko a program committee member, so we had 150 proposals and 50 to review by each member.
00:36:10.357 --> 00:36:14.097
But you clearly see that, oh, I saw this proposal somewhere.
00:36:14.097 --> 00:36:17.297
It's just the same, nothing like no word changed.
00:36:17.297 --> 00:36:17.841
I don't like that.
00:36:17.841 --> 00:36:18.489
I don't like that.
00:36:18.489 --> 00:36:20.115
I don't like that attitude.
00:36:20.115 --> 00:36:31.391
If you're proposing something to the conference, try to address the conference you're proposing to Make it fit the topic, the location, whatever.
00:36:31.391 --> 00:36:32.476
I think it's important.
00:36:32.476 --> 00:36:43.777
That's why we're building this one-time CFP app Just to encourage people to fill a new application every time, so maybe they come up with a better idea.
00:36:45.371 --> 00:36:46.414
As regional conferences.
00:36:46.414 --> 00:36:48.580
I mean they're already getting more and more popular.
00:36:48.580 --> 00:37:00.705
With RailsConf going away, I expect that having only one major Ruby conference in the States next year will hopefully drive even more people to do even more regional.
00:37:00.705 --> 00:37:13.399
It'll be very helpful for them because unless you're going
to do an Andy Kroll with Brighton and just hand select all of your no CFP process, I just want this person and this person speaking at this conference.
00:37:13.399 --> 00:37:31.463
Conference like unless you're going to do one of those, you are going to need a tool, and not having to pay for sessionize or deal with the clunkiness of their UI is definitely a good thing, especially when there's so many other things that go on in planning a regional conference.
00:37:31.463 --> 00:37:35.339
That'll be a great open source project for folks.
00:37:36.409 --> 00:37:43.161
Yeah, we hope so, and we also want it to be an example of building with Rails and Inertia Rails.
00:37:43.161 --> 00:37:45.357
That's what we chose for that project.
00:37:45.357 --> 00:37:54.020
The actual reason why we chose Inertia is that because the UI and front-end was mostly AI-generated using boldnew.
00:37:54.020 --> 00:37:55.454
That's actually the same.
00:37:55.454 --> 00:37:57.737
That's a project by StackBlades, I already mentioned.
00:37:57.737 --> 00:37:59.603
That's where you can just build JavaScript projects and run it in the same.
00:37:59.603 --> 00:38:00.853
That is a project by StackBlitz, I already mentioned.
00:38:00.853 --> 00:38:02.469
That's where you can just build JavaScript projects and run it in the browser.
00:38:02.790 --> 00:38:09.099
That's how we built conference website, like its initial version and UI for the CFP app.
00:38:09.099 --> 00:38:19.524
And well, it requires some manual tuning, but that's why we managed to get everything just in a matter of of week, not months.
00:38:19.524 --> 00:38:21.815
Right, right, Sure, and it looks pretty good.
00:38:21.815 --> 00:38:25.281
I think it's better than we could afford.
00:38:25.281 --> 00:38:28.940
So that's actually well, some kind of spoiler.
00:38:28.940 --> 00:38:40.764
Another idea I keep for this year we want to release a few internal Rails apps over the year showcasing different.
00:38:40.764 --> 00:38:45.638
I just want to release, I just want to open source some stuff I work on.
00:38:45.638 --> 00:38:52.757
I think for me it's just a burden when I work on some private repository for the company.
00:38:52.757 --> 00:38:55.183
So we have the CFP app, have some internal.
00:38:55.183 --> 00:39:02.154
We have AnyCable Plus app, which is our managed AnyCable solution, and actually we want to open source it as well.
00:39:02.154 --> 00:39:05.655
Maybe part of it Because why not?
00:39:08.182 --> 00:39:16.295
I want to share some code I wrote for that, for example, I share it in the blog post or in the talk, but I can't send the link, for example.
00:39:16.295 --> 00:39:19.449
So I just can't resist that.
00:39:19.449 --> 00:39:24.862
I don't want it to be hidden inside our tiny world.
00:39:24.862 --> 00:39:44.670
So and that's probably going to be serious of open source projects with some blog posts, of course, but we're going to just tell them oh, that's how we do form wizards, for example that's a code you can run and try, or that's how we style emails or configure queue components or whatever.
00:39:45.070 --> 00:39:51.641
So those apps are tiny, but they all have some cool ideas I would like to share.
00:39:51.641 --> 00:39:53.364
We'll see, we'll see.
00:39:53.364 --> 00:39:54.935
So that's the plans.
00:39:54.935 --> 00:39:58.629
That's actually part of my job as a principal engineer.
00:39:58.629 --> 00:40:58.422
I need to think about spreading the word, increasing awareness of what we're doing, what we can, and just continuously remind the community engineers that we are here on this planet.
00:40:59.563 --> 00:41:09.574
You briefly talked, or at least mentioned, some blockers, and that is the next portion of the show is when I would normally say what are blockers that you have?
00:41:09.574 --> 00:41:49.536
So you've briefly touched on a little bit of them, but is there one in particular that you currently have that's interesting to talk about or maybe work through, or one that you've recently had that you've already solved and we can talk about how you went about solving it, like what went on to go from I'm blocked to I'm unblocked in general, my primary blocker is time, yeah sure, and destruction sure, everyone's blocker is time, and that's actually something that we can talk about a little bit is how do you organize your time, because you have quite a bit on your plate and you're a principal engineer.
00:41:49.556 --> 00:41:58.081
You've been doing this for long enough that you've come up with your own ways of handling ongoing projects and a lot of different projects.
00:41:58.081 --> 00:42:05.025
But how do you handle managing your time when you have this many things on your plate concurrently?
00:42:06.306 --> 00:42:10.074
Well, sometimes it's just working after hours.
00:42:10.074 --> 00:42:17.777
Sure, it's not just working after hours, it's working when you're mostly capable of achieving the results.
00:42:17.777 --> 00:42:23.337
So for me, it's usually early in the mornings because I have to wake up early.
00:42:23.337 --> 00:42:25.913
We have a team in Europe and Japan.
00:42:25.913 --> 00:42:27.748
Japan is actually more important.
00:42:28.168 --> 00:42:42.894
I have to wake up at 7 am to attend some calls, so people in Japan can not wait till the very night, and that's what productivity sparks and I try to do some focused work this time.
00:42:42.894 --> 00:42:55.717
And then another productivity segment is actually closer to the night, and that's when everyone has stopped working and I can just be sure that no one's going to bother me.
00:42:55.717 --> 00:43:00.974
So I would say it's more about distributing work and effort.
00:43:00.974 --> 00:43:07.931
So if I know that, okay, it's middle of the day, it's sun outside, I'm not going to work on anything, I just want to.
00:43:07.931 --> 00:43:23.831
I just want to hang out with family, take a walk, listen to something, read the book, because I know if I start,
if I have no desire to sit at my desk and stare at the laptop, I'm just not going to do that.
00:43:24.192 --> 00:43:32.974
So I better wait for this moment to come and then I sit and work and it's really efficient.
00:43:32.974 --> 00:43:39.358
So I think it started six years ago when I was my parental leave first time.
00:43:39.358 --> 00:43:42.626
I expected, okay, I'm not gonna have time for anything now.
00:43:42.626 --> 00:43:46.233
Right, I have a small human, where is that?
00:43:46.233 --> 00:43:48.998
And I can't just leave it on their own.
00:43:48.998 --> 00:43:52.105
And and I can't just leave it on their own.
00:43:52.105 --> 00:43:56.384
And it turned out that distribution of work time and do not even try to work time.
00:43:56.384 --> 00:44:04.295
That's when it appeared and it turned out to be more productive than just, okay, I have this nine to six work day.
00:44:04.295 --> 00:44:06.893
I'm going to try to fill it with useful stuff.
00:44:06.893 --> 00:44:12.831
But if you try to fill it, maybe we would think about okay, I need to fill it with useful stuff.
00:44:12.831 --> 00:44:13.675
That's doing something wrong.
00:44:13.675 --> 00:44:16.186
You just need to do that when the moment comes.
00:44:17.367 --> 00:44:43.914
And for me, of course, I've been working remotely for the last 10 years and without a strict schedule like working hours, so it was natural just to go and sit and park and start coding because oh, okay, I know how to solve this problem and then again just spend two hours and do nothing If I have a blocker and I have no idea how to overcome it, I just let it go, let it stay.
00:44:43.914 --> 00:44:45.878
Maybe someday later I will come to that.
00:44:45.878 --> 00:44:56.509
And given that I mostly work open source stuff and that's where I see blockers, because when I work on projects usually I don't have blockers, I just all I need is time.
00:44:56.509 --> 00:45:06.614
But for all this open source, like VASM challenges, there are a lot of blockers appears, but I just keep them somewhere on the surface of the mind.
00:45:06.614 --> 00:45:14.849
So I think about it all the time, even if I'm not doing any work, and at some point, okay, if I have an idea worth trying, I just sit and try.
00:45:15.291 --> 00:45:18.427
But I'm not staring at a blank page when I have no idea.
00:45:18.427 --> 00:45:21.030
When I have a blank page, I only know how I'm going to fill it.
00:45:21.030 --> 00:45:24.108
So that's the process.
00:45:24.108 --> 00:45:35.233
And actually, speaking of the blockers, right now I have one related to the Rails weapon, boson, which I haven't yet figured out, and that's why I haven't started working on that.
00:45:35.233 --> 00:45:44.808
There is one gem that Rails depends on, that's been causing issues to many developers, and it starts with N.
00:45:44.808 --> 00:45:49.494
You probably know the name of this gem Nokogiri yes.
00:45:49.976 --> 00:45:50.684
Yeah, okay.
00:45:50.610 --> 00:45:51.547
I
was going to say, if it's a major gem that starts with N, it's Nokogiri.
00:45:51.547 --> 00:45:53.471
Yes, yeah, okay, I was going to say if it's a major gem that starts with N.
00:45:53.512 --> 00:46:02.628
it's probably Nokogiri yeah so unfortunately right now I don't know how to make it work on RASM.
00:46:02.628 --> 00:46:08.125
So the Nokogiri C extension, at least as far as I know it's not compilable to RASM.
00:46:08.125 --> 00:46:11.715
It requires some C coding probably to make it work.
00:46:11.715 --> 00:46:17.157
I'm pretty sure it's doable, but my level of my C knowledge is not enough.
00:46:17.157 --> 00:46:23.335
I don't want to waste time on that because that's the kind of work when I don't know what's going to be the result.
00:46:23.335 --> 00:46:24.650
I try to avoid that.
00:46:24.650 --> 00:46:26.070
I try to explore other options.
00:46:26.744 --> 00:46:31.985
But at this point we have an action text part in the Rails tutorial options.
00:46:31.985 --> 00:46:34.308
But at this point we have an action text part in the Rails tutorial.
00:46:34.308 --> 00:46:42.485
Action text depends on Nakagiri for parsing HTML and unwrapping attachables and I don't know how to make it work.
00:46:42.485 --> 00:46:46.052
I already made one attempt to solve this problem.
00:46:46.052 --> 00:46:51.701
I found pure Ruby Jam that does HTML parsing and transformation.
00:46:51.701 --> 00:46:53.110
It's kind of abundant.
00:46:53.110 --> 00:46:55.492
I updated it to modern Ruby version.
00:46:55.492 --> 00:47:05.117
It kind of works, but it's not like API compatible with Nakagiri and I managed to make it probably 70, 80% work.
00:47:05.344 --> 00:47:10.853
Extra text work with this Jam, but it's always the last 20% that's most difficult.
00:47:10.853 --> 00:47:17.911
So I just stopped and that's another probably way of managing time.
00:47:17.911 --> 00:47:24.528
I agreed with myself so that I have two hours to try this approach.
00:47:24.528 --> 00:47:33.967
If I'm not going to make it work or see the light in the end of the tunnel that I'll just stop it here.
00:47:33.967 --> 00:47:35.009
I'm not wasting my time on that anymore.
00:47:35.009 --> 00:47:40.570
Maybe next time maybe I'm gonna ask some of my effect engineers who in between projects to do that.
00:47:40.570 --> 00:47:44.822
But that's where I'm at right now and I don't know.
00:47:44.822 --> 00:47:45.704
I'm gonna do that.
00:47:45.704 --> 00:47:50.592
Well, we still have a month to rails conference to solve this problem and I always have a plan B.
00:47:50.592 --> 00:47:59.708
Oh, if I'm not going to solve the action text problem, that's going to be a few slides and my talk.
00:47:59.708 --> 00:48:01.380
Oh, the problems we have and they are not solvable yet.
00:48:01.380 --> 00:48:01.784
Oh, action text.
00:48:02.485 --> 00:48:05.474
And we're just going to skip this part of the tutorial Not a big deal.
00:48:05.474 --> 00:48:09.255
So yeah, that's an example of actually blocker.
00:48:09.255 --> 00:48:10.307
That kind of bothers me.
00:48:10.307 --> 00:48:14.358
I always think, I keep it in mind but still haven't had a solution.
00:48:14.358 --> 00:48:27.434
I'm thinking, actually, when Mark Roth announced his new herb project, which is a ERP parser, whatever an HTML parser, I started thinking maybe that's the way to go.
00:48:27.434 --> 00:48:33.230
Maybe we should just make action text, not Kagiri less, but use like herb instead.
00:48:33.230 --> 00:48:47.712
So I have some ideas to try, but I just let this blocker itch me from the inside to the point that I either give up and just throw it away completely or I find a cure right.
00:48:47.712 --> 00:48:53.411
So right now I don't have the answer to this problem, but that's going to be interesting, I think.
00:48:53.411 --> 00:48:53.773
Maybe.
00:48:54.404 --> 00:48:58.536
It doesn't solve the problem of solving it before RailsConf.
00:48:58.536 --> 00:49:04.373
But worst case scenario, if you do show up at RailsConf, going well, we don't have action text working, but everything else does.
00:49:04.373 --> 00:49:08.967
I'm pretty sure Mike D'Alessio and Aaron Patterson will be at the last RailsConf.
00:49:08.967 --> 00:49:14.155
You can just say, hey, any thoughts of making Nokogiri WASM compatible?
00:49:14.155 --> 00:49:20.572
Maybe they'll be like, yeah, well, I don't know, They've been working on that gem forever and a day, so they probably know the ins and outs.
00:49:20.764 --> 00:49:22.010
Well, actually I don't even know.
00:49:22.010 --> 00:49:27.206
Maybe it's actually WASM compatible, but it's not just easier to compile, I don't know Well.
00:49:27.206 --> 00:49:38.625
Well, the whole building pipeline for ruby vasm is just a black box for me, because when you like, try to compile vas model including your dependencies and c extensions.
00:49:38.625 --> 00:49:41.096
Some extensions are compilable, some not.
00:49:41.096 --> 00:49:41.818
I don't know why.
00:49:41.818 --> 00:49:48.333
I don't know what's happening on the hood, because there's a lot of commands, like with some compilers, tons of flags.
00:49:48.333 --> 00:50:01.099
I don't know how to do that, and maybe someone smarter than me will eventually make it less tricky, because we want Ruby Wasm to be.
00:50:01.099 --> 00:50:23.757
There is a concept of component model and Wasm when you can actually compile dependencies independently and then stitch them together into a single WASM module or even load independently into the runtime and connect to each other through the interfaces, and that should solve the problem of having everything compiled separately.
00:50:23.757 --> 00:50:29.454
Probably that will simplify the flow, but I'm not there to just contribute to that.
00:50:29.454 --> 00:50:30.117
Unfortunately.
00:50:30.117 --> 00:50:37.572
That would require a lot of time just to learn how things work, even in the age of AI everywhere.
00:50:37.572 --> 00:50:40.579
I'm not sure it's going to be
helpful for me.
00:50:40.579 --> 00:50:43.293
You need to learn a lot of stuff for that.
00:50:43.293 --> 00:50:46.012
Speaking of blockers and I started talking about this.
00:50:46.012 --> 00:50:55.983
I want to share one interesting blocker we had at the project actually where we managed, I think, to find a solution and I think it could be useful.
00:50:55.983 --> 00:50:59.795
Maybe it's kind of relevant to many Rails projects.
00:50:59.795 --> 00:51:11.735
So we have a client with well, it's a pretty large Rails application and we help him with performance issues and that's the performance issues of this, to give you an idea, idea what we're trying to do.
00:51:11.735 --> 00:51:24.427
So we're trying to tune Garbage Collector at the level where we fight for every dozen of milliseconds of latency, so it's not just M plus ones and all that stuff.
00:51:24.427 --> 00:51:26.855
So it's more about at the VM level.
00:51:27.985 --> 00:51:36.271
And right now we're exploring switching from Puma to Pitchfork, which is Shopify's web server.
00:51:36.271 --> 00:52:02.416
We expect it to give us a better utilization of resources and better results in terms of latency, first of all because we don't really like threads that are not good for latency, especially like B95 and so on, so they affect that because, well, we have this chill, so we want to go all in with processes, but we want processes to fork and share memory efficiently, and that's where pitchfork is coming from.
00:52:02.416 --> 00:52:22.346
And we found that for typical rails application like modern, it's not possible to use pitchfork due to the vips, leap, vips dependency, because it's not kind of fork safe, so it runs a lot of c threads internally and they're not forkable.
00:52:22.346 --> 00:52:25.471
And that's was the blocker.
00:52:25.471 --> 00:52:33.637
For us to give pitchfork a try, or the same new as a kind of Moldfork, I don't know what is it.
00:52:33.637 --> 00:52:40.052
Okay, that's again something I haven't touched myself, just my teammates.
00:52:40.666 --> 00:52:43.045
But we were thinking about okay, how can we simplify the problem?
00:52:43.045 --> 00:53:05.451
If you have a Ruby process with Sleepweeps running and doing some processing and then you want to fork it and continue using it as a web server, the WIP's integration is going to be corrupted the one that was in the original fork and in the new fork there is some problem at the C-level, so we cannot really fork it.
00:53:05.451 --> 00:53:10.309
You just need to kill the process and spawn a new one, but you cannot refork.
00:53:10.309 --> 00:53:11.771
So refork is not possible.
00:53:11.771 --> 00:53:17.331
And refork is important because we can share as much memory as possible.
00:53:17.331 --> 00:53:20.275
So we don't need to and not just share memory.
00:53:20.275 --> 00:53:25.291
There is no like warming up memory stage, so latency is not increasing when you refork.
00:53:25.291 --> 00:53:28.994
And we were trying to think okay, what do we do?
00:53:28.994 --> 00:53:30.447
We can fix WIPs.
00:53:30.447 --> 00:53:47.996
But we found that actually Jean Bousiel already approached WIPs offers, mentioned this problem and they were discussing it, and it turned out that it's much trickier than it seems because there are a lot of non-shareable resources and at the WIPs level there is no just easy way to do that.
00:53:47.996 --> 00:53:54.335
And now we came up with the idea and my team is going to implement it and see if it's going to work.
00:53:55.065 --> 00:53:59.445
But that's actually the beauty of again, the Ruby openness and Rails openness.
00:53:59.445 --> 00:54:04.471
So we have an image processing gem that uses libvips through native extensions.
00:54:04.471 --> 00:54:15.333
But technically, image processing has just a few APIs that are called by active storage to transform images or get some information.
00:54:15.333 --> 00:54:30.206
What we can do instead of calling directly the C extension, we can put this tiny Ruby daemon with VEAPs running into a separate process and communicate with it through GRB, for example.
00:54:30.206 --> 00:54:40.695
And just generating a new adapter for image processing is going to be not just VEPS but VEPS daemon, and in this case we don't need to fork the VEPS process.
00:54:40.695 --> 00:54:50.306
It's going to be just running every time and we can fork the Rails process and refork is going to work because we don't have VEPS loaded anymore.
00:54:50.306 --> 00:54:54.672
That's what we're trying to achieve and that's actually similar to what I do for Basm.
00:54:55.166 --> 00:55:31.733
If something doesn't work, we go layer by layer from the implementation to the Rails and find the layer that we can hijack, inject our implementation, keep the API compatibility and just instead of weeps, for example, in the browser, if we want to have image processing work in the browser, which is I don't know if we want, but anyway for Rails we can just, instead of calling T extension or internal process, we can just call WIPs compiled into VASM and running in the browser outside of the Rails VASM through the JavaScript interface and that's going to work.
00:55:31.733 --> 00:55:53.409
So that's the kind of thing that we can do when a language is open, like runtime is open, right, ruby is open and B the framework is kind of well-architectured in terms of high coupling between implementations because Rails is not coupled In most places.
00:55:53.409 --> 00:56:04.755
We have layers in Rails, naturally, because most Rails abstractions are pure Ruby abstractions, and then we go down to the actual implementation and this combination.
00:56:04.755 --> 00:56:09.114
That's what makes it possible to do many things with Rails.
00:56:09.114 --> 00:56:12.266
On VASM, not on VASM, the same idea applied.
00:56:12.266 --> 00:56:19.791
Something we learned from dealing with VASM was applied to production application on regular Rails.
00:56:19.791
--> 00:56:25.016
So that's just the same idea, the concept which we ported there.
00:56:25.721 --> 00:56:26.567
I'm not sure it's going to work.
00:56:26.567 --> 00:56:29.168
If it's going to work, we're probably going to write about it because it's cool.
00:56:29.168 --> 00:56:29.811
That's very cool.
00:56:29.811 --> 00:56:39.032
That's why why coming back to the fact that I mentioned about Laravel, so why we go into that direction?
00:56:39.032 --> 00:56:47.119
Because we want to try new things, try to see how our tool, our software, works in a new environment.
00:56:47.119 --> 00:56:54.313
Probably we're going to find some problems that could later be ported back to Rails to solve similar problems, right?
00:56:54.313 --> 00:57:13.353
So that's like traveling across the world and learning from different cultures and then accumulating the best parts, or trying to reuse someone else's knowledge to solve your particular problem, because you can see someone else's or whatever, and that could be done in software as well.
00:57:14.045 --> 00:57:14.505
That's awesome.
00:57:14.505 --> 00:57:20.311
That's an awesome way of figuring out your blocker and sharing those learnings from.
00:57:20.311 --> 00:57:27.951
I don't want to call the Rails on Wasm project like a toy project, but this is not client work.
00:57:27.951 --> 00:57:30.277
This is not your primary job.
00:57:30.277 --> 00:57:50.414
This is something you're doing for a conference talk, but it's giving you those learnings that are helping you solve a real client problem and that's the best when you are like I got myself unblocked and I've learned this new way of doing it and now we've got this whole new way of solving a problem that we were completely stuck on before.
00:57:51.545 --> 00:58:06.394
And I think that's actually an important aspect of learning and why we should continue learning and not just orchestrating AIs and whatever, because it's not important that I have learned how to do some crazy stuff as Rails and VASP.
00:58:06.394 --> 00:58:12.846
It's important that I learn the technique right and that kind of a critical thinking.
00:58:12.846 --> 00:58:19.065
So that's why important actually to learn even like abstract things like mathematics.
00:58:19.065 --> 00:58:25.543
I learned a lot of stuff that I never gonna use in my life right, who cares about that?
00:58:25.543 --> 00:58:34.259
But I learned how to solve abstract problems and the technique I learned I could apply to real-world problems, and the same here.
00:58:34.259 --> 00:58:50.817
When you solve in one problem, what's important is the experience of something that's left not in the code but here in your mind, and that's what we should aim for, I think, as engineers.
00:58:51.887 --> 00:58:53.534
I can agree with that wholeheartedly.
00:58:53.534 --> 00:59:00.733
The last question is going to be a really tough one, because you have talked about so much cool stuff.
00:59:00.733 --> 00:59:09.376
So much cool stuff that
borders on new too, like I have heard of the Ruby Wasm.
00:59:09.376 --> 00:59:13.155
I knew about your talk because I'm on the programming committee.
00:59:13.155 --> 00:59:32.614
It's not terribly new, but there's probably a fair amount of people who are listening to this going wait, you can do what in who with the what, but because the question does not require it to be coding related, but it can be, I'm going to ask it anyway and you can take a minute to think about it if you'd like.
00:59:32.614 --> 00:59:39.275
But what is something cool, new or interesting that you've recently learned, discovered could have been built?
00:59:39.275 --> 00:59:42.905
Doesn't have to be coding related, but it can be just.
00:59:42.905 --> 00:59:45.625
What is something that you want to share that you're just like.
00:59:45.625 --> 00:59:53.057
This is cool and made me excited and I want to share it A few weeks ago I attended a large BriggsCon.
00:59:53.317 --> 01:00:08.454
It's called Briggs Cascade, it's like LegoCon in Portland, oregon, and I was born and raised in Russia and we had Lego years after everyone in the world had it and we just had a few stores in the country and so on.
01:00:08.454 --> 01:00:14.938
But attending an event and seeing that people doing cool stuff actually.
01:00:14.938 --> 01:00:17.393
So there are different kinds of people.
01:00:17.393 --> 01:00:30.157
Like someone preserving old collections you can see Lego from the 70s, 80s, 90s, from your childhood and someone just building huge installations with a lot of stuff.
01:00:30.157 --> 01:00:35.677
And that's something that was new for me because, well, I've never seen anything like that.
01:00:35.784 --> 01:00:43.134
I'm not attending any conventions, except for Ruby and Rails conventions, right, but that's a different kind of hobby.
01:00:43.134 --> 01:00:55.666
I don't think it's a hobby actually for them because I take a lot of time, but that's the way of living with this technology idea, whatever.
01:00:55.666 --> 01:01:14.706
Like passion, I've seen people passionate about Lego bricks as something new to me because like, wow, it's a bit of envy because, well, I could not afford dealing with, like building a million pieces, copy of some building in Lego or whatever, but it's really cool to see people doing that.
01:01:14.706 --> 01:01:17.233
They're not doing that for money, obviously, right.
01:01:17.233 --> 01:01:25.375
They're doing that because they love that and that's always cool to see people enjoying what they're doing, right?
01:01:25.375 --> 01:01:30.070
Yeah, I can't say that about myself all the time, right?
01:01:30.070 --> 01:01:31.773
Any software engineer, engineer?
01:01:31.773 --> 01:01:34.699
I don't think a lot of people enjoy that, to be honest.
01:01:34.699 --> 01:01:41.297
So seeing that there is another way of enjoying what you're doing is cool.
01:01:41.677 --> 01:01:42.099
I'm with you.
01:01:42.099 --> 01:01:53.538
Yeah, as a kid who grew up with Legos, I can confirm they are awesome and fun and probably influenced my decision to become a developer.
01:01:53.538 --> 01:02:07.032
There's a lot of parallels between you're just taking a bunch of bricks and building something by layering on on top of one another, and so I've never been to a Lego convention, but it's always been on my list of like.
01:02:07.032 --> 01:02:12.454
That would actually be kind of cool to go just because I've seen pictures, but seeing it in real life is always better.
01:02:12.454 --> 01:02:21.195
Of some of the stuff these guys can do with legos is like I've been playing with legos for over 30 years now well, over, holy crap.
01:02:21.195 --> 01:02:22.686
I'm not gonna do that math.
01:02:23.286 --> 01:02:35.949
I don't think I could do that, and these guys are building huge and I think it was even better than legoland, for me at least, maybe not, maybe not for kids, because we also went to Legoland this year with my son.
01:02:35.949 --> 01:02:40.451
It was cool oh, I guess something you saw on TV when he was fighting.
01:02:40.451 --> 01:02:48.853
Now you're there, but the convention is just different and we actually have one big coming to Seattle in September.
01:02:48.853 --> 01:02:51.570
I guess it's one of the largest in the States.
01:02:51.570 --> 01:02:55.724
So I would definitely recommend checking that kind of events locally.
01:02:55.724 --> 01:03:01.523
Yeah for sure, just to hang out, just to shift the environment, to see something different.
01:03:01.543 --> 01:03:07.853
Building a Lego set feels a lot like building software, but it's much more tangible and you can probably learn from that.
01:03:08.505 --> 01:03:10.152
Now, when you know both, you can see how people build.
01:03:10.152 --> 01:03:16.387
Now, when you know Buff, you can see how people build Legos and you can say oh wait, I can structure my application like that.
01:03:16.750 --> 01:03:18.367
That's going to work, why not?
01:03:18.547 --> 01:03:24.851
I can't imagine that as parallel universes, they all work by the same rules, actually under the hood.
01:03:24.851 --> 01:03:29.152
Fundamentally, we just need to dig deeper to find this.
01:03:29.344 --> 01:03:31.452
Yeah, there's a lot of overlap in places.
01:03:31.452 --> 01:03:36.125
It all comes back to like you were saying with mathematics, like that joy of problem solving.
01:03:36.125 --> 01:03:42.724
Yeah, that I think a lot of developers have just like this joy of solving the problem, figuring it out.
01:03:42.724 --> 01:03:47.010
That is not unique at all to software engineering.
01:03:47.010 --> 01:03:48.293
That goes everywhere.
01:03:48.293 --> 01:03:59.846
So you can practice your software engineering skills by getting better at problem solving, by doing other things, so that you're not burning yourself out.
01:04:00.626 --> 01:04:09.494
Oh, I just worked 10 hours on my work project and now I'm going to work another five on my personal project and then the next day not want to look at code ever again.
01:04:09.494 --> 01:04:25.576
Like you can say, I'm going to go build a Lego set and still be helping your brain figure out how to be a better problem solver, a better builder, better at thinking through layers of abstractions without actually continuing to stare at a screen or code.
01:04:25.576 --> 01:04:28.494
I think that's a good one, very cool.
01:04:28.494 --> 01:04:36.277
So where can people find you and all of your projects and all of the cool things you work on on the internet?
01:04:36.277 --> 01:04:37.971
Where is the best way to connect with you?
01:04:38.905 --> 01:04:42.271
I'm on GitHub mostly, so that's the browser tab.
01:04:42.271 --> 01:04:45.751
I have all the software and that's my social network.
01:04:45.751 --> 01:04:48.974
That's what I communicate the most and social coding.
01:04:48.974 --> 01:04:59.583
I post some stuff on Twitter and evilmartianscom, so, where we have also other announcements and stuff coming on, I think it's just free primary.
01:05:00.628 --> 01:05:05.250
Yeah, I'll put your links to your github, your twitter, evilmartians.
01:05:05.250 --> 01:05:11.059
I'll put a link to SFRuby's meetup and the conference all in the show notes.
01:05:11.059 --> 01:05:17.052
So if anybody was inspired after listening to the episode, check out the show notes and you'll find all the links there.
01:05:17.052 --> 01:05:18.769
It was awesome having you on.
01:05:18.769 --> 01:05:34.489
I feel like we could have talked for another hour on all the things that you're working on, so we'll have to have you on again, maybe a little closer to the San Francisco conference and we can talk a little bit about the conference actually yeah, there you go.
01:05:35.032 --> 01:05:41.036
We'll talk about some of the cool things you learned during that whole process, but thanks for coming on.
01:05:41.056 --> 01:05:51.074
I really appreciate you taking time out of the day, great, great talking to you, great conversation hopefully I'll see you at the last rails, conf and listeners, hopefully I will see you there too.
01:05:51.074 --> 01:05:55.420
Tickets are still on sale even as this episode is coming out.
01:05:55.420 --> 01:06:07.637
You should definitely come to Philly, have a bang and cheese steak with me, and Andrew Mason and Chris Oliver and everybody else in the community hope to see you there and we'll see you in the next episode.
01:06:07.637 --> 01:06:08.978
Bye.