text stringlengths 0 2.35k |
|---|
• Possibility of invoking Golang from PHP to perform complex tasks like machine learning comparisons |
• Process manager issues with PHP, including crashing and requiring correct parameters |
• Managing dependencies and plugins for HTTP endpoint integration with RabbitMQ |
• Difficulty in solving integrational hell between plugins and Roadrunner |
• Creation of a container to solve these problems and provide a framework for application servers |
• Isolation methods for processes running within the same system, including permission models and user groups |
• Multi-tenancy approach and how to implement it on the application design level |
• Roadrunner's design and functionality in a Docker or container-based environment |
• Developing an algorithmic container that can mutate based on configuration |
• Dependency injection and managing connections between plugins |
• Implementing topological sorting to ensure proper initialization and configuration of plugins |
• Managing race conditions in a distributed environment using GoLang |
• Designing a protocol (Gorich) for communicating with PHP parts, including IP protocol and variable length options |
• Creating worker pools for handling tasks and statistics collection |
• Developing a scheduler for scheduling jobs inside the Roadrunner |
• Implementing binary HIPs algorithm to sort jobs by priorities |
• Complexity and challenges in creating user-friendly APIs |
• The importance of abstraction to hide complexity "under the hood" |
• Contributing to open-source projects, specifically Roadrunner |
• Requirements for contributing, including language expertise (PHP or GoLang) |
• Flexibility in contributions, allowing developers to focus on their area of expertise |
• Advertising for LaunchDarkly and FlatFile services |
• The speaker discusses the challenges of optimizing software performance, particularly with 64KB stack limits. |
• They highlight how modern computing has made certain hardware considerations less important, allowing for more scalable applications. |
• The conversation turns to open-source development, and the speaker shares their experiences with users who don't provide sufficient information or testing when submitting issues. |
• He emphasizes the complexity of working in open-source, citing the need to handle multiple virtual machines, operating systems, and versions. |
• The speaker also touches on the difficulty of debugging code due to user misunderstandings and lack of clear problem descriptions. |
• Requests for future podcast episodes and submissions |
• Thanking sponsors and contributors |
• Discussion of the previous episode's guest, Frank Kruger, and his practical guide to solving hard problems |
• The host's experience of finding a solution to a complex problem in an old resource (the Dragon Book) |
• Metaphors for learning and understanding complex concepts (e.g. "standing on the shoulder of giants", "becoming a wizard") |
• Promotion of the next episode in the maintenance series |
[0.00 --> 3.76] But if you also know Golang, you can do even crazier stuff. |
[3.98 --> 8.30] Like you can take, for example, machine learning model from Keras, compress it, put it into |
[8.30 --> 12.44] the Golang SDK, and then invoke from PHP, and ta-dum, you now have machine learning |
[12.44 --> 14.68] embedded directly into PHP via Golang Bridge. |
[15.12 --> 19.14] So you can do these crazy things if you know multiple languages, specifically Golang. |
[19.28 --> 22.02] Golang is beautiful because it's quite easy to learn it, right? |
[22.04 --> 26.18] It doesn't have many of these legacy overhead and nuances you have to remember. |
[26.18 --> 31.00] So it's not required, but if you do, well, you're essentially a superhero in PHP world. |
[35.08 --> 38.70] This episode is brought to you by our friends at Sourcegraph. |
[38.80 --> 41.38] They recently launched a new feature called Code Insights. |
[41.70 --> 45.12] Now you can track what really matters to you and your team in your code base, transform |
[45.12 --> 49.38] your code into a querable database to create customizable visual dashboards in seconds. |
[49.78 --> 52.66] Here's how engineering teams are using Code Insights. |
[52.66 --> 56.88] They can track migrations, adoption, and deprecation across the code base. |
[57.14 --> 60.36] They can detect and track versions of languages or packages. |
[60.78 --> 64.18] They can ensure the removal of security vulnerabilities like Log4j. |
[64.46 --> 69.74] They can understand code by team, track code smells and health, and visualize configurations |
[69.74 --> 70.72] and services. |
[71.30 --> 73.88] Here's what the engineering manager at Prezi has to say about this new feature. |
[74.30 --> 74.40] Quote, |
[74.40 --> 99.24] The next step is to see how other teams are using this awesome feature. |
[99.24 --> 104.38] Head to about.sourcegraph.com slash code dash insights. |
[104.62 --> 106.12] This link will be in the show notes. |
[106.24 --> 110.98] Again, about.sourcegraph.com slash code dash insights. |
[125.62 --> 126.60] Let's do it. |
[127.16 --> 128.22] It's go time. |
[128.22 --> 130.52] Welcome to go time. |
[130.78 --> 133.74] Your source for diverse discussions from around the go community. |
[134.14 --> 136.60] We record live on Tuesdays at 3 p.m. |
[136.68 --> 137.00] U.S. |
[137.02 --> 137.68] Eastern time. |
[137.96 --> 141.72] Subscribe at youtube.com slash changelog so you don't miss it. |
[141.92 --> 144.62] And don't forget to follow the show on Twitter at go time FM. |
[144.94 --> 149.44] Special thanks to our partners at Fastly for shipping our shows super fast to wherever you |
[149.44 --> 149.76] listen. |
[150.02 --> 151.94] Check them out at fastly.com. |
[152.18 --> 153.38] Okay, here we go. |
[158.22 --> 163.18] Welcome to this episode of go time everyone. |
[163.18 --> 165.12] Glad to have you back. |
[165.62 --> 170.64] So, go and PHP sitting in a tree. |
[171.36 --> 175.70] I don't know there's, you know, kissing going on, but we're going to figure out why go and |
[175.70 --> 179.32] PHP are together on this particular episode. |
[179.32 --> 183.24] Because last time I touched PHP was many years ago. |
[183.24 --> 187.66] And although it has it had its charms, it did have some quirks as well. |
[187.66 --> 190.12] And we may touch on those during this episode. |
[190.12 --> 197.68] But joining me today are two folks who actually work with go and PHP on a regular basis. |
[197.68 --> 199.64] And that got us curious. |
[199.90 --> 202.30] Actually, someone actually suggested this episode. |
[202.54 --> 203.56] I believe. |
[203.68 --> 204.86] Let me, let me look up there. |
[204.86 --> 210.34] Oh, I will find who it was and give them a shout out for suggesting this episode. |
[210.34 --> 219.74] Shout out to listener Seb for requesting this episode and putting Roadrunner and PHP on our |
[219.74 --> 220.04] radar. |
[220.56 --> 221.08] Thanks, Seb. |
[223.84 --> 227.64] And they actually recommended Roadrunner, which is a project we'll definitely be touching on |
[227.64 --> 231.56] by name as an example of go and PHP working well together. |
[231.84 --> 239.92] So, joining me today are two guests, Mr. Valerie, and I'm going to butcher your last name, Piacchansky |
[239.92 --> 241.14] Did I get that right? |
[241.88 --> 242.38] Close enough. |
[244.18 --> 247.00] And then also Anton Titov. |
[247.10 --> 248.10] Hopefully I got that right. |
[248.20 --> 248.88] Yeah, that's correct. |
[249.18 --> 249.72] Nice to meet you. |
[249.94 --> 250.16] Okay. |
[250.80 --> 256.18] So, Valerie is a software developer at Spiral Scout, the team that works on Roadrunner, |
[256.26 --> 258.12] the particular project that we'll be touching on. |
[258.34 --> 263.34] He enjoys working on algorithms, writing his own operating system for learning purposes in |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.