POPULARITY
Categories
1,092 episodes with WP
79 episodes with WP
52 episodes with WP
45 episodes with WP
28 episodes with WP
19 episodes with WP
16 episodes with WP
16 episodes with WP
11 episodes with WP
13 episodes with WP
7 episodes with WP
21 episodes with WP
10 episodes with WP
8 episodes with WP
6 episodes with WP
7 episodes with WP
12 episodes with WP
12 episodes with WP
8 episodes with WP
125 episodes with WP
9 episodes with WP
4 episodes with WP
22 episodes with WP
5 episodes with WP
11 episodes with WP
12 episodes with WP
7 episodes with WP
6 episodes with WP
8 episodes with WP
6 episodes with WP
4 episodes with WP
4 episodes with WP
5 episodes with WP
6 episodes with WP
5 episodes with WP
5 episodes with WP
4 episodes with WP
5 episodes with WP
3 episodes with WP
7 episodes with WP
3 episodes with WP
8 episodes with WP
6 episodes with WP
2 episodes with WP
2 episodes with WP
16 episodes with WP
3 episodes with WP
3 episodes with WP
4 episodes with WP
2 episodes with WP
2 episodes with WP
3 episodes with WP
6 episodes with WP
2 episodes with WP
In this WP Builds episode, I chat with Remkus de Vries and dive into website optimisation. Remkus, co-founder of Scanfully, a site health monitoring tool, shares his expertise on caching strategies, optimal hosting, and addressing plugin inefficiencies. He emphasises the importance of integrating performance throughout the build process, not just at the end. Remkus also discusses the upcoming features for Scanfully and highlights useful optimisation tools like Code Profiler and Query Monitor. The conversation underscores that user experience and quick load times are crucial for site success. So join us and have a listen...
The WordPress news from the last week which commenced Monday 25th November 2024.
Pełnej wersji podcastu posłuchasz w aplikacji Onet Audio. [AUTOPROMOCJA] W tym odcinku podcastu „Raport Międzynarodowy” gościem Witolda Jurasza jest dr Witold Sokała. W rozmowie poruszane są między innymi następujące wątki: • Stan polskiej demokracji. • Wpływ polsko-polskiej wojny domowej na politykę zagraniczną. • Istota polskiego konfliktu politycznego. • Liberalne poczucie przynależności do elity. • Potencjalna poprawa skuteczności polityki, gdyby większą rolę odgrywały nowe elity.
The full schedule for Latent Space LIVE! at NeurIPS has been announced, featuring Best of 2024 overview talks for the AI Startup Landscape, Computer Vision, Open Models, Transformers Killers, Synthetic Data, Agents, and Scaling, and speakers from Sarah Guo of Conviction, Roboflow, AI2/Meta, Recursal/Together, HuggingFace, OpenHands and SemiAnalysis. Join us for the IRL event/Livestream! Alessio will also be holding a meetup at AWS Re:Invent in Las Vegas this Wednesday. See our new Events page for dates of AI Engineer Summit, Singapore, and World's Fair in 2025. LAST CALL for questions for our big 2024 recap episode! Submit questions and messages on Speakpipe here for a chance to appear on the show!When we first observed that GPT Wrappers are Good, Actually, we did not even have Bolt on our radar. Since we recorded our Anthropic episode discussing building Agents with the new Claude 3.5 Sonnet, Bolt.new (by Stackblitz) has easily cleared the $8m ARR bar, repeating and accelerating its initial $4m feat.There are very many AI code generators and VS Code forks out there, but Bolt probably broke through initially because of its incredible zero shot low effort app generation:But as we explain in the pod, Bolt also emphasized deploy (Netlify)/ backend (Supabase)/ fullstack capabilities on top of Stackblitz's existing WebContainer full-WASM-powered-developer-environment-in-the-browser tech. Since then, the team has been shipping like mad (with weekly office hours), with bugfixing, full screen, multi-device, long context, diff based edits (using speculative decoding like we covered in Inference, Fast and Slow).All of this has captured the imagination of low/no code builders like Greg Isenberg and many others on YouTube/TikTok/Reddit/X/Linkedin etc:Just as with Fireworks, our relationship with Bolt/Stackblitz goes a bit deeper than normal - swyx advised the launch and got a front row seat to this epic journey, as well as demoed it with Realtime Voice at the recent OpenAI Dev Day. So we are very proud to be the first/closest to tell the full open story of Bolt/Stackblitz!Flow Engineering + Qodo/AlphaCodium UpdateIn year 2 of the pod we have been on a roll getting former guests to return as guest cohosts (Harrison Chase, Aman Sanger, Jon Frankle), and it was a pleasure to catch Itamar Friedman back on the pod, giving us an update on all things Qodo and Testing Agents from our last catchup a year and a half ago:Qodo (they renamed in September) went viral in early January this year with AlphaCodium (paper here, code here) beating DeepMind's AlphaCode with high efficiency:With a simple problem solving code agent:* The first step is to have the model reason about the problem. They describe it using bullet points and focus on the goal, inputs, outputs, rules, constraints, and any other relevant details.* Then, they make the model reason about the public tests and come up with an explanation of why the input leads to that particular output. * The model generates two to three potential solutions in text and ranks them in terms of correctness, simplicity, and robustness. * Then, it generates more diverse tests for the problem, covering cases not part of the original public tests. * Iteratively, pick a solution, generate the code, and run it on a few test cases. * If the tests fail, improve the code and repeat the process until the code passes every test.swyx has previously written similar thoughts on types vs tests for putting bounds on program behavior, but AlphaCodium extends this to AI generated tests and code.More recently, Itamar has also shown that AlphaCodium's techniques also extend well to the o1 models:Making Flow Engineering a useful technique to improve code model performance on every model. This is something we see AI Engineers uniquely well positioned to do compared to ML Engineers/Researchers.Full Video PodcastLike and subscribe!Show Notes* Itamar* Qodo* First episode* Eric* Bolt* StackBlitz* Thinkster* AlphaCodium* WebContainersChapters* 00:00:00 Introductions & Updates* 00:06:01 Generic vs. Specific AI Agents* 00:07:40 Maintaining vs Creating with AI* 00:17:46 Human vs Agent Computer Interfaces* 00:20:15 Why Docker doesn't work for Bolt* 00:24:23 Creating Testing and Code Review Loops* 00:28:07 Bolt's Task Breakdown Flow* 00:31:04 AI in Complex Enterprise Environments* 00:41:43 AlphaCodium* 00:44:39 Strategies for Breaking Down Complex Tasks* 00:45:22 Building in Open Source* 00:50:35 Choosing a product as a founder* 00:59:03 Reflections on Bolt Success* 01:06:07 Building a B2C GTM* 01:18:11 AI Capabilities and Pricing Tiers* 01:20:28 What makes Bolt unique* 01:23:07 Future Growth and Product Development* 01:29:06 Competitive Landscape in AI Engineering* 01:30:01 Advice to Founders and Embracing AI* 01:32:20 Having a baby and completing an Iron ManTranscriptAlessio [00:00:00]: Hey everyone, welcome to the Latent Space Podcast. This is Alessio, partner and CTO at Decibel Partners, and I'm joined by my co-host Swyx, founder of Smol.ai.Swyx [00:00:12]: Hey, and today we're still in our sort of makeshift in-between studio, but we're very delighted to have a former returning guest host, Itamar. Welcome back.Itamar [00:00:21]: Great to be here after a year or more. Yeah, a year and a half.Swyx [00:00:24]: You're one of our earliest guests on Agents. Now you're CEO co-founder of Kodo. Right. Which has just been renamed. You also raised a $40 million Series A, and we can get caught up on everything, but we're also delighted to have our new guest, Eric. Welcome.Eric [00:00:42]: Thank you. Excited to be here. Should I say Bolt or StackBlitz?Swyx [00:00:45]: Like, is it like its own company now or?Eric [00:00:47]: Yeah. Bolt's definitely bolt.new. That's the thing that we're probably the most known for, I imagine, at this point.Swyx [00:00:54]: Which is ridiculous to say because you were working at StackBlitz for so long.Eric [00:00:57]: Yeah. I mean, within a week, we were doing like double the amount of traffic. And StackBlitz had been online for seven years, and we were like, what? But anyways, yeah. So we're StackBlitz, the company behind bolt.new. If you've heard of bolt.new, that's our stuff. Yeah.Swyx [00:01:12]: Yeah.Itamar [00:01:13]: Excellent. I see, by the way, that the founder mode, you need to know to capture opportunities. So kudos on doing that, right? You're working on some technology, and then suddenly you can exploit that to a new world. Yeah.Eric [00:01:24]: Totally. And I think, well, not to jump, but 100%, I mean, a couple of months ago, we had the idea for Bolt earlier this year, but we haven't really shared this too much publicly. But we actually had tried to build it with some of those state-of-the-art models back in January, February, you can kind of imagine which, and they just weren't good enough to actually do the code generation where the code was accurate and it was fast and whatever have you without a ton of like rag, but then there was like issues with that. So we put it on the shelf and then we got kind of a sneak peek of some of the new models that have come out in the past couple of months now. And so once we saw that, once we actually saw the code gen from it, we were like, oh my God, like, okay, we can build a product around this. And so that was really the impetus of us building the thing. But with that, it was StackBlitz, the core StackBlitz product the past seven years has been an IDE for developers. So the entire user experience flow we've built up just didn't make sense. And so when we kind of went out to build Bolt, we just thought, you know, if we were inventing our product today, what would the interface look like given what is now possible with the AI code gen? And so there's definitely a lot of conversations we had internally, but you know, just kind of when we logically laid it out, we were like, yeah, I think it makes sense to just greenfield a new thing and let's see what happens. If it works great, then we'll figure it out. If it doesn't work great, then it'll get deleted at some point. So that's kind of how it actually came to be.Swyx [00:02:49]: I'll mention your background a little bit. You were also founder of Thinkster before you started StackBlitz. So both of you are second time founders. Both of you have sort of re-founded your company recently. Yours was more of a rename. I think a slightly different direction as well. And then we can talk about both. Maybe just chronologically, should we get caught up on where Kodo is first and then you know, just like what people should know since the last pod? Sure.Itamar [00:03:12]: The last pod was two months after we launched and we basically had the vision that we talked about. The idea that software development is about specification, test and code, etc. We are more on the testing part as in essence, we think that if you solve testing, you solve software development. The beautiful chart that we'll put up on screen. And testing is a really big field, like there are many dimensions, unit testing, the level of the component, how big it is, how large it is. And then there is like different type of testing, is it regression or smoke or whatever. So back then we only had like one ID extension with unit tests as in focus. One and a half year later, first ID extension supports more type of testing as context aware. We index local, local repos, but also 10,000s of repos for Fortune 500 companies. We have another agent, another tool that is called, the pure agent is the open source and the commercial one is CodoMerge. And then we have another open source called CoverAgent, which is not yet a commercial product coming very soon. It's very impressive. It could be that already people are approving automated pull requests that they don't even aware in really big open sources. So once we have enough of these, we will also launch another agent. So for the first one and a half year, what we did is grew in our offering and mostly on the side of, does this code actually works, testing, code review, et cetera. And we believe that's the critical milestone that needs to be achieved to actually have the AI engineer for enterprise software. And then like for the first year was everything bottom up, getting to 1 million installation. 2024, that was 2023, 2024 was starting to monetize, to feel like how it is to make the first buck. So we did the teams offering, it went well with a thousand of teams, et cetera. And then we started like just a few months ago to do enterprise with everything you need, which is a lot of things that discussed in the last post that was just released by Codelm. So that's how we call it at Codelm. Just opening the brackets, our company name was Codelm AI, and we renamed to Codo and we call our models Codelm. So back to my point, so we started Enterprise Motion and already have multiple Fortune 100 companies. And then with that, we raised a series of $40 million. And what's exciting about it is that enables us to develop more agents. That's our focus. I think it's very different. We're not coming very soon with an ID or something like that.Swyx [00:06:01]: You don't want to fork this code?Itamar [00:06:03]: Maybe we'll fork JetBrains or something just to be different.Swyx [00:06:08]: I noticed that, you know, I think the promise of general purpose agents has kind of died. Like everyone is doing kind of what you're doing. There's Codogen, Codomerge, and then there's a third one. What's the name of it?Itamar [00:06:17]: Yeah. Codocover. Cover. Which is like a commercial version of a cover agent. It's coming soon.Swyx [00:06:23]: Yeah. It's very similar with factory AI, also doing like droids. They all have special purpose doing things, but people don't really want general purpose agents. Right. The last time you were here, we talked about AutoGBT, the biggest thing of 2023. This year, not really relevant anymore. And I think it's mostly just because when you give me a general purpose agent, I don't know what to do with it.Eric [00:06:42]: Yeah.Itamar [00:06:43]: I totally agree with that. We're seeing it for a while and I think it will stay like that despite the computer use, et cetera, that supposedly can just replace us. You can just like prompt it to be, hey, now be a QA or be a QA person or a developer. I still think that there's a few reasons why you see like a dedicated agent. Again, I'm a bit more focused, like my head is more on complex software for big teams and enterprise, et cetera. And even think about permissions and what are the data sources and just the same way you manage permissions for users. Developers, you probably want to have dedicated guardrails and dedicated approvals for agents. I intentionally like touched a point on not many people think about. And of course, then what you can think of, like maybe there's different tools, tool use, et cetera. But just the first point by itself is a good reason why you want to have different agents.Alessio [00:07:40]: Just to compare that with Bot.new, you're almost focused on like the application is very complex and now you need better tools to kind of manage it and build on top of it. On Bot.new, it's almost like I was using it the other day. There's basically like, hey, look, I'm just trying to get started. You know, I'm not very opinionated on like how you're going to implement this. Like this is what I want to do. And you build a beautiful app with it. What people ask as the next step, you know, going back to like the general versus like specific, have you had people say, hey, you know, this is great to start, but then I want a specific Bot.new dot whatever else to do a more vertical integration and kind of like development or what's the, what do people say?Eric [00:08:18]: Yeah. I think, I think you kind of hit the, hit it head on, which is, you know, kind of the way that we've, we've kind of talked about internally is it's like people are using Bolt to go from like 0.0 to 1.0, like that's like kind of the biggest unlock that Bolt has versus most other things out there. I mean, I think that's kind of what's, what's very unique about Bolt. I think the, you know, the working on like existing enterprise applications is, I mean, it's crazy important because, you know, there's a, you look, when you look at the fortune 500, I mean, these code bases, some of these have been around for 20, 30 plus years. And so it's important to be going from, you know, 101.3 to 101.4, et cetera. I think for us, so what's been actually pretty interesting is we see there's kind of two different users for us that are coming in and it's very distinct. It's like people that are developers already. And then there's people that have never really written software and more if they have, it's been very, very minimal. And so in the first camp, what these developers are doing, like to go from zero to one, they're coming to Bolt and then they're ejecting the thing to get up or just downloading it and, you know, opening cursor, like whatever to, to, you know, keep iterating on the thing. And sometimes they'll bring it back to Bolt to like add in a huge piece of functionality or something. Right. But for the people that don't know how to code, they're actually just, they, they live in this thing. And that was one of the weird things when we launched is, you know, within a day of us being online, one of the most popular YouTube videos, and there's been a ton since, which was, you know, there's like, oh, Bolt is the cursor killer. And I originally saw the headlines and I was like, thanks for the views. I mean, I don't know. This doesn't make sense to me. That's not, that's not what we kind of thought.Swyx [00:09:44]: It's how YouTubers talk to each other. Well, everything kills everything else.Eric [00:09:47]: Totally. But what blew my mind was that there was any comparison because it's like cursor is a, is a local IDE product. But when, when we actually kind of dug into it and we, and we have people that are using our product saying this, I'm not using cursor. And I was like, what? And it turns out there are hundreds of thousands of people that we have seen that we're using cursor and we're trying to build apps with that where they're not traditional software does, but we're heavily leaning on the AI. And as you can imagine, it is very complicated, right? To do that with cursor. So when Bolt came out, they're like, wow, this thing's amazing because it kind of inverts the complexity where it's like, you know, it's not an IDE, it's, it's a, it's a chat-based sort of interface that we have. So that's kind of the split, which is rather interesting. We've had like the first startups now launch off of Bolt entirely where this, you know, tomorrow I'm doing a live stream with this guy named Paul, who he's built an entire CRM using this thing and you know, with backend, et cetera. And people have made their first money on the internet period, you know, launching this with Stripe or whatever have you. So that's, that's kind of the two main, the two main categories of folks that we see using Bolt though.Itamar [00:10:51]: I agree that I don't understand the comparison. It doesn't make sense to me. I think like we have like two type of families of tools. One is like we re-imagine the software development. I think Bolt is there and I think like a cursor is more like a evolution of what we already have. It's like taking the IDE and it's, it's amazing and it's okay, let's, let's adapt the IDE to an era where LLMs can do a lot for us. And Bolt is more like, okay, let's rethink everything totally. And I think we see a few tools there, like maybe Vercel, Veo and maybe Repl.it in that area. And then in the area of let's expedite, let's change, let's, let's progress with what we already have. You can see Cursor and Kodo, but we're different between ourselves, Cursor and Kodo, but definitely I think that comparison doesn't make sense.Alessio [00:11:42]: And just to set the context, this is not a Twitter demo. You've made 4 million of revenue in four weeks. So this is, this is actually working, you know, it's not a, what, what do you think that is? Like, there's been so many people demoing coding agents on Twitter and then it doesn't really work. And then you guys were just like, here you go, it's live, go use it, pay us for it. You know, is there anything in the development that was like interesting and maybe how that compares to building your own agents?Eric [00:12:08]: We had no idea, honestly, like we, we, we've been pretty blown away and, and things have just kind of continued to grow faster since then. We're like, oh, today is week six. So I, I kind of came back to the point you just made, right, where it's, you, you kind of outlined, it's like, there's kind of this new market of like kind of rethinking the software development and then there's heavily augmenting existing developers. I think that, you know, both of which are, you know, AI code gen being extremely good, it's allowed existing developers, it's allowing existing developers to camera out software far faster than they could have ever before, right? It's like the ultimate power tool for an existing developer. But this code gen stuff is now so good. And then, and we saw this over the past, you know, from the beginning of the year when we tried to first build, it's actually lowered the barrier to people that, that aren't traditionally software engineers. But the kind of the key thing is if you kind of think about it from, imagine you've never written software before, right? My co-founder and I, he and I grew up down the street from each other in Chicago. We learned how to code when we were 13 together and we've been building stuff ever since. And this is back in like the mid 2000s or whatever, you know, there was nothing for free to learn from online on the internet and how to code. For our 13th birthdays, we asked our parents for, you know, O'Reilly books cause you couldn't get this at the library, right? And so instead of like an Xbox, we got, you know, programming books. But the hardest part for everyone learning to code is getting an environment set up locally, you know? And so when we built StackBlitz, like kind of the key thesis, like seven years ago, the insight we had was that, Hey, it seems like the browser has a lot of new APIs like WebAssembly and service workers, et cetera, where you could actually write an operating system that ran inside the browser that could boot in milliseconds. And you, you know, basically there's this missing capability of the web. Like the web should be able to build apps for the web, right? You should be able to build the web on the web. Every other platform has that, Visual Studio for Windows, Xcode for Mac. The web has no built in primitive for this. And so just like our built in kind of like nerd instinct on this was like, that seems like a huge hole and it's, you know, it will be very valuable or like, you know, very valuable problem to solve. So if you want to set up that environments, you know, this is what we spent the past seven years doing. And the reality is existing developers have running locally. They already know how to set up that environment. So the problem isn't as acute for them. When we put Bolt online, we took that technology called WebContainer and married it with these, you know, state of the art frontier models. And the people that have the most pain with getting stuff set up locally is people that don't code. I think that's been, you know, really the big explosive reason is no one else has been trying to make dev environments work inside of a browser tab, you know, for the past if since ever, other than basically our company, largely because there wasn't an immediate demand or need. So I think we kind of find ourselves at the right place at the right time. And again, for this market of people that don't know how to write software, you would kind of expect that you should be able to do this without downloading something to your computer in the same way that, hey, I don't have to download Photoshop now to make designs because there's Figma. I don't have to download Word because there's, you know, Google Docs. They're kind of looking at this as that sort of thing, right? Which was kind of the, you know, our impetus and kind of vision from the get-go. But you know, the code gen, the AI code gen stuff that's come out has just been, you know, an order of magnitude multiplier on how magic that is, right? So that's kind of my best distillation of like, what is going on here, you know?Alessio [00:15:21]: And you can deploy too, right?Eric [00:15:22]: Yeah.Alessio [00:15:23]: Yeah.Eric [00:15:24]: And so that's, what's really cool is it's, you know, we have deployment built in with Netlify and this is actually, I think, Sean, you actually built this at Netlify when you were there. Yeah. It's one of the most brilliant integrations actually, because, you know, effectively the API that Sean built, maybe you can speak to it, but like as a provider, we can just effectively give files to Netlify without the user even logging in and they have a live website. And if they want to keep, hold onto it, they can click a link and claim it to their Netlify account. But it basically is just this really magic experience because when you come to Bolt, you say, I want a website. Like my mom, 70, 71 years old, made her first website, you know, on the internet two weeks ago, right? It was about her nursing days.Swyx [00:16:03]: Oh, that's fantastic though. It wouldn't have been made.Eric [00:16:06]: A hundred percent. Cause even in, you know, when we've had a lot of people building personal, like deeply personal stuff, like in the first week we launched this, the sales guy from the East Coast, you know, replied to a tweet of mine and he said, thank you so much for building this to your team. His daughter has a medical condition and so for her to travel, she has to like line up donors or something, you know, so ahead of time. And so he actually used Bolt to make a website to do that, to actually go and send it to folks in the region she was going to travel to ahead of time. I was really touched by it, but I also thought like, why, you know, why didn't he use like Wix or Squarespace? Right? I mean, this is, this is a solved problem, quote unquote, right? And then when I thought, I actually use Squarespace for my, for my, uh, the wedding website for my wife and I, like back in 2021, so I'm familiar, you know, it was, it was faster. I know how to code. I was like, this is faster. Right. And I thought back and I was like, there's a whole interface you have to learn how to use. And it's actually not that simple. There's like a million things you can configure in that thing. When you come to Bolt, there's a, there's a text box. You just say, I need a, I need a wedding website. Here's the date. Here's where it is. And here's a photo of me and my wife, put it somewhere relevant. It's actually the simplest way. And that's what my, when my mom came, she said, uh, I'm Pat Simons. I was a nurse in the seventies, you know, and like, here's the things I did and a website came out. So coming back to why is this such a, I think, why are we seeing this sort of growth? It's, this is the simplest interface I think maybe ever created to actually build it, a deploy a website. And then that website, my mom made, she's like, okay, this looks great. And there's, there's one button, you just click it, deploy, and it's live and you can buy a domain name, attach it to it. And you know, it's as simple as it gets, it's getting even simpler with some of the stuff we're working on. But anyways, so that's, it's, it's, uh, it's been really interesting to see some of the usage like that.Swyx [00:17:46]: I can offer my perspective. So I, you know, I probably should have disclosed a little bit that, uh, I'm a, uh, stack list investor.Alessio [00:17:53]: Canceled the episode. I know, I know. Don't play it now. Pause.Eric actually reached out to ShowMeBolt before the launch. And we, you know, we talked a lot about, like, the framing of, of what we're going to talk about how we marketed the thing, but also, like, what we're So that's what Bolt was going to need, like a whole sort of infrastructure.swyx: Netlify, I was a maintainer but I won't take claim for the anonymous upload. That's actually the origin story of Netlify. We can have Matt Billman talk about it, but that was [00:18:00] how Netlify started. You could drag and drop your zip file or folder from your desktop onto a website, it would have a live URL with no sign in.swyx: And so that was the origin story of Netlify. And it just persists to today. And it's just like it's really nice, interesting that both Bolt and CognitionDevIn and a bunch of other sort of agent type startups, they all use Netlify to deploy because of this one feature. They don't really care about the other features.swyx: But, but just because it's easy for computers to use and talk to it, like if you build an interface for computers specifically, that it's easy for them to Navigate, then they will be used in agents. And I think that's a learning that a lot of developer tools companies are having. That's my bolt launch story and now if I say all that stuff.swyx: And I just wanted to come back to, like, the Webcontainers things, right? Like, I think you put a lot of weight on the technical modes. I think you also are just like, very good at product. So you've, you've like, built a better agent than a lot of people, the rest of us, including myself, who have tried to build these things, and we didn't get as far as you did.swyx: Don't shortchange yourself on products. But I think specifically [00:19:00] on, on infra, on like the sandboxing, like this is a thing that people really want. Alessio has Bax E2B, which we'll have on at some point, talking about like the sort of the server full side. But yours is, you know, inside of the browser, serverless.swyx: It doesn't cost you anything to serve one person versus a million people. It doesn't, doesn't cost you anything. I think that's interesting. I think in theory, we should be able to like run tests because you can run the full backend. Like, you can run Git, you can run Node, you can run maybe Python someday.swyx: We talked about this. But ideally, you should be able to have a fully gentic loop, running code, seeing the errors, correcting code, and just kind of self healing, right? Like, I mean, isn't that the dream?Eric: Totally.swyx: Yeah,Eric: totally. At least in bold, we've got, we've got a good amount of that today. I mean, there's a lot more for us to do, but one of the nice things, because like in web container, you know, there's a lot of kind of stuff you go Google like, you know, turn docker container into wasm.Eric: You'll find a lot of stuff out there that will do that. The problem is it's very big, it's slow, and that ruins the experience. And so what we ended up doing is just writing an operating system from [00:20:00] scratch that was just purpose built to, you know, run in a browser tab. And the reason being is, you know, Docker 2 awesome things will give you an image that's like out 60 to 100 megabits, you know, maybe more, you know, and our, our OS, you know, kind of clocks in, I think, I think we're in like a, maybe, maybe a megabyte or less or something like that.Eric: I mean, it's, it's, you know, really, really, you know, stripped down.swyx: This is basically the task involved is I understand that it's. Mapping every single, single Linux call to some kind of web, web assembly implementation,Eric: but more or less, and, and then there's a lot of things actually, like when you're looking at a dev environment, there's a lot of things that you don't need that a traditional OS is gonna have, right?Eric: Like, you know audio drivers or you like, there's just like, there's just tons of things. Oh, yeah. Right. Yeah. That goes . Yeah. You can just kind, you can, you can kind of tos them. Or alternatively, what you can do is you can actually be the nice thing. And this is, this kind of comes back to the origins of browsers, which is, you know, they're, they're at the beginning of the web and, you know, the late nineties, there was two very different kind of visions for the web where Alan Kay vehemently [00:21:00] disagree with the idea that should be document based, which is, you know, Tim Berners Lee, you know, that, and that's kind of what ended up winning, winning was this document based kind of browsing documents on the web thing.Eric: Alan Kay, he's got this like very famous quote where he said, you know, you want web browsers to be mini operating systems. They should download little mini binaries and execute with like a little mini virtualized operating system in there. And what's kind of interesting about the history, not to geek out on this aspect, what's kind of interesting about the history is both of those folks ended up being right.Eric: Documents were actually the pragmatic way that the web worked. Was, you know, became the most ubiquitous platform in the world to the degree now that this is why WebAssembly has been invented is that we're doing, we need to do more low level things in a browser, same thing with WebGPU, et cetera. And so all these APIs, you know, to build an operating system came to the browser.Eric: And that was actually the realization we had in 2017 was, holy heck, like you can actually, you know, service workers, which were designed for allowing your app to work offline. That was the kind of the key one where it was like, wait a second, you can actually now run. Web servers within a [00:22:00] browser, like you can run a server that you open up.Eric: That's wild. Like full Node. js. Full Node. js. Like that capability. Like, I can have a URL that's programmatically controlled. By a web application itself, boom. Like the web can build the web. The primitive is there. Everyone at the time, like we talked to people that like worked on, you know Chrome and V8 and they were like, uhhhh.Eric: You know, like I don't know. But it's one of those things you just kind of have to go do it to find out. So we spent a couple of years, you know, working on it and yeah. And, and, and got to work in back in 2021 is when we kind of put the first like data of web container online. Butswyx: in partnership with Google, right?swyx: Like Google actually had to help you get over the finish line with stuff.Eric: A hundred percent, because well, you know, over the years of when we were doing the R and D on the thing. Kind of the biggest challenge, the two ways that you can kind of test how powerful and capable a platform are, the two types of applications are one, video games, right, because they're just very compute intensive, a lot of calculations that have to happen, right?Eric: The second one are IDEs, because you're talking about actually virtualizing the actual [00:23:00] runtime environment you are in to actually build apps on top of it, which requires sophisticated capabilities, a lot of access to data. You know, a good amount of compute power, right, to effectively, you know, building app in app sort of thing.Eric: So those, those are the stress tests. So if your platform is missing stuff, those are the things where you find out. Those are, those are the people building games and IDEs. They're the ones filing bugs on operating system level stuff. And for us, browser level stuff.Eric [00:23:47]: yeah, what ended up happening is we were just hammering, you know, the Chromium bug tracker, and they're like, who are these guys? Yeah. And, and they were amazing because I mean, just making Chrome DevTools be able to debug, I mean, it's, it's not, it wasn't originally built right for debugging an operating system, right? They've been phenomenal working with us and just kind of really pushing the limits, but that it's a rising tide that's kind of lifted all boats because now there's a lot of different types of applications that you can debug with Chrome Dev Tools that are running a browser that runs more reliably because just the stress testing that, that we and, you know, games that are coming to the web are kind of pushing as well, but.Itamar [00:24:23]: That's awesome. About the testing, I think like most, let's say coding assistant from different kinds will need this loop of testing. And even I would add code review to some, to some extent that you mentioned. How is testing different from code review? Code review could be, for example, PR review, like a code review that is done at the point of when you want to merge branches. But I would say that code review, for example, checks best practices, maintainability, and so on. It's not just like CI, but more than CI. And testing is like a more like checking functionality, et cetera. So it's different. We call, by the way, all of these together code integrity, but that's a different story. Just to go back to the, to the testing and specifically. Yeah. It's, it's, it's since the first slide. Yeah. We're consistent. So if we go back to the testing, I think like, it's not surprising that for us testing is important and for Bolt it's testing important, but I want to shed some light on a different perspective of it. Like let's think about autonomous driving. Those startups that are doing autonomous driving for highway and autonomous driving for the city. And I think like we saw the autonomous of the highway much faster and reaching to a level, I don't know, four or so much faster than those in the city. Now, in both cases, you need testing and quote unquote testing, you know, verifying validation that you're doing the right thing on the road and you're reading and et cetera. But it's probably like so different in the city that it could be like actually different technology. And I claim that we're seeing something similar here. So when you're building the next Wix, and if I was them, I was like looking at you and being a bit scared. That's what you're disrupting, what you just said. Then basically, I would say that, for example, the UX UI is freaking important. And because you're you're more aiming for the end user. In this case, maybe it's an end user that doesn't know how to develop for developers. It's also important. But let alone those that do not know to develop, they need a slick UI UX. And I think like that's one reason, for example, I think Cursor have like really good technology. I don't know the underlying what's under the hood, but at least what they're saying. But I think also their UX UI is great. It's a lot because they did their own ID. While if you're aiming for the city AI, suddenly like there's a lot of testing and code review technology that it's not necessarily like that important. For example, let's talk about integration tests. Probably like a lot of what you're building involved at the moment is isolated applications. Maybe the vision or the end game is maybe like having one solution for everything. It could be that eventually the highway companies will go into the city and the other way around. But at the beginning, there is a difference. And integration tests are a good example. I guess they're a bit less important. And when you think about enterprise software, they're really important. So to recap, like I think like the idea of looping and verifying your test and verifying your code in different ways, testing or code review, et cetera, seems to be important in the highway AI and the city AI, but in different ways and different like critical for the city, even more and more variety. Actually, I was looking to ask you like what kind of loops you guys are doing. For example, when I'm using Bolt and I'm enjoying it a lot, then I do see like sometimes you're trying to catch the errors and fix them. And also, I noticed that you're breaking down tasks into smaller ones and then et cetera, which is already a common notion for a year ago. But it seems like you're doing it really well. So if you're willing to share anything about it.Eric [00:28:07]: Yeah, yeah. I realized I never actually hit the punchline of what I was saying before. I mentioned the point about us kind of writing an operating system from scratch because what ended up being important about that is that to your point, it's actually a very, like compared to like a, you know, if you're like running cursor on anyone's machine, you kind of don't know what you're dealing with, with the OS you're running on. There could be an error happens. It could be like a million different things, right? There could be some config. There could be, it could be God knows what, right? The thing with WebConnect is because we wrote the entire thing from scratch. It's actually a unified image basically. And we can instrument it at any level that we think is going to be useful, which is exactly what we did when we started building Bolt is we instrumented stuff at like the process level, at the runtime level, you know, et cetera, et cetera, et cetera. Stuff that would just be not impossible to do on local, but to do that in a way that works across any operating system, whatever is, I mean, would just be insanely, you know, insanely difficult to do right and reliably. And that's what you saw when you've used Bolt is that when an error actually will occur, whether it's in the build process or the actual web application itself is failing or anything kind of in between, you can actually capture those errors. And today it's a very primitive way of how we've implemented it largely because the product just didn't exist 90 days ago. So we're like, we got some work ahead of us and we got to hire some more a little bit, but basically we present and we say, Hey, this is, here's kind of the things that went wrong. There's a fix it button and then a ignore button, and then you can just hit fix it. And then we take all that telemetry through our agent, you run it through our agent and say, kind of, here's the state of the application. Here's kind of the errors that we got from Node.js or the browser or whatever, and like dah, dah, dah, dah. And it can take a crack at actually solving it. And it's actually pretty darn good at being able to do that. That's kind of been a, you know, closing the loop and having it be a reliable kind of base has seemed to be a pretty big upgrade over doing stuff locally, just because I think that's a pretty key ingredient of it. And yeah, I think breaking things down into smaller tasks, like that's, that's kind of a key part of our agent. I think like Claude did a really good job with artifacts. I think, you know, us and kind of everyone else has, has kind of taken their approach of like actually breaking out certain tasks in a certain order into, you know, kind of a concrete way. And, and so actually the core of Bolt, I know we actually made open source. So you can actually go and check out like the system prompts and et cetera, and you can run it locally and whatever have you. So anyone that's interested in this stuff, I'd highly recommend taking a look at. There's not a lot of like stuff that's like open source in this realm. It's, that was one of the fun things that we've we thought would be cool to do. And people, people seem to like it. I mean, there's a lot of forks and people adding different models and stuff. So it's been cool to see.Swyx [00:30:41]: Yeah. I'm happy to add, I added real-time voice for my opening day demo and it was really fun to hack with. So thank you for doing that. Yeah. Thank you. I'm going to steal your code.Eric [00:30:52]: Because I want that.Swyx [00:30:52]: It's funny because I built on top of the fork of Bolt.new that already has the multi LLM thing. And so you just told me you're going to merge that in. So then you're going to merge two layers of forks down into this thing. So it'll be fun.Eric [00:31:03]: Heck yeah.Alessio [00:31:04]: Just to touch on like the environment, Itamar, you maybe go into the most complicated environments that even the people that work there don't know how to run. How much of an impact does that have on your performance? Like, you know, it's most of the work you're doing actually figuring out environment and like the libraries, because I'm sure they're using outdated version of languages, they're using outdated libraries, they're using forks that have not been on the public internet before. How much of the work that you're doing is like there versus like at the LLM level?Itamar [00:31:32]: One of the reasons I was asking about, you know, what are the steps to break things down, because it really matters. Like, what's the tech stack? How complicated the software is? It's hard to figure it out when you're dealing with the real world, any environment of enterprise as a city, when I'm like, while maybe sometimes like, I think you do enable like in Bolt, like to install stuff, but it's quite a like controlled environment. And that's a good thing to do, because then you narrow down and it's easier to make things work. So definitely, there are two dimensions, I think, actually spaces. One is the fact just like installing our software without yet like doing anything, making it work, just installing it because we work with enterprise and Fortune 500, etc. Many of them want on prem solution.Swyx [00:32:22]: So you have how many deployment options?Itamar [00:32:24]: Basically, we had, we did a metric metrics, say 96 options, because, you know, they're different dimensions. Like, for example, one dimension, we connect to your code management system to your Git. So are you having like GitHub, GitLab? Subversion? Is it like on cloud or deployed on prem? Just an example. Which model agree to use its APIs or ours? Like we have our Is it TestGPT? Yeah, when we started with TestGPT, it was a huge mistake name. It was cool back then, but I don't think it's a good idea to name a model after someone else's model. Anyway, that's my opinion. So we gotSwyx [00:33:02]: I'm interested in these learnings, like things that you change your mind on.Itamar [00:33:06]: Eventually, when you're building a company, you're building a brand and you want to create your own brand. By the way, when I thought about Bolt.new, I also thought about if it's not a problem, because when I think about Bolt, I do think about like a couple of companies that are already called this way.Swyx [00:33:19]: Curse companies. You could call it Codium just to...Itamar [00:33:24]: Okay, thank you. Touche. Touche.Eric [00:33:27]: Yeah, you got to imagine the board meeting before we launched Bolt, one of our investors, you can imagine they're like, are you sure? Because from the investment side, it's kind of a famous, very notorious Bolt. And they're like, are you sure you want to go with that name? Oh, yeah. Yeah, absolutely.Itamar [00:33:43]: At this point, we have actually four models. There is a model for autocomplete. There's a model for the chat. There is a model dedicated for more for code review. And there is a model that is for code embedding. Actually, you might notice that there isn't a good code embedding model out there. Can you name one? Like dedicated for code?Swyx [00:34:04]: There's code indexing, and then you can do sort of like the hide for code. And then you can embed the descriptions of the code.Itamar [00:34:12]: Yeah, but you do see a lot of type of models that are dedicated for embedding and for different spaces, different fields, etc. And I'm not aware. And I know that if you go to the bedrock, try to find like there's a few code embedding models, but none of them are specialized for code.Swyx [00:34:31]: Is there a benchmark that you would tell us to pay attention to?Itamar [00:34:34]: Yeah, so it's coming. Wait for that. Anyway, we have our models. And just to go back to the 96 option of deployment. So I'm closing the brackets for us. So one is like dimensional, like what Git deployment you have, like what models do you agree to use? Dotter could be like if it's air-gapped completely, or you want VPC, and then you have Azure, GCP, and AWS, which is different. Do you use Kubernetes or do not? Because we want to exploit that. There are companies that do not do that, etc. I guess you know what I mean. So that's one thing. And considering that we are dealing with one of all four enterprises, we needed to deal with that. So you asked me about how complicated it is to solve that complex code. I said, it's just a deployment part. And then now to the software, we see a lot of different challenges. For example, some companies, they did actually a good job to build a lot of microservices. Let's not get to if it's good or not, but let's first assume that it is a good thing. A lot of microservices, each one of them has their own repo. And now you have tens of thousands of repos. And you as a developer want to develop something. And I remember me coming to a corporate for the first time. I don't know where to look at, like where to find things. So just doing a good indexing for that is like a challenge. And moreover, the regular indexing, the one that you can find, we wrote a few blogs on that. By the way, we also have some open source, different than yours, but actually three and growing. Then it doesn't work. You need to let the tech leads and the companies influence your indexing. For example, Mark with different repos with different colors. This is a high quality repo. This is a lower quality repo. This is a repo that we want to deprecate. This is a repo we want to grow, etc. And let that be part of your indexing. And only then things actually work for enterprise and they don't get to a fatigue of, oh, this is awesome. Oh, but I'm starting, it's annoying me. I think Copilot is an amazing tool, but I'm quoting others, meaning GitHub Copilot, that they see not so good retention of GitHub Copilot and enterprise. Ooh, spicy. Yeah. I saw snapshots of people and we have customers that are Copilot users as well. And also I saw research, some of them is public by the way, between 38 to 50% retention for users using Copilot and enterprise. So it's not so good. By the way, I don't think it's that bad, but it's not so good. So I think that's a reason because, yeah, it helps you auto-complete, but then, and especially if you're working on your repo alone, but if it's need that context of remote repos that you're code-based, that's hard. So to make things work, there's a lot of work on that, like giving the controllability for the tech leads, for the developer platform or developer experience department in the organization to influence how things are working. A short example, because if you have like really old legacy code, probably some of it is not so good anymore. If you just fine tune on these code base, then there is a bias to repeat those mistakes or old practices, etc. So you need, for example, as I mentioned, to influence that. For example, in Coda, you can have a markdown of best practices by the tech leads and Coda will include that and relate to that and will not offer suggestions that are not according to the best practices, just as an example. So that's just a short list of things that you need to do in order to deal with, like you mentioned, the 100.1 to 100.2 version of software. I just want to say what you're doing is extremelyEric [00:38:32]: impressive because it's very difficult. I mean, the business of Stackplus, kind of before bulk came online, we sold a version of our IDE that went on-prem. So I understand what you're saying about the difficulty of getting stuff just working on-prem. Holy heck. I mean, that is extremely hard. I guess the question I have for you is, I mean, we were just doing that with kind of Kubernetes-based stuff, but the spread of Fortune 500 companies that you're working with, how are they doing the inference for this? Are you kind of plugging into Azure's OpenAI stuff and AWS's Bedrock, you know, Cloud stuff? Or are they just like running stuff on GPUs? Like, what is that? How are these folks approaching that? Because, man, what we saw on the enterprise side, I mean, I got to imagine that that's a huge challenge. Everything you said and more, like,Itamar [00:39:15]: for example, like someone could be, and I don't think any of these is bad. Like, they made their decision. Like, for example, some people, they're, I want only AWS and VPC on AWS, no matter what. And then they, some of them, like there is a subset, I will say, I'm willing to take models only for from Bedrock and not ours. And we have a problem because there is no good code embedding model on Bedrock. And that's part of what we're doing now with AWS to solve that. We solve it in a different way. But if you are willing to run on AWS VPC, but run your run models on GPUs or inferentia, like the new version of the more coming out, then our models can run on that. But everything you said is right. Like, we see like on-prem deployment where they have their own GPUs. We see Azure where you're using OpenAI Azure. We see cases where you're running on GCP and they want OpenAI. Like this cross, like a case, although there is Gemini or even Sonnet, I think is available on GCP, just an example. So all the options, that's part of the challenge. I admit that we thought about it, but it was even more complicated. And it took us a few months to actually, that metrics that I mentioned, to start clicking each one of the blocks there. A few months is impressive. I mean,Eric [00:40:35]: honestly, just that's okay. Every one of these enterprises is, their networking is different. Just everything's different. Every single one is different. I see you understand. Yeah. So that just cannot be understated. That it is, that's extremely impressive. Hats off.Itamar [00:40:50]: It could be, by the way, like, for example, oh, we're only AWS, but our GitHub enterprise is on-prem. Oh, we forgot. So we need like a private link or whatever, like every time like that. It's not, and you do need to think about it if you want to work with an enterprise. And it's important. Like I understand like their, I respect their point of view.Swyx [00:41:10]: And this primarily impacts your architecture, your tech choices. Like you have to, you can't choose some vendors because...Itamar [00:41:15]: Yeah, definitely. To be frank, it makes us hard for a startup because it means that we want, we want everyone to enjoy all the variety of models. By the way, it was hard for us with our technology. I want to open a bracket, like a window. I guess you're familiar with our Alpha Codium, which is an open source.Eric [00:41:33]: We got to go over that. Yeah. So I'll do that quickly.Itamar [00:41:36]: Yeah. A pin in that. Yeah. Actually, we didn't have it in the last episode. So, so, okay.Swyx [00:41:41]: Okay. We'll come back to that later, but let's talk about...Itamar [00:41:43]: Yeah. So, so just like shortly, and then we can double click on Alpha Codium. But Alpha Codium is a open source tool. You can go and try it and lets you compete on CodeForce. This is a website and a competition and actually reach a master level level, like 95% with a click of a button. You don't need to do anything. And part of what we did there is taking a problem and breaking it to different, like smaller blocks. And then the models are doing a much better job. Like we all know it by now that taking small tasks and solving them, by the way, even O1, which is supposed to be able to do system two thinking like Greg from OpenAI like hinted, is doing better on these kinds of problems. But still, it's very useful to break it down for O1, despite O1 being able to think by itself. And that's what we presented like just a month ago, OpenAI released that now they are doing 93 percentile with O1 IOI left and International Olympiad of Formation. Sorry, I forgot. Exactly. I told you I forgot. And we took their O1 preview with Alpha Codium and did better. Like it just shows like, and there is a big difference between the preview and the IOI. It shows like that these models are not still system two thinkers, and there is a big difference. So maybe they're not complete system two. Yeah, they need some guidance. I call them system 1.5. We can, we can have it. I thought about it. Like, you know, I care about this philosophy stuff. And I think like we didn't see it even close to a system two thinking. I can elaborate later. But closing the brackets, like we take Alpha Codium and as our principle of thinking, we take tasks and break them down to smaller tasks. And then we want to exploit the best model to solve them. So I want to enable anyone to enjoy O1 and SONET and Gemini 1.5, etc. But at the same time, I need to develop my own models as well, because some of the Fortune 500 want to have all air gapped or whatever. So that's a challenge. Now you need to support so many models. And to some extent, I would say that the flow engineering, the breaking down to two different blocks is a necessity for us. Why? Because when you take a big block, a big problem, you need a very different prompt for each one of the models to actually work. But when you take a big problem and break it into small tasks, we can talk how we do that, then the prompt matters less. What I want to say, like all this, like as a startup trying to do different deployment, getting all the juice that you can get from models, etc. is a big problem. And one need to think about it. And one of our mitigation is that process of taking tasks and breaking them down. That's why I'm really interested to know how you guys are doing it. And part of what we do is also open source. So you can see.Swyx [00:44:39]: There's a lot in there. But yeah, flow over prompt. I do believe that that does make sense. I feel like there's a lot that both of you can sort of exchange notes on breaking down problems. And I just want you guys to just go for it. This is fun to watch.Eric [00:44:55]: Yeah. I mean, what's super interesting is the context you're working in is, because for us too with Bolt, we've started thinking because our kind of existing business line was going behind the firewall, right? We were like, how do we do this? Adding the inference aspect on, we're like, okay, how does... Because I mean, there's not a lot of prior art, right? I mean, this is all new. This is all new. So I definitely am going to have a lot of questions for you.Itamar [00:45:17]: I'm here. We're very open, by the way. We have a paper on a blog or like whatever.Swyx [00:45:22]: The Alphacodeum, GitHub, and we'll put all this in the show notes.Itamar [00:45:25]: Yeah. And even the new results of O1, we published it.Eric [00:45:29]: I love that. And I also just, I think spiritually, I like your approach of being transparent. Because I think there's a lot of hype-ium around AI stuff. And a lot of it is, it's just like, you have these companies that are just kind of keep their stuff closed source and then just max hype it, but then it's kind of nothing. And I think it kind of gives a bad rep to the incredible stuff that's actually happening here. And so I think it's stuff like what you're doing where, I mean, true merit and you're cracking open actual code for others to learn from and use. That strikes me as the right approach. And it's great to hear that you're making such incredible progress.Itamar [00:46:02]: I have something to share about the open source. Most of our tools are, we have an open source version and then a premium pro version. But it's not an easy decision to do that. I actually wanted to ask you about your strategy, but I think in your case, there is, in my opinion, relatively a good strategy where a lot of parts of open source, but then you have the deployment and the environment, which is not right if I get it correctly. And then there's a clear, almost hugging face model. Yeah, you can do that, but why should you try to deploy it yourself, deploy it with us? But in our case, and I'm not sure you're not going to hit also some competitors, and I guess you are. I wanted to ask you, for example, on some of them. In our case, one day we looked on one of our competitors that is doing code review. We're a platform. We have the code review, the testing, et cetera, spread over the ID to get. And in each agent, we have a few startups or a big incumbents that are doing only that. So we noticed one of our competitors having not only a very similar UI of our open source, but actually even our typo. And you sit there and you're kind of like, yeah, we're not that good. We don't use enough Grammarly or whatever. And we had a couple of these and we saw it there. And then it's a challenge. And I want to ask you, Bald is doing so well, and then you open source it. So I think I know what my answer was. I gave it before, but still interestingEric [00:47:29]: to hear what you think. GeoHot said back, I don't know who he was up to at this exact moment, but I think on comma AI, all that stuff's open source. And someone had asked him, why is this open source? And he's like, if you're not actually confident that you can go and crush it and build the best thing, then yeah, you should probably keep your stuff closed source. He said something akin to that. I'm probably kind of butchering it, but I thought it was kind of a really good point. And that's not to say that you should just open source everything, because for obvious reasons, there's kind of strategic things you have to kind of take in mind. But I actually think a pretty liberal approach, as liberal as you kind of can be, it can really make a lot of sense. Because that is so validating that one of your competitors is taking your stuff and they're like, yeah, let's just kind of tweak the styles. I mean, clearly, right? I think it's kind of healthy because it keeps, I'm sure back at HQ that day when you saw that, you're like, oh, all right, well, we have to grind even harder to make sure we stay ahead. And so I think it's actually a very useful, motivating thing for the teams. Because you might feel this period of comfort. I think a lot of companies will have this period of comfort where they're not feeling the competition and one day they get disrupted. So kind of putting stuff out there and letting people push it forces you to face reality soon, right? And actually feel that incrementally so you can kind of adjust course. And that's for us, the open source version of Bolt has had a lot of features people have been begging us for, like persisting chat messages and checkpoints and stuff. Within the first week, that stuff was landed in the open source versions. And they're like, why can't you ship this? It's in the open, so people have forked it. And we're like, we're trying to keep our servers and GPUs online. But it's been great because the folks in the community did a great job, kept us on our toes. And we've got to know most of these folks too at this point that have been building these things. And so it actually was very instructive. Like, okay, well, if we're going to go kind of land this, there's some UX patterns we can kind of look at and the code is open source to this stuff. What's great about these, what's not. So anyways, NetNet, I think it's awesome. I think from a competitive point of view for us, I think in particular, what's interesting is the core technology of WebContainer going. And I think that right now, there's really nothing that's kind of on par with that. And we also, we have a business of, because WebContainer runs in your browser, but to make it work, you have to install stuff from NPM. You have to make cores bypass requests, like connected databases, which all require server-side proxying or acceleration. And so we actually sell WebContainer as a service. One of the core reasons we open-sourced kind of the core components of Bolt when we launched was that we think that there's going to be a lot more of these AI, in-your-browser AI co-gen experiences, kind of like what Anthropic did with Artifacts and Clod. By the way, Artifacts uses WebContainers. Not yet. No, yeah. Should I strike that? I think that they've got their own thing at the moment, but there's been a lot of interest in WebContainers from folks doing things in that sort of realm and in the AI labs and startups and everything in between. So I think there'll be, I imagine, over the coming months, there'll be lots of things being announced to folks kind of adopting it. But yeah, I think effectively...Swyx [00:50:35]: Okay, I'll say this. If you're a large model lab and you want to build sandbox environments inside of your chat app, you should call Eric.Itamar [00:50:43]: But wait, wait, wait, wait, wait, wait. I have a question about that. I think OpenAI, they felt that people are not using their model as they would want to. So they built ChatGPT. But I would say that ChatGPT now defines OpenAI. I know they're doing a lot of business from their APIs, but still, is this how you think? Isn't Bolt.new your business now? Why don't you focus on that instead of the...Swyx [00:51:16]: What's your advice as a founder?Eric [00:51:18]: You're right. And so going into it, we, candidly, we were like, Bolt.new, this thing is super cool. We think people are stoked. We think people will be stoked. But we were like, maybe that's allowed. Best case scenario, after month one, we'd be mind blown if we added a couple hundred K of error or something. And we were like, but we think there's probably going to be an immediate huge business. Because there was some early poll on folks wanting to put WebContainer into their product offerings, kind of similar to what Bolt is doing or whatever. We were actually prepared for the inverse outcome here. But I mean, well, I guess we've seen poll on both. But I mean, what's happened with Bolt, and you're right, it's actually the same strategy as like OpenAI or Anthropic, where we have our ChatGPT to OpenAI's APIs is Bolt to WebContainer. And so we've kind of taken that same approach. And we're seeing, I guess, some of the similar results, except right now, the revenue side is extremely lopsided to Bolt.Itamar [00:52:16]: I think if you ask me what's my advice, I think you have three options. One is to focus on Bolt. The other is to focus on the WebContainer. The third is to raise one billion dollars and do them both. I'm serious. I think otherwise, you need to choose. And if you raise enough money, and I think it's big bucks, because you're going to be chased by competitors. And I think it will be challenging to do both. And maybe you can. I don't know. We do see these numbers right now, raising above $100 million, even without havingEric [00:52:49]: a product. You can see these. It's excellent advice. And I think what's been amazing, but also kind of challenging is we're trying to forecast, okay, well, where are these things going? I mean, in the initial weeks, I think us and all the investors in the company that we're sharing this with, it was like, this is cool. Okay, we added 500k. Wow, that's crazy. Wow, we're at a million now. Most things, you have this kind of the tech crunch launch of initiation and then the thing of sorrow. And if there's going to be a downtrend, it's just not coming yet. Now that we're kind of looking ahead, we're six weeks in. So now we're getting enough confidence in our convictions to go, okay, this se
Today is a big day. It's episode #400 of the WP Builds podcast. This is an important milestone, and as suck I'm going to do absolutely nothing of any kind whatsoever to celebrate it, aside from this paragraph of text. So there! I'm joined on the podcast by Bud Kraus. Bud is a WordPress educator and content creator, best known for his educational materials on joyofwp.com. His expertise in WordPress and his engaging instructional style have made him a pillar in the WordPress community. In this episode, we dive deep into Bud's journey, exploring how his passion for teaching and creating content started. We'll also talk about his podcast, "Seriously BUD?" which offers a refreshing departure from traditional WordPress content by focusing on stories and light-hearted conversations. Bud shares his motivation behind starting the podcast and the joy he finds in uncovering fascinating personal stories from his guests. So, join us as we celebrate Bud Kraus's contributions to the WordPress ecosystem, share some intriguing personal stories, and gain insight into what makes the WordPress community so special.
The WordPress news from the last week which commenced Monday 18th November 2024.
Joining us is Joost de Valk, the mastermind behind the immensely popular Yoast SEO plugin. But today, Joost is here to share his latest project, Progress Planner - a tool designed to revolutionise the way we maintain and update our websites. Imagine a blend between a "Fitbit for websites" and Duolingo. That's precisely what Progress Planner aims to be, combining gamification techniques with practical maintenance strategies to keep users engaged and their sites up-to-date. In our chat, Joost unveils the features, from special badges and weekly activity emails to a task management dashboard right inside of WordPress. We explore how these elements work together to reduce procrastination and make website upkeep a fun, interactive endeavour. So, whether you're a non-tech-savvy business owner struggling to keep your site relevant, an agency looking for ways to enhance client interaction, or someone simply curious about innovative WordPress tools, this episode has something for you.
W świecie kryptowalut, gdzie nie ma miejsca na półśrodki, Janusz Zieliński wyrósł na jednego z liderów polskiej sceny blockchainu. Jego historia to opowieść o odwadze, determinacji i chęci do podejmowania ryzyka, które napędzały go do przekraczania kolejnych granic. Z blokowiska do Londynu - droga pełna wyzwań Janusz Zieliński, wychowany na poznańskich Jeżycach, postanowił w młodym wieku wyrwać się ze środowiska, które nie dawało mu perspektyw na rozwój. Życie na osiedlu pełne było trudnych sytuacji, które kształtowały jego osobowość - od świadków kradzieży po bolesne wydarzenia, takie jak śmierć dawnego kolegi. To właśnie te doświadczenia sprawiły, że Janusz zdecydował się obrać zupełnie inną drogę. W 2013 roku, z plecakiem pełnym marzeń, wyruszył do Londynu. Bez pewnego planu, bez znajomości, jedynie z biletem powrotnym na „wszelki wypadek”, rzucił się na głęboką wodę. Wynajem łóżka w hostelu, oszczędności rzędu 1600 funtów i skromna praca na wózku widłowym były początkiem jego emigracyjnej przygody. To właśnie ten moment, kiedy na londyńskich ulicach, otoczony wieżowcami City, zrozumiał, że świat ma mu do zaoferowania coś więcej. Początki fascynacji kryptowalutami Zainteresowanie kryptowalutami rozpoczęło się jeszcze przed Londynem, w 2012 roku. To były czasy, kiedy świat blockchainu dopiero stawiał swoje pierwsze kroki, a Janusz był jednym z tych, którzy uwierzyli w rewolucję finansową. Pierwszego bitcoina kupił za około 30 złotych. Eksplorował nieznane wówczas rejony internetowe, takie jak Silk Road - platformę, która zmieniła jego postrzeganie o cyfrowym pieniądzu. Choć z powodu zamknięcia Silk Road przez FBI stracił kilka bitcoinów, jego zainteresowanie nie wygasło. Wręcz przeciwnie - jeszcze bardziej zaangażował się w świat cyfrowych walut. PARTNERZY ODCINKA:
Patronite Okiem Deva: https://patronite.pl/okiemdeva Discord Okiem Deva: https://discord.gg/4anD7dJJn8 Linki: https://linktr.ee/okiemdeva Kompilacja ofert pracy: https://docs.google.com/document/d/1agVeF3cW5aK4skDnHnB0IVwmma7n1rD8Sm9btTCTFdw/edit?usp=sharing Pytania do następnego live'a https://forms.gle/4rEHhLdoiPUDWdtE7 Tajemnice sukcesu Half-Life 2 00:00:00 Intro 00:01:56 Cabal 00:03:42 Organizacja zespołów projektowych 00:05:06 Innowacje technologiczne 00:07:42 Proces iteracyjny i testowanie 00:11:17 Narracja i projektowanie poziomów 00:12:59 Zarządzanie zasobami 00:16:01 Rozwój silnika Source 00:18:26 Wyzwania i rozwiązywanie problemów 00:19:28 Wpływ na branżę gier 00:20:29 Dziedzictwo i długoterminowy sukces 00:25:32 Podsumowanie 00:27:27 Outro ---------------- Wspierający Intern: KasiaNie, Piotr Łyp Junior Dev: Kruszynka Izka, Daniel Zabłocki, Konrad Wągrowski, nothing, Tomek Mar, Marcin McFly, Anna Weglarz, kondi16, ExitWound, Kojo Bojo, ZajacccXD, Marcin Pietrzyk, Ania Węglarzy, FiSherMan414, MichalDev, Lukas P, Aliwera, Malwina Rybak, sovl Regular Dev: Natsu, Bonga, Sebbx8,vxd555, PabloRal, Remigiusz Maciaszek, Anatae GG, Arrora, Jakub Staniszewski, Ari Gold, bibruRG_78, Leniwa Ola, Sebastian Sadowy, Tek, Michał Wiśniewski, Bartosz Romanowski, Adam Kabalak, Kaspa Anonim, Martyna Szubka, Bartosz Mateńko, Jon der, Patryk Szkop, Aquatofana, Bartosz Złotowski, Mateusz Stolarz Stolarczyk, Karolina Czech, Adam Bart, Marcin Ignasiak, Kamil Czerepak, sayonara usotsuki Senior Dev: Maja, Dawid Kuc, Arti ,,Niezłomny＂, Miras, jmozgawa, Pawelek1329 STUDIOS, Pielgrzym, Morfiniusz, Jakub Kornatowski (@GramyNaMacu), Mariusz Kowalski, Cezary Łysoń, Rafał Jaszczuk, enonemasta, HARDCOROWYKOŚCIU GAMEPLAY!, Łukasz Klejnberg, Tomasz Berej, Jakub WmH, Michał Król, Gatki, Arkadiusz Rekowski, Sebastian Rubacha, Michał Kondzior, Marek Leśniak,Jan Skiba, Mateusz Śródka, Agata Pławna, Radosław Paszkowski, Magdalena Porath, Agnieszka Rumińska, Mateusz Myga, Damian Kowalski Principal Dev: Regito93, Jan Dorozynski, Wojciech Uziębło, Leszek Lisowski, Zuzanna Lepianka, Kamil Górecki, Michał Stankiewicz https://workplays.it/ ---------------- Źródła: https://arstechnica.com/gaming/2024/11/how-valve-made-half-life-2-and-set-a-new-standard-for-future-games/ https://combineoverwiki.net/wiki/Development_of_Half-Life_2 https://www.gamedeveloper.com/design/classic-postmortem-the-making-of-i-half-life-2-i- https://www.gamedeveloper.com/design/the-cabal-valve-s-design-process-for-creating-i-half-life-i-
The WordPress news from the last week which commenced Monday 11th November 2024.
Stało się - Elon Musk jest najpotężniejszym przedsiębiorcą na świecie. Jego wpływy polityczne i biznesowe już dziś są duże, a będą jeszcze większe. Co może zyskać "współprezydent USA"? Dużo: ulgi finansowe dla swoich firm, łagodniejszy kurs regulacyjny, usunięcie denerwujących go urzędników lub wyciszenie toczących się postępowań. Przykłady można mnożyć. Musk będzie teraz jednym z ważniejszych doradców prezydenta-elekta. A jakie podejście do technologii przyjmie sam Trump? Czy bigtechy mogą otwierać szampana? I co jego polityka będzie oznaczała dla każdego z nas? O tym właśnie rozmawiamy w tym odcinku Techstorii. Zastanowimy się więc, czy to faktycznie ostatni rok TikToka w USA? Czy sztuczna inteligencja pod rządami Truska nabierze wiatru w żagle? Czy kryptolobby czeka teraz prawdziwy złoty wiek? No i czy państwem da się zarządzać tak, jak Twitterem. GOŚĆMI ODCINKA SĄ: - Krystian Łukasik, analityk gospodarki cyfrowej z Polskiego Instytutu Ekonomicznego - Jan Jęcz, analityk gospodarki cyfrowej z Polityki Insight - Dr Marcin Przychodniak, główny specjalista i analityk Chin w programie Azja i Pacyfik Polskiego Instytutu Spraw Międzynarodowych NA SKRÓTY DO TREŚCI: 00:00:00 - Wprowadzenie 00:05:07 - Wpływy Muska 00:13:00 - DOGE i krypto 00:40:14 - Deregulacje i BigTechy 00:51:18 AI 01:09:51 - Chipy i Tajwan 01:13:05 Chiny LINKI DO ŻRÓDEŁ: - O finansowaniu kampanii: https://www.opensecrets.org/elections-overview/biggest-donors - O tym, jak Musk jest finansowo powiązany z rządem; https://www.nytimes.com/2024/10/20/us/politics/elon-musk-federal-agencies-contracts.html - O bromansie Muska i Trumpa: https://xyz.pl/jak-elon-musk-pomogl-trumpowi-wygrac-wyscig-do-bialego-domu/ - Ogłoszenie o pracę w DOGE: https://twitter.com/DOGE/status/1857076831104434289 - Musk o tym, czy będzie płacić: https://twitter.com/elonmusk/status/1857112441529700671 - Koszulka DOGE: https://win.donaldjtrump.com/trump-national-committee-jfc/storefront/trump-doge-t-shirt/details/ - Komentarz o broligarchii i McMuskizmie: https://www.theguardian.com/commentisfree/2024/nov/17/how-to-survive-the-broligarchy-20-lessons-for-the-post-truth-world-donald-trump - Co wydarzy się z CHIPS Act: https://www.bloomberg.com/news/articles/2024-11-08/trump-s-win-sets-off-race-to-complete-chips-act-subsidy-deals - Trump pogłębi zimną wojnę z Chinami: https://www.washingtonpost.com/technology/2024/11/14/us-china-ai-tech-export-controls/ POLECANE WCZEŚNIEJSZE ODCINKI TECHSTORII: - https://audycje.tokfm.pl/podcast/137168,31-Techstorie-i-Twitter-od-srodka-Byli-pracownicy-o-kulisach-rzadow-Muska - https://audycje.tokfm.pl/podcast/163426,91-Przedsiebiorca-polityk-maciwoda-Ktora-maska-Muska-jest-dzis-prawdziwa - https://audycje.tokfm.pl/podcast/163772,92-Krypto-lobby-a-wybory-Jak-steruje-sie-polityka-USA-z-tylnego-siedzenia
Po co Koalicja Obywatelska organizuje prawybory na kandydata na prezydenta? Czy publikacja sondaży na kilka dni przed głosowaniem faktycznie rozstrzyga wynik? O potencjalnych skutkach politycznych tej decyzji oraz szerszym kontekście, w tym wpływie wyborów w USA na polską scenę polityczną, Marzena Tabor Olszewska rozmawia z Marcinem Dumą, szefem IBRIS. - Prawybory w Koalicji Obywatelskiej to nie tylko wybór między Rafałem Trzaskowskim a Radosławem Sikorskim, ale też strategia wzbudzenia zaangażowania w strukturach partyjnych - Marcin Duma podkreśla, że choć sondaże publikowane przed głosowaniem wskazują na przewagę Trzaskowskiego, należy zachować ostrożność. - 10 lat temu Bronisław Komorowski również miał wygrać w pierwszej turze, a rzeczywistość okazała się zupełnie inna – przypomina ekspert. Porównanie rywalizacji Sikorskiego i Trzaskowskiego do walki Mike'a Tysona z młodszym youtuberem Jake'm Paulem jest przywołane z przymrużeniem oka, ale też wskazuje na istotną różnicę w stylach i potencjale obu kandydatów. Marcin Duma zauważa, że Sikorski pokazuje determinację, choć wynik może wydawać się przesądzony. Czy rzeczywiście chodzi tylko o wzmacnianie pozycji w partii, czy też Sikorski liczy na niespodziewany zwrot akcji? Jak zmienia się elektorat w Polsce? Gość podcastu zwraca uwagę na grupy wyborców, które mogą zdecydować o wyniku wyborów prezydenckich. Młodsi, mniej aktywni wyborcy odegrali kluczową rolę w parlamentarnym zwycięstwie opozycji 15 października. Pytanie, czy równie licznie zagłosują w wyborach prezydenckich, pozostaje otwarte. Duma wskazuje też na potencjalną szansę dla „królika z kapelusza” – niezależnego kandydata spoza głównych partii politycznych. - Po 1989 roku nie było jeszcze tak sprzyjających warunków, aby ktoś spoza politycznego układu miał realną szansę na drugą turę – zauważa ekspert, przywołując sukcesy Szymona Hołowni czy Pawła Kukiza. - Dzisiaj miejsca dla tego trzeciego kandydata jest chyba najwięcej w historii. Polska ma wrażliwość na kandydatów, których nikt wcześniej nie brał pod uwagę. Jeśli znajdzie się ktoś, kto opowie historię o bezpieczeństwie zewnętrznym i ekonomicznym, to może powstać czarny koń tych wyborów – mówi Marcin Duma. Wpływ wyborów w USA na polską politykę Powrót Donalda Trumpa do Białego Domu budzi pytania o globalne trendy i ich wpływ na Polskę. Według Dumy zwycięstwo Trumpa podkreśla przesunięcie priorytetów społecznych z kwestii ideologicznych, takich jak prawa kobiet, na bezpieczeństwo ekonomiczne. - To sygnał, że bytowe postulaty dominują nad światopoglądowymi – komentuje ekspert. Polska polityka może również dostosować się do nowych wyzwań związanych z wojną w Ukrainie. Intensyfikacja konfliktu może sprzyjać kandydatom kojarzonym z bezpieczeństwem, takim jak Radosław Sikorski, podczas gdy zakończenie wojny mogłoby wzmocnić Trzaskowskiego jako lidera odbudowy i stabilizacji. Przyszłość sceny politycznej Choć Koalicja Obywatelska wkrótce wyłoni swojego kandydata, PiS wciąż nie podjął decyzji. Brak nominacji po stronie największej partii opozycyjnej to jeden z czynników, który wprowadza element niepewności w wyścigu prezydenckim. W tej sytuacji niezależny kandydat mógłby wstrząsnąć układem sił. - Przyszłe wybory prezydenckie mogą być wyjątkowe pod wieloma względami – od demografii elektoratu po wpływ globalnych wydarzeń – ocenia Duma. Na razie jednak oczy wszystkich są zwrócone na prawybory w Koalicji Obywatelskiej. Zapraszamy do wysłuchania całego odcinka na stronie rp.pl oraz w serwisach streamingowych. #PodcastRzeczWTym; #RzeczpospolitaPodcast; #PolitykaPodcast; #SłuchamPodcastów; #Prawybory2024; #KoalicjaObywatelska; #RafałTrzaskowski; #RadosławSikorski; #WyboryPrezydenckie; #PolitykaPL; #WyboryPolska; #DonaldTrump2024; #EfektTrumpa; #WyboryUSA; #PolskaPolityka; #PolskaDecyduje; #NowePrzywództwo; #BezpieczeństwoiStabilność; #NewsPL; #Aktualności; #TrendingPL; #PodcastNaDziś
In this episode, Nathan Wrigley and Rae Morey discuss key events in the WordPress community. Highlights include an automated plugin review system achieving zero backlog, the expansion of the Kim Parsell Memorial Scholarship to WordCamp Europe and Asia, and HeroPress' call for sponsorship. They address the ongoing conflict between Automattic and WP Engine, including legal disputes and community fallout, alongside the departure of WordPress Executive Director Josepha Haden Chomposy and Mary Hubbard's new leadership. Despite the drama, the episode offers insights into WordPress's design updates, featured events, and efforts to improve gender diversity. Check it out...
Przed Tobą 203. odcinek Urbcastu: Krajobraz i architektura: jak natura kształtuje życie i miasta Norwegów?
The WordPress news from the last week which commenced Monday 4th November 2024.
Dołącz do grona Patronów tego podcastu na http://www.patronite.pl/maopowiedziane Posłuchaj dalszej części odcinka na kanale Mao Powiedziane Plus na Spotify: Jak połączyć konto na Patronite ze Spotify https://patronite.pl/post/71266/polacz-konto-na-patronite-ze-spotify Nie tylko Stany Zjednoczone, ale i cały świat z zapartym tchem śledziły amerykańskie wybory prezydenckie. Ich wynik wywołał lawinę komentarzy i analiz, w tym spekulacje na temat przyszłego podejścia wobec Chin. Państwo Środka pozostaje priorytetem numer jeden w polityce zagranicznej Waszyngtonu. Ale jak wygląda percepcja amerykańskiej polityki wobec Chin w samych Chinach? Jakie były reakcje na wybór Trumpa na drugą kadencję? A jak wspomina się jego pierwszą? W tym odcinku podcastu Mao Powiedziane przyglądamy się polityce i relacjom chińsko-amerykańskim w kontekście niedawnych wyborów prezydenckich. Spis treści:(0:00) Postrzeganie Ameryki w Chinach (11:20) Wpływ COVID na relacje chińsko-amerykańskie(21:52) Pierwsza kadencja Trumpa wobec Chin(30:45) Idea wojny handlowej z Chinami(38:12) Odbiór zwycięstwa Trumpa wśród Chińczyków(44:52) Odbiór zwycięstwa Trumpa wśród chińskiej diaspory w USA Dołącz do naszego Discorda (dla Patronów) https://patronite.pl/post/59230/jak-dolaczyc-do-naszego-discordaPostaw nam kawę na http://buycoffee.to/maopowiedzianeInstagram: http://instagram.com/maopowiedzianeInstagram Nadii: http://instagram.com/nadia.urbanInstagram Weroniki: http://instagram.com/wtruszczynskaNapisz do nas: kontakt@maopowiedziane.pl
WOW! TYLE ODCINKÓW JUŻ DLA WAS NAGRALIŚMY! TYLKO SPÓJRZCIE! Dużo czasu minęło, od momentu, kiedy opuściliśmy WP. Aż się łezka w oku kręci, że wciąż możemy dla Was produkować content. I wciąż jesteście z nami i nas słuchacie! A nawet trochę Was przybywa! Serce się raduje i chce się nam dalej starać! W tym tygodniu […]
Данила Гальперович знакомит вас с самыми важными новостями о войне в Украине и реакции на нее в мире. В этом выпуске: WP: Трамп и Путин поговорили об Украине | Повреждена дамба около Курахово | ЕС – за оружие для Киева без «красных линий»
Patronite Okiem Deva: https://patronite.pl/okiemdeva Discord Okiem Deva: https://discord.gg/4anD7dJJn8 Linki: https://linktr.ee/okiemdeva Kompilacja ofert pracy: https://docs.google.com/document/d/1agVeF3cW5aK4skDnHnB0IVwmma7n1rD8Sm9btTCTFdw/edit?usp=sharing Pytania do następnego live'a https://forms.gle/4rEHhLdoiPUDWdtE7 Jak NAPRAWDĘ funkcjonuje Sweet Baby Inc. ? 00:00:00 Intro 00:01:07 Historia i początki Sweet Baby Inc. 00:02:23 Rzeczywistość za kulisami 00:06:36 Geneza kontrowersji 00:16:16 Eskalacja i konsekwencje 00:18:27 Prawda kontra mity 00:26:02 Wpływ na branżę gier 00:29:23 Przyszłość i perspektywy 00:32:01 Podsumowanie 00:35:57 Outro ---------------- Wspierający Intern: KasiaNie, Piotr Łyp Junior Dev: Kruszynka Izka, Daniel Zabłocki, Konrad Wągrowski, nothing, Tomek Mar, Marcin McFly, Anna Weglarz, kondi16, ExitWound, Kojo Bojo, ZajacccXD, Marcin Pietrzyk, Ania Węglarzy, FiSherMan414, MichalDev, Lukas P, Aliwera, kondi16, Malwina Rybak, sovl Regular Dev: Natsu, Bonga, Sebbx8, Agnieszka Rumińska, vxd555, PabloRal, Remigiusz Maciaszek, Anatae GG, Arrora, Jakub Staniszewski, Ari Gold, bibruRG_78, Leniwa Ola, Sebastian Sadowy, Tek, Michał Wiśniewski, Bartosz Romanowski, Adam Kabalak, Kaspa Anonim, Martyna Szubka, Bartosz Mateńko, Jon der, Patryk Szkop, Aquatofana, Bartosz Złotowski, Mateusz Stolarz Stolarczyk, Karolina Czech, Adam Bart, Marcin Ignasiak, Kamil Czerepak, sayonara usotsuki Senior Dev: Maja, Dawid Kuc, Arti ,,Niezłomny＂, Miras, jmozgawa, Pawelek1329 STUDIOS, Pielgrzym, Morfiniusz, Jakub Kornatowski (@GramyNaMacu), Mariusz Kowalski, Cezary Łysoń, Rafał Jaszczuk, enonemasta, HARDCOROWYKOŚCIU GAMEPLAY!, Łukasz Klejnberg, Tomasz Berej, Jakub WmH, Michał Król, Gatki, Arkadiusz Rekowski, Sebastian Rubacha, Michał Kondzior, Marek Leśniak,Jan Skiba, Mateusz Śródka, Agata Pławna, Radosław Paszkowski, Magdalena Porath Principal Dev: Regito93, Jan Dorozynski, Wojciech Uziębło, Leszek Lisowski, Zuzanna Lepianka, Kamil Górecki, Michał Stankiewicz https://workplays.it/ ---------------- Źródła: https://www.thegamer.com/sweet-baby-inc-interview-grant-roberts-online-abuse-alan-wake-2-spider-man/ https://mezha.media/en/articles/a-conspiracy-theory-in-the-gaming-industry-western-game-developers-are-accused-of-promoting-woke-values-what-is-sweet-baby-inc-and-what-is-going-on/ https://tomsgaming.com/2024/03/07/the-sweet-baby-inc-controversy/ https://www.readergrev.com/p/sweet-baby-inc-paranoid-style-hofstadter https://www.theshortcut.com/p/sweet-baby-inc-detected-what-actually-happened https://thatparkplace.com/sweet-baby-inc-employee-admits-goal-is-burning-the-games-industry-to-the-ground/ https://thatparkplace.com/sweet-baby-inc-defender-who-says-every-lever-must-be-pulled-to-push-lgbtq-agenda-announces-shes-joined-cd-projekt-red/ https://youtu.be/GfMsxjWgUbI
Síguenos en: En el episodio de hoy Nahuai nos explica su experiencia el pasado fin de semana en la Rome Core Days ¿Qué tal la semana? Semana esther Refinando UN y DN Meetup Terrassa Empezando a preparar Karma Next Semana Nahuai Medio lunes sin internet, un drama. Meetup Terrassa con la charla de Esther en la que nos contó las principales cosas a tener en cuanta cuando quieres transformar un tema clásico en uno de bloques. Vuelta a la reflexión del “peligro” de dejar cosas a medias, en este caso un tutorial. Jugando con los hooks de bloques y aplicándolo en el plugin de cambio de tipografía y color. Ya lo tenemos implementado en la página de demo de Uprising Next. Contenido Nahuai Tema de la semana: Giuseppe Mazzapica, código que sea fácil de mantener. Crear test para probar plugins (Composer + Github actions). Olga Gleckler, cómo contribuir a WP core( dar ideas, proponer diseños, test y reportar bugs, organizar otros contribuyentes, revisar código de otros, unit tests, otras herramientas). Carlos Bravo, block bindings, patrones sincronizados, mejoras de interfaz, API publica, nuevos filtros. Y mejoras futuras. Carlo Daniele, patrones de bloques, tipos (sincronizados, overrides), estructura. Carolina Nymark, creación del TT5 (espacios, tipografía, paleta de colores, diseño de elementos, tests) Website Speed building chalenge. André Maneiro y Riad Bengela, Data views, componente visual, taller. Panel sobre el editor de bloques (data views y block binding). Preguntando por maneras de introducir patrones desde una fuente externa y sobre el onboarding de temas Mesa redonda sobre temas de bloques Novedades Ya está disponible la RC4 de WordPress 6.7 y todo parece indicar que se lanzará mañana (18 de noviembre)
Donald Trump e Vladimir Putin hanno avuto un contatto telefonico sulla guerra tra Russia e Ucraina. Il neo presidente americano e il presidente russo hanno parlato giovedì in quello che è il primo confronto diretto dopo le elezioni andate in scena il 5 novembre negli Stati Uniti.
Viewpoint This Sunday with Malcolm Out Loud – Forecaster Alan Lichtman and Pollster Nate Silver were positive Kamala Harris would win. 'I admit I was wrong': Allan Lichtman explains why his election prediction failed. Senator Ron Johnson is here for a big post-election talk on ‘the machine.' Jeff Bezos at the WP says it's time to fix the ‘media distrust.' Trevor Loudon says that America nearly escaped becoming a socialist-communist nation… this time...
Viewpoint This Sunday with Malcolm Out Loud – Forecaster Alan Lichtman and Pollster Nate Silver were positive Kamala Harris would win. 'I admit I was wrong': Allan Lichtman explains why his election prediction failed. Senator Ron Johnson is here for a big post-election talk on ‘the machine.' Jeff Bezos at the WP says it's time to fix the ‘media distrust.' Trevor Loudon says that America nearly escaped becoming a socialist-communist nation… this time...
Kiedyś był rzepak i rzepiary, teraz jest wyginanie i wyginiary. Jednak bystre oko obserwatora zauważy pewne różnice. Otóż Joanna Opozda jako osoba bardziej znana, silniej ucelebrycona jest w jednoczęściowym kostiumie, podczas gdy Julia Tychoniewicz jest w dwuczęściowym, popularnym bikini. Wynika z tego, że celeberetki mniej znane, wyginając się, muszą się bardziej obnażać. Oddajmy głos matematyce. Współczynnik wygięcia W jest odwrotnie proporcjonalny do popularności P czyli im mniejsza popularność P tym współczynnik wygięcia W jest większy, co można wyrazić wzorem W= P dzielone przez f, gdzie f jest faktorem. Max faktorem.
Paris Marx is joined by tante to discuss troubling developments in the open source world as Wordpress goes to war with WP Engine and a new definition of open source AI doesn't require being open about training data.tante is a sociotechnologist, writer, speaker, and Luddite working on tech and its social impact.Tech Won't Save Us offers a critical perspective on tech, its worldview, and wider society with the goal of inspiring people to demand better tech and a better world. Support the show on Patreon.The podcast is made in partnership with The Nation. Production is by Eric Wickham. Transcripts are by Brigitte Pawliw-Fry.Also mentioned in this episode:tante wrote about the problem with the Open Source Initiative's definition of open source AI.Check out this link for the full breakdown on the Wordpress drama.Wordpress changed its trademark guidelines on September 19 regarding the use of the WP abbreviation.Tumblr and Wordpress started selling user data for AI training earlier this year.A lot of the controversy around Richard Stallman started blowing up in 2019.Support the show
In this episode of WP Builds, I'm joined by Ben Butler, who runs the Headless Hostman static WordPress hosting solution. Ben shares insights on their approach to enhancing security and performance for WordPress sites. The challenges faced by sites running things like NitroPack and WooCommerce. And dynamic functionalities managed via CloudFlare. They plan a Shopify plugin extension soon, and are actively developing a WooCommerce static solution. Their innovative infrastructure boasts high traffic handling and many other features discussed in the episode. Ben also highlights their seamless integrations with Elementor, WP Rocket, and WPML, aiming to help enterprises manage large-scale, traffic-heavy websites effectively.
Pełnej wersji podcastu posłuchasz w aplikacji Onet Audio. [AUTOPROMOCJA] W tym odcinku podcastu “Raport międzynarodowy” Zbigniew Parafianowicz i Witold Jurasz rozmawiają o: Wpływie prezydentury Donalda Trumpa na Polskę i Europę. Mocnym przesunięciu Partii Republikańskiej na prawo i jego skutkach. Reakcjach europejskich polityków, w tym Donalda Tuska, na Trumpa. Wyborach w Mołdawii i subtelniejszych, niż te militarne, działaniach Rosji. Głośnym we Francji procesie o podżeganie do zabójstwa oraz kwestii wolności słowa. O internetowych bojówkach PO, które nie różnią się od hejterów wspierających PiS.
Czy duże modele językowe (LLM) to rewolucja, czy zagrożenie dla prawników? W tym odcinku przybliżam możliwości dużych modeli językowych (LLM) w automatyzacji procesów prawnych, tworzeniu dokumentów, tłumaczeniach prawniczych i compliance. To, co wydaje się przyszłością, dzieje się już teraz – ale czy to na pewno oznacza koniec klasycznego prawa?Partnerem podcastu jest DataWorkshop.
The WordPress news from the last week which commenced Monday 28th October 2024.
Dołącz do grona Patronów tego podcastu na http://www.patronite.pl/maopowiedziane Posłuchaj dalszej części odcinka na kanale Mao Powiedziane Plus na Spotify: https://open.spotify.com/episode/1LU2Kjoc29yk3htUHzsTQ7?si=wxGluY0mQ02hVL5SLLCgygJak połączyć konto na Patronite ze Spotify https://patronite.pl/post/71266/polacz-konto-na-patronite-ze-spotify Chiny mogą kojarzyć się na Zachodzie z odmiennością, a nawet zaprzeczeniem kultury rozwiniętego świata Globalnej Północy. Zamiłowanie młodych ludzi w chińskich miastach do obchodzenia Halloween może więc zaskakiwać. Największe imprezy odbywały się oczywiście w Szanghaju, gdzie w ostatnich latach zaczęły one niekiedy przybierać formy, które niekoniecznie mogły podobać się władzom. Stroje stawały się bowiem komentarzami na temat chińskiej rzeczywistości społecznej i politycznej – nierzadko krytycznymi i prześmiewczymi. W tym roku Szanghaj zdecydował, że żarty się skończyły, i zarządził, aby ludzie w przebraniach zniknęli z ulic miasta. Spis treści:(0:00) Wpływ japońskiej kultury i chiński cosplay(15:24) Zamiłowanie Chińczyków do przebierania się(19:19) Problematyczny Halloween w Szanghaju (37:58) Dlaczego władze nie chcą Halloween Dołącz do naszego Discorda (dla Patronów) https://patronite.pl/post/59230/jak-dolaczyc-do-naszego-discordaPostaw nam kawę na http://buycoffee.to/maopowiedzianeInstagram: http://instagram.com/maopowiedzianeInstagram Nadii: http://instagram.com/nadia.urbanInstagram Weroniki: http://instagram.com/wtruszczynskaNapisz do nas: kontakt@maopowiedziane.pl
In questa puntata:✅ Monitor grandi✅ WP drama✅ Marketing turistico✅ Team meeting aziendale✅ Browser e tab verticali
Today we have the first instalment of our (yet another) new quarterly show. This one is called "At The Core,", and I'll bet you can't guess what it's about!?! Erm... WordPress Core, and all the recent updates that we can squeeze into 45 minutes! For this new show I'm joined by Birgit Pauli-Haack. She's an Automattician, massive fan of Gutenberg, and all around lovely person! She's also the founder of the Gutenberg Times, which you really should check out. In this premiere episode (ha!), we talk about the latest and greatest developments in the WordPress universe; spotlighting WordPress Playground, a revolutionary tool that allows users to effortlessly spin up websites directly in their browsers - no hosting or database required. We discuss its cutting-edge features, including managing multiple sites from one browser and the much-anticipated blueprints for easy site setup. This episode is packed with resources and discussions, so check it out right away...
Czy zastanawiałeś się kiedyś, jak social media wpływają na Twoje zdrowie psychiczne?W tym odcinku analizuję rosnący trend cyfrowego minimalizmu i świadomego ograniczania obecności w mediach społecznościowych.Inspiracją do jego nagrania był fascynujący trend młodzieży z Brooklynu, która całkowicie rezygnuje ze smartfonów.To skłoniło mnie do przemyśleń nad własną obecnością w sieci i rolą sekcji komentarzy w budowaniu autentycznych relacji online.
Hey Strangers, Grab 20% off Selected item and subscription using my Link: https://livezesty.com/CODINGWITHSTRAN... or use my code at checkout: CODINGWITHSTRANGERS #wordpress #drama #MattMullenweg ************************************************ A lot of open source programming languages have one person that runs things. For Wordpress, that person is named Matt, and he's one of the co-founders. While we've all thought of this as a community project, Matt has a company, AutoMATTic, and a nonprofit that play key roles. There are many companies that specialize in hosting Wordpress sites, and Automattic is one of them. One of their biggest competitors is WPEngine. Automattic holds the trademark for Wordpress, but everyone has been allowed to use WP in their branding. The way the law works, if you don't defend a trademark, it can be difficult to enforce in the future. While Automattic probably couldn't win a trademark lawsuit against WPEngine, they were hoping to pressure WPEngine to pay 8%(!) of revenue to Automattic. Then when WPEngine refused, Matt went ballistic and has engaged in a daily campaign of attacks against WPEngine, who are now suing Matt and Automattic. ======================================= Something Strange https://www.youtube.com/watch?v=GRjVc2TZqN4&t=4s ************************************************** article links: https://www.reddit.com/r/Wordpress/comments/1g2jo1j/explain_me_the_wordpress_drama_like_im_5/ ====================================== Today is for push-ups and Programming and I am all done doing push-ups Discord https://discord.gg/MYvNgYYFxq TikTok https://www.tiktok.com/@strangestcoder Youtube https://www.youtube.com/channel/UCe9xwdRW2D7RYwlp6pRGOvQ?sub_confirmation=1 Twitch https://www.twitch.tv/CodingWithStrangers Twitter https://twitter.com/strangestcoder merch Support CodingWithStrangers IRL by purchasing some merch. All merch purchases include an alert: https://streamlabs.com/codingwithstrangers/merch Github Follow my works of chaos https://github.com/codingwithstrangers Tips https://streamlabs.com/codingwithstrangers/tip Patreon https://www.patreon.com/TheStrangers Webull https://act.webull.com/vi/c8V9LvpDDs6J/uyq/inviteUs/ Join this channel https://www.youtube.com/channel/UCe9xwdRW2D7RYwlp6pRGOvQ/join Timeline 00:00 intro 00:26 What Talking We Talking About 06:53 Article 10:30 My Thoughts 26:01 outro anything else? Take Care --- Send in a voice message: https://podcasters.spotify.com/pod/show/coding-with-strangers/message
In this episode we have Topher DeRosia discussing HeroPress, a platform sharing inspiring stories within the WordPress community. Topher highlights HeroPress' mission to counteract negativity by showcasing WordPress's potential. He shares truly impactful stories, such as a child in a stock photo symbolising HeroPress's motivation to help, and individuals like Hari from India who found success through WordPress. Despite funding challenges, Topher remains committed to maintaining the core essays and possibly starting a storytelling podcast, urging support through recurring donations. Check out the episode today!
The WordPress news from the last week which commenced Monday 14th October 2024.
Zapisz się na Darmowy Newsletter: ✉️ bit.ly/e1t1-newsletter • Zostań patronką lub patronem Podcastu i odbierz Bonusy:
So, here we are with yet another WP Builds show. Shiny! In this episode, Remkus de Vries discusses building a high-performance WordPress website, emphasising a solid foundation with good hosting and theme selection. He highlights the importance of "bare metal" speed, Time to First Byte, and independent hosting reviews. Remkus recommends starting with the WordPress site editor and tools like the 'Create Block Theme' plugin. He advises against relying on third-party page builders which may induce complexity and vendor lock-in. The conversation stresses early optimisation and concludes with plans for future discussions on extending WordPress capabilities. Check it out...
Michael Houston is president of the US for the holding company. He assumed that role in 2022 following 15 years with Grey Group, one of the holding company's constituency agencies. He's responsible for promoting WP's offering and collective capabilities, and has a good handle on these team WPP pitches.Before this role, Michael served as worldwide CEO of Grey for five years and as part of a 15-year run at the agency. We chat to Michael about the pitch, how these team pitches work, how holding companies are going to market in 2024, as well as creativity, procurement, the time when you need to collaborate, the time when you need to go it alone and much more.Listen and subscribe to wherever you get your podcasts. campaignlive.com What we know about advertising, you should know about advertising. Start your 1-month FREE trial to Campaign US.
The WordPress news from the last week which commenced Monday 7th October 2024.
.io domains have been in vogue for over a decade, but now that the British government has decided to give up sovereignty over the small set of islands in the Indian Ocean that owned that country code on the Internet, it will soon cease to exist. Evan You, of Vue JS and Vite fame, has started a new company VoidZero Inc. to build the next generation toolchain for JavaScript. While trying to make Vite even better, Evan realized he needed a full-time team and funding to build the best toolchain around, and the engineers and investors agreed.StackBlitz enters the AI arena as well with its bolt.new offering, AI-powered software development allowing users to prompt, run, edit, and deploy full-stack web apps directly in the browser.WordPress drama reaches new levels of pettiness with a new checkbox that users must check before signing into their WP accounts swearing they are not affiliated with WP Engine in any way. In happier news, Sentry doubles down on its support for open source software (and the maintainers) by creating the Open Source Pledge where companies who use OSS for profit are encouraged to commit to paying the maintainers of the software they use so that burnout and related security issues can be better addressed.News:Paige - void(0) JavaScript toolingJack - StackBlitz's Bolt.new AI dev toolTJ - The end of .io domainsBonus News:Waymo updateWordPress updateSentry launches the Open Source PledgeSentry itself gave $500k to OS maintainers this yearDeno 2 is officially out!Fire Starters:HTTP QUERYWhat Makes Us Happy this Week:Paige - The Lord of the Rings: Rings of Power season 2Jack - The Substance movieTJ - Cider millsThanks as always to our sponsor, the Blue Collar Coder channel on YouTube. You can join us in our Discord channel, explore our website and reach us via email, or Tweet us on X @front_end_fire and BlueSky.Front-end Fire websiteBlue Collar Coder on YouTubeBlue Collar Coder on DiscordReach out via emailTweet at us on X @front_end_fireFollow us on Bluesky @front-end-fire.com
Matt Laue, founder of Mindspun, discusses how his company aims to revolutionise digital purchases by enabling users to buy products online in seconds using seamless tools like digital wallets and fingerprint scans. He highlights the advantages of reducing checkout time and tackling cart abandonment. Matt shares the complexities behind developing Mindspun's WordPress payment plugin, including integrating block-based design and maintaining compatibility with systems like Stripe. He also reflects on the challenges of standing out in a competitive market and the evolving WordPress community, expressing optimism about its future and adaptability. So, join us as we learn about a possible future for e-commerce and digital wallets!
The WordPress news from Monday 30th September 2024.
Tim Nash, seasoned WordPress security expert, launches "Feeling insecure?" podcast discussing tools, legislation, vulnerabilities, and security best practices for WordPress. This show, just like the other new shows I've recently started (and the ones I'm still to unveil) will happen about once a quarter, and this is the first one! We explore a range of pressing security topics. Tim begins by discussing the relevance of tools like Patchstack for comprehensive security and the potential legal ramifications of software vulnerabilities highlighted by new legislation such as the European Cyber Resilience Act. The conversation turns to looking into real-world examples, including the CUPS vulnerability affecting Linux systems, illustrating the far-reaching impact of security flaws (or not!). You'll hear Tim's expert opinion on the topic of 'responsible disclosure' and the recent actions of major security players like Ubuntu and Red Hat. There's loads more, so have a listen...