Podcasts about WYSIWYG

Episode 488 of the Lens Shark Photography Podcast In This Episode If you subscribe to the Lens Shark Photography Podcast, please take a moment to rate and review us to help make it easier for others to discover the show. Sponsors: - Build Your Legacy with Fujifilm. Latest savings at FujfilmCameraSavings.com - Shop with the legends at RobertsCamera.com, and unload your gear with UsedPhotoPro.com -  Elinchrom's new Transmitter Pro X at Elinchrom.com - Calibrate's big WYSIWYG savings! - More mostly 20% OFF codes at LensShark.com/deals. Stories: Insta360 unveils its Luna Ultra. (#) You might want to wait on updating this Panasonic. (#) These types of cameras are doing especially well. (#) Fujifilm announces Fujikina NYC. (#) Adobe's latest updates are very useful. (#) Zeiss sets the record straight on these lenses. (#)   Connect With Us Thank you for listening to the Lens Shark Photography Podcast! Connect with me, Sharky James on Twitter, Instagram Vero, and Facebook (all @LensShark).

ChatGPT tasks are back, Jack. ✅While we were collectively ping-ponging the Anthropic vs. U.S. government saga, the big tech AI players rolled out a TON of fresh AI features that are available today. ↳ Claude Design got a big upgrade↳ Google Vids got some serious AI sparkle↳ And there's a new Open Weights model king We'll break it all down. ChatGPT's Task Comeback, Claude's Design upgrade, Codex Copies your workflow and 7 other Fresh AI features you'll Want to use Today -- An Everyday AI Chat with Jordan WilsonNewsletter: Sign up for our free daily newsletterMore on this Episode: Episode PageToday's Episode on LinkedIn: Thoughts on this? Join the convo on LinkedIn and connect with other AI leaders.Upcoming Episodes: Check out the upcoming Everyday AI Livestream lineupWebsite: YourEverydayAI.comEmail The Show: info@youreverydayai.comConnect with Jordan on LinkedInTopics Covered in This Episode:ChatGPT Pulse Sunsetting and Tasks Comeback2. ChatGPT Scheduled Tasks Features and Access Tiers3. Claude Design June Update Overview4. WYSIWYG Editing and Design System Imports in Claude Design5. Claude Design Export Options and Third-Party Integrations6. Google Vids AI Avatars Upgrade with Veo 3.17. OpenRouter Fusion Multi-Model Synthesis Feature8. Claude Code Artifacts for Team and Enterprise Plans9. GLM 5.2 from ZAI Open Weights Model Overview10. GLM 5.2 Benchmarks and Enterprise Use Cases11. OpenAI Codex Record and Replay Feature Explained12. Codex Record and Replay vs. Traditional RPA ToolsTimestamps:00:00 Intro: 7 new AI features you can use today02:35 ChatGPT Tasks: Pulse is gone, Tasks are back04:31 Who has access to ChatGPT Tasks08:18 Claude Design June update overview09:14 WYSIWYG editing and Claude Code integration12:07 Claude Design export options and third-party integrations15:21 Google Vids AI Avatars upgrade18:15 OpenRouter Fusion multi-model synthesis21:54 Claude Code Artifacts for teams25:36 GLM 5.2 from ZAI open weights model29:02 OpenAI Codex Record and ReplayKeywords: ChatGPT Tasks, ChatGPT Pulse, OpenAI, scheduled tasks, proactive AI agent, Claude Design, WYSIWYG editor, Claude Code, design system import, PowerPoint export, Google Vids, AI avatars, Veo 3.1, Gemini 3.1 Flash, OpenRouter Fusion, model fusion, multi-model synthesis, Claude Code Artifacts, Claude Team plan, GLM 5.2, ZAI, open weights, MIT license, mixture of experts, Codex Record and Replay, RPA, workflow automation, Artificial Analysis, Hugging Face, Canva integrationSend Everyday AI and Jordan a text message. (We can't reply back unless you leave contact info) Start Here ▶️Not sure where to start when it comes to AI? Start with our Start Here Series. You can listen to the first drop -- Episode 691 -- or get free access to our Inner Cricle community and all episodes: StartHereSeries.com Also, here's a link to the entire series on a Spotify playlist. 

Odd Spot Prints – https://www.marketingsharks.com/odd-spot-prints-create-and-sell-odd-one-out-puzzle-books/Odd Spot Prints – Create And Sell Odd One Out Puzzle Books – The Only Tool Your Audience Needs To Create And Sell Odd One Out Puzzle Books From Scratch, No Canva, No Design Skills, No Manual Page Creation RequiredThe Only Tool Your Audience Needs To Create And Sell Odd One Out Puzzle Books From ScratchNo Canva, No Design Skills, No Manual Page Creation RequiredCreate puzzle pages in a WYSIWYG editor with all the tools built right inEliminate the usual barriers to entering the Odd One Out book niche and finally start creating with confidenceAccess thousands of beautifully designed emoji icons across multiple categories, all ready to usePurpose-built for creating full, publish-ready books with export in PDF, JPG, PNG, and PPT at multiple canvas sizesWork from anywhere with a cloud-based app, no installations, no heavy software, just log in and createA clean, beginner-friendly interface that is simple, intuitive, and easy to use with no design skills or tech experience requiredFull commercial and PLR rights on every page, publish and sell your outputs on any platform30-day money-back guarantee for your peace of mind

Hubo una época en la que trabajar para Apple significaba firmar tanto papel que tu mano izquierda ni siquiera sabía para quién trabajaba la derecha. Y aun así, había gente dispuesta a coger un avión a Los Ángeles para hacer anuncios de un teléfono que todavía no existía. Una de esas personas fue nuestra invitada.Noelia Meltzer es directora creativa en TBWA España y una de las pocas personas que puede contarte, con nombres y apellidos, cómo se lanzó el iPhone en España desde dentro. Pasó por Wysiwyg, por McCann Interactive, y estuvo en Media Arts Lab (la agencia creada en exclusiva para Apple) en los años en que enseñarle a la gente a tocar una pantalla era, literalmente, el briefing.Hablamos de guardaespaldas para teléfonos, de historias de amor internacionales, de viajes a Las Vegas, de lo que significa adaptar una campaña global a un país donde el iPhone todavía era un mito, de consistencia y coherencia (que es el mantra que tienes que aprender antes tocar nada), de por qué los guiones más sencillos de la historia de la publicidad fueron posiblemente los más difíciles de escribir, y de cómo se defiende una decisión creativa delante de cincuenta personas cuando tú eres el mercado más pequeño de la sala. No está mal, ¿no?Pues hay más, también hablamos de lo que pasa cuando el secretismo absoluto se mezcla con semanas enteras viviendo en la misma ciudad, en la misma agencia, con los mismos equipos, en una utopía extraña.Si eres de los que creen que la publicidad racional y la publicidad emocional son especies distintas, este episodio te va a hacer el lío. Y eso es está bien.Nuevo programa en tres semanas.Patrocina: Madrid Content SchoolUna producción de Obvio y RaroCreado por Dei Arroyo y Leonor MuñozEdición de sonido: Adrián FernándezPresidente Honorífico: Toni SegarraNo-Bullshit Creative Director: Ferran LópezEl Becario: Edu Pou

We're bringing back favorite episodes over the summer as encore editions. Since this episode first aired, poet Jen Siraganian won the 2026 Perugia Press Prize for her debut collection "Everything Has Been Moved, Even the Dead," which is forthcoming in September 2026. Congratulations, Jen!  Slushies, we invoke the retelling of a ghostly experience shared by Kathy and Marion at the Hotel Figueroa in California earlier this year partway into this episode. Two poems by Jen Siraganian are at the heart of our discussion, and it's the first of these that puts ghosts into our heads. This poem also causes us to consider at some length the physical form chosen by or for a poem, and how this can utterly enhance the experience of the poem when it's just right. It's also an opportunity for Jason to raise the spectre of the virgule (or slash) once again, and we even pause briefly to recall when WYSIWYG was a useful acronym. We end the episode with an ekphrastic that prompts an on-the-spot tie breaker (thanks to our sound engineer Lillie for saving the day!).   https://whitney.org/collection/works/2171 https://www.nga.gov/collection/highlights/gorky-the-artist-and-his-mother.html    At the table: Kathleen Volk Miller, Marion Wrenn, Lisa Zerkle, Jason Schneiderman, Dagne Forrest, Jodi Gahn, Derek Grebis (sound engineer)   Jen Siraganian is an Armenian-American writer, educator, and former Poet Laureate of Los Gatos, California. Her poetry has appeared or is forthcoming in AGNI, Barrow Street, Best New Poets, Cortland Review, Poetry Daily, Prairie Schooner, The Rumpus, Smartish Pace, and other journals. Her work has been nominated for a Pushcart Prize and won the 2024 New Ohio Review Poetry Prize. A former managing director of Litquake: San Francisco's Literary Festival, she is a current Lucas Artist Fellow. jensiraganian.com      Social media handles:   Facebook @jen.siraganian, Instagram @jsiraganian, Bluesky @jsiraganian.bsky.social, Website   Walking into St. James Cathedral as If We Were Already Ghosts     My Father and I View Two Versions of Arshile Gorky's The Artist and his Mother   Lip corners sink, an upturned bowl dripping its contents onto the white   of her dress. Her eyes, Armenian saucers of round, outline hollows of darkness.   Sharing color only, no overlap of limbs or space, shades of pink echo his coat,   her lap, a paleness descends. My father nudges my elbow. He seldom mentions   his mothers, the one who raised him, the other who gave him away. I want him   to discuss the lack of daisies in the boy's hands, the mother's face swaddled in a cocoon of scarf.   Instead, he stands, cloud-drifts across the gallery. We bench in front of The Liver is the Cock's Comb.   He points to the ferns feuding with triangles, the thorned stems breathing blossom.  

In this episode, I speak with Peter Staar of Docling about the wonderful open-source project that converts messy documents into structured data, perfect for ingestion into AI tools and more. Recorded live at PyTorch con in 2026. Want the power of Mermaid for enterprises? Mermaid chart brings WYSIWYG editing, generative AI, collaboration, and more to the flexible syntax of Mermaid.https://go.chrischinchilla.com/mermaid For show notes and an interactive transcript, visit chrischinchilla.com/podcast/To reach out and say hello, visit chrischinchilla.com/contact/To support the show for ad-free listening and extra content, visit chrischinchilla.com/support/ Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

Joseph Wilson was loosing the battle to Kodak when he discovered the xerography machine. Then he made it sellable. Dave Young: Welcome to the Empire Builders Podcast, teaching business owners the not so secret techniques that took famous businesses from mom and pop to major brands. Stephen Simple is a marketing consultant, story collector and storyteller. I’m Stephen’s sidekick and business partner, Dave Young. Before we get into today’s episode, a word from our sponsor, which is, well, it’s us, but we’re highlighting ads we’ve written and produced for our clients. So here’s one of those. [Handyside Ad] Dave Young: Welcome to the Empire Builders Podcast. I’m Dave Young and that’s Stephen Semple. Welcome to the Empire Builders Podcast. I’m Dave Young and there’s Steve Semple. Welcome. Oh wait, I got stuck making copies of copies. See what I did there? Stephen Semple: You’re so clever. Dave Young: You know what I did there, right? Yeah. Stephen Semple: I saw it, yeah. Dave Young: Today we’re talking about Xerox. Stephen Semple: Talking about copies of copies. Dave Young: Copies of copies of copies. Stephen Semple: Oh, and back in the day there were a lot of copies. A lot of copies. Dave Young: Oh man. I have copier stories. Yeah. Stephen Semple: I bet. I think those of us of our genre- Dave Young: Honestly, so Xerox, and we’re going to learn the story of the Xerox corporation and we’re going to… I don’t know their whole story, but I can tell you this, the photocopier or before there was something else before that. There was carbon paper. Stephen Semple: Yes, yes. Dave Young: But nobody owned a printing press. Stephen Semple: Correct, yeah. Dave Young: And so I would make the case that a photocopier was the first social media meme sharing engine. Stephen Semple: Oh, because we could photocopy our butts and share it the office. Dave Young: No, no, no, no, not your butt. I mean, I don’t know what you do in Canada. Here, I remember as a kid going to coffee, but my dad, small town, small town America, and he went to coffee twice a day with his buddies, 10 o’clock and three o’clock. They’d go down to the local cafe and they’d sit around a table and have coffee, eight or 10 of them. And somebody would always have a copy of a copy of a copy of a copy of a joke. Stephen Semple: Right. Dave Young: A cartoon, a usually off color story and they’d pass it around and then somebody would take it and make another copy of it and share it somewhere else. But you couldn’t do that if you didn’t have a copier. Stephen Semple: Well, that’s true. Dave Young: So thank you, Xerox. Stephen Semple: For making our lives richer. Dave Young: And now we can just electronically copy stuff and shoot it off as a text and a meme. Stephen Semple: One of the things you’re going to love about this story is it involves a fire extinguisher. So I’ve got your attention. Dave Young: Oh, I am all in. Stephen Semple: You’re all in. And Xerox is still pretty big. They do 7 billion in sales, but back in the early ’70s, Xerox was a monster. It’s estimated that over 10 billion copies a year were being done. Dave Young: 10 billion. Stephen Semple: That’s a lot of copies of copies of copies- Dave Young: Yeah. Once people had it, they were like, “I’m a printer.” Stephen Semple: Of copies. Yeah. Dave Young: I’m a publisher now. Stephen Semple: Yeah. In 1973, they did 3 billion in sales, which would equate to about 20 billion today. And they were close to 90% of the copier market with profit margins close to 20%. That’s just huge. It was one of the most valuable companies in the world. Dave Young: Until there started to be some competitors, Xerox became the generic word for a photocopy. Stephen Semple: Correct. Dave Young: “Give me a Xerox of this.” Stephen Semple: Yeah. So our story starts back with Joseph Wilson in Rochester, New York, which as we also know, is the home of Kodak. And Joseph was the new president of a company called Haloid, which was a Rochester based company doing photographic paper that was founded in 1906. And frankly, they were getting killed by Kodak, which at that point was 90% of the industry. And so Joseph’s trying to make headway in the photography paper business and basically is just like get nowhere. No matter what he does, he just cannot seem to create traction. Dave Young: One of his problems, Stephen? Stephen Semple: Yeah. Dave Young: Haloid. Stephen Semple: Yeah, maybe. Dave Young: That’s not a good name. Stephen Semple: Yeah, maybe. But what he decides to do is look for new opportunities. He’s actively searching through the National Patent Archive. So meanwhile, we got to think about this. It’s the mid ’40s. World War II has recently ended and the GI Bill is out there and it’s really fueling the growth of service-based industries. Banking, insurance is exploding. White collar is becoming now the thing to do. The American office is now basically the new engine of the US economy, but it’s still pretty primitive and labor-intensive. You think about going back to your whole thing, how did you copy and share information? Things were typically retyped or it was typed with a carbon paper, which meant you had one copy or a single document. Dave Young: Yeah, like a mimeograph sort of a thing maybe. Stephen Semple: Yeah, yeah. Single document could take an hour. And secretaries were manually retyping documents using carbon paper which created smudges or like as you said, the mimeograph machines, which were clunky Dave Young: Or send it, I mean, if you need more of that, you send it off to a printer. You send it off to somebody that can load it up on a printing press. Stephen Semple: Yeah. And for the people who don’t remember mimeograph machines, because I barely remember them, they stank. Dave Young: They smelled wonderful. Stephen Semple: Oh God, they were foul. They were this like, oh my God. Dave Young: The teacher would come in with a stack of stuff and hand it out and everybody would smell it. You just put it up your face and inhale. Stephen Semple: It was instead of glute. Dave Young: Weird, weird purple-y ink. I don’t even know how it worked, but yeah. Stephen Semple: So anyway, so Joseph is searching through patent archives and he comes across this invention by Chester Carlson, who’s a physicist who has got really bad arthritis and was looking for a better way to make copies. And Carlson had created, I got to read this, created an electrophotographic apparatus for dry writing. A process he turned xerography. Dave Young: Xerography, yes. Stephen Semple: There we go. Dave Young: And Haloid finally has a better name. Stephen Semple: Exactly. But the prototype was clumsy. It was large. It had been rejected by lots of people, but it caught Wilson’s eye. He could see the potential to revolutionize the office. And so it’s 1946 and he makes this big gamble. He purchases the patent for $10,000. Dave Young: Wow, okay. Stephen Semple: At that time, Haloid’s annual revenues is just a little over 100 grand. Dave Young: All right, man. Stephen Semple: So that’s a big bet. Dave Young: Huge. Stephen Semple: And the challenge was he had to turn this clumsy prototype into a viable commercial product. And there were a lot of challenges including the high heat from the fuser. It’s basically a toaster oven inside of a unit that bakes toner onto paper. Dave Young: Yeah. It puts a hydrostatic image of whatever’s on the paper on a blank piece of paper and little tiny particles of toner stick to that image and then you bake them in. Stephen Semple: Yeah. Dave Young: The little tiny microplastic things. Stephen Semple: And yes, it can catch fire. More on this later. Dave Young: Yeah. That’s why when you’re done making a bunch of copies, it all comes out warm. Stephen Semple: Yeah, exactly. So to raise money, Wilson sold some personal stock. He downsized a factory, did a bunch of things, raised about $12 million, which would be equivalent to about 140 million today and put it into development. So in 1954, after nine years of development, he has the first copier. It weighs 650 pounds. Dave Young: Sure. Stephen Semple: And it’s called the Xerox 914 because it used 9×14 paper. Dave Young: 9×14, that’s a choice. Stephen Semple: Right. Dave Young: Okay. Stephen Semple: So in addition to the $12 million that they invested, they’ve also got millions of dollars in debt. Dave Young: I’m stuck on the 9×14, Stephen. I’m thinking it’s the size of an accounting ledger, something like that. Stephen Semple: I didn’t look into why that size or… Because again, a lot of times what becomes standards change. Dave Young: Yeah. But see, that’s why you do what you do on this podcast and I do what I do. I’d have gotten stuck researching this into the 9×14 and followed that off into the woods and it would be a whole different podcast. Stephen Semple: It would be. It would be probably better. Dave Young: Oh, I don’t know about that. Anyway, I interrupted you again. Stephen Semple: So they’ve invested all this money. They’re millions in debt. They finally got a prototype and they basically say, “Okay, here’s what we got to do. We got to find a production partner to make this happen because we’re not going to produce this thing.” Dave Young: 600 pounds, yeah. Stephen Semple: Because that’s not what we do. So Wilson approaches IBM who basically at that point is a rising tech leader. Dave Young: Sure. Stephen Semple: And a lot of people don’t realize how old IBM is. I’ve got a picture of an old IBM cheese cutting machine. Dave Young: Yes, yeah. Stephen Semple: They were around forever. But anyway- Dave Young: I did a college internship at IBM. Stephen Semple: Oh, did you really? Wow. Dave Young: Where they made copiers. Yeah, I got copiers. Stephen Semple: Oh yeah. Oh, this comes back. Dave Young: Yeah, yeah. Stephen Semple: So IBM’s being run by Thomas Watson Jr. and he rejects the idea because basically it’s going to be about a $10,000 price tag and it’s going to fill a room all just for copying. He thinks this is a really, really bad idea. So Wilson doubles down, mortgages everything to make it themselves and they’re still facing these huge challenges. They meet a guy who works with equipment manufacturer AMF who’s developed this brand new sales strategy that he’s using for selling bowling alley equipment. Dave Young: Oh, is this the lease purchase? Stephen Semple: Yes, sir. Yes. So this is this brand new idea. What they decide to do is to lease the Xerox 914 for $95 a year and it would include 2,000 copies plus a nickel for each additional copy. Dave Young: Okay. So they’re selling copies, not machines. Yes, yes, yes. Stephen Semple: Right. Dave Young: Yeah. Stephen Semple: Here’s where it gets funny. It’s September 1959. The Xerox 914 makes its public debut in Manhattan. And during the demonstration, the machine bursts in the flames. Dave Young: Perfect. I’ll take three. Stephen Semple: Well, here’s the funny thing is it becomes this spectacle. It attracts onlookers and in fact the event is a resounding success. Dave Young: Yes, because the smart people will go, “Oh, they’ll fix that.” Stephen Semple: Right. Dave Young: Look, the copies came out, but they’ll fix the fire thing. Stephen Semple: Here’s what they did. Instead of re-engineering the device, remember, this is the late ’50s. The world’s a different place. Instead of re-engineering device, Wilson’s team ingeniously packages it with a fire extinguisher that they rebrand as the scorch eliminator. Dave Young: Hell yeah. Stephen Semple: Honest to God, I cannot make this up. The scorch eliminator. Oh, instead of re-engineering it, we’ll just give everybody a free fire extinguisher. Dave Young: That’s fantastic. I love that. So you could fill the paper tray with dough and pizza would come out the other end. These guys are geniuses. Stephen Semple: It’s a year later. It’s the 1960s and the machine is now available nationwide and it’s like a resounding earth-shattering success. Dave Young: Stay tuned. We’re going to wrap up this story and tell you how to apply this lesson to your business right after this. [Using Stories To Sell] Dave Young: Let’s pick up our story where we left off and trust me, you haven’t missed a thing. Stephen Semple: It’s a year later. It’s the 1960s and the machine is now available nationwide and it’s like, a resounding earth-shattering success. Production basically started at 50 per month and quickly went to 100 a day. At the end of the first year, they leased 200,000 [inaudible 00:14:32]. Dave Young: Well, this whole story, this is proof of what a good idea it was. Stephen Semple: Oh, absolutely. Dave Young: People don’t care if it catches fire as long as I get some copies out of it. Stephen Semple: Yeah. And the copier room becomes a new social hub. It becomes the way we share jokes. Dave Young: You want to make sure it has some overhead sprinklers. Stephen Semple: Well, you’ve got the scorch eliminator. You’re good. The company gets officially renamed Xerox Corporation and really it launches the information revolution. The stock quadruples, revenue soared at 250 million. Now, remember IBM? Dave Young: Oh yeah, they come around. Stephen Semple: The guys who rejected the idea. So the number of copies being made annually in the United States surges from 20 million to over 9 billion with Xerox basically dominating. And IBM, remember, took a pass, but they decided to enter the business in the early 1970s. They create their own copier. Now- Dave Young: They figured out that they were the biggest customer of Xerox. Stephen Semple: Yeah, essentially. Yeah. Dave Young: Yeah. Stephen Semple: Now, Joseph had a choice at this point. He knew they were leveraging his technology, but he also knew that it would be hard for him to win on legal grounds alone. So what he decided that he needed to do was to out innovate them. Dave Young: Okay. Stephen Semple: And so what Joseph Wilson envisioned was an office of the future because he saw computers coming. Remember, this guy was a visionary. He saw computers coming. Dave Young: Oh, yeah. I love this guy. Stephen Semple: But the problem, computers were large, difficult to use, but he was like, “I saw what happened with the photocopier, it went from being massive to small. Computers, same thing’s going to happen.” Dave Young: Yeah, yeah. Stephen Semple: So he decided to invest the equivalent of $20 million to establish PARC, the Palo Alto Research Center. Now, he hired a top computer scientist from ARPA, Robert Taylor, and gave him a clear mandate, “Pull together the brightest folks and create the next technological revolution.” The goal was for it to be this visionary think tank to leapfrog everybody. Here’s what they created. Gary Bernier and I did another podcast on this, which talked about this failure of Xerox. And there’s something I didn’t realize until doing this research, which kind of filled in a blank. So I actually recommend people go back and listen to that podcast. But here’s what they created, networking, the mouse, and the graphical user interface. If Xerox had developed that today, Xerox would be the giant of the industry. Could you imagine? Dave Young: Did they also figure out printing to like laser printing? Stephen Semple: I’m not sure whether it was laser printing- Dave Young: I’m sure who- Stephen Semple: But they did invent the whole idea of what you see is what you get, like that whole idea that the screen… But I’m not sure whether it was laser or not. Dave Young: Basically, when I was at IBM, that’s what they were making, were photocopiers that were also laser printers. You could go photocopy something by standing at the machine or you could send a document to it and have it printed. Stephen Semple: And so here’s the interesting thing because I’d always wondered why did these things not get to market? And here’s what actually happened. Before these things were finally created in terms of prototype level, Wilson died and the executives who were basically under him took over and they didn’t have the vision and they saw the paperless office as cannibalizing their business. Kind of like Kodak. Remember Kodak developed all the stuff for digital cameras and went, “Oh, well, we can’t do this because it’s going to cannibalize our business.” Dave Young: Yeah. WYSIWYG, mouse. That’s not the business. Stephen Semple: Right. Well, and remember we did an episode a little while ago where we were talking about the iPhone and the brilliance of Steve Jobs. He was willing to cannibalize their own business to make that happen. When you’re unwilling to cannibalize your own business, you got a problem. This is the same thing that killed Kodak. It’s the thing Jobs overcame to create the iPhone. So speaking about Jobs, the idea for the Mac came from a visit at PARC. In 1979, Jobs negotiated a tour of PARC in exchange for allowing Xerox to invest in Apple’s pre-IPO stock. And basically Jobs saw all this stuff, saw the mouse, saw the graphical user interface and went, “Holy crap, this is the future. This is the future.” So again, when Gary and I did this episode talking about Xerox and the failure of Xerox and the success of, har, Palo Alto, I never realized the timing of the death of the founder. Dave Young: Yeah. Stephen Semple: And it explains so much in terms of the execs not getting the idea. He would’ve. Joseph would’ve. Dave Young: Oh, I think so. Yeah, for sure. Stephen Semple: He would’ve been all over it. And Xerox would be a different company today. Dave Young: Yeah. Pretty amazing. Stephen Semple: But the things that I really loved on this is, again, Joseph was looking, he saw this world trend. He was in the photo paper business and he saw this whole idea of a copier, but also greater than that, it wasn’t just the idea of the copier. He saw what was the importance of the office and what was going on in office space. And the other part that I loved, and then proactively went looking for innovative ideas. And the part that I really love the most is they didn’t let the fire stop them. Dave Young: I do. Yeah, that’s so great. I don’t know. Yeah, some people say that’s a negative, but here’s a fire extinguisher. Stephen Semple: Right. Now granted, it was the late 50s, early 60s, different era. Dave Young: Here’s the thing, Stephen, offices can be kind of boring. And if you can introduce the prospect that there’s going to be a fire down in the copy room every now and then, there’s something to talk about while you’re standing around the water cooler. So when I worked for- Stephen Semple: It’s a whole different thing of lighting a fire under people’s ass. Dave Young: Oh yeah, yeah. I keep an emergency bag of marshmallows in my desk drawer in the hope that the copier catches fire. I did my college internship at IBM. It was a paid internship. So I can legitimately say I worked for IBM back in the day. It was back in the day when they actually manufactured stuff. IBM made machines. Now they just… I don’t even know what they do. They consult? Do they- Stephen Semple: There’s still a lot of IBM technology in the backgrounds, like with servers and things along… How much they manufacture versus just license, that I don’t know. Dave Young: So they’re a software and consulting company and felt all of that. But in 1984 they were still manufacturing, I worked for their Boulder, Colorado plant and it was 5,000 people working there. Stephen Semple: Amazing. Dave Young: And they made floppy drives and printers and printer/copiers. So you could buy a photocopier/printer the size of a large deep freeze and they’d install it. And I think they probably same thing, probably same business model. You’d pay by the copy, you’d rent the machine. One of the coolest things was that they had a laboratory at that facility. And in the laboratory, they had a copier lab where they had Xerox and Canon and all the other competitors, they had machines installed. They would call Xerox and say, “Hey, we need a machine, bring it here, install it in the lab and we want the usual maintenance agreement. So you got to send a Xerox guy to come maintain this thing.” And they would run that machine all day long making test patterns. They would print test patterns all day long and then evaluate them, put them under the microscope, see where that machine was performing and how it performed against theirs. I mean, it was kind of a cool lab. Who does that? Stephen Semple: So the other thing I just want to add on Xerox before we finish off, because I forgot to mention this as one of the lessons and this is actually probably the most important lesson. And that is, they looked at the guy selling bowling alley equipment and did the leasing. That was brand new, but they did an interesting twist to it that I think can be overlooked in terms of the real power of what they did. Because sure, leasing made it easier to purchase, but there’s two additional things that they did that made it easy to purchase 2,000 copies included. Which meant immediately if you’re going, “I’m leasing this for 100 dollars a year, 2,000 copies. Oh, that means my copy is so many cents a copy.” Dave Young: And if I never make another copy, yeah. Stephen Semple: Right away I’m saving money. So it allows for the financial justification becomes really easy. But here’s the other thing that becomes wild is, when I put the machine in, I’m not saying to people, “Hey, be careful how much you use this.” My goal is I want 2,000 copies to happen. Once I create the habit of people creating copies, it’s now embedded in the business. Dave Young: And then you have bean counters that tell you… Yeah. Stephen Semple: Well, could you imagine how different it would be is if it was less money, $50.05 a copy, you’d be telling everybody, “Now be careful how often you copy.” Dave Young: Yeah, but even then they were. Stephen Semple: Right, no, but the point is it allowed the habit. It allowed the habit to happen. It was just because you wanted to use up the 2,000, 2,000 copies. So anyway, I just think there was brilliant, especially for brand new technology, a brilliance in terms of how they structured that lease. Dave Young: They found an interesting business model to copy- Stephen Semple: They did. Dave Young: In a completely unrelated field. Stephen Semple: They did. Dave Young: And that’s the benefit of getting outside of your category to look for innovation. Stephen Semple: And then put a twist on it that eliminated friction of using that equipment because the first 2,000 copies were free. Anyway, I just thought it was brilliant. I just wanted to point that out. Dave Young: Yeah. I love, what was his name again, Wells? Stephen Semple: Joseph Wilson. Dave Young: Wilson. Well, I know there’s a W in there. Joseph Wilson. Stephen Semple: Yeah, Joseph Wilson. Yeah. Dave Young: All right. It was a good he didn’t name it Wilsonography. But I love it. I love the Xerox story. Thank you, Stephen. Stephen Semple: All right. Awesome. Thanks, David. Dave Young: Thanks for listening to the podcast. Please share us, subscribe on your favorite podcast app and leave us a big, fat, juicy five star rating and review at Apple Podcasts. And if you’d like to schedule your own 90 minute empire building session, you can do it at empirebuildingprogram.com.

Episode 487 of the Lens Shark Photography Podcast In This Episode If you subscribe to the Lens Shark Photography Podcast, please take a moment to rate and review us to help make it easier for others to discover the show. Sponsors: - Build Your Legacy with Fujifilm. Latest savings at FujfilmCameraSavings.com - Shop with the legends at RobertsCamera.com, and unload your gear with UsedPhotoPro.com - 20% OFF with code SHARKY2026 at BenroUSA.com - Calibrate's big WYSIWYG savings! - More mostly 20% OFF codes at LensShark.com/deals. Stories: Sony unveils its a7R VI. (#) The new Sony FE 100-400mm f/4.5 GM OSS. (#) Maven's ingenious way to control these. (#) Brightin Star's fisheye is a funk buster. (#) This camera does it again. (#) Nikon breaks a record you don't want to break. (#) Meike's 56mm f/1.7. (#)   Connect With Us Thank you for listening to the Lens Shark Photography Podcast! Connect with me, Sharky James on Twitter, Instagram Vero, and Facebook (all @LensShark).

What do a teenager with swimming goggles, a half-eaten Nutella cruffin, and a 20yr old x-ray result all have in common? They all turned up in one conversation with my daughter Tiana, and every single one of them broke my brain a little.Have you seen any kids wandering around shopping centres with swimming goggles around their necks? We can explain it! We also talk about a kinda secret (and awesome) thing that Baker's Delight do, doll hospitals, TLDR, WYSIWYG, and how I've somehow spent my entire life not questioning something that's actually very obviously wrong with my body!Today's episode has lots of laughs and a bunch of things you may have never known about!

The first, and most obvious reason is the money issue (and we're not just talking about the CAMERA cost) and then there's the faster memory cards, computer (yes, you can do proxies) and more...but what we're really talking about here is keeping things low-stress, simple, and WYSIWYG...

Episode 486 of the Lens Shark Photography Podcast In This Episode If you subscribe to the Lens Shark Photography Podcast, please take a moment to rate and review us to help make it easier for others to discover the show. Sponsors: - Build Your Legacy with Fujifilm. Latest savings at FujfilmCameraSavings.com - Shop with the legends at RobertsCamera.com, and unload your gear with UsedPhotoPro.com - 20% OFF with code SHARKY2026 at BenroUSA.com - Calibrate's big WYSIWYG savings! - More mostly 20% OFF codes at LensShark.com/deals. Stories: The new, affordable Godox LE200D. (#) Brightin Star's 11mm funk buster. (#) Think Tank's PhotoCross v2 sling. (#) Fujifilm's two newest Fujikina events. (#) Amaran's new, affordable Halo series. (#) TTArtisan's AF 17mm f/1.8 Air. (#) A 31.5" Eizo. (#)   Connect With Us Thank you for listening to the Lens Shark Photography Podcast! Connect with me, Sharky James on Twitter, Instagram Vero, and Facebook (all @LensShark).

I speak with Ewelina Kurtys about Final Spark, a company building a bioprocessor, which they believe will enhance AI growth with no energy restrictions. Want the power of Mermaid for enterprises? Mermaid chart brings WYSIWYG editing, generative AI, collaboration, and more to the flexible syntax of Mermaid. https://go.chrischinchilla.com/mermaid For show notes and an interactive transcript, visit chrischinchilla.com/podcast/To reach out and say hello, visit chrischinchilla.com/contact/To support the show for ad-free listening and extra content, visit chrischinchilla.com/support/ Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

Pour de nombreux développeurs web, intégrer un véritable éditeur de documents compatible avec Microsoft Word dans une application en ligne relève souvent du casse-tête. Les solutions existantes reposent généralement sur des systèmes lourds côté serveur ou sur des services propriétaires via des API payantes, ce qui peut rapidement devenir coûteux et complexe à déployer. Un nouveau projet open source pourrait toutefois simplifier les choses. Il s'appelle docx-js-editor, et il propose une approche différente : permettre d'ouvrir, modifier et enregistrer des fichiers .docx directement dans le navigateur, sans passer par un serveur distant.Le principe repose sur un éditeur dit WYSIWYG, acronyme de What You See Is What You Get — littéralement « ce que vous voyez est ce que vous obtenez ». Autrement dit, le document affiché à l'écran correspond exactement au résultat final, comme dans un traitement de texte classique. La particularité de cet outil est qu'il a été conçu spécifiquement pour l'environnement React, une bibliothèque très populaire utilisée pour construire des interfaces web modernes. Toute la phase d'édition se fait localement sur l'ordinateur de l'utilisateur, dans le navigateur lui-même. Résultat : les documents ne sont pas envoyés vers un serveur externe pour être traités, ce qui peut représenter un avantage en matière de confidentialité des données.Sur le plan technique, l'éditeur repose sur une architecture proche de ProseMirror, un moteur open source utilisé pour créer des éditeurs de texte complexes sur le web. Cela permet notamment d'ajouter facilement des plugins, c'est-à-dire des modules complémentaires qui étendent les fonctionnalités de l'outil. Contrairement à certains éditeurs web qui convertissent les documents Word de manière approximative, la gestion du format DOCX est ici intégrée directement dans le cœur du système. L'objectif est de maintenir une compatibilité maximale avec les fichiers créés dans Microsoft Word.Dans les fonctionnalités de base, on retrouve l'essentiel d'un traitement de texte : mise en forme du texte — gras, italique, polices et couleurs — insertion d'images, création de tableaux ou encore gestion des hyperliens. L'outil se veut également extensible. Par exemple, un plugin permet de surligner automatiquement les balises utilisées par Docxtemplater, un système souvent employé pour générer automatiquement des documents comme des factures, des contrats ou des rapports à partir de modèles. Distribué sous licence MIT, l'une des licences open source les plus permissives, docx-js-editor pourrait donc intéresser les développeurs qui cherchent une solution légère pour intégrer l'édition de documents Word dans leurs applications web, sans avoir recours à des infrastructures complexes ou à des services payants. Hébergé par Acast. Visitez acast.com/privacy pour plus d'informations.

Introducing Rob Ruiz Meet Rob Ruiz, a seasoned Senior Full Stack Developer with nearly two decades of expertise in WordPress innovation and open-source magic. As the Lead Maintainer of WP Rig since 2020, Rob has been the driving force behind this groundbreaking open-source framework that empowers developers to craft high-performance, accessible, and progressively enhanced WordPress themes with ease. WP Rig isn’t just a starter theme—it’s a turbocharged toolkit that bundles modern build processes, linting, optimization, and testing to deliver lightning-fast, standards-compliant sites that shine on any device. Show Notes For more on Rob and WP Rig, check out these links: LinkedIn Profile: https://www.linkedin.com/in/robcruiz WP Rig Official Site: https://wprig.io GitHub Repository: https://github.com/wprig/wprig Latest Releases: https://github.com/wprig/wprig/releases WP Rig 3.1 Announcement: https://wprig.io/wp-rig-3-1/ Transcript: Topher DeRosia: Hey everybody. Welcome to Hallway Chats. I’m your host Topher DeRosia, and with me today I have- Rob Ruiz: Rob Ruiz. Topher: Rob. You and I have talked a couple of times, once recently, and I learned about a project you’re working on, but not a whole lot about you. Where do you live? What do you do for a living? Rob: Yeah, for sure. Good question. Although I’m originally from Orlando, Florida, I’ve been living in Omaha, Nebraska for a couple of decades now. So I’m pretty much a native. I know a lot of people around here and I’ve been fairly involved in various local communities over the years. I’m a web developer. Started off as a graphic designer kind of out of college, and then got interested in web stuff. And so as a graphic designer turned future web developer, I guess, I was very interested in content management systems because it made the creating and managing of websites very, very easy. My first couple of sites were Flash websites, sites with macro media Flash. Then once I found content management systems, I was like, “Wow, this is way easier than coding the whole thing from scratch with Flash.” And then all the other obvious benefits that come from that. So I originally started with Joomla, interestingly enough, and used Joomla for about two or three years, then found WordPress and never looked back. And so I’ve been using WordPress ever since. As the years have gone on, WordPress has enabled me to slowly transition from a more kind of web designer, I guess, to a very full-blown web developer and software engineer, and even software architect to some degree. So here we are many years later. Topher: There’s a big step from designer to developer. How did that go for you? I’m assuming you went to PHP. Although if you were doing Flash sites, you probably learned ActionScript. Rob: Yeah. Yeah. That was very convenient when I started learning JavaScript. It made it very easy to learn JavaScript faster because I already had a familiarity with ActionScript. So there’s a lot of similarities there. But yeah. Even before I started doing PHP, I started learning more HTML and CSS. I did do a couple of static websites between there that were just like no content management system at all. So I was able to kind of sharpen my sword there with the CSS and HTML, which wasn’t particularly hard. But yeah, definitely, the PHP… that was a big step was PHP because it’s a proper logical programming language. There was a lot there I needed to unpack, and so it took me a while. I had to stick to it and really rinse and repeat before I finally got my feet under me. Topher: I can imagine. All right. So then you work for yourself or you freelance or do you have a real job, as it were? Rob: Currently, I do have a real job. Currently, I’m working at a company called Bold Orange out of Minneapolis. They’re a web agency. But I kind of bounce around from a lot of different jobs. And then, yes, I do freelance on the side, and I also develop my own products as well for myself and my company. Topher: Cool. Bold Orange sounds familiar. Who owns that? Rob: To be honest, I don’t know who the owners are. It’s just a pretty big web agency out of Minneapolis. They are a big company. You could just look them up at boldorange.com. They work for some pretty big companies. Topher: Cool. All right. You and I talked last about WP Rig. Give me a little background on where that came from and how you got it. Rob: Yeah, for sure. Well, there was a period of time where I was working at a company called Proxy Bid that is in the auction industry, and they had a product or a service — I don’t know how you want to look at that —called Auction Services. That product is basically just building WordPress sites for auction companies. They tasked us with a way to kind of standardize those websites essentially. And what we realized is that picking a different theme for every single site made things difficult to manage and increase tech debt by a lot. So what we were tasked with was, okay, if we’re going to build our own theme that we’re just going to make highly dynamic so we can make it look different from site to site. So we want to build it, but we want to build it smart and we want to make it reusable and maintainable. So let’s find a good framework to build this on so that we can maintain coding standards and end up with as little tech debt as possible, essentially. That’s when I first discovered WP Rig. In my research, I came across it and others. We came across Roots Sage and some of the other big names, I guess. It was actually a team exercise. We all went out and looked for different ones and studied different ones and mine that I found was WP Rig. And I was extremely interested in that one over the other ones. Interestingly enough- Topher: Can you tell me why over the other ones? Rob: That’s a great question. Yeah. I really liked the design patterns. I really liked the focus on WordPress coding standards. So having a system built in that checked all the code against WordPress coding standards was cool. I loved the compiling transpiling, whatever, for CSS and JavaScript kind of built in. That sounded really, really interesting. The fact that there was PHP unit testing built into it. So there’s like a starter testing framework built in that’s easy to extend so that you can add additional unit tests as your theme grows. We really wanted to make sure… because we were very into CICD pipelines. So we wanted to make sure that as developers were adding or contributing to any themes that we built with this, that we could have automated tests run and automated builds run, and just automate as much as possible. So WP rig just seemed like something that gave us those capabilities right out of the box. So that was a big thing. And I loved the way that they did it. Roots Sage does something similar, but they use their blade templating engine built in there. We really wanted to stick to something that was a bit more standard WordPress so that there wasn’t like a large knowledge overhead so that we didn’t have to say like, okay, if we’re bringing on other developers, like junior developers work on it, oh, it would be nice if you use Laravel too because we use this templating engine in all of our themes. We didn’t want to have to worry about that essentially. It was all object-oriented and all that stuff too. That’s what looked interesting to me. We ended up building a theme with WP Rig. I don’t know what they ended up doing with it after that, because I ended up getting let go shortly thereafter because the company had recently been acquired. Also, this was right after COVID too. So there was just a lot of moving parts and changing things at the time. So I ended up getting let go. But literally a week after I got let go, I came across a post on WP Tavern about how this framework was looking for new maintainers. Basically, this was a call put out by Morton, the original author of WP Rig. He reached out to WP Tavern and said, “Look, we’re not interested in maintaining this thing anymore, but it’s pretty cool. We like what we’ve built. And so we’re looking for other people to come in and adopt it essentially.” So I joined a Zoom meeting with a handful of other individuals that were also interested in this whole endeavor, and Morton reached out to me after the call and basically just said, “I looked you up. I liked some of the input that you had during the meeting. Let’s talk a little bit more.” And then that eventually led to conversations about me essentially taking the whole project over entirely. So, the branding, the hosting of the website, being lead maintainer on the project. Basically, gave me the keys to the kingdom in terms of GitHub and everything. So that’s how it ended up going in terms of the handoff between Morton and I. And I’m very grateful to him. They really created something super cool and I was honored to take it over and kind of, I don’t know, keep it going, I guess. Topher: I would be really curious. I don’t think either of us have the answer. I’d be curious to know how similar that path is to other project handoffs. It’s different from like an acquisition. You didn’t buy a plugin from somebody. It was kind of like vibes, I guess. Rob: It was like vibes. It was very vibey. I guess that’s probably the case in an open source situation. It’s very much an open source project. It’s a community-driven thing. It’s for everybody by everybody. I don’t know if all open source community projects roll like that, but that’s how this one worked out. There was some amount of ownership on Morton’s behalf. He did hire somebody to do the branding for WP Rig and the logo. And then obviously he was paying for stuff like the WPrig.io domain and the hosting through SiteGround and so on and so forth. So, we did have to transfer some of that and I’ve taken over those, I guess, financial burdens, if you want to think of it like that. But I’m totally okay with it. Topher: All right. You sort of mentioned some of the things Rig does, compiling and all that kind of stuff. Can you tell me… we didn’t discuss this before. I’m sitting at my desk and I think I want a website. How long does it take to go from that to looking at WordPress and logging into the admin with Rig? Rob: Okay. Rig is not an environment management system like local- Topher: I’m realizing my mistake. Somebody sends me a design in Figma. How long does it take me to go from that to, I’m not going to say complete because I mean, that’s CSS, but you know, how long does it take me to get to the point where I’m looking at a theme that is mine for the client that I’m going to start converting? Rob: Well, if you’re just looking for a starting point, if you’re just like, okay, how long does it take to get to like, okay, here’s my blank slate and I’m ready to start adopting all of these rules that are set up in Figma or whatever, I mean, you’re looking at maybe 5 minutes, 10 minutes, something like that. It’s pretty automated. You just need some simple knowledge of Git. And then there are some prerequisites to using WP Rig. You do have to have composer installed because we do leverage some Composer packages to some of it, although to be honest, you could probably get away with not using Composer. You just have to be okay with sacrificing some of the tools the WP Rig assumes you’re going to have. And then obviously Node. You have to have Node installed. A lot of our documentation assumes that you have NPM, that you’re using NPM for all your Nodes or your package management. But we did recently introduce support for Bun. And so you can use Bun instead of NPM, which is actually a lot faster and better in many ways. Topher: Okay. A lot of my audience are not developers, users, or light developers, like they’ll download a theme, hack a template, whatever. Is this for them? Am I boring those people right now? Rob: That’s a great question. I mean, and I think this is an interesting dichotomy and paradigm in the WordPress ecosystem, because you’ve got kind of this great divide. At least this is something I’ve noticed in my years in the WordPress community is you have many people that are not coders or developers that are very interested in expanding their knowledge of WordPress, but it’s strictly from a more of a marketing perspective where it’s like, I just want to know how to build websites with WordPress and how to use it to achieve my goals online from a marketing standpoint. You have that group of people, and then you have this other group of people that are very developer centric that want to know how to extend WordPress and how to empower those other people that we just discussed. Right? Topher: Right. Rob: So, yeah, that’s a very good question. I would say that WP Rig is very much designed for the developers, not for the marketers. The assumption there is that you’re going to be doing some amount of coding. Now, can you get away with doing a very light amount of coding? Yes. Yes, you can. I mean, if you compare what you’re going to get out of that assumed workflow to something that you would get off like Theme Forest or whatever, it’s going to be a night and day difference because those theme, Forest Themes, have hours, hundreds, sometimes hundreds of hours of development put into them. So, you’re not going to just out of the box immediately get something that is comparable to that. Topher: You need to put in those hundreds of hours of development to make a theme. Rob: As of today, yes. That may change soon though. Topher: Watch this space. Rob: That’s all I’ll say. Topher: Okay. So now we know who it’s for. I’m assuming there’s a website for it. What is it? Rob: Yeah. If you go to WPrig.io, we have a homepage that shows you all the features that are there in WP Rig. And then there’s a whole documentation area that helps people get up and running with WP Rig because there is a small learning curve there that’s pretty palatable for anybody who’s familiar with modern development workflows. So that is a thing. So the type of person that this is designed for anybody that wants to make a theme for anything. Let’s say you’re a big agency and you pull in a big client and that client wants something extremely custom and they come to you with Figma designs. Sure, you could go out there and find some premium theme and try to like child theme and overhaul that if you want. But in many situations, I would say in most situations, if you’re working from a Figma design that’s not based off of another theme already that’s just kind of somebody else’s brainchild, then you’re probably going to want to start from scratch. And so the idea here is that this is something to replace an approach, like underscores an approach. Actually, WP Pig was based off of underscores. The whole concept of it, as Morton explained it to me, was that he wanted to build an underscores that was more modern and full-featured from a development standpoint. Topher: Does it have any opinions about Gutenberg? Rob: It does now, but it did not when I took it over because Gutenberg did not exist yet when I took over WP Rig. Topher: Okay. What are its opinions? Rob: Yeah, sure. The opinion right out of the gate is that you can use Gutenberg as an editor and it has support like CSS rules in it for the standard blocks. So you should be able to use regular Gutenberg blocks in your theme and they should look just fine. There’s no resets in there. It doesn’t start from scratch. There’s not a bunch of styling you have to do for the blocks necessarily. Now, if you go to the full site editing or block-based mentality here, there are some things you need to do in WP Rig to convert the out-of-the-box WP Rig into another paradigm essentially. Right when you pull WP Rig, the assumption is you’re building what most people would refer to as a hybrid theme. The theme supports API or whatever, and the assumption is that you’re not going to be using the site editor. You’re just going to kind of do traditional WordPress, but you might be using Gutenberg for your content. So you’re just using Gutenberg kind of to author your pages and your posts and stuff like that, but not necessarily the whole site. WP Rig has the ability to kind of transform itself into other paradigms. So the first paradigm we built out was the universal theme approach. And the idea there is that you get a combination of the full site editing capabilities. But then you also have the traditional menu manager and the settings customizer framework or whatever is still there, right? These are things that don’t exist in a standard block-based theme. So I guess an easy example would be like the 2025 WordPress theme that comes right out of the box. It comes installed in WordPress. That is a true block-based theme, not a universal theme. So it doesn’t have those features because the assumption there is that it doesn’t need those features. You can kind of transform WP Rig into a universal theme that’s kind of a hybrid between a block-based and a classic theme. And then it can also transform into a strictly block-based theme as well. So following the same architecture as like the WordPress 2025 theme or Ollie or something like that is also a true block-based theme as well. So you can easily convert or transform the starting point of WP Rig into either of those paradigms if that’s the type of theme you’re setting out to build. Topher: Okay. That sounds super flexible. How much work is it to do that? Rob: It’s like one command line. Previously we had some tutorials on the website that showed you step-by-step, like what you needed to change about the theme to do that. You would have to add some files, delete some files, edit some code, add some theme supports into the base support class and some other stuff. I have recently, as of like a year and a half ago or a year ago, created a command line or a command that you can type into the command line that basically does that entire conversion process for you in like the blink of an eye. It takes probably a second to a second and a half to perform those changes to the code and then you’re good to go. It is best to do that conversion before you start building out your whole theme. It’s not impossible to do it after. But you’re more likely to run into problems or conflicts if you’ve already set out building your whole theme under one paradigm, and then you decide how the project you want to switch over to block-based or whatever. You’re likely to run into the need to refactor a bunch of stuff in that situation. So it is ideal to make that choice extremely early on in the process of developing your theme. But either way it’ll still work. That’s just one of the many tools that exist in WP Rig to transform it or convert it in several ways. That’s just one example. There are other examples of ways that Rig kind of converts itself to other paradigms as well. Topher: Yeah. All right. In my development life, I’ve had two parts to it. And one is the weekend hobbyist, or I download cadence and I whip something up in 20 minutes because I just want to experiment and the other is agency life where everything’s in Git, things are compiled, there are versions, blah, blah, blah. This sounds very friendly to that more professional pathway. Rob: Absolutely. Yes. Or, I mean, there’s another situation here too. If you’re a company who develops themes and publishes them to a platform like ThemeForest or any other platform, perhaps you’re selling themes on your own website, whatever, if you’re making things for sale, there’s no reason you couldn’t use WP Rig to build your themes. We have a bundle process that bundles your theme for publication or publishing. Whether you’re an agency or whether you’re putting your theme out for sale, it doesn’t matter, during that bundle process, it does actually white label the entire code base to where there’s no mention of WP Rig in the code whatsoever. Let’s say you were to build a theme that you wanted to put up for sale because you have some cool ideas. Say, page transitions now are completely supported in all modern or in most modern browsers. And when I say print page transitions, for those that are in the know, I am talking about not single page app page transitions, but through website page transitions. You can now do that. Let’s say you were like, “Hey, I’m feeling ambitious and I want to put out some new theme that comes with these page transitions built in,” and that’s going to be fancy on ThemeForest when people look at my demo, people might want to buy that. You could totally use WP Rig to build that out into a theme and the bundle process will white label all of the code. And then when people buy your theme and download that code, if they’re starting to go through and look through your code, they’re not going to have any way of knowing that it was built with WP Rig unless they’re familiar with the base WP Rig architecture, like how it does its object-oriented programming. It might be familiar with the patterns that it’s using and be able to kind of discern like, okay, well, this is the same pattern WP Rig uses, so high likelihood it was built with WP Rig. But they’re not going to be able to know by reading through the code. It’s not going to say WP Rig everywhere. It’s going to have the theme all over the place in the code. Topher: Okay. So then is that still WP Rig code? It just changed its labels? Rob: Yeah. Topher: So, it’s not like you’re exporting HTML, CSS and JavaScript? The underlying Rig framework is still there. Rob: Yeah. During the bundle process, it is bundling CSS and HTML. Well, HTML in the case of a block-based theme. But, yeah, it is bundling your PHP, your CSS, your JavaScript into the theme that you’re going to let people download when they buy it, or that you’re going to ship to your whatever client’s website. But all that code is going to be transpiled. In the case of CSS and JavaScript, there’s only going to be minified versions of that code in that theme. The source code is not actually going to be in there. Topher: This sounds pretty cool. You mentioned some stuff might be coming. You don’t have to tell me what it is, but do you have a timeline? When should we be watching for the next cool thing from Rig? Rob: Okay, cool. Well, I’m going to keep iterating on Rig forever. Regardless of any future products that might be built on WP Rig, WP Rig will always and forever remain an open source product for anybody to use for free and we, I, and possibly others in the future will continue to update it and support it over time. We just recently put out 3.1. You could expect the 3.2 anytime in the next six months to a year, probably closer to six months. One feature I’m looking at particularly closely right now is the new stuff coming out in version 6.9 of WordPress around the various APIs that are there. I think one of them is called the form… There’s a field API and a form API or view API or something like that. So WP Rig comes with a React-based settings framework in it. So if you want your theme to have a bunch of settings in it to make it flexible for whoever buys your theme, you can use this settings framework to easily create a bunch of fields, and then that framework will automatically manage all your fields and store all the data from those fields and make it easy to retrieve the values of the input on those fields, without knowing any React at all. Now, if you know React, you can go in there and, you know, embellish what’s already there, but it takes a JSON approach. So if you just understand JSON, you can go in and change the JSON for the framework, and that will automatically add fields into the settings framework. So you don’t even have to know React to extend the settings page if you want. That will likely get an overhaul using these new APIs being introduced into Rig. Topher: All right. How often have you run into something where, “Oh, look, WordPress has a new feature, I need to rebuild my system”? Rob: Over the last four or five years, it’s happened a lot because, yeah, I mean, like I said, when I first took this thing over, Gutenberg had not even been introduced yet. So, you had the introduction of Gutenberg and blocks. That was one thing. Then this whole full site editing became a thing, which later became the site editor. So that became a whole thing. Then all these various APIs. I mean, it happens quite frequently. So I’ve been working to keep it modern and up to date over the past four years and it’s been an incredible learning experience. It not only keeps my WordPress knowledge extremely sharp, but I’ve also learned how various other toolkits are built. That’s been the interesting thing. From a development standpoint, there’s two challenges here. One of the challenges is staying modern on the WordPress side of things. For instance, WordPress coding standards came out with a version 3 and then a version 3.1 about two years ago. I had to update WP Rig to leverage those modern coding standards. So that’s one example is as WordPress changes, the code in WP Rig also needs to change. Or for instance, if new CSS standards change, right, new CSS properties come out, it is ideal for the base CSS in WP Rig, meaning the CSS that you get right out of the box with it, comes with some of these, for instance, CSS grid, Flexbox, stuff like that. If I was adopting a theme framework to build a theme on, I would expect some of that stuff to be in there. And those things were extremely new when I first took over WP Rig and were not all baked in there essentially. So I’ve had to add a lot of that over time. Now there’s another side to this, which is not just keeping up with WordPress and CSS and PHP, 8. whatever, yada yada yada. You’ve also got the toolkit. There are various node packages and composer packages of power WP Rig and the process in which it does the transpiling, the bundling, the automated manipulation of your code during various aspects of the usage of WP Rig is a whole nother set of challenges because now you have to learn concepts like, well, how do I write custom node scripts? Right? Like there were no WP CLI commands built into WP Rig when I first took it over. Now there’s a whole list. There’s a whole library of WP CLI commands that come in Rig right out of the gate. And so I’ve had to learn about that. So just various things that come with knowing how do you automate the process of converting code, that’s something that was completely foreign to me when I first took over WP Rig. That’s been another incredible learning experience is understanding like what’s the difference between Webpack and Gulp. I didn’t know, right? I would tell people I’m using Gulp and WP Rig and they would be like, “Well, why don’t you just use Webpack?” and I would say, “I don’t know. I don’t know what the difference is.” So over time I could figure out what are the differences? Why aren’t we using Webpack? And I’m glad I spent some time on that because it turns out Webpack is not the hottest thing anymore, so I just skipped right over all that. When I overhauled for version 3, we’re now not using Gulp anymore as of 3.1. We’re now using more of a Vite-like process, far more modern than Webpack and far better and faster and sleeker and lighter. I had to learn a bunch about what powers Vite. What is Vite doing under the hood that we might be able to also do in WP Rig, but do it in a WordPress way. Because Vite is a SaaS tool. If you’re building a SaaS, like React with a… we’re not a SaaS. I guess a spa is a better term to use here. If you’re building a single page application with React or view or belt or whatever, right, then knowing what Vite is and just using Vite right out of the box is perfect. But it doesn’t translate perfectly to WordPress land because WordPress has its own opinions. And so I did have to do some dissecting there and figure out what to keep and what to not keep to what to kind of set aside so that WordPress can keep doing what WordPress does the way WordPress likes to do it, but also improve on how we’re doing some of the compiling and transpiling and the manipulation of the code during these various. Topher: All right. I want to pivot a little bit to some personal-ish questions. Rob: Okay. Topher: This is a big project. I’m sure it takes up plenty of your time. How scalable is that in your life? Do you want to do this for the rest of your life? Rob: That’s a fantastic question. I don’t know about the rest of my life. I mean, I definitely want to do web development for the rest of my life because the web has, let’s be honest, it’s transformed everyone’s way of life, whether you’re a web developer or not. You know, the fact that we have the internet in our pocket now, you know, it has changed everything. Apps, everything. It’s all built on the web. So I certainly want to be involved in the web the rest of my life. Do I want to keep doing WordPress the rest of my life? I don’t know. Do I want to keep doing WP Rig the rest of my life? I don’t know. But I will say that you bring up a very interesting point, which is it does take up a lot of time and also trust in open source over the past four or five years I would argue has diminished a little bit as a result of various events that have occurred over the past two or three years. I mean, we could cite the whole WP Engine Matt Mullerwig thing. We can also cite what’s going on with Oracle and JavaScript. Well, I mean, there’s many examples of this. I mean, we can cite the whole thing that happened… I mean, there’s various packages out there that are used and developed and open source to anybody, and some of them are going on maintained and it’s causing security vulnerabilities and degradation and all this stuff. So it’s a very important point. One thing I started thinking about after considering that in relation to WP Rig was I noticed that there’s usually a for-profit arm of any of these frameworks that seems to extend the lifespan of it. Let’s just talk about React, for example, React is an open source JavaScript framework, but it’s used by Facebook and Facebook is extremely for-profit. So companies that are making infrastructural or architectural decisions, they will base their choice on whether or not to use a framework largely on how long they think this framework is going to remain relevant or valid or maintained, right? A large part of that is, well, is there a company making money off of this thing? Because if there is, the chances- Topher: They’re going to keep doing that. Rob: They’re going to keep doing it. It’s going to stay around. That’s good. I think that’s healthy. A lot of people that like open source and want everything to be free, they might look at something like that and say like, well, I don’t want you to make a paid version of it or there shouldn’t be a pro version. I think that’s a very short-sighted way of looking at that software and these innovations. I think a more experienced way of looking at it is if you want something to remain relevant and maintained for a long period of time, having a for-profit way in which it’s leveraged is a very good thing. I mean, let’s be real. Would WordPress still be what it is today if there wasn’t a wordpress.com or if WooCommerce wasn’t owned by Automattic or whatever, right? They’ll be on top. I mean, it’s obviously impossible to say, but my argument would be, probably not. I mean, look at what’s happened to the other content management systems out there. You know, Joomla Drupal. They don’t really have a flourishing, you know, paid pro service that goes with their thing that’s very popular, at least definitely not as popular as WordPress.com or WordPress VIP or some of these other things that exist out there. And so having something that’s making and generating money that can then contribute back into it the way Automattic has been doing with WordPress over these years has, in my opinion, been instrumental. I mean, people can talk smack about Gutenberg all they want, but let’s be real, it’s 2025, would you still feel that WordPress is an elegant solution if we were still working from the WYSIWYG and using the classic editor? And I know a lot of people are still using the classic editor and there’s classic for us, the fork and all that stuff. But I mean, that only makes sense in a very specific implementation of WordPress, a very specific paradigm. If you want to explore any of these other paradigms out there, that way of thinking about WordPress kind of falls apart pretty quickly. I, for one, am happy that Gutenberg exists. I’m very happy that Automattic continues. And I’m grateful, actually, that Automattic continues to contribute back into WordPress. And not just them, obviously there’s other companies, XWP, 10Up, all these other companies are also contributing as well. But I’m very grateful that this ecosystem exists and that there’s contribution going back in and it’s happening from companies that are making money with this. And I think that’s vital. All that to say that WP Rig may and likely will have paid products in the future that leverage WP Rig. So that’s not to say that WP Rig will eventually cost money. That’s just to say that eventually people can expect other products to come out in the future that will be built on WP Rig and incentivize the continued contributions back into WP Rig. The open source version of WP Rig. Topher: That’s cool. I think that’s wise. If you want anything to stay alive, you have to feed it. Rob: That’s right. Topher: I had some more questions but I had forgotten them because I got caught up in your answer. Rob: Oh, thank you. I’ll take that as a compliment. I mean, my answer was eloquent. But I’m happy to expand on anything, know you, WordPress related, me related, you know, whether it comes to the ecosystem in WordPress, the whole WordCamp meetup thing is very interesting. I led the WP Omaha meetup for many years here in Omaha, Nebraska and I also led the WordCamp, the organizing of WordCamp here in Omaha for several years as well. That whole community, the whole ecosystem, at least in America seems to have largely fallen apart. I don’t know if you want to talk about that at all. But yeah, I’m ready to dive into any topics. Topher: I’m going to have one more question and then we’re going to wrap up. And it was that you were talking about all the things you had to learn. I’m sure there were nights where you were looking at your computer thinking, “Oh man, I had it working, now I gotta go learn a new thing.” I would love for you to go back in time and blog all of that if you would. But given that you can’t, I would be interested in a blog moving forward, documenting what you’re learning, how you’re learning it and starting maybe with a post that’s summarizes all of that. Obviously, that’s up to you and how you want to spend your time, but I think it’d be really valuable to other people starting a project, picking up somebody else’s project to see what the roadmap might look like. You know what I mean? Rob: For sure. Well, I can briefly summarize what I’ve learned over the years and where I’m at today with how I do this kind of stuff. I will say that a lot of the improvements to WP Rig that have happened over the last year or two would not be possible without the advent of AI. Topher: Interesting. Rob: That’s a fancy way of saying that I have been by coding a lot of WP Rig lately. If you know how to use AI, it is extremely powerful and it can help you do many things very quickly that previously would have taken much longer or more manpower. So, yeah, perhaps if there was like five, six, seven people actively, excuse me, actively contributing to WP Rig, then this type of stuff would have been possible previously, but that’s not the case. There is one person, well, one main contributor to WP Rig today and you’re talking to them. There are a handful of other people that have been likely contributing to WP Rig over the versions and you can find their contributions in the change log file in WP Rig. But those contributions have been extremely light compared to what I’ve been doing. I wouldn’t be able to do any of it without AI. I have learned my ability to learn things extremely rapidly has ramped up tenfold since I started learning how to properly leverage LLMs and AI. So that’s not to say that like, you know, WP Rig, all the code is just being completely written by AI and I’m just like. make it better, enter, and then like WP Rig is better. I wish it was that easy. It’s certainly not that. But when I needed to start asking some of these vital questions that I really didn’t have anyone to turn to to help answer them, I was able to turn to AI. For instance, let’s go back to the Webpack versus Gulp situation. Although Gulp is no longer used in WP Rig, you know, it was used in WP Rig until very recently. So I had to understand like, what is this system, how does it work, how do I extend it and how do I update it and all these things, right? And why aren’t we using WebPack and you know, is there validity to this criticism behind you should use webpack instead of Gulp or whatever, right? I was able to use AI to ask these questions and be able to get extremely good answers out of it and give me the direction I needed to make some of these kind of higher level decisions on like architecturally where should WP Rig go? It was through these virtual conversations with LLMs that I was able to refine the direction of WP Rig in a direction that is both modern and forward-thinking and architecturally sound. I learned a tremendous amount from AI about the architecture, about the code, about all of it. My advice to anybody that wants to extend their skill set a little bit in the development side of things is to leverage this new thing that we have in a way that is as productive as possible for you. So that’s going to vary from person to person. But for me, if I’m on a flight or if I’m stuck somewhere for a while, like, let’s say I got to take my kid to practice or something and I’m stuck there for an hour and I got to find some way to kill my time 9 times out of 10, I’m on my laptop or on my phone having conversations with Grok or ChatGPT or Gemini or whatever. I am literally refining… I’m just sitting there asking it questions that are on my mind that I wish I could ask somebody who’s like 10 times more capable than me. It has been instrumental. WP Rig wouldn’t be where it is today if it wasn’t for that. I would just say to anybody, especially now that it’s all on apps and you don’t have to be on a browser anymore, adopt that way of thinking. You know, if you’re on your lunch break or whatever and you have an hour lunch break and you only take 15 minutes to eat, what could you be doing with those other 45 minutes? You could just jump on this magical thing that we have now and start probing it for questions. Like, Hey, here’s what I know. Here’s what I don’t know. Fill these knowledge gaps for me.” And it is extremely good at doing that. Topher: So my question was, can you blog this and your answer told me that there’s more there that I want to hear. That’s the stuff that should be in your book when you write your book. Rob: I’m flattered that you would be interested in reading anything that I write. So thank you. I’ve written stuff in the past and it hasn’t gotten a lot of attention. But I also don’t have any platforms to market it either. But yeah, no, I made some… I’m sorry. Topher: I think your experience is valuable far beyond Rig or WordPress. If you abstract it out of a particular project to say, you know, I did this with a project, I learned this this way, I think that would be super valuable. Rob: Well, I will say that recently at my current job, I was challenged to create an end to end testing framework with Playwright that would speed up how long it takes to test things and also prevent, you know, to make things fail earlier, essentially, to prevent broken things from ending up in the wild, right, and having to catch them the hard way. I didn’t know a lot about Playwright, but I do know how toolkits work now because of WP Rig. And I was able to successfully in a matter of, I don’t know, three days, put together a starter kit for a test framework that we’re already using at work to test any website that we create for any client. It can be extended and it can be hooked into any CI CD pipeline and it generates reports for you and it does a whole bunch of stuff. I was able to do this relatively quickly. This knowledge, yes, does come in handy in other situations. Will I end up developing other toolkits like WP Rig in the future for other things? I guess if I can give any advice to anybody listening out there, another piece of advice I would give people is, you know, especially if you’re a junior developer and you’re still learning or whatever, or you’re just a marketing person and just want to have more control over the functionality side of what you’re creating or more insight into that so you could better, you know, manage projects or whatever. My advice would be to take on a small little project that is scoped relatively small that’s not too much for you to chew and go build something and do it with… Just doing that will be good. But if you can do it with the intent to then present it in some fashion, whether it be a blog article or creating a YouTube video or going to a meetup and giving a talk on it or even a lunch and learn at work or whatever, right, that will, in my experience, it will dramatically amplify how much you learn from that little pet project that’s kind of like a mini learning experience. And I highly encourage anybody out there to do that on the regular. Actually, no matter what your experience level is in development, I think you should do these things on a regular basis. Topher: All right. I’m going to wrap this up. I got to get back to work. You probably have to get back to work. Rob: Yeah. Topher: Thanks for talking. Rob: Thanks for having me, Topher. Really appreciate it. Topher: Where could people find you? WPrig.io?  Rob: Yeah, WPrig.io. WP rig has accounts on all of the major platforms and, even on Bluesky and Mastodon. You can look me up, Rob Ruiz. You can find me on LinkedIn. You can find me on all of those same platforms as well. You can add me on Facebook if you want, whatever. And I’m also in the WordPress Slack as well as Rob Ruiz. You can find me in the WordPress Slack. And then I’m on the WordPress Reddit and all that stuff. So yeah, reach out. If anybody wants to have any questions about Rig or anything else, I’m happy to engage.  Topher: Sounds good. All right, I’ll see you. Rob: All right, thanks, Topher. Have a good day. Topher: This has been an episode of the Hallway Chats podcast. I’m your host Topher DeRosia. Many thanks to our sponsor Nexcess. If you’d like to hear more Hallway Chats, please let us know on hallwaychats.com.

K vytvoření webových stránek už dávno nepotřebujete umět HTML, PHP a CSS. Dokonce i moderní no-code/WYSIWYG editory webů koukají českému Macaly na záda. Tom se svým týmem naprogramoval úspěšnou AI-driven platformu, která umí jednoduše generovat kompletní webový kód na základě promptů a instrukcí v chatu. Frontend, backend, databáze, grafika, texty – to všechno Macaly zvládá díky vlastnímu prompt management nástroji Langtail nebo integracím s Pexels a GPT 4.0

I speak with with Jonas van den Bogaard of Alliander about the Linux Foundation's energy community that fosters open source energy generation and distributionWant the power of Mermaid for enterprises?Mermaid chart brings WYSIWYG editing, generative AI, collaboration, and more to the flexible syntax of Mermaid.https://go.chrischinchilla.com/mermaid For show notes and an interactive transcript, visit chrischinchilla.com/podcast/To reach out and say hello, visit chrischinchilla.com/contact/To support the show for ad-free listening and extra content, visit chrischinchilla.com/support/ Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

Cursor has a big problem, Alireza Bashiri thinks plaintext beats todo apps, Manish built an offline AI workspace, OverType is a WYSIWYG markdown editor that's just a textarea, and sshrc lets you bring your config with you to remote machines.

Cursor has a big problem, Alireza Bashiri thinks plaintext beats todo apps, Manish built an offline AI workspace, OverType is a WYSIWYG markdown editor that's just a textarea, and sshrc lets you bring your config with you to remote machines.

Cursor has a big problem, Alireza Bashiri thinks plaintext beats todo apps, Manish built an offline AI workspace, OverType is a WYSIWYG markdown editor that's just a textarea, and sshrc lets you bring your config with you to remote machines.

Fast rewind back to February and I had some fascinating conversations with various projects at FOSDEM in Brussels, including the Rust Foundation, Sysdig about StratoShark, Nextcloud, and Mastodon. Want the power of Mermaid for enterprises?Mermaid chart brings WYSIWYG editing, generative AI, collaboration, and more to the flexible syntax of Mermaid.https://go.chrischinchilla.com/mermaid Try the best git GUI for macOS and WindowsGrapple git without the grief and try Tower, the best graphical interface for git on macOS and Windows.https://go.chrischinchilla.com/tower For show notes and an interactive transcript, visit chrischinchilla.com/podcast/To reach out and say hello, visit chrischinchilla.com/contact/To support the show for ad-free listening and extra content, visit chrischinchilla.com/support/

I spoke with Dom Weatherbee of Regenx to discuss their precious metal recovery technology and how it can benefit the circular economy for new gadgets and devices.Want the power of Mermaid for enterprises? Try Mermaid Chart Mermaid chart brings WYSIWYG editing, generative AI, collaboration, and more to the flexible syntax of Mermaid.Sign up at go.chrischinchilla.com/mermaid For show notes and an interactive transcript, visit chrischinchilla.com/podcast/To reach out and say hello, visit chrischinchilla.com/contact/To support the show for ad-free listening and extra content, visit chrischinchilla.com/support/

What began as a quick SEO tip while Meredith was swimming with whales in Tonga evolved into a comprehensive Fundamentals Series ShowIt, WordPress, and Squarespace users.Visit the Fundamentals Serieshttps://seiq.meredithshusband.com/c/welcome-fundamentalsIn this episode...[0:24] Origin of the Fundamentals series for Showit users[1:08] Why Showit needs specific SEO guidance[2:37] What is WYSIWYG and Showit's visual interface[4:03] How Showit splits sites between Showit and WordPress[5:00] The unique problem of dual sitemaps[5:20] Configuring Yoast properly for Showit blogs[5:54] Connecting Google tools (Analytics and Search Console)[6:48] How to monitor Google Search Console after setup[7:41] Why Google Business Profile is also a “fundamental”[8:20] Thank-you message and free access for contributors ---Meredith's Husbandhttps://www.meredithshusband.com

Slushies, we invoke the retelling of a ghostly experience shared by Kathy and Marion at the Hotel Figueroa in California earlier this year partway into this episode. Two poems by Jen Siraganian are at the heart of our discussion, and it's the first of these that puts ghosts into our heads. This poem also causes us to consider at some length the physical form chosen by or for a poem, and how this can utterly enhance the experience of the poem when it's just right. It's also an opportunity for Jason to raise the spectre of the virgule (or slash) once again, and we even pause briefly to recall when WYSIWYG was a useful acronym. We end the episode with an ekphrastic that prompts an on-the-spot tie breaker (thanks to our sound engineer Lillie for saving the day!).   https://whitney.org/collection/works/2171 https://www.nga.gov/collection/highlights/gorky-the-artist-and-his-mother.html  At the table: Kathleen Volk Miller, Marion Wrenn, Lisa Zerkle, Jason Schneiderman, Dagne Forrest, Jodi Gahn, Lillie Volpe (sound engineer)   Jen Siraganian is an Armenian-American writer, educator, and former Poet Laureate of Los Gatos, California. Her poetry has appeared or is forthcoming in AGNI, Barrow Street, Best New Poets, Cortland Review, Poetry Daily, Prairie Schooner, The Rumpus, Smartish Pace, and other journals. Her work has been nominated for a Pushcart Prize and won the 2024 New Ohio Review Poetry Prize. A former managing director of Litquake: San Francisco's Literary Festival, she is a current Lucas Artist Fellow. jensiraganian.com      Social media handles:   Facebook @jen.siraganian, Instagram @jsiraganian, Bluesky @jsiraganian.bsky.social, Website

If something never goes away, you're never able to miss it. That's why there's an incredible amount of cynicism surrounding The Last of Us Complete, yet another re-release of the 2013 original and its 2020 sequel, a package that combines both games into something more accessible and affordable for PlayStation 5 owners. Naturally, this is heavily tied into the return of The Last of Us on HBO, and clearly this sort of thing isn't really aimed at us at all. In fact, it's likely very smart business. But that doesn't mean we're longing for something else. Anything else, really. For once. Plus: PS+ price increases slam headlong into Latin America, Portal gets some key UI and UX updates catered toward streaming users, PlayStation's concert series seemingly suffers poor ticket sales, and more. Then: Listener inquries! Should console manufacturers limit hardware sales to their most hardcore audience first? Considering the length of both Uncharted 4 and TLoU2, should be expect Intergalactic to be a very long game? Is the "games are too expensive" argument ultimately a dead end? Can Colin mystify his sons with the '90s tech magic of WYSIWYG? Please keep in mind that our timestamps are approximate, and will often be slightly off due to dynamic ad placement. Timestamps: 0:00:00 - Intro 0:37:06 - Larger shirts selling out 0:42:17 - Dealing with grief 0:44:51 - Kids listening to Sacred 0:46:02 - Espresso tips 0:52:04 - Lawn boys rise up 0:56:21 - Timestamps on what we're playing (no) 1:00:21 - Dustin's art of the deal 1:03:19 - PS+ price increase in Latin America 1:12:52 - Marathon reveal incoming 1:30:30 - HBO renews Last of Us for Season 3 1:38:28 - PS Portal update 1:41:06 - Animated background on PS5 1:43:58 - Vampire Survivors cross-save wont come to PlayStation 1:51:23 - PlayStation Concerts being canceled 1:56:08 - Death Stranding film details 2:03:06 - What We've Been Playing (The Last of Us: Part II, Breakout Beyond, Ready or Not, Blue Prince, Marathon 2: Durandal, Assassin's Creed Shadows) 2:35:58 - The Last of Us Complete 2:44:21 - New PlayStation+ games 2:52:47 - PSN Top Downloads 3:02:15 - Post-apocalyptic media 3:11:34 - Preorders looking at accounts 3:18:27 - Intergalactic's runtime 3:23:20 - Best weather in videos games 3:29:25 - Games industry and economics 3:40:48 - Lilymo and Kickstarter Learn more about your ad choices. Visit podcastchoices.com/adchoices

In this episode, I speak with Chad Whitacre of Sentry about their functional software license and the open-source pledge.Want the power of Mermaid for enterprises? Try Mermaid Chart Mermaid chart brings WYSIWYG editing, generative AI, collaboration, and more to the flexible syntax of Mermaid.Sign up at go.chrischinchilla.com/mermaid For show notes and an interactive transcript, visit chrischinchilla.com/podcast/To reach out and say hello, visit chrischinchilla.com/contact/To support the show for ad-free listening and extra content, visit chrischinchilla.com/support/

From misbehaving power supplies to a WYSIWYG editor that thought it was running on a PlayStation, today's stories dive deep into the weirdest corners of tech support. We've got cables in chaos, corporate facepalms, and one very patient IT guy who just wanted someone to turn on their TV. These stories are frustrating, hilarious, and oddly satisfying — especially when the fix is something as simple as tilting a phone. Whether you're an IT pro or just enjoy watching disaster unfold from a safe distance, this one's for you. Grab your coffee and enjoy the madness.Submit your own stories to KarmaStoriesPod@gmail.com.Karma Stories is available on all major Podcasting Platforms and on YouTube under the @KarmaStoriesPodcast handle. We cover stories from popular Reddit Subreddits like Entitled Parents, Tales From Tech Support, Pro Revenge and Malicious Compliance. You can find new uploads here every single day of the week!Rob's 3D Printing Site: https://Dangly3D.comBecome a supporter of this podcast: https://www.spreaker.com/podcast/karma-stories--5098578/support.

In this episode Cate and Chris talk about the future of European tech in the wake of the many challenges the block faces from the US, Russia, China, and more.Want the power of Mermaid for enterprises? Try Mermaid Chart Mermaid chart brings WYSIWYG editing, generative AI, collaboration, and more to the flexible syntax of Mermaid.Sign up at go.chrischinchilla.com/mermaid For show notes and an interactive transcript, visit chrischinchilla.com/podcast/To reach out and say hello, visit chrischinchilla.com/contact/To support the show for ad-free listening and extra content, visit chrischinchilla.com/support/

This podcast interview focuses on the entrepreneurial journey to build a global SaaS company with 25 million users without venture funding. My guest is Aytekin Tank, Founder and CEO of Jotform. Aytekin founded Jotform in 2006, creating a pioneering WYSIWYG online form builder that has grown to serve over 25 million users worldwide today.  What's remarkable is that he bootstrapped the company from the ground up. This allowed Jotform to remain 100% independent and define its own rules and company culture as it grew. Under his leadership, Jotform has experienced impressive international growth, with offices in seven different cities around the world. Their growth and style were recognized as Jotform was named one of the "Best Privately-Owned Companies in America" by Entrepreneur Magazine. Aytekin is not just a successful entrepreneur but also an automation enthusiast. He recently published a book titled "Automate Your Busywork. His book shares his insights on the automation philosophy he applied to grow Jotform. This inspired me, so I invited Aytekin to my podcast. We explore his biggest lessons learned from bootstrapping a form-building tool to leading a global company with 25 million users. He elaborates on his approach around continuous innovation and maintaining momentum (rather than worrying about competitors) and shares his insights on prioritizing product development and growth. Last but not least, he talks about how he recently gave new meaning to his 'Founder' role and why every SaaS entrepreneur should do that. Here's one of his quotes Being a founder is not just about leading a team, coaching a team, managing a team. But it's also about improving myself, growing myself. Because being a founder is about growth. It's about growth mindset. It's about growing yourself with the company. It's about growing your company. And it requires some dedication to do that - growing knowledge and learning. During this interview, you will learn four things: How he's working with customers to ensure JotForm's success His first principles for managing growth and avoiding getting bogged down in busy work. How he's organized his development teams and their rituals to ensure momentum on the one hand and optimal alignment on the other hand. How he approached competition from Google Forms to come out stronger themselves.  For more information about the guest from this week: Aytekin Tank Website: Jotform Subscribe to the Daily SaaS Reflection Get my free, 1 min daily reflection on shaping a B2B SaaS business no one can ignore. Subscribe here Yes, it's actually daily. And yes, people actually stay subscribed (Just see what peer B2B SaaS CEOs say) My promise: It's short. To the point. Inspiring. And valuable. Learn more about your ad choices. Visit megaphone.fm/adchoices

Redwood is a state-of-the-art graphical interface that defines the look and feel of the new Oracle Cloud Redwood Applications.   In this episode, hosts Lois Houston and Nikita Abraham, along with Senior Principal OCI Instructor Joe Greenwald, take a closer look at the intent behind the design and development aspects of the new Redwood experience. They also explore Redwood page templates and components.   Survey: https://customersurveys.oracle.com/ords/surveys/t/oracle-university-gtm/survey?k=focus-group-2-link-share-5   Developing Redwood Applications with Visual Builder: https://mylearn.oracle.com/ou/learning-path/developing-redwood-applications-with-visual-builder/112791   Oracle University Learning Community: https://education.oracle.com/ou-community   LinkedIn: https://www.linkedin.com/showcase/oracle-university/   X (formerly Twitter): https://twitter.com/Oracle_Edu   Special thanks to Arijit Ghosh, David Wright, and the OU Studio Team for helping us create this episode.   ---------------------------------------------------------   Episode Transcript:   00:00 Welcome to the Oracle University Podcast, the first stop on your cloud journey. During this series of informative podcasts, we'll bring you foundational training on the most popular Oracle technologies. Let's get started. 00:26 Nikita: Hello and welcome to the Oracle University Podcast! I'm Nikita Abraham, Team Lead: Editorial Services with Oracle University, and with me is Lois Houston, Director of Innovation Programs. Lois: Hi everyone! Thanks for joining us for this Best of 2024 series, where we're playing for you our four most popular episodes of the year.    Nikita: Today's episode is #3 of 4 and is a throwback to another conversation with Joe Greenwald, our Senior Principal OCI Instructor. We asked Joe about Oracle's Redwood design system and how it helps us create stunning, world-class enterprise applications and user experiences.  01:04 Lois: Yeah, Redwood is the basis for all the new Oracle Cloud Applications being re-designed, developed, and delivered. Joe is the best person to ask about all of this because he's been working with our Oracle software development tools since the early 90s and is responsible for OU's Visual Builder Studio and Redwood course content. So, let's dive right in! Joe: Hi Lois. Hi Niki. I am excited to join you on this episode because with the release of 24A Fusion applications, we are encouraging all our customers to adopt the new Redwood design system and components, and take advantage of the world-class look and feel of the new Redwood user experience. Redwood represents a new approach and direction for us at Oracle, and we're excited to have our customers benefit from it. 01:49 Nikita: Joe, you've been working with Oracle user interface development tools and frameworks for a long time. How and why is Redwood different? Joe: I joined Oracle in 1992, and the first Oracle user interface I experienced was Oracle Forms. And that was the character mode. I came from a background of Smalltalk and its amazing, pioneering graphical user interface (GUI) design capabilities. I worked at Apple and I developed my own GUIs for a few years on PCs and Macs. So, Character Mode Forms, what we used to call DMV (Department of Motor Vehicles) screens, was a shock, to say the least. Since then, I've worked with almost every user interface and development platform Oracle has created: Character Mode Forms, GUI Forms, Power Objects, HyperCard on the Macintosh, that was pre-OS X by the way, Sedona, written in native C++ and ActiveX and OLE, which didn't make it to a product but appeared in other things later, ADF Faces, which uses Java to generate HTML pages, and APEX, which uses PL/SQL to generate HTML pages. And I've worked with and wrote training classes for Java Swing, an excellent GUI framework for event-driven desktop and enterprise applications, but it wasn't designed for the web. So, it's with pleasure that I introduce you to the Redwood design system, easily the best effort I've ever seen, from the look and feel of holistic user-goal-centered design philosophy and approach to the cutting-edge WYSIWYG design tools.  03:16 Lois: Joe, is Redwood just another set of styles, colors, and fonts, albeit very nice-looking ones? Joe: The Redwood platform is new for Oracle, and it represents a significant change, not just in the look and feel, colors, fonts, and styles, I mean that too, but it's also a fundamental change in how Oracle is creating, designing, and imagining user interfaces. As you may be aware, all Oracle Cloud Applications are being re-designed, re-engineered, and re-rebuilt from the ground up, with significant changes to both back-end and front-end architectures. The front end is being redesigned, re-developed, and re-created in pure HTML5, CSS3, and JavaScript using Visual Builder Studio and its design-time browser-based Integrated Development Environment. The back end is being re-architected, re-designed, and implemented in a modern microservice architecture for Oracle Cloud using Kubernetes and other modern technologies that improve performance and work better in the cloud than our current legacy architecture. The new Oracle Cloud Applications platform uses Redwood for its design system—its tools, its patterns, its components, and page templates. Redwood is a richer and more productive platform to create solutions while still being cost-effective for Oracle. It encourages a transformation of the fundamental user experience, emphasizing identifying, meeting, and understanding end users' goals and how the applications are used.  04:39 Nikita: Joe, do you think Oracle's user interface has been improved with Redwood? In what ways has the UI changed? Joe: Yes, absolutely. Redwood has changed a lot of things. When I joined Oracle back in the '90s, there was effectively no user interface division or UI team. Everybody just did their own thing. There was no user interface lab—and that was started in the mid-‘90s—and I was asked to give product usability feedback and participate in UI tests and experiments in those labs. I also helped test the products I was teaching at the time. I actually distinctly remember having to take a week to train users on Oracle's Designer CASE tool product just to prep the participants enough to perform usability testing. I can still hear the UI lab manager shaking her head and saying any product that requires a week of training to do usability testing has usability issues! And if you're like me and you've been around Oracle long enough, you know that Oracle's not always been known for its user interfaces and been known to release products that look like they were designed by two or more different companies. All that has changed with Redwood. With Redwood, there's a new internal design group that oversees the design choices of all development teams that develop products. This includes a design system review and an ongoing audit process to ensure that all the products being released, whether Fusion apps or something else, all look and feel similar so it looks like it's designed by a single company with a single thought in mind. Which it is. There's a deeper, consistent commitment in identifying user needs, understanding how the applications are being used, and how they meet those user needs through things like telemetry: gathering metrics from the actual components and the Redwood system itself to see how the applications are being used, what's working well, and what isn't.  This telemetry is available to us here at Oracle, and we use it to fine tune the applications' usability and purpose.  06:29 Lois: That's really interesting, Joe. So, it's a fundamental change in the way we're doing things. What about the GUI components themselves? Are these more sophisticated than simple GUI components like buttons and text fields? Joe: The graphical components themselves are at a much higher level, more comprehensive, and work better together. And in Redwood, everything is a component. And I'm not just talking about things like input text fields and buttons, though it applies to these more fine-grained components as well. Leveraging Oracle's deep experience in building enterprise applications, we've incorporated that knowledge into creating page templates so that the structure and look and feel of the page is fixed based on our internal design standards. The developer has control over certain portions of it, but the overall look and feel of the page is controlled by Oracle. So there is consistency of look and feel within and across applications. These page templates come with predefined functionalities: headers, titles, properties, and variables to manipulate content and settings, slots for other components to hold like search fields, collections, contextual information, badges, and images, as well as primary and secondary actions, and variables for events and event handling through Visual Builder action chains, which handle the various actions and processing of the request on the page. And all these page templates and components are responsive, meaning they respond to the change in the size of the page and the orientation. So, when you move from a desktop to a handheld mobile device or a tablet, they respond appropriately and consistently to deliver a clean, easy-to-use interface and experience. 08:03 Nikita: You mentioned WYSIWYG design tools and their integration with Visual Builder Studio's integrated development environment. How does Redwood work with Visual Builder Studio? Joe: This is easily one of my most favorite aspects about Redwood and the integration with Visual Builder Studio Designer. The components and page templates are responsive at runtime as well as responsive at design time! In over 30 years of working with Oracle software development products, this is the first development system and integrated development environment I've seen Oracle produce where what you see is what you get at design time. Now, with products such as Designer and JDeveloper ADF Faces and even APEX—all those page-generation types of products—you have to generate the page, deploy it, and only then can you view the final page to see whether it meets the needs of your user interface. For example, with Designer, there were literally hundreds of configuration parameters that you could set to control how forms and reports looked when they were generated —down to how many buttons on a row or how many rows to a page, that sort of thing, all done in text mode. Then you'd generate and run the page to see what the result was and then go back and modify things until you got what you wanted. I remember hearing the product managers for Oracle ADF Faces being asked…well, a customer asked, “What happens if I put this component here and this component here? What will the page look like?” and they'd say, “I don't know. Render the page and let's see.” That's just crazy talk. With Redwood and its integration with Visual Builder Studio Designer, what you see on the page at design time is literally what you get. And if I make the page narrower or I even convert it to a mobile display while in the Designer itself, I immediately see what the page looks like in that new mode. Everything just moves accordingly, at design time. For example, when changing to a mobile UI, everything stacks up nicely; the components adjust to the page size and change right there in the design environment. Again, I can't emphasize enough the simple luxury of being able to see exactly what the user is going to see on my page and having the ability to change the resolution, orientation, and screen size, and it changes right there immediately in my design environment. 10:06 Lois: I'm intrigued by the idea of page templates that are managed by Oracle but still leave room for the developer to customize aspects of the look and feel and functionality. How does that work? Joe: Well, the page templates themselves represent the typical pages you would most likely use in an enterprise application. Things like a welcome page, a search page, and edit and create pages, and a couple of different ways to display summary information, including foldout pages, though this is not an exhaustive list of course. Not only do they provide a logical and complete starting point for the layout of the page itself, but they also include built-in functionality. These templates include functionality for buttons, primary and secondary actions, and areas for holding contextual information, badges, avatars, and images. And this is all built right into the page, and all of them use variables to describe the contents for the various parts, so the contents can change programmatically as the variables' contents change, if necessary. 11:04 Do you have an idea for a new course or learning opportunity? We'd love to hear it! Visit the Oracle University Learning Community and share your thoughts with us on the Idea Incubator. Your suggestion could find a place in future development projects. Visit mylearn.oracle.com to get started.  11:24 Nikita: Welcome back! So, Joe, let's say I'm a developer. How do I get started working with Redwood? Joe: One of the easiest ways to do it is to use Visual Builder Studio Designer and create a new visual application. If you're creating a standalone, bespoke custom application, you can choose a Redwood starter template, which will include all the Redwood components and page templates automatically. Or, if you're extending and customizing an Oracle Fusion application, Redwood is already included.  Either way, when you create a new page, you have a choice of different page templates—welcome page templates, edit pages, search pages, etc. —and all you have to do is choose a page that you want and begin configuring it. And actually if you make a mistake, it's easy to switch page templates. All the components, page templates, and so on have documentation right there inside Visual Builder Studio Designer, and we do recommend that you read through the documentation first to get an understanding of what the use case for that template is and how to use it. And some components are more granular, like a collection container which holds a collection of rows of a list or a table and provides capabilities like toolbars and other actions that are already built and defined. You decide what actions you want and then use predefined event listeners that are triggered when an event occurs in the application—like a button being clicked or a row being selected—which kicks off a series of actions to be performed. 12:42 Lois: That sounds easy enough if you know what you're doing. Joe, what are some of the more common pages and what are they used for?  Joe: Redwood page templates can be broken down into categories. There are overview templates like the welcome page template, which has a nice banner, colors, and illustrations that can be used for a welcoming page—like for entering a new application or a new logical section of the application. The dashboard landing page template displays key information values and their charts and graphs, which can come from Oracle Analytics, and automatically switches the display depending on which set of data is selected.  The detail templates include a general overview, which presents read-only information related to a single record or resource. The item overview gives you a small panel to view summary information (for example, information on a customer) and in the main section, you can view details like all the orders for that customer. And you can even navigate through a set of customers, clicking arrows for next-previous navigation. And that's all built in. There's no programming required. The fold-out page template folds out horizontally to show you individual panels with more detail that can be displayed about the subject being retrieved as well as overflow and drill-down areas. And there's a collection detail template that will display a list with additional details about the selected item (for example, an order and its order line items). The smart search page does exactly what it says. It has a search component that you use to filter or search the data coming back from the REST data sources and then display the results in a list or a table. You define the filter yourself and apply it using different kinds of comparators, so you can look for strings that start with certain values or contain values, or numerical values that are equal to or less than, depending on what you're filtering for. And then there are the transactional templates, which are meant to make changes. This includes both the simple create and edit and advanced create and edit templates.  The simple create and edit page template edits a single record or creates a single record. And the advanced page template works well if you're working with master-detail, parent-child type relationships. Let's say you want to view the parent and create children for it or even create a parent and the children at the same time. And there's a Gantt chart page for project management–type tracking and a guided process page for multiple-step processes and there's a data management page template specifically for viewing and editing data collections like Excel spreadsheets. 14:55 Nikita: You mentioned that there's a design system behind all this. How is this used, and how does the customer benefit from it? Joe: Redwood comprises both a design system and a development system. The design system has a series of steps that we follow here at Oracle and can suggest that you, our customers and partners, can follow as well. This includes understanding the problem, articulating the vision for the page and the application (what it should do), identifying the proper Redwood page templates to use, adding detail and refining the design and then using a number of different mechanisms, including PowerPoint or Figma design tools to specify the design for development, and then monitor engagement in the real world. These are the steps that we follow here at Oracle. The Redwood development process starts with learning how to use Redwood components and templates using the documentation and other content from redwood.oracle.com and Visual Builder Studio. Then it's about understanding the design created by the design team, learning more about components and templates for your application, specifically the ones you're going to use, how they work, and how they work together. Then developing your application using Visual Builder Studio Designer, and finally improving and refining your application. Now, right now, as I mentioned, telemetry is available to us here at Oracle so we can get a sense of the feedback on the pages of how components are being used and where time is being spent, and we use that to tune the designs and components being used. That telemetry data may be available to customers in the future. Now, when you go to redwood.oracle.com, you can access the Redwood pattern book that shows you in detail all the different page templates that are available: smart search page, data grid, welcome page, dashboard landing page, and so on, and you can select these and read more about them as well as the actual design specifications that were used to build the pages—defining what they do and what they respond to. They provide a lot of detailed information about the templates and components, how they work and how they're intended to be used. 16:50 Lois: That's a lot of great resources available. But what if I don't have access to Visual Builder Studio Designer? Can I still see how Redwood looks and behaves? Joe: Well, if you go to redwood.oracle.com, you can log in and work with the Redwood reference application, which is a live application working with live data. It was created to show off the various page templates and components, their look and feel and functionality from the Redwood design and development systems. This is an order management application, so you can do things like view filtered pending orders, create new orders, manage orders, and view information about customers and inventory. It uses the different page templates to show you how the application can perform. 17:29 Nikita: I assume there are common aspects to how these page templates are designed, built, and intended to be used. Is that a good way to begin understanding how to work with them? Becoming familiar with their common properties and functionality? Joe: Absolutely! Good point! All pages have titles, and most have primary and secondary actions that can be triggered through a variety of GUI events, like clicking a button or a link or selecting something in a list or a table. The transactional page templates include validation groups that validate whether the data is correct before it is submitted, as well as a message dialog that can pop up if there are unsaved changes and someone tries to leave the page. All the pages can use variables to display information or set properties and can easily display specific contextual information about records that have been retrieved, like adding the Order Number or Customer Name and Number to the page title or section headers. 18:18 Lois: If I were a developer, I'd be really excited to get started! So, let's say I'm a developer. What's the best way to begin learning about Redwood, Joe? Joe: A great place to start learning about the Redwood design and development system is at the redwood.oracle.com page I mentioned. We have many different pages that describe the philosophy and fundamental basis for Redwood, the ideas and intent behind it, and how we're using it here at Oracle. It also has a list of all the different page templates and components you can use and a link to the Redwood reference application where you can sign in and try it yourself. In addition, we at Oracle University offer a course called Design and Develop Redwood Applications, and in there, we have both lecture content as well as hands-on practices where you build a lightweight version of the Redwood reference application using data from the Fusion apps application, as well as the pages that I talked about: the welcome page, detail pages, transactional pages, and the dashboard landing page.  And you'll see how those pages are designed and constructed while building them yourself.  It's very important though to take one of the free Visual Builder Developer courses first: either Build Visual Applications Using Visual Builder Studio and/or Develop Fusion Applications Using Visual Builder Studio before you try to work through the practices in the Redwood course because it uses a lot of Visual Builder Designer technology.  You'll get a lot more out of the Redwood practices if you understand the basics of Visual Builder Studio first. The Build Visual Applications Using Visual Builder Studio course is probably a better place to start unless you know for a fact you will be focusing on extending Oracle Fusion Applications using Visual Builder Studio. Now, a lot of the content is the same between the two courses as they share much of the same technology and architectures. 19:58 Lois: Ok, so Build Visual Applications Using Visual Builder Studio and Develop Fusion Applications Using Visual Builder Studio…all on mylearn.oracle.com and all free for anyone who wants to take them, right? Joe: Yes, exactly. And the free Redwood learning path leads to an Associate certification. While our courses are a great place to start in preparing for your certification exam, they are not, of course, by themselves sufficient to pass and you will want to study and be familiar with the redwood.oracle.com content as well. The learning path is free, but you do have to pay for the certification exam. Nikita: We hope you enjoyed that conversation. A quick reminder about the short survey we've created to gather your insights and suggestions for the podcast. It's really quick. Just click the link in the show notes to complete the survey. Thank you so much for helping us make the show better. Join us next week for another throwback episode. Until then, this is Nikita Abraham... Lois: And Lois Houston, signing off! 20:58 That's all for this episode of the Oracle University Podcast. If you enjoyed listening, please click Subscribe to get all the latest episodes. We'd also love it if you would take a moment to rate and review us on your podcast app. See you again on the next episode of the Oracle University Podcast.

This show has been flagged as Explicit by the host. table td.shrink { white-space:nowrap } hr.thin { border: 0; height: 0; border-top: 1px solid rgba(0, 0, 0, 0.1); border-bottom: 1px solid rgba(255, 255, 255, 0.3); } New hosts Welcome to our new host: SolusSpider. Last Month's Shows Id Day Date Title Host 4240 Fri 2024-11-01 The First Doctor, Part 1 Ahuka 4241 Mon 2024-11-04 HPR Community News for October 2024 HPR Volunteers 4242 Tue 2024-11-05 Interview with Lorenzo 'kelset' Sciandra Ken Fallon 4243 Wed 2024-11-06 Hand Warmer, long term product review MrX 4244 Thu 2024-11-07 Two methods of digitizing photos. Henrik Hemrin 4245 Fri 2024-11-08 What's in my bag? Trey 4246 Mon 2024-11-11 Bytes, Pages and Screens Lee 4247 Tue 2024-11-12 Installing GuixSD--Part Deux Rho`n 4248 Wed 2024-11-13 Millie Perkins Ken Fallon 4249 Thu 2024-11-14 Audio Streams on the Command Line Kevie 4250 Fri 2024-11-15 Playing Civilization IV, Part 3 Ahuka 4251 Mon 2024-11-18 Dave and MrX turn over a new leaf Dave Morriss 4252 Tue 2024-11-19 Privacy is not hiding Some Guy On The Internet 4253 Wed 2024-11-20 A brief introduction of myself Kinghezy 4254 Thu 2024-11-21 Cake Money Money Cake Money Money Cake! operat0r 4255 Fri 2024-11-22 What is on My Podcast Player 2024, Part 1 Ahuka 4256 Mon 2024-11-25 Birds of a Feather Talk at OLF 2024 Thaj Sara 4257 Tue 2024-11-26 Movie review: The Artifice Girl Kevie 4258 Wed 2024-11-27 Introduction and History of Using Computers SolusSpider 4259 Thu 2024-11-28 Why digitize photos Henrik Hemrin 4260 Fri 2024-11-29 The Golden Age Ahuka Comments this month These are comments which have been made during the past month, either to shows released during the month or to past shows. There are 61 comments in total. Past shows There are 21 comments on 17 previous shows: hpr0870 (2011-12-02) "Computer Memories" by Deltaray. Comment 3: SolusSpider - Peter Paterson on 2024-11-29: "Commonality on Deltaray's computer experiences" hpr1322 (2013-08-27) "Kevin O'Brien - Ohio LinuxFest 2013" by Ken Fallon. Comment 1: SolusSpider - Peter Paterson on 2024-11-26: "Attended OLF2013" hpr1642 (2014-11-18) "Frist Time at Oggcamp" by Al. Comment 2: SolusSpider - Peter Paterson on 2024-11-27: "Al at Oggcamp - 10 years later" hpr1890 (2015-10-30) "A short walk with my son" by thelovebug. Comment 4: SolusSpider - Peter Paterson on 2024-11-11: "Comment on A short walk with my son" hpr2503 (2018-03-07) "My journey into podcasting" by thelovebug. Comment 3: SolusSpider - Peter Paterson on 2024-11-18: "Comment on TheLoveBug journey into podcasting." hpr2673 (2018-10-31) "Urandom - Ohio Linux Fest 2-18 Podcaster Roundtable" by Thaj Sara. Comment 1: SolusSpider - Peter Paterson on 2024-11-26: "Wonderful OLF Podcasters Banter" hpr3315 (2021-04-16) "tesseract optical character recognition" by Ken Fallon. Comment 2: SolusSpider - Peter Paterson on 2024-11-28: "Tessaract OCR User" Comment 3: SolusSpider - Peter Paterson on 2024-11-29: "Spelling of tesseract" hpr3998 (2023-11-29) "Using open source OCR to digitize my mom's book" by Deltaray. Comment 3: SolusSpider - Peter Paterson on 2024-11-29: "Experience with Tesseract OCR software" hpr4106 (2024-04-29) "My tribute to feeds" by Henrik Hemrin. Comment 1: SolusSpider - Peter Paterson on 2024-11-27: "New(ish) to Feeds" Comment 2: Henrik Hemrin on 2024-11-29: "Thanks for feedback" hpr4129 (2024-05-30) "How I found Hacker Public Radio" by Henrik Hemrin. Comment 1: SolusSpider - Peter Paterson on 2024-11-27: "My own story of finding HPR" hpr4132 (2024-06-04) "Urandom talks about the future of HPR" by Thaj Sara. Comment 4: SolusSpider - Peter Paterson on 2024-11-18: "Comment on Urandom talks about the future of HPR" hpr4195 (2024-08-30) "Hacking HPR Hosts" by Ken Fallon. Comment 2: SolusSpider - Peter Paterson on 2024-11-29: "Another comment for Ken - he hacked this host" hpr4200 (2024-09-06) "Intro to Doctor Who" by Ahuka. Comment 5: SolusSpider - Peter Paterson on 2024-11-09: "Comment on Introduction To Doctor Who" hpr4220 (2024-10-04) "How Doctor Who Began" by Ahuka. Comment 1: SolusSpider - Peter Paterson on 2024-11-11: "Comment on How Doctor Who Began" hpr4233 (2024-10-23) "OggCamp 2024 Day 1" by Ken Fallon. Comment 1: @geospart on 2024-11-09: "Nice" hpr4236 (2024-10-28) "History of Nintendo" by Lochyboy. Comment 3: SolusSpider - Peter Paterson on 2024-11-10: "Comment on History of Nintendo" Comment 4: John Curwood - blindape on 2024-11-20: "Virtual Boy" hpr4238 (2024-10-30) "Snaps are better than flatpaks" by Some Guy On The Internet. Comment 2: Elliot B on 2024-11-01: "Snaps are the least worst" Comment 3: mpardo on 2024-11-02: "Snaps are indeed better that Flatpaks" This month's shows There are 40 comments on 16 of this month's shows: hpr4240 (2024-11-01) "The First Doctor, Part 1" by Ahuka. Comment 1: Kevie on 2024-10-31: "Keep them coming"Comment 2: Kevin O'Brien on 2024-11-02: "More to come"Comment 3: Ken Fallon on 2024-11-07: "Daleks" hpr4241 (2024-11-04) "HPR Community News for October 2024" by HPR Volunteers. Comment 1: ClaudioM on 2024-11-04: "Commentary on Ep. 4231 (Tmux+dd+FreeBSD)"Comment 2: Torin Doyle on 2024-11-10: "Hunting, Buzzing"Comment 3: Dave Morriss on 2024-11-14: "Buzzing?"Comment 4: Dave Lee (thelovebug) on 2024-11-16: "Dave's buzzing"Comment 5: Torin Doyle on 2024-11-18: "Re: Buzzing (more like a hum) in the audio for Dave Morriss."Comment 6: Dave Morriss on 2024-11-18: "The buzzing of the brain" hpr4244 (2024-11-07) "Two methods of digitizing photos." by Henrik Hemrin. Comment 1: Henrik Hemrin on 2024-11-07: "Clarification equipment for repro photo"Comment 2: Ken Fallon on 2024-11-07: "What hardware are you using"Comment 3: Henrik Hemrin on 2024-11-07: "Response to Ken"Comment 4: Charles in NJ on 2024-11-08: "Missed this show because feed is broken"Comment 5: Ken Fallon on 2024-11-08: "Bug Report"Comment 6: Ken Fallon on 2024-11-09: "Please send me your version of bashpodder" hpr4245 (2024-11-08) "What's in my bag?" by Trey. Comment 1: men Fallon on 2024-11-07: "Backdoors and breaches" hpr4246 (2024-11-11) "Bytes, Pages and Screens" by Lee. Comment 1: Ken Fallon on 2024-11-07: "Terry Pratchett"Comment 2: Torin Doyle on 2024-11-18: "Podcasts, Books, TV" hpr4248 (2024-11-13) "Millie Perkins" by Ken Fallon. Comment 1: Kevie on 2024-11-13: "A fantastic Oggcamp Talk" hpr4249 (2024-11-14) "Audio Streams on the Command Line" by Kevie. Comment 1: Ken Fallon on 2024-11-07: "Great Tips"Comment 2: SolusSpider - Peter Paterson on 2024-11-14: "Comment on Audio Streams on the Command Line"Comment 3: Jan on 2024-11-14: "Just Thanks"Comment 4: Henrik Hemrin on 2024-11-29: "Command Line" hpr4251 (2024-11-18) "Dave and MrX turn over a new leaf" by Dave Morriss. Comment 1: FXB on 2024-11-23: "using wttr.in"Comment 2: Dave Morriss on 2024-11-23: "Re: wttr.in" hpr4252 (2024-11-19) "Privacy is not hiding" by Some Guy On The Internet. Comment 1: Tim J on 2024-11-20: "Big Tech is Watching You" hpr4253 (2024-11-20) "A brief introduction of myself" by Kinghezy. Comment 1: SolusSpider - Peter Paterson on 2024-11-20: "Comment on kinghezy's introduction show hpr4253" hpr4256 (2024-11-25) "Birds of a Feather Talk at OLF 2024" by Thaj Sara. Comment 1: Ken Fallon on 2024-11-21: "Suspense"Comment 2: Thaj on 2024-11-25: "Resolution"Comment 3: Windigo on 2024-11-26: "Future shows"Comment 4: Torin Doyle on 2024-11-30: "OLF?" hpr4257 (2024-11-26) "Movie review: The Artifice Girl" by Kevie. Comment 1: SolusSpider - Peter Paterson on 2024-11-26: "Also watched The Atifice Girl" hpr4258 (2024-11-27) "Introduction and History of Using Computers" by SolusSpider. Comment 1: Dave Lee (thelovebug) on 2024-11-18: "Welcome to the HPR family"Comment 2: present_arms on 2024-11-19: "This Podcast hpr4258 :: Introduction and History of Using Computers"Comment 3: archer72 on 2024-11-27: "Welcome to HPR"Comment 4: Henrik Hemrin on 2024-11-29: "Welcome as HPR host!" hpr4259 (2024-11-28) "Why digitize photos" by Henrik Hemrin. Comment 1: SolusSpider - Peter Paterson on 2024-11-28: "The thoughts behind digitizing photos"Comment 2: Henrik Hemrin on 2024-11-29: "Thanks for your comment" hpr4272 (2024-12-17) "Embed Mastodon Threads" by hairylarry. Comment 1: Ken Fallon on 2024-11-28: "Wayne Myers ?? Where did I hear that name before ?" hpr4320 (2025-02-21) "Switching my Mastodon account" by Ahuka. Comment 1: Ken Fallon on 2024-11-25: "Target Audience of 1" Mailing List discussions Policy decisions surrounding HPR are taken by the community as a whole. This discussion takes place on the Mail List which is open to all HPR listeners and contributors. The discussions are open and available on the HPR server under Mailman. The threaded discussions this month can be found here: https://lists.hackerpublicradio.com/pipermail/hpr/2024-November/thread.html Events Calendar With the kind permission of LWN.net we are linking to The LWN.net Community Calendar. Quoting the site: This is the LWN.net community event calendar, where we track events of interest to people using and developing Linux and free software. Clicking on individual events will take you to the appropriate web page. Any other business It's been another hectic month here at HPR Towers. As we discussed on the mailing list most of the time was taken by the migration to Mastodon, and the implementation of the mirrors on the Community Content Delivery Network. Some daily stats are been updated on https://hub.hackerpublicradio.org/hpr_ccdn_stats.tsv Summary of the changes to the repo https://repo.anhonesthost.net/HPR Dave updated his tooling for processing shows and they are now available on the Gitea repo. We finally got around to creating the HPR Documentation wiki. Community Content Delivery Network (CCDN) A location to track the deployment of the HPR Community Content Delivery Network, that provides a mirror network for our content. HPR Website Design This is literally in the whiteboard phase of the HPR website redesign. Where we can track Compatibility of the clients subscribed to our feeds. Useful Resources Where we can link to other free culture sites that provide useful services. Requested Topics Where we can track topics that have been requested, and link to shows that addressed them. There is also a list with information about Podcatcher and Podcasting Platform Compatibility. If anyone wants to adopt a player then please do so. The section on Workflow will be changing shortly due to Dave stepping aside, and also the need to distribute to multiple end points. All the processing will happen first, and then all the checks will be done at the same stage just prior to posting. For this to work we need help finding a simple manageable WYSIWYG editor that can produce sane HTML when the host uploads the show. We also need a new system to distribute the files from an origin to all the mirrors. Other changes and fixes. The day of the week is now available on the website. Fixed the RSS feed to show explicit status. Fixed a bug that limited the future feed to just 10 shows. Fixed a typo in the status page. Following feedback, added emphasis about the upcoming two weeks, to the scheduling guidelines. Notable shout out to the people who are promoting HPR and are helping people out with audio issues. Provide feedback on this episode.

At React Summit in New York, KBall & Nick sat down with Kent C. Dodds & Theo Browne for two fascinating conversations. Both of them showed us the whole gamut of their personalities! Kent shared his insights on effective teaching methodologies and the future of developer education, while diving deep into React and the Remix/React Router ecosystem, and closing on an appeal for kindness int he world. Then Theo took us behind the scenes of his developer-focused content creation, from streaming to the origins of the T3 stack, and how his online persona (including T3!) is "just him".

At React Summit in New York, KBall & Nick sat down with Kent C. Dodds & Theo Browne for two fascinating conversations. Both of them showed us the whole gamut of their personalities! Kent shared his insights on effective teaching methodologies and the future of developer education, while diving deep into React and the Remix/React Router ecosystem, and closing on an appeal for kindness int he world. Then Theo took us behind the scenes of his developer-focused content creation, from streaming to the origins of the T3 stack, and how his online persona (including T3!) is "just him".

Javid and Robert are two guys who dive into the long, boring stuff of standards and protocols so you don't have to. Because of them, you will know which cables and wires to use for your DMX512 projects. You have the ANSI E1.27-2 Task Group to thank for setting the standards for “Permanently Installed Control Cables for Use with ANSI E1.11 (DMX512-A) and USITT DMX512/1990 Products.” Did you know that DMX512 needs a specific kind of cable? Well… now you know. Javid Butler is a lighting designer and energy engineer who holds LC, CEM, and CMVP certifications. He has contributed to the development of many lighting standards including RDM and sACN, and chaired the task group for E1.27 DMX512 cabling standards. He presently chairs the E1.68 DMX512 Compliance task group. In addition to lighting standards Javid enjoys teaching Fundamentals of Lighting. He also writes science fiction under the pen name David Pax. Robert Bell a Consulting Director for Product Market at Acuity Brands and oversees the development of the entire Pathway Connectivity product line. Robert has been awarded multiple US Patents for lighting controls and networking which have been assigned to Acuity Brands. In 1992, he won the first every Wally Russell Newcomer Award as the creator of WYSIWYG, the Emmy Award winning previsualization software. His is a regular contributor to entertainment lighting periodicals and is the author of the book Let There Be Light, Conversations with Lighting Pioneers. With roots in the Rock ‘n Roll touring world and broadcast Television during the 1990's, he spent the 2000's as a product manager for Strand Lighting and as brand ambassador for Vari*Lite. For the past 20 years, Robert has sat on ESTA's Control Protocol Working Group, the body that brought DMX, RDM and sACN forward as ANSI standards. 

Adam meets with Elliot Azhdam from Golden State Corals to dive into his methods and technics, culturing an amazingly array of colorful and unique corals. They discuss the store's display tank, his use of high par LED lighting, some tricks for the photoperiod, along with his implementation of kalkwasser and calcium reactors. Check out Golden State Coral's website at the link below and don't miss out on the current 50% off WYSIWYG sale!Golden State Corals Links:https://goldenstatecorals.com/https://facebook.com/goldenstatecorals/https://instagram.com/goldenstatecorals/https://www.reef2reef.com/forums/golden-state-corals-gsc.1096/Frag Garage Links:https://www.patreon.com/BeyondTheReefPodcasthttps://fraggarage.ca/https://www.instagram.com/fraggarage/https://www.youtube.com/channel/UCLkiAJNqvoIRDRTFs34e6Twhttps://www.facebook.com/fraggarageBeyond the Reef Merch!https://fraggarage.ca/product-category/swag/ Hosted on Acast. See acast.com/privacy for more information.

3:02:46 – Frank in New Jersey, plus the Other Side. Topics include: The DMV, new recorder, Phish at Dick’s, Tweezer Reprise, Mitch Hedberg, The Sharper Image, dead mall, gun incident, Futurama, secret action figure, VHS effects, vegan Nutella, Wacky Packages, Florida trip, The Obtuse Angle with Steve Dupont, Upon a Wysiwyg Yonder, British Empire Exhibition, The Rings […]

3:02:46 – Frank in New Jersey, plus the Other Side. Topics include: The DMV, new recorder, Phish at Dick’s, Tweezer Reprise, Mitch Hedberg, The Sharper Image, dead mall, gun incident, Futurama, secret action figure, VHS effects, vegan Nutella, Wacky Packages, Florida trip, The Obtuse Angle with Steve Dupont, Upon a Wysiwyg Yonder, British Empire Exhibition, The Rings […]

Elvis and Barb are back again this week recording wonderful people at the Jensen Dental (https://jensendental.com/) booth at the Florida Dental Laboratory Association (https://www.fdla.net/) Symposium. THANK YOU JENSEN! (go get MIYO) First up is MIYO (https://miyoworld.com/) expert, teacher, guru Terry McQuiston. Terry talks about his dental journey that eventually landed him at Jensen Dental teaching everyone the wonders of this amazing liquid ceramic. His role now is onboarding labs and making sure they have their "ah ha" moment and not become "missing in action". Then we meet the new VP of Global Sales for Argen (https://argen.com/), Juston Gates. Juston is new to not only Argen, but also our industry. He talks about where he came from, how it compares to our profession, and some exciting things that Argen has just released. We wrap up the episode with everyone's favorite person to see at a dental show (and if you don't know her, go be her friend), Nina Rapuano. Nina talks about joining Jensen Dental as her first "adult job", why she loves the people and culture, and giving back every year and swimming during the Race For the Future (https://dentallabfoundation.org/news-events/race-for-the-future/). Introducing Ivotion Digital Dentures (https://www.ivoclar.com/en_us/products/digital-processes/ivotion) from Ivoclar (https://www.ivoclar.com/en_us) – Experience unparalleled precision and efficiency with Ivoclar‘s state-of-the-art digital denture workflow. Ivotion is available in their patent pending monolithic disc that combines denture base and tooth materials in one seamless puck. Or if you lab needs more flexibility, Ivotion is also available as stand-alone discs - Ivotion Base, Dent and Dent Multi all in 98mm width to fit your favorite milling machine. With Ivotion you can streamline your lab's processes, reduce production time, and enhance patient satisfaction. Elevate your lab's capabilities with Ivotion Digital Dentures – where innovation meets perfection. Discover the future of dentures today with Ivoclar." Thanks for your continued support of the podcast Ivoclar. Join the GOLDEN BENCH CLUB! All you have to do is leave us a 5-star review and comment on the Apple Podcast app (or any other app and email us a screen shot) and we will read your review on the podcast and welcome you to the Golden Bench Club. This super elite club is only for the best of the best. Special Guests: Juston Gates, Nina Rapuano , and Terry McQuiston.

Join us for an in-depth review of Clutch's seminal 2004 album, "Blast Tyrant"! 'Trucker' Andy from the  All Apologies Podcast is a 30-year Clutch veteran and Ryan is the newcomer to the band. Join us as we dive deep into each track, offering unique perspectives and analysis. We'll explore the album's stoner rock roots, Neil Fallon's cryptic lyrics, and the band's musical evolution. From the opening riffs of "Mercury" to the closing jam of "WYSIWYG," we'll dissect the highs and lows of this pivotal release. Stick around to the end as we controversially pick what we consider the album's weakest track. Whether you're a die-hard fan or new to Clutch, this episode is packed with insights, laughs, and pure rock appreciation. YouTube: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Watch Here⁠ join our Discord ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://discord.gg/ndZwrUpeA5⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ email us worstofthebestpodcast@gmail.com

TinyMCE is a great library to add a WYSIWYG Editor to your Web app. This week we had Mrina Sugosh sharing everything you need to know about TinyMCE and its Angular Wrapper!More about Mark and Angular 17X: @mrinasugosh    @jointinyLinkedIn: Mrina Sugosh                TinyMCEFollow us on X: The Angular Plus Show The Angular Plus Show is a part of ng-conf. ng-conf is a multi-day Angular conference focused on delivering the highest quality training in the Angular JavaScript framework. Developers from across the globe converge on Salt Lake City, UT every year to attend talks and workshops by the Angular team and community experts.Join: http://www.ng-conf.org/Attend: https://ti.to/ng-confFollow: https://twitter.com/ngconf             https://www.linkedin.com/company/ng-conf             https://bsky.app/profile/ng-conf.bsky.social             https://www.facebook.com/ngconfofficialRead: https://medium.com/ngconf Watch: https://www.youtube.com/@ngconfonline Stock media provided by JUQBOXMUSIC/ Pond5

Eno and DVR discuss aging stars whose long-term value might be on the cusp of falling, as well as a few players to target despite an overall body of work that leaves something to be desired. Rundown10:07 Freddie Freeman Is the Power & Speed Drop a Sign of Things to Come?18:02 Marcus Semien & Nearly Impossible Durability23:12 Jose Altuve & Extreme Pull Tendencies Over Time28:59 Vladimir Guerrero Jr.: Should We Still Chase A 2021 Ceiling?34:58 Adolis García: Fearing the Fast Peak From Late Bloomers with Aggressive Approaches36:37 Oneil Cruz: Will He Improve Enough Against Lefties in the Long Run?43:02 Zach Neto: Sacrificing Ceiling for a Safer Floor?46:01 Jordan Walker: No Homers at Triple-A This Season?!53:58 Alex Kirilloff: A Delayed Breakout Coming, or WYSIWYG?1:02:14 Project Prospect: The Prospects to Target Via Trade As Top 100 Lists Have In-Season UpdatesFollow Eno on Twitter: @enosarrisFollow DVR on Twitter: @DerekVanRipere-mail: ratesandbarrels@gmail.comJoin our Discord: https://discord.gg/FyBa9f3wFeJoin us this Thursday 1p ET/10a PT for our livestream episode!https://www.youtube.com/c/ratesbarrelsSubscribe to The Athletic: theathletic.com/ratesandbarrels Hosted on Acast. See acast.com/privacy for more information.

Eno and DVR discuss aging stars whose long-term value might be on the cusp of falling, as well as a few players to target despite an overall body of work that leaves something to be desired.  Rundown 10:07 Freddie Freeman Is the Power & Speed Drop a Sign of Things to Come? 18:02 Marcus Semien & Nearly Impossible Durability 23:12 Jose Altuve & Extreme Pull Tendencies Over Time 28:59 Vladimir Guerrero Jr.: Should We Still Chase A 2021 Ceiling? 34:58 Adolis García: Fearing the Fast Peak From Late Bloomers with Aggressive Approaches 36:37 Oneil Cruz: Will He Improve Enough Against Lefties in the Long Run? 43:02 Zach Neto: Sacrificing Ceiling for a Safer Floor? 46:01 Jordan Walker: No Homers at Triple-A This Season?! 53:58 Alex Kirilloff: A Delayed Breakout Coming, or WYSIWYG? 1:02:14 Project Prospect: The Prospects to Target Via Trade As Top 100 Lists Have In-Season Updates Follow Eno on Twitter: @enosarris Follow DVR on Twitter: @DerekVanRiper e-mail: ratesandbarrels@gmail.com Join our Discord: https://discord.gg/FyBa9f3wFe Join us this Thursday 1p ET/10a PT for our livestream episode! https://www.youtube.com/c/ratesbarrels Subscribe to The Athletic: theathletic.com/ratesandbarrels Learn more about your ad choices. Visit megaphone.fm/adchoices

Dan Maines, bassist and founding member of the iconic hard rock band CLUTCH, is my guest this week! Dan and I connected just before Clutch's show at Vinyl Music Hall in Pensacola on May 12. We talk touring, family, record label changes & what keeps Clutch going after all these years. The band released its 13th full-length album Sunrise on Slaughter Beach on September 16, 2022.Dan describes the special bond he shares with the other three members of the band — all of whom met while attending Seneca Valley High School in Germantown, MD 35 years ago. The foursome have continuously recorded and toured since the release of their first independent EP Pitchfork in 1991.Clutch wraps up its April/May New World Samarai Tour on May 19 — then embarks on its first tour of Latin America on July 18! The band returns to North America for a September/October "Two-Headed Beast" co-headlining tour with Rival Sons.Dan plays the Fender Precision Bass, Rickenbacker 4003 & Gibson EB-3 Bass.Be sure to visit Clutch's web site for merch, tour & band news — and follow the band across the socials. You can find the limited edition Transnational Speedway League signed 12" LP; Sunrise on Slaughter Beach 7" Box Set (Limited), CDs, apparel & more.www.clutchmerch.com@OfficialClutch - YouTube@clutchofficial - Instagram, XClutch - FacebookEpisode Art/Photo Credit: Dan Winters (@danwintersphoto)Very special thanks to Stefan KosterSongs appearing in this episode - used with permission:"WYSIWYG" (opening minutes of episode — appears on the album Blast Tyrant)"Hot Bottom Feeder" (20:56 mark — appears on the album Book of Bad Decisions)"Firebirds!" (outro of episode — appears on the album Psychic Warfare)

This teaching is taken from Colossians 3:8 and teaches you how the words you say create the results you see. /// If you have any questions, or you would like to share how our teachings have affected your life, please email us or visit us at www.rejoicingheart.net God bless you! Rob and Donna /// Rejoice In You From the Integrity Music Release One, featuring Planetshakers Ministries Int'l ©2009 Planetshakers Publishing (APRA) (admin. By Music Services, www.musicservices.org) All Rights Reserved. Used by permission.

Today we are talking about CKEditor 4 End of Life, Moving to CKEditor 5, and what you can expect from CKEditor 5 now and in the future with guest Wim Leers. We'll also cover CKEditor 5 Premium Features as our module of the week. For show notes visit: www.talkingDrupal.com/438 Topics CKEditor 4 end of life June 2023 Issues people might see if they are still on CKE4 Why a third party library and not roll our own Are there other alternatives Why did Drupal decide on CKEditor Drupal 10 moved to CKE5 How should people update Upgrade gotchas What's new in CKE5 What is on the roadmap regarding Drupal and CKE5 Is there going to be a CKE6 Native Web Components Does CKE in core affect Gutenberg Resources CKEditor 4 End Of Life Contrib Core, prioritized upstream blockers Core, all issues blocked on upstream (currently 29), if we look just at bugs there's 17 (1 of which is critical, 6 major) Drastically improve the linking experience in CKEditor 5 Drupal Image ability to opt in to SVG image uploads Native and UX https://www.drupal.org/project/drupal/issues/3274635 Extended html filter Views / ckeditor custom elements Guests Wim Leers - wimleers.com Wim Leers Hosts Nic Laflin - nLighteneddevelopment.com nicxvan John Picozzi - epam.com johnpicozzi Ivan Stegic - ten7.com ivanstegic MOTW Correspondent Martin Anderson-Clutz - mandclu Brief description: Have you ever wanted to offer your content creators advanced capabilities like real-time collaboration? There's a module for that. Module name/project name: CKEditor 5 Premium Features Brief history How old: created in Sep 2022 by Wiktor Walc, although recent releases are by Wojciech (vOYchekh) Kukowski, both of CKSource, the company behind CKEditor (Wiktor was on episode 372 https://talkingdrupal.com/372) Current version available: 1.2.5 which works with Drupal 9 and 10 Maintainership Actively maintained, latest release in the past month User Guide available, link is in the README Number of open issues: 16, 8 of which are bugs Usage stats: 159 sites Module features and usage To me, the most compelling features enabled by this module are the ones that turn your Drupal WYSIWYG into a robust collaboration tool, similar to what users may be used to in tools like Google Docs or Office 365 Real-time inline comments and changes from multiple users Track changes to suggest ways the content could be improved A history of changes made in the WYSIWYG, independent of the saved Drupal revisions Tag users with @ mentions to have them notified There's also a Productivity Pack to enhance your WYSIWYG, and again some of these will be familiar to users that also use popular online collaboration tools A document outline that uses heading within your content to make navigation for moving quickly within the document Can generate a linked Table of Contents, which will automatically update as headings are added or changed Slash commands to execute actions Enhanced Paste from Office, to preserve complex incoming content structures, but with clean HTML as the result And more! Another premium feature is the ability to export to Word or PDF, and it can also restore full screen editing, a feature that didn't make the transition from CKEditor 4 to 5, as part of the open source offering Finally, it also includes an AI Assistant that provides yet another interesting way to empower your content authors to leverage AI tools for their writing, including the ability to change the style, length, or tone of selected content using pre-made prompts, or generate content with custom queries. It also works with a number of different models out of the box, so you're not restricted to ChatGPT The module is open source but using these premium features does require a subscription. The pricing will depend on the number of active users and which features you need, so if you'd like more information you can use the contact form at ckeditor.com Also worth mentioning here that the team at Palantir has released a YouTube video of an open source collaborative editor that they're calling Edit Together. It's based on the ProseMirror rich-text editor framework, and the blog where they announced it mentioned a mid-2024 release, but that was back in Jul 2023 and I haven't been able to find any updates since then

Hey friends, today is a first impressions episode about Sysreptor, which according to their GitHub page, is a fully customisable, offensive security reporting solution designed for pentesters, red teamers and other security-related people alike.  It is easy to stand up with Docker, has built-in MFA and a great hybrid WYSIWYG/code editor.  The only scary part?  There is no export to Word (insert suspenseful music here!) - your reports just go right to PDF, friends!  The killer feature for us, though, is the ability to create reports from the command line and send files, notes and findings to Sysreptor automagically!

Connect with Beatrice Bruno   Beatrice Bruno, WYSIWYG, PGP  The Drill Sergeant of Life www.DrillSergeantofLife.com Cell: (720) 212-9780   Author | Speaker | Ghostwriter | Editor | US Army Veteran The Drill Sergeant of Life mission is to empower you to be all you care to be on the Battlefield of Life. You can be a Commander in Life! Be Bold and Courageous! God's Got You...   Facebook: https://www.facebook.com/DrillSergeantofLife/ Website: www.drillsergeantoflife.com Facebook: https://www.facebook.com/DrillSergeantofLife/ Website: www.drillsergeantoflife.com Order Beatrice's Books here: The Baby Chronicles - Where You Were Before You Were https://amzn.to/3DHgqXK How to Get Over Yourself, Get Out of Your Own Way, and Get What YOU Want Out of Life! https://amzn.to/3lcTnxA How To Get Over Yourself and Let Go of the PAST! https://amzn.to/3REzHyE Chronicles of Grief https://amzn.to/3Yuxb0s Up the Down Escalator: Are You Really Saved? https://amzn.to/3jz3Wun God Has Prepared the Table! Why Aren't You Eating? https://amzn.to/3HCe6Cw   Connect with Terry Lohrbeer Facebook: https://www.facebook.com/groups/2658545911065461/ LinkedIn: https://www.linkedin.com/in/terrylohrbeer/ Instagram: kickassboomers Twitter: @kickassboomers Website:  kickassboomers.com   Connect to Premiere Podcast Pros for podcast editing: premierepodcastpros@gmail.com   LEAVE A REVIEW and join me on my journey to become and stay a Kickass Boomer! Visit http://kickassboomers.com/ to listen to the previous episodes. Also check us out on Facebook, Twitter, Instagram, and LinkedIn.   Email terry@kickassboomers.com and connect with me online and on Facebook, Twitter, Instagram, and LinkedIn. 

Connect with Beatrice Bruno   Beatrice Bruno, WYSIWYG, PGP  The Drill Sergeant of Life www.DrillSergeantofLife.com Cell: (720) 212-9780   Author | Speaker | Ghostwriter | Editor | US Army Veteran The Drill Sergeant of Life mission is to empower you to be all you care to be on the Battlefield of Life. You can be a Commander in Life! Be Bold and Courageous! God's Got You...   Facebook: https://www.facebook.com/DrillSergeantofLife/ Website: www.drillsergeantoflife.com Facebook: https://www.facebook.com/DrillSergeantofLife/ Website: www.drillsergeantoflife.com Order Beatrice's Books here: The Baby Chronicles - Where You Were Before You Were https://amzn.to/3DHgqXK How to Get Over Yourself, Get Out of Your Own Way, and Get What YOU Want Out of Life! https://amzn.to/3lcTnxA How To Get Over Yourself and Let Go of the PAST! https://amzn.to/3REzHyE Chronicles of Grief https://amzn.to/3Yuxb0s Up the Down Escalator: Are You Really Saved? https://amzn.to/3jz3Wun God Has Prepared the Table! Why Aren't You Eating? https://amzn.to/3HCe6Cw   Connect with Terry Lohrbeer Facebook: https://www.facebook.com/groups/2658545911065461/ LinkedIn: https://www.linkedin.com/in/terrylohrbeer/ Instagram: kickassboomers Twitter: @kickassboomers Website:  kickassboomers.com   Connect to Premiere Podcast Pros for podcast editing: premierepodcastpros@gmail.com   LEAVE A REVIEW and join me on my journey to become and stay a Kickass Boomer! Visit http://kickassboomers.com/ to listen to the previous episodes. Also check us out on Facebook, Twitter, Instagram, and LinkedIn.   Email terry@kickassboomers.com and connect with me online and on Facebook, Twitter, Instagram, and LinkedIn. 

Salman Paracha, Founder & CEO at Katanemo Labs, joins Corey at Screaming in the Cloud to discuss his vision for the future of SaaS application development. Salman and Corey discuss what led him to take the leap into founding a start-up, and Salman shares how he believes the future of SaaS application development is at an inflection point. Salman also explains why it's critical to focus on the outcome your customers experience over infrastructure, and shares his vision for future developers looking to build the next wave of SaaS applications. About SalmanBuilding high-growth, high-tech software products that affect the lives of millions of customers. 15+ years of experience in building successful products and highly effective teams. I am deeply interested in bringing the power of the cloud to end customers, large scale data problems, and delivering scalable services on commodity hardware.Links Referenced: Katanemo: https://www.katanemo.com/ LinkedIn: https://www.linkedin.com/in/salmanparacha/ Email: mailto:salman@katanemo.com Twitter: https://twitter.com/salman_paracha TranscriptAnnouncer: Hello, and welcome to Screaming in the Cloud with your host, Chief Cloud Economist at The Duckbill Group, Corey Quinn. This weekly show features conversations with people doing interesting work in the world of cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. This is Screaming in the Cloud.Corey: Welcome to Screaming in the Cloud. I'm Corey Quinn. And this promoted guest episode of Screaming in the Cloud is brought to us by our friends at Katanemo, who is—when you talk to small startups, like, “Who should we talk to?” They invariably look around the room, figure out who they should throw directly into the grist mill, and in this particular case, they have selected Salman Paracha, who is the founder and CEO. Salman, thank you for joining me.Salman: Hey, thanks for having me. Second time.Corey: It is. And every time we talk, it seems like there has been an interesting progression in your career. Originally, when we first started talking, you were the GM of the serverless application repository at AWS, and of AWS SAM, the Serverless Application Model that most people know because of the giant psychotic squirrel running around the expo hall at events. Then you went to be a group VP at Oracle Cloud, and now you look around the landscape and decide, you know, what I've done my entire career? Worked at big companies where everything is, you know, convenient in certain ways. And that sucks. I want everything to be three times harder, at least, so I'm going to go start a startup of my own. Presumably. I'm assuming that is the thought process that led you here. What's the actual story behind why you decided to leave giant corporate entities and go to a small startup?Salman: Thanks for that intro. The primary reason to sort of pursue this dream was something was pulling at me for the past four to five years. As a person who considers himself a builder, the most happiest I am when I'm actually trying to ship software out for customers. And so, I've been pulling on this thread for a very, very long time, that the world of the modern reference architecture, as it goes more microservices and explodes in the face of developers, has gotten to a point that we are now being inundated with all these micro-primitives, if you would, on infrastructure that actually slow the rate of innovation down. And why hasn't there been a move and reversion to the other side?And so, as I looked around, and at my time at Serverless particularly, where we were trying to champion this idea of serverless compute where you don't manage your servers, I kind of was ruminating on this notion of how do you get to zero infrastructure? And the idea that how can we actually orchestrate out all the complexity behind the scenes and you can truly focus on what your application does. And in that part of the journey, I've been chatting with developers across swath of industries and varying degrees of sophistication if you would, and the thing that emerged is that the most complex, perhaps the most complex piece to build in the cloud is a SaaS application. And there's inherent complexity in sort of thinking through the various concerns of the shapes and sizes of your customers that you're serving, the security and safety controls that you have to give them, the operational burdens that you take to serve a very large customer versus a very small customer who is perhaps in your free tier.And so, I was pulling on this thread for a very long time, even at my time, somewhat, at AWS, having—I chatted folks like Twilio and Slack at that time, and I said, “I think there has to be a much, much better way.” It cannot be more; it has to be less, and that less is actually getting us closer to what we believe is the future of cloud infrastructure, which is no infrastructure. So, that's it. I mean, I think the core thesis was, “Hey, if I've operated at this intersection of hyperscale cloud infrastructure and SaaS applications for the past 20 years, what is the compression algorithm that I can apply and give to developers so that they can truly focus on building something phenomenal without having to worry about the complexity of the infrastructure, the security of the scaling of the operational, and the access logs, and all that stuff that they have to today focus on?” And then I'm very fortunate to have had a phenomenal team that have joined and humbled me in my journey here.Since last year, we have folks across the spectrum who have built these things at scale and at Lyft, at Dropbox, at Meta, at AWS, at Cloudera, and et cetera. And so, we've been really fortunate that we have a very firm belief of where we want to take the future of infrastructure and who we want to serve in that market segment. And I said to myself, I don't think I'm getting any younger. My parents, my South Asian parents, perhaps they're going to be more happy to see me sort of fight it out and battle it out versus just naturally climb the corporate ladder. Nothing wrong with that, of course.Corey: It's not too late to go be a doctor. I say that as someone who grew up in a Jewish home where there were certain expectations and pressures placed upon me that I continue to disappoint four decades later.Salman: Yeah, so anywho [laugh], on that front, so I think I'm kind of living to the expectations I had for myself 20 years ago when I joined the workforce, and I now have the great fortune to build alongside these amazing builders and see what we can unlock for the developer community.Corey: One of the challenges with the approach that I found historically has been Heroku did something very similar and then everyone tried to build the next Heroku, except for the company that bought Heroku, they were content to let that thing sit and never think about it again, for whatever reason. But another example would be something like NPM, the Node Package Manager, where it abstracts away stupendous complexity. You tell it to npm install for some project and it just starts scrolling huge amounts of text past and doing all kinds of work and your computer fans start screaming, and you're like, “Wow, it's doing an awful lot of fascinating stuff underneath the hood, and I really hope this works. If it breaks halfway through, I haven't first idea where to look under the hood to make sure that this actually works and doesn't break my application.”The problem that I have historically with the things in this space is it requires a certain element of trust. That said, looking at the things you've done before, the places you've been, I don't have to explain that to you. You have clearly spent your entire career in environments where mistakes matter because they're going to show very quickly to an awful lot of customers if they wind up getting out there. That feels to me like it's a significant competitive advantage versus, not to be disparaging, but a couple of founders fresh out of a boot camp who have never worked in the industry before, but they have an idea, gosh darn it, this is what they're going to build.Salman: You know, you'll find builders, and you'll have builders surprise you. And I, you know, salute all those who come out and start something new. I have a whole bunch of respect for that, just the courage that takes it. But there's an advantage that the team has, and we're very fortunate on having that advantage, having seen things break. And I think we're at this inflection point, perhaps now that there's been an incredible amount of effort done in the open-source community relative to [dis-established 00:06:56] standards.Like if you imagine, what, 25+ years ago, when HTTP and HTTP 1.1 came out, that created an explosion of people hosting these web services and HTTP-based applications. I think we're at the point where we can preserve the developer experience, preserve the operator experience, but never have to sort of have you tinker in the bowels of the infrastructure … to build a SaaS application. And I think that the interesting part of this is knowing how successful these projects can be, but also how complex they can be to manage. But if you (the developer) can just focus on dev experience and operator experience and ask what's the most pressing question to answer, which is…Can you know who (your customers) are and what they're doing in your system, and have the ability to shape their experience versus shaping the infrastructure?”I think we'll be in a much better state as an industry, we'll be much happier developers, we'll just be in a much higher place than we are today. Where as I said earlier, which is the modern reference architecture of microservices perhaps gives you some powers, but it really explodes the amount of choices and results in this massive drag on innovation. And that's that part of the lessons and learnings and insights that we have and we're going to compress that, hopefully, on behalf of developers as we build out Katanemo, particularly, you know, going towards this future of no infrastructure, zero infrastructure. So yeah, all respect to everyone who's building. You know, we've had the good fortune and we hope to pass that fortune back in terms of a product experience.Corey: This feels like a problem that never really goes away, at any scale, for that matter. I want to build out something new. Maybe it's just a ridiculous static site. Maybe it's some serverless-powered shitposting app. I have several of those in existence.And every time it's like, “Oh, you have a great idea for an application. Cool. Step one: do a whole bunch of infrastructure provisioning nonsense along the way first because that's going to be the important thing to get done.” And then, only then, do you get to start getting into the application logic and the rest. And it always feels like boilerplate, but it's specific boilerplate, in that it has to be right for this environment with this constraint and this use case, and it just feels like it's undifferentiated work that I don't want to be doing.Salman: I think that actually is magnified to a certain degree when you're thinking about an enterprise-grade SaaS application. And my impression is it's magnified of perhaps an order of magnitude more. Because in any modern SaaS experience, you would have to think through the list of concerns relative to your small customer base that's trying your product, teams that are relying on your experience that their workflows don't break, or perhaps large enterprises who you're trying to serve and upsell to. And that inherent complexity then gets baked into the choices on “Hey, should I have more nodes or should I have more concurrency or should I have more isolation boundaries? How do I think about security for multiple customers within my system?”And I think that's the really hard nut to crack. And we're focused there first because we believe we can serve that community really well, get off on the get-go, and then create the right level of experiences, perhaps for general business-to-consumer applications as well. But this problem, I think, it's magnified even more for the [unintelligible 00:10:01] dot community that's trying to start off with a developer-led motion but naturally wants to upsell to teams, organizations, and enterprises with their suite of services, perhaps a next-generation ChatGPT, if you would. So yeah, I'm with you. I hear you, and I think the problems amplified, in our view, to that other community that sort of struggles with this and has to hire specific talent to build that stack out.Corey: I have to ask, because I alluded to, it seems like every company has been trying to build the next version of Heroku, which when you distill down what the value would actually deliver doesn't sound that far removed from what it is that you're proposing to build. Hasn't this been done yet?Salman: So, I think the way we think about this problem is it's across multiple layers. And some components to this problem that's worth talking about. Of course, when you say zero infrastructure and no infrastructure, what does that even mean? Like, I think people naturally get confused. So, three weeks ago, we actually launched what we call our first set of capabilities on behalf of this community as we break things out in components, which is zero-trust capability.So, if you think about the space, there's a whole bunch of these undifferentiated essentials that you need to build something meaningful and serve users, teams, organizations, and enterprises. And Heroku is this approach was an abstraction—and a fine one, if you want to build a general purpose app that is just serving the consumer, perhaps. And we're sort of taking a very different position. We're saying we're here to solve you if you're building something that's going to serve developers, teams, or organizations. So, we are very different in terms of how we're approaching the market relative to what we want to go solve for.That's just number one. And B, as the thing that we recently launched, is how do we break this problem down on behalf of the community and be targeted to solve a particular problem? So, when I connected with developers in my journey for the past six to nine months as we've been in business, is that they felt that the modern state and fragmented nature of identity and access management is really complex for their application. Why? Because now you have this very interesting usage patterns for your applications.There's no longer users using something you're built. There are, of course, as I mentioned, teams, and of course, there's an enterprise component to this. There are machine keys for your APIs. And all these vectors now of uses all naturally become a threat vector that you have to protect for and they have to be neatly thought through from a access management strategy. And so, what we've set out to do is, like, how do we unify this experience today, and solve a real problem, which is you can effortlessly onboard any customer of any size and upsell through zero-trust capabilities like role-based access control, attribute-based access control, and give your customers the ability to achieve least privileged access?So, meaning how do you safeguard the most protected resources off your SaaS application and make sure they will be safeguarded, but if your users want to create for more sharing and collaboration experiences, you have the means for them to go achieve that without having to build custom logic, custom code, and perhaps spend, many months cycles and perfecting it? And that engineer that built it, and when it left, who's going to take over and maintain that piece of code?Corey: Not to mention you're going to get it wrong, and as a result, mistakes there have security implications that can be dire.Salman: I think that's where developers tell us, this is why—you know, I was talking to one potential developer the other day and the thinking was, hey, you know, it was really hard for us to, perhaps, let go of these security controls because we want to build them ourselves. And I asked them this question: “Where do you store your username and passwords for your applications?” Like, “I don't store them anymore.” Like, I think the reason why people have moved away from having these concerns is because it's a compliance security risk, it's a threat vector. And there are others who have hired teams and staff of experts to make sure that thing never breaks, on their behalf.And similarly, I think as you think about this multimodal identity experiences, this permissions experience that we have built for developers, we are the experts in this domain. We have advisors, past advisors from AWS IAM, perhaps people know that's a very popular. It serves billions of transactions a second, and securing cloud infrastructure at this rate of $100 billion worth of workloads. And so, we've got the expertise to help think through, like, what do developers need to create these safety guardrails, but with a phenomenal developer experience? And I'll give you an example of that, Corey.Like, in order for you to, sort of, interact with Katanemo, all you need to do is capture your API surface area in an OpenAPI specification or a GraphQL specification. And that submission of that specification means we know your resources, we know your resource model, your data paths, your access control mechanisms from the HTTP methods that you're exposing, and then we create the entire identity, customer identity, and finding permissions experience that the developer can expose to their customers in a self-service way to construct their own roles, construct their own SSO, construct their own access log controls, if you would, and just move past this, like, can we get to an enterprise-grade experience instantly as we serve, users, teams as effortlessly with us, and through their business lifecycle. Like, no developer is going to serve necessarily an enterprise on day one; they're going to get these teams really excited about their product and then they're going to have an upsell motion. But having to build these by bespoke experiences on onboarding and safety for each different cohort of the customers that they want to serve, that's just time away from stuff that they can build, cool things that are differentiating for them.Corey: One of the things has always sucked for me about building applications, even from an infrastructure perspective, has been that I don't know what I don't know. And I always feel like I am making a bunch of decisions now that make perfect sense, but when I start scaling or having to take this into a more serious environment, I'm going to have to throw so much of it away and backtrack massively. And oh, I shouldn't roll my own authentication subsystem and whatnot. But finding the right path forward that matches the current state of the art from an industry perspective really feels like a crapshoot, it's you're looking at all the horses, wondering which one you want to bet on and it carries a cost to get it wrong.Salman: In my time at Serverless, at EC2, even my time at Oracle, the whole idea was to make sure that we reduce this crapshoot behavior on behalf of developers. Of course, at AWS, at Oracle, it was very wide and horizontal in its appeal to any type of developer, but we have felt that if you sort of flipped on its head and go with a verticalized approach, and particularly target one persona and their use cases and their needs, that actually helps us, sort of, look at the problem very holistically and solve that thing just for them. And as I mentioned, we sort of focused on that SaaS use case, particularly, because we believe there's inherent and unbounded complexity there. So, this is just for playing from the experiences and learnings I've had in the past, which is, yeah, this stuff is hard. It's incredibly hard to get right, and just as, you know, the industry moved to hey, I can trust somebody else who's an expert here, we're saying we complete that story. And we look to the modern ways people access your applications through APIs and API keys, or users, or teams, or SSL, whatever, and we compress it, saying single API call to us and you get those capabilities out of the box so you can focus on what matters: moving fast, closing customers even faster.Corey: I think that is the grail that people are chasing. The problem I found, especially in the enterprise space, has been that it sounds great in theory, but in practice, it's a oh great, the old Model T story, you can get in any color you want, as long as it's black. And it's well, okay, that's a path, but it doesn't comport with our security requirements and our guardrails and our compliance objectives, et cetera, et cetera, et cetera. Rightly or—more often—wrongly, people tend to believe that they are bespoke unicorns whose problems could never possibly be realized by anything that wasn't brewed in-house at their own company. I don't find that to be true, but I imagine you're getting a lot of pushback from that direction.Salman: I think there are two pieces of feedback that we normally hear. “Oh, hey. We built some of this stuff. How do we sort of untangle the mess that we have?” That's fine. We can help them we have some components that easily wrap around their experience and give them the ability to sort of move to a better state.But if we build this stuff as a meaningful framework using open standards, like OpenAPI and GraphQL, as the only way you interact with us today, that means that your customers can now build, have a framework in which they set their own security standards against your service, against your application. And I think that makes you getting out of the business of defining the security posture to giving them the ability to construct their security posture is using open standards so their teams can plug down their own SEIM tools if they have to. But you have that framework powering your security and safety experience, your identity and access management experience, without having to build it.Going back to the earlier thing that we talked about, we believe we're in an inflection point where standards do establish a lot of innovation, specifically in infrastructure, and we're going to leverage as much as we can on behalf of developers to bet on those standards. Like I said, OpenAPI, GraphQL, AsyncAPI, so that their customers can say, “Yeah, I get it. I understand your surface area. I can construct these things at least privileged or coarse grained. That's my choice. You're going to give me access logs so I know what I did, or who did what, when, and how, so, you know, I can confirm for my compliance requirements.”And they're off the hook. They're actually truly off the hook without having to think about, I think I can do it better because my customers are pi—or second, their customers put these requirements that take them and create [sort of 00:19:29] Rube Goldberg type of scenario in terms of their own stack. So, we think we have something to really serve the market and make it such that it's not necessarily bespoke.Corey: I think that you're probably right that there's a lot of opportunity to develop those things. I mean, you spent enough time at Amazon, for example, to have benefited from the realization of some of this. One of the nice things I have to imagine, about building a product or a service at AWS is so much of the infrastructure work has already been done. You're not going to convince me that individual service teams have to sit there and come up with, well, we need to implement a global, highly available block store. S3 already exists. It's right there. You can use it.Same with authentication in the form of IAM, et cetera, et cetera, et cetera, a bunch of internal infrastructure stuff that's there and ready to go. Now, the counterargument, of course, is, as you're building this out, you don't have that, I guess, luxury anymore of big company, massive, awesome infrastructure there and ready to go, other than what is available to the rest of us mere mortals. So, I have to ask, is that the big part of what sucks about building SaaS these days or are you finding the friction and challenging parts somewhere else?Salman: So, it's a good question because Katanemo is built on Katanemo. It's a very [mind-tingling 00:20:46] type of discussion, but the one principle that we took is if we're going to build something on behalf of the community, then our product and service has to consume it as well, and specifically in talking about identity and access management for our SaaS service. Because there's nothing in the market that neatly solves this problem today. And should we rely on the cloud infrastructure and build on top of AWS and perhaps others in the market like Azure or GCP trying to do? Yeah, absolutely.We're not here to reinvent the primitives that are there for low-level infrastructure. We have a very strong non-religious belief that hey, we should leverage what we have, so we can move faster into market. So, we have a whole bunch of usage on, you know, openly speaking, we, when customers ask us, “How do you [unintelligible 00:21:27]? I'm like, “We use KMS for securing some of the things that we do on your behalf.” We have architected around the complexity on [unintelligible 00:21:34] groups and pools and multiples and trying keys and all that stuff. And so, we are trying to use as much as we can, but as I go back to this earlier notion, we're trying to develop a purpose-built experience that dramatically simplifies for that developer community.And tomorrow, as we go in towards our [unintelligible 00:21:51] infrastructure future, we will then design something very particular for that next community. And perhaps it's going to be a gaming community if we want to solve their problems. And that's going to be the ethos of the company. It has to be purpose-built, it has to be developer experiences phenomenal, not just digging any large cloud provider, but that is a missing component tree and how to think about it, and make sure that we can compress our infrastructure and systems knowledge so that they don't have to build it. And so, that's the mission that we're on. And we're, of course, very excited about what we're doing and very fortunate to have both the team and the backing that we have so far to pursue this a little bit further.Corey: You're putting your finger right on a very painful spot that has been resonating with me for a long time, which is that it feels like building something on top of AWS natively is a lot like going to the Home Depot and building a cabinet. Well, you go walk up and down the aisles and you pick the exact wood you want, the exact stain for it, the fasteners, et cetera, et cetera, et cetera, whereas sometimes you just want something to store some bowls, so going to Target is going to be the better solution. But now you're so forced to go and build these things yourself from parts. And that just feels like it has been such a heavy lift for folks because there's so much you need to understand. And it's more or less a shipping of AWS's internal product culture.But containers, databases, networks, compute, et cetera, are all things that any customer building even a Hello World app has to think about. But that falls across five different talk tracks at re:Invent, for example. It's too much burden that has been put on the customer and as a result, I think that there's a lot of value being left on the table. I spend roughly equivalent amounts of money every month on AWS and on Retool. For AWS, I spent about 450 bucks to get about 450 bucks worth of infrastructure services.Retool, which is basically a WYSIWYG app that designs in-house applications charges me about 400 bucks for which I receive probably about 20 cents worth of infrastructure services, but the value it presents by stringing those things together for me means I am happy to pay it. I really feel like there's a massive untapped value in being able to deliver not building blocks, but conceived solutions that get out of the way and let people build the differentiated thing that they're in business to build.Salman: We feel the same way. I think part of this realization is developers who are building these things continue to stumble upon the explosion of courses and certification material and all that stuff to train themselves to do something. As of course, naturally, AI comes into play and the way that you know the future of applications continues to press upon, you have to build something quickly, you will see that this notion of just [hugging 00:24:32] your primitives or hugging these low-level infrastructure primitives is going to go away because the world is moving at an incredibly breakneck pace. And that will be true, but there is truly now an inflection point where everyone wants to move even faster.And our talk track with, I guess, our customers is, focus on what really matters to grow your business. And if you are a SaaS developer, or perhaps you're a gaming developer, or perhaps you're thinking very specifically in terms of vertical industry that you want to unlock, like, a healthcare company, for example, you should focus on great patient care, you should focus on great gaming experience, you should focus on great X, Y, Z. Don't focus on infrastructure. Infrastructure is not the outcome. The outcome is your customers are happy and you're going to serve them.And your customers are not all equal size, equal shape, and never will be, but you need to give equal shape, equal size, type of price performance or great experience to them. Because you're not necessarily going to spend the effort to make sure that your free tier is the most highly performant place for you serve your customers and leave your perhaps platinum or enterprise customers hanging dry, as an example. But yeah, I mean, I think that's the ethos of our company and the spirit of what we are trying to go build. As I said, we're humbled to be—I am humbled to be surrounded by folks who are much smarter than me and been better builders, and customers who are so excited about our journey. So, this is a good time for us at the moment.Corey: I understand the grass is always greener when it comes to looking at the road not taken. For me, I see one of the advantages of running a services business as I do, in that, well, I can start a services business on Monday and by you know, Friday or so, I have my first client lined up and I'm ready to start performing work and get paid immediately. SaaS on the other hand feels a lot more like a real estate adjacent, where you have to go ahead and buy the land and get everyone lined up and sink the massive investment into it to get it built up, and you won't know for years in some cases whether this is something that is going to catch on, much less even justify the cost of building it in the first place. Where are you on that journey as far as validating that you're building something that's resonating?Salman: So, we have design partners, we call them because they're shaping our product experience. And we don't call them customers yet, just because we're in sort of the early stages. But we have designed partners across four critical industries. One of them which is AI, as the booming next-generation AI company is going to be API-first, we have that use case that we can target really well. They're really early in their days and they need support across their business lifecycle. Hey, I'm just going to support three users tinkering of my product to 3000 customers in an enterprise.But that's one. We are very much engaged in the healthcare space because the healthcare is actually going through a very massive legal transformation through—well, what's happening there's this HL7 FHIR standard which is actually making healthcare records more interoperable. So, you actually can get patient records if you go from one doctor to the other and not be blocked by the healthcare Gods to say, “No, you cannot do that.” And that is actually creating a very net-new experience in the healthcare space, so we have very customers excited about how we can self-solve their problems in terms of identity and authorization. We have customers in the Web3 off-chain space.So, on-chain is all permissionless and it's a whole bunch of different type of development experience, but off-chain has very much of the same characteristics that you will find on a traditional SaaS application. They [need 00:27:56] about safety, you think about privacy, you think about users and teams and API keys and a whole bunch of stuff that sort of baked into it. And the general developer tools who are going from an open-source experience to perhaps a cloud service experience, they've got a really great project in the GitHub, they got a bunch of stars and they now have to think about how to provide a better value to customers? And they have to go through a journey.So, in those four general sort of in buckets is where we are operating right now. We're very excited about that. And, you know, this opportunity to talk to you is to connect with more folks, especially as we, as I travel in the to AWS New York Summit, or perhaps just meeting up through one-on-ones through Calendly, or whatever have you, and figuring out how we can unlock more value for customers in these use case verticals, or perhaps something that we haven't necessarily thought through yet.Corey: I think that one of the clear signs of someone who used to work at Amazon is that—I don't even have to ask; I already know the answer—of are you talking to prospective customers before you start building things? Whereas start to finish everyone I've ever met at AWS is highly focused on the customer experience, whereas when you talk to people building things who have not been through that, a depressing amount of the time, your question is, okay, so what do your prospective customers think about this? Like, “Oh, we haven't talked to any of those people, yet. Talking to people is scary and we're here to write code.” It's, “You might be surprised by what you learn.”And there's no immunity to it. When I started this place, I thought I knew pretty well what people thought about their AWS bill, and it turns out, I was way off. There were nuances of the way customers talked about it that I didn't fully understand. So, to that end, in fact, we can prove it relatively easily. What is something you have learned about your space since you started the company from customer conversations?Salman: Oh, we actually made a pivot into this space that we are in at the moment because customers told us that's something that they do not want to focus their efforts on. Repeatedly. We did not write a single line of code all up until November of last year, but once we got the signal from our, as I said, as I mentioned, design partners, they're like, “This is a problem worth solving.” They're like, “We're going to get to work for you. You have these use cases, you have these scenarios that are coming up in your conversations with your customers. Let us be that accelerant for you and be an extension of your team in some ways, so that you can focus on what's really, really, really important.”So, you know, I think that's just survival, Corey. Part, of course—naturally, of course, you work backwards from customers and that was the framework I used when I joined Amazon back in 2012. And even in my time at Oracle, that's been the ethos of my, I guess, my personal self. But in our case, particularly, we actually talked about a very different idea, we wanted to start, but then customers told us, “You know what? Don't start there. Start here.”And I think that's obviously, just the nature of surviving in through the first few years of your company existence is… getting people to say yes and getting people to say no, and then no, is actually really valuable in many cases because it tells you what to adjust to. And so, we adjusted here as a result of those conversations.Corey: That may be the best answer to that question I think I've ever gotten. That is a phenomenal way to approach things. We started building a SaaS product here and two months later, we sunset the SaaS product because it turned out that what we were building and what customers wanted were not necessarily aligned. I like you said didn't even write a line of code until last November, just because of the conversations were still shaping what was actually needed in the marketplace. You would be astonished how rare that is.Salman: I guess. The startup founders that I have the privilege to call peers, they actually taught me some of the stuff. So, we've got the startup founders we want to just connect on the founder journey, we're happy to connect. Just, but yeah, I think that the strength of the team is sort of making sure that we have our ears to the ground. Get out of the building. You got to get out of the building. And we've been trying to get out of the building as much as we can with Katanemo. And I think that journey just continues. The learning journey, the evolution of what we're doing on behalf of SaaS developers continues, and we hope to delight them.Corey: I want to thank you for taking the time to speak with me. If people want to learn more, where should they go?Salman: So, they can go to katanemo.com, which is where our website is, and they can learn a little bit about what we do today and also where we're headed with the venture. They can reach out to me directly on LinkedIn. Salman Paracha. I'm not super hard to find on LinkedIn. You search for me and say Katanemo or AWS and Oracle, I think you'll be able to get to me. I'm also going to the AWS New York Summit, which happens on July 26, I believe. I might run into you there.Corey: Oh, yes. The night before I'll be hosting a drink up at Vol de Nuit at eight o'clock. You're welcome there, as anyone who's listening. And oh, it's always a pleasure to go and talk to people doing interesting things and just talk shop. But that's the reason I throw the drink up.Salman: Ah, okay. I'll take you up on that. And good, we'll get to see each other face-to-face after some time. You can reach out to me, as I said, even basic email, and I'll say that to you, and LinkedIn if you're just a chat. And there's just so many ways to get to me. On Twitter, I'm @salmanparacha, and it should be a bit easier to find me.Don't hesitate to reach out or search or connect with us. We are eager to talk to folks who are trying to solve or crack this Gordian Knot on terms of the what they're building. And especially if you're building towards the next-generation AI application and think through safety, we believe we are years ahead in terms of thinking about safety in that space. It's early days for us there, but we're obviously interacting with customers and developers who are trying to think through, how do I now take what was understood to be a table stakes, okay, API-first experiences, [user seems 00:33:31], keys, all that good jazz, and provide safety for that? But I think the new world that we're going to live in is not only going to just be deterministic responses from APIs; it's going to be probabilistic responses from large language models. And we got something going on in that space, particularly. We feel fairly bullish on it. But more, customer conversations before we write a piece of code is important. So, just connect with us. I'm salman@katanemo.com, on LinkedIn, Twitter, and I will be quick to reach back out to you.Corey: And I will, of course, put links to that in the [show notes 00:34:02]. And I've also filled out the contact us form on katanemo.com because I have a couple of problems it sounds like this might absolutely be a way to solve. Because otherwise, God help us all. I'm writing another login page.Salman: Right. So, just see Corey Quinn just signed up for our access. So, I will give you access. So.Corey: You think I'm kidding. I assure you I'm not. That's the scariest part is that I'm often being completely serious and people think I'm making a joke. Thank you so much for taking the time to speak with me. I really appreciate it.Salman: Hey, thanks for the time. I appreciate the opportunity.Corey: Salman Paracha, founder and CEO at Katanemo. I'm Cloud Economist Corey Quinn and this has been a promoted guest episode of Screaming in the Cloud brought to us by our friends at Katanemo. If you've enjoyed this podcast, please leave a five-star review on your podcast platform of choice, whereas if you've hated this podcast, please leave a five-star review on your podcast platform of choice, along with it insulting comment talking about how difficult it was to build that platform yourself from scratch because of all the infrastructure moving parts before it would take that insulting comment.Corey: If your AWS bill keeps rising and your blood pressure is doing the same, then you need The Duckbill Group. We help companies fix their AWS bill by making it smaller and less horrifying. The Duckbill Group works for you, not AWS. We tailor recommendations to your business and we get to the point. Visit duckbillgroup.com to get started.

In this supper club episode of Syntax, Wes and Scott talk with Steve Krouse about val.town, what it is, his philosophies on teaching people to code, the tech stack for val.town, and the benefits of inspiring kids to learn to code. Show Notes 00:36 Welcome 01:27 Who is Steve Krouse? Steve Krouse Future of Coding stevekrouse (Steve Krouse) · GitHub Steve Krouse (@stevekrouse) on Twitter Coding Classes for Kids & Teens | Coding for Kids | The Coding Space 03:06 What is Val.town? Val Town 08:35 Where did the inspiration for social dev environments come from? 12:52 WYSIWYG code vs being code first 16:30 How does val.town inspire people? 20:26 How do you prevent people abusing val.town? 24:57 What's the UI story for snippets on val.town? 27:31 Do you plan to support express? 29:03 What's the tech stack behind the front end of val.town? 30:35 What's the tech stack for the back end of val.town? 34:37 How do you measure for pricing? 37:07 Who is using val.town? 42:00 What's your methodology for teaching kids to code? 47:44 Supper Club questions GitHub - pomdtr/sunbeam: Generate powerful TUIs from simple scripts written in any language. Deno — A modern runtime for JavaScript and TypeScript A Small Matter of Programming The Unison language CodeMirror A Small Matter of Programming: Perspectives on End User Computing Stripe Press — Ideas for progress pomdtr/sunbeam: Generate powerful TUIs from simple scripts written in any language. Seymour Papert woofjs.com Bret Victor Welcome | Future of Coding Tom MacWright (@tmcw) 55:54 SIIIIICK ××× PIIIICKS ××× ××× SIIIIICK ××× PIIIICKS ××× SwitchBot Wi-Fi Smart Lock Shameless Plugs Val Town Tweet us your tasty treats Scott's Instagram LevelUpTutorials Instagram Wes' Instagram Wes' Twitter Wes' Facebook Scott's Twitter Make sure to include @SyntaxFM in your tweets Wes Bos on Bluesky Scott on Bluesky Syntax on Bluesky