Podcasts about Eclipse Foundation

Oh my, Spring is around the corner and OffHeap was again invited to be part of DevNexus! This episode is so awesome because we got a chance to talk to three Open Source Foundations: Apache Software Foundation, Eclipse Foundation, and CommonHaus Foundation. We discussed how they are similar, and (more interestingly) how they are different. […]

Deb Bryant discusses her career journey and the significant role of open source software in public policy, particularly in the US and Europe. She highlights her work with the Open Source Initiative, Oregon State University, and Red Hat, emphasizing the importance of open source in government operations and cybersecurity. Deb also addresses the challenges and evolution of open source policies, the critical need for sustainability in open source projects, and her current focus on AI's impact on the ecosystem. She concludes by advocating for harmonized international regulations and human-centered AI approaches. 00:00 Introduction 00:44 Government and Open Source Software 01:38 Experiences in the Private Sector 02:14 Open Source in Public Policy 04:31 Cybersecurity and Open Source 07:42 Sustainability in Open Source 15:05 Future of Open Source and AI 18:53 Conclusion and Final Thoughts Guest: Deb Bryant, Director, US Policy and Founder, Open Policy Alliance Open Source Initiative Throughout her career, Deborah has lent her voice to supporting open source projects and developers, building bridges between academia, industry, non-profits, and government along the way. Today she provides guidance to open source foundations seeking to support public policy development in open technology domains. She has worked in emerging technology and has been an advocate of free and open source software and the community that makes it so since the 1990s. Deborah is board director emeritus at the Open Source Initiative (OSI); serves on the DemocracyLab board; serves on the advisory boards of Open Source Elections Technology Foundation and the OASIS Open Project, and as an advisor to the Brandeis University Open Technology Management program. She also represents OSI as a member of the Digital Public Goods Alliance. For eight years prior to her reentry into the nonprofit world, she led one of the world's largest open source program offices (OSPO) at Red Hat where her global team was responsible for the company's strategy and stewardship in open source software communities. While at Red Hat she served on the Eclipse Foundation board for two years. Deborah's published academic research includes the Use of Open Source in Cybersecurity in the Energy Industry and Collaborative Models for Creating Software in the Public Sector.  

In this episode of the IoT For All Podcast, Frédéric Desbiens, IoT and Edge Computing Program Manager at The Eclipse Foundation, joins Ryan Chacon to discuss the latest findings from the 2024 IoT & Embedded Developer Survey Report. The conversation covers the sectors leading the IoT space, such as industrial automation and automotive, trends in sustainability, security, and safety-critical systems, the growing importance of open source, UX design in IoT, industrial IoT protocols and MQTT, and changes in safety certifications. 2024 IoT & Embedded Developer Survey Report: https://outreach.eclipse.foundation/iot-embedded-developer-survey-2024 Frédéric Desbiens is the IoT and Edge Computing Program Manager at The Eclipse Foundation. His job is to help the community innovate by bringing devices and software together. He pairs his domain knowledge, skills, and experience in open source, IoT, and cloud platforms with social engagement to grow Foundation awareness and commercial adoption. He has held positions at Pivotal Software (contributing to the Cloud Foundry open source BOSH project), Cisco, and Oracle. The Eclipse Foundation provides a global community of individuals and organizations with a business-friendly environment for open source software collaboration and innovation. They host the Eclipse IDE, Adoptium, Software Defined Vehicle, Jakarta EE, and over 420 open source projects, including runtimes, tools, specifications, and frameworks for cloud and embedded applications, IoT, AI, automotive, systems engineering, open processor designs, and many others. Headquartered in Brussels, Belgium, The Eclipse Foundation is an international non-profit association supported by over 385 members. Discover more about IoT at https://www.iotforall.com Find IoT solutions: https://marketplace.iotforall.com More about The Eclipse Foundation: https://www.eclipse.org Connect with Frédéric: https://www.linkedin.com/in/fredericdesbiens/ Our sponsor: https://www.qoitech.com (00:00) Sponsor (00:34) Intro (00:48) Frédéric Desbiens and The Eclipse Foundation (01:32) 2024 IoT & Embedded Developer Survey Report (03:09) Leading sectors in IoT and use cases (06:57) The shift to IoT solutions (08:10) Security priorities in IoT (12:08) Safety-critical systems and certifications (16:32) UX and UI design in IoT (19:24) Industrial IoT protocols and MQTT (21:32) The importance of open source (24:19) Developer demographics and insights (26:48) Learn more and follow up Subscribe on YouTube: https://bit.ly/2NlcEwm Join Our Newsletter: https://newsletter.iotforall.com Follow Us on Social: https://linktr.ee/iot4all

I interviewed Gorkem Ercan from Jozu about a few essential topics within the development ecosystem that apply to many different technologies, including Apple development.Gorkem at JozuEclipse Foundation(00:00) - Introduction (00:23) - Jozu (01:54) - Eclipse Foundation (08:10) - Train your inbox (09:46) - Open Source (12:25) - CI/CD (18:17) - Support the Podcast (18:37) - AI/ML (31:06) - Coffee is on me (44:18) - Jozu (44:42) - Support the podcast (44:49) - Rate and review Become a Patreon member and help this Podcast survivehttps://www.patreon.com/compileswiftYou can also show your support by buying me a coffeehttps://peterwitham.com/bmcFollow me on Mastodonhttps://iosdev.space/@Compileswift Thanks to our monthly supporters Tung Vo Adam Wulf bitSpectre Arclite ★ Support this podcast on Patreon ★

In this episode, we are joined by Thabang Mashologu, VP of community at the Eclipse Foundation, who dives into the findings of the organization's recent study on the State of Open Source in the Global South.Key talking points include: The positive impact that open source is having in the Global SouthHow developers are using it to drive career growthUsing open source to solve gender inequality issues Download the Report: https://outreach.eclipse.foundation/open-source-global-south-developers 

This week on The Business of Open Source I spoke with Mike Milinkovich, executive director at the Eclipse Foundation. We had a wide-ranging conversation about the role of open source foundations in the open source ecosystem, especially as related to open source businesses. The existence of open source foundations, and how companies decide to engage (or not) with them, is one of the aspects of open source businesses that is truly unique. Perhaps one of the key things to keep in mind from this conversation is that a foundation's priority is project sustainability — and that is not always aligned with the goal of increasing profits for a company. On the other hand, there are a lot of advantages to contributing a project to a foundation. But founders should be aware of both the advantages and the constraints that working with a foundation entails. Here are some of the things that stood out from our conversation: Investors want a successful business more than they want a successful project; foundations' priorities are opposite. You have to take into account commercial/financial interests if you're thinking about sustainability of a project, because you have to put food on the table; projects take time to maintain.The only community you get around an open source project is the one you build — contributing a project to a foundation is not a magic community pill, and building a community takes work. Running a foundation is not free, so if you're going to contribute a project to a foundation seriously consider supporting that foundation financially.Your customers should also become sponsors or members of the foundation(s) that your project(s) are hosted under, and you should actively encourage them to do so. Listen to the entire episode for even more insights! 

Guests Tracy Hinds | Ashley Williams Panelist Richard Littauer Show Notes On today's episode of Sustain, host Richard Littauer is joined by guests, Tracy Hinds and Ashley Williams, to discuss the structural inequities and funding issues in open source. The episode delves deep into the misaligned incentives in the open source community, how regulatory and policy awareness is growing, and the potential for government regulations to create opportunities for open source maintainers. The conversation also covers the roles of various open source foundations, the impact of large corporations, and the need for more effective advocacy and compensation avenues for contributors. Tracy and Ashley announce their involvement in a working group focused on the European CRA legislation, aiming to bridge gaps between maintainers and policymakers. Press download now! [00:02:22] Ashley responds to Richard's comment about everything being “totally screwed” in open source, but also points out misaligned incentives. She discusses the economic challenges of open source, such as the failure of sustaining efforts and its broader economic impact. [00:04:54] Richard mentions his other podcast “Open Source for Climate” which focuses on leveraging open source technology to combat the climate crisis. [00:06:10] There's a discussion about potential regulatory and policy changes affecting open source, highlighting the need for a more equitable system. Ashley delves into economic theories relating to open source, particularly the concept of externalities and potential regulatory solutions, and upcoming regulations like the software bill of materials. [00:10:05] Tracy stresses the importance of involving open source maintainers in policy discussions to avoid misrepresentation by larger organizations alone. [00:11:47] Richard and Ashley discuss the representations of open source interests in policy making, particularly the dominance of large companies and the potential exclusion of individual maintainers. [00:16:04] Ashley critiques many language-based foundations for their minimal contribution to ecosystem, using Node Foundation as an example of one that has been beneficial due to its library ecosystem, notably NPM. [00:17:35] Tracy acknowledges the efforts of the Python Software Foundation (PSF) and Open Collective in fostering ecosystems that support paid contributors, emphasizing the importance of these roles for sustainability. [00:19:50] Richard notes that while centralized support like AWS services vouchers are helpful, these foundations do not effectively facilitate crucial conversations between maintainers and governments regarding open source regulation and standardization. [00:21:52] Ashley reflects on her experience as the Individual Membership Director at the Node Foundation, discussing the challenges of representing a diverse community within open source projects and foundations. [00:24:45] Tracy mentions her role as the first community seat director on the board, highlighting the evolution and ongoing adjustments in community representation within foundation governance. Also, she discusses the importance of involving individual maintainers in regulatory discussions. [00:27:47] Tracy talks about the economic opportunities in open source, facilitated by platforms like GitHub Sponsors and Patreon, which help reduce barriers for maintainers seeking financial support for their projects. [00:29:20] Ashley puts a small spin on Tracy's optimistic view, noting significant opposition to the empowerment of small open source businesses, primarily due to corporate-dominated structures and antitrust-friendly environments in tech. She argues that open source has been consolidating. [00:33:29] Ashley fills us in on where you can follow her and their future discussions. She mentions a working group at the Eclipse Foundation focusing on CRA legislation, announcing an initiative to gather maintainer feedback on this legislation through a reading group. [00:35:42] Tracy mentions where you can find her online. Quotes [00:03:30] “We have open source – people who maintain open source don't really make a lot of money from it. Attempts to sustain open source have largely failed.” [00:06:24] “Every OSS hacker is also incentivized to be a lawyer.” Spotlight [00:36:32] Richard's spotlight is Jingna Zhang and her new social network, Cara. [00:37:25] Tracy's spotlight is the book, Working in Public: The Making and Maintenance of Open Source Software. [00:38:09] Ashley's spotlight is exercising for mental health. Links SustainOSS (https://sustainoss.org/) SustainOSS Discourse (https://discourse.sustainoss.org/) podcast@sustainoss.org (email) (mailto:podcast@sustainoss.org) richard@theuserismymom.com (email) (mailto:richard@theuserismymom.com) SustainOSS Mastodon (https://mastodon.social/tags/sustainoss) Open Collective-SustainOSS (Contribute) (https://opencollective.com/sustainoss) Richard Littauer Socials (https://www.burntfen.com/2023-05-30/socials) Tracy Hinds X/Twitter (https://x.com/hackygolucky?lang=en) Tracy Hinds Mastodon (https://mastodon.social/@hackygolucky) Sustain Podcast-Episode 135 featuring Tracy Hinds (https://podcast.sustainoss.org/guests/hinds) Ashley Williams Twitter (https://x.com/ag_dubs) Ashley Williams LinkedIn (https://www.linkedin.com/in/ashleygwilliams/) Sustain Podcast-Episode 145 featuring Ashley Williams (https://podcast.sustainoss.org/guests/williams) Open Source Initiative (https://opensource.org/) OSS for Climate Podcast (https://ossforclimate.sustainoss.org/) Eclipse Foundation (https://www.eclipse.org/org/foundation/) Jingna Zhang (https://www.zhangjingna.com/) Cara (https://cara.app/login) Working in Public: The Making and Maintenance of Open Source Software by Nadia Eghbal (https://www.amazon.com/Working-Public-Making-Maintenance-Software/dp/0578675862) Sustain Podcast-Episode 51 featuring Nadia Eghbal (https://podcast.sustainoss.org/guests/nadia) Credits Produced by Richard Littauer (https://www.burntfen.com/) Edited by Paul M. Bahr at Peachtree Sound (https://www.peachtreesound.com/) Show notes by DeAnn Bahr Peachtree Sound (https://www.peachtreesound.com/) Special Guests: Ashley Williams and Tracy Hinds.

This is part 3 of the JCON interviews. In this episode, Frank meets Otavio Santana, who recently wrote the book "Mastering the Java Virtual Machine." At JCON, he talked about the persistence layer and how you can evolve your career. You'll also learn more about Jakarta EE, GlassFish, and a PET project with messaging via Telegram. Content00:42 Otavio Santana: Book Author, Talks about the persistence layer and evolving your career thanks to open-source.https://www.linkedin.com/in/otaviojava 08:44 Arjan Tijms: Jakarta EE, Eclipse Foundation, Which version of Java to use https://www.linkedin.com/in/arjan-tijms-1214aa1b1 17:08 Ondro Mihalyi – Jakarta EE, Eclipse GlassFish, Creating small Java applications, Edge devices https://www.linkedin.com/in/mihalyiondrej 24:09 Buhake Sindi – Talks about Jakarta EE in the cloud, Comparing Jakarta EE to other frameworks, Java community in South Africa https://www.linkedin.com/in/buhake-sindi 31:50 Patrick Baumgartner – Swiss community, Talks about a PET project with messaging via Telegram https://www.linkedin.com/in/patbaumgartner

On this episode of Embedded Insiders, we're discussing why multi-camera synchronization is a key feature in cameras that enable industrial robotics, retail application, autonomous mobility, and more, with Mr. Maharajan Veerabahu, co-founder & vice president of product design services at e-con Systems.Next, Heiko Huettel, VP of software products at HARMAN International, joins us to discuss his company's role in the Eclipse Foundation's recent SDV Working Group, which has formed in an effort to develop an open-source hardware platform that can be used in today's software-defined vehicles.But first, Embedded Computing Design is hosting a Smart Manufacturing Day virtual event focused on AI/ML-Infused Automation and Manufacturing on March 12th. For more information, visit embeddedcomputing.com

A few years ago, Microsoft acquired Express Logic, who's key product was the ThreadX operating system. Fast forward to today, and Microsoft has released that operating system to the open-source community. Why did they do that? And what does that mean to the development community? I was really curious about these issues, so I spoke to Frédéric Desbiens, who manages the embedded, IoT, and Edge computing programs at the Eclipse Foundation on this week's Embedded Executives podcast.

In this episode of ⁠⁠⁠⁠BragTalks⁠⁠⁠⁠, Carmen Delgado shares her career path to the technology space with host Heather VanCura. Carmen is a member of the Java developer community and she shares how her journey from working in a traditional financial role, to a fintech role, to technical developer community management. Season 5 is all about sharing stories of pathways to promotion and Carmen has an inspiring story to share. Listen to learn how to chart your unique path to success and career satisfaction. Biography Carmen Delgado joined Eclipse Foundation as Adoptium Community Manager in October 2022 and is responsible for helping the Eclipse Adoptium working group members achieve their goals and objectives and being the bridge between their procedures and Eclipse Foundation processes and Staff. Carmen has a project, operations, and financial management background in SMEs, non-profits, and start-ups from different industries: healthcare, Pharma, Fintech, and Tech. She also volunteers as a group manager and mentor at Step4ward, a mentoring program in Spain for women starting in the tech world.

Guests Wolfgang Gehring | Ana Jiménez Santamaría Panelist Richard Littauer Show Notes Hello and welcome to Sustain! Today, Richard is joined by two guests from FOSS Backstage 2023 in Berlin. His first guest is Wolfgang Gehring, OSPO Head at Mercedes-Benz Tech Innovation. Wolfgang discusses the importance of open source at Mercedes-Benz. He mentions the company's recent FOSS convention, explains his role in getting people to work together, and talks about the challenges of de-risking and softening legal requirements. Richard asks for advice on how other large industrial companies can get started with OSPO. Finally, Wolfgang discusses his involvement with the Eclipse Foundation and their efforts to revise the Cyber Resiliency Act in the EU, and a great conversation about how large industries use and evangelize open source. Richard's next guest he has another great conversation with is Ana Jiménez Santamaría. She discusses her work with the OSPO community and the importance of sustainability in open source ecosystems. Richard and Anna discuss a survey done by the TODO Group. Also, Ana talks about the importance of educating non-tech audiences on open source, and her new YouTube channel helping teach open source in an easy way to those not familiar with the tech stuff, particularly in Spanish, where there is a lack of content. Download this episode to hear more! Links SustainOSS (https://sustainoss.org/) SustainOSS Twitter (https://twitter.com/SustainOSS?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor) SustainOSS Discourse (https://discourse.sustainoss.org/) podcast@sustainoss.org (mailto:podcast@sustainoss.org) Richard Littauer Twitter (https://twitter.com/richlitt?lang=en) FOSS Backstage 2023 (https://foss-backstage.de/) Wolfgang Gehring LinkedIn (https://de.linkedin.com/in/dr-wolfgang-gehring-9a8723201) Open Source Mercedes-Benz (https://opensource.mercedes-benz.com/) Mercedes-Benz Group GitHub (https://github.com/mercedes-benz) Eclipse Foundation (https://www.eclipse.org/) Ana Jiménez Santamaría Twitter (https://twitter.com/anajsana95?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor) Ana Jiménez Mastodon (https://mastodon.social/@anajsana@fosstodon.org) Ana Jiménez Santamaría LinkedIn (https://es.linkedin.com/in/ana-jim%C3%A9nez-santamar%C3%ADa/en) Ana Jiménez Santamaría YouTube (https://www.youtube.com/@anajsana) TODO Group (https://todogroup.org/) Credits Produced by Richard Littauer (https://www.burntfen.com/) Edited by Paul M. Bahr at Peachtree Sound (https://www.peachtreesound.com/) Show notes by DeAnn Bahr Peachtree Sound (https://www.peachtreesound.com/) Special Guests: Ana Jiménez Santamaría and Dr. Wolfgang Gehring.

In this episode, News Editor Jenna Barron spoke with Mike Milinkovich, executive director of the Eclipse Foundation, about Europe's Cyber Resilience Act (CRA). He talks about why the CRA would be bad for open source development.

Mike Brevoort, Chief Product Officer at Gitpod, joins Corey on Screaming in the Cloud to discuss all the intricacies of remote development and how Gitpod is simplifying the process. Mike explains why he feels the infinite resources cloud provides can be overlooked when discussing remote versus local development environments, and how simplifying build abstractions is a fantastic goal, but that focusing on the tools you use in a build abstraction in the meantime can be valuable. Corey and Mike also dive into the security concerns that come with remote development, and Mike reveals the upcoming plans for Gitpod's local conference environment, CDE Universe. About MikeMike has a passion for empowering people to be creative and work together more effectively. He is the Chief Product Officer at Gitpod striving to remove the friction and drudgery from software development through Cloud Developer Environments. He spent the previous four years at Slack where he created Workflow Builder and “Platform 2.0” after his company Missions was acquired by Slack in 2018. Mike lives in Denver, Colorado and enjoys cycling, hiking and being outdoors.Links Referenced: Gitpod: https://www.gitpod.io/ CDE Universe: https://cdeuniverse.com/ 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: It's easy to **BEEP** up on AWS. Especially when you're managing your cloud environment on your own!Mission Cloud un **BEEP**s your apps and servers. Whatever you need in AWS, we can do it. Head to missioncloud.com for the AWS expertise you need. Corey: Have you listened to the new season of Traceroute yet? Traceroute is a tech podcast that peels back the layers of the stack to tell the real, human stories about how the inner workings of our digital world affect our lives in ways you may have never thought of before. Listen and follow Traceroute on your favorite platform, or learn more about Traceroute at origins.dev. My thanks to them for sponsoring this ridiculous podcast. Corey: Welcome to Screaming in the Cloud, I'm Corey Quinn. I have had loud, angry, and admittedly at times uninformed opinions about so many things over the past few years, but something that predates that a lot is my impression on the idea of using remote systems for development work as opposed to doing local dev, and that extends to build and the rest. And my guest today here to argue with me about some of it—or agree; we'll find out—is Mike Brevoort, Chief Product Officer at Gitpod, which I will henceforth be mispronouncing as JIT-pod because that is the type of jerk I am. Mike, thank you for joining me.Mike: Thank you for insulting my company. I appreciate it.Corey: No, by all means, it's what we do here.Mike: [laugh].Corey: So, you clearly have opinions on the idea of remote versus local development that—I am using the word remote development; I know you folks like to use the word cloud, in place of remote, but I'm curious to figure out is, is that just the zeitgeist that has shifted? Do you have a belief that it should be in particular places, done in certain ways, et cetera? Where do your opinion on this start and stop?Mike: I think that—I mean, remote is accurate, an accurate description. I don't like to emphasize the word remote because I don't think it's important that it's remote or local. I think that the term cloud connotes different values around the elasticity of environments and the resources that are more than what you might have on your local machine versus a remote machine. It's not so much whether the one machine is local or remote as much of it is that there are infinite numbers of resources that you can develop across in the cloud. That's why we tend to prefer our cloud development environments.Corey: From my perspective, I've been spending too many years now living in basically hotels and airports. And when I was doing that, for a long time, the only computer I bring with me has been my iPad Pro. That used to be a little bit on the challenging side and these days, that's gotten capable enough where it's no longer interesting in isolation. But there's no local development environment that is worth basically anything on that. So, I've been SSHing into things and using VI as my development environment for many years.When I started off as a grumpy Unix sysadmin, there was something reassuring about the latest state of whatever it is I'm working on lives in a data center somewhere rather than on a laptop, I'm about to leave behind a coffee shop because I'm careless. So, there's a definite value and sense that I am doing something virtuous, historically. But it didn't occur to me till I started talking to people about this, just how contentious the idea was. People would love to ask all kinds of fun objections to this where it was, “Oh, well, what about when you're on a plane and need to do work?” It's, well, I spend an awful lot of time on planes and that is not a limiting factor in me writing the terrible nonsense that I will charitably called code, in my case. I just don't find that that idea holds up anywhere. The world has become so increasingly interconnected that that seems unlikely. But I do live in San Francisco, so here, every internet is generally pretty decent; not every place is. What are your thoughts?Mike: I agree. I mean, I think one thing is, I would just like not to think about it, whether I can or can't develop because I'm connected or not. And I think that we tend to be in a world where that is moreso the case. And I think a lot of times when you're not connected, you become reconnected soon, like if your connection is not reliable or if you're going in and out of connectivity issues. And when you're trying to work on a local laptop and you're connecting and disconnecting, it's not like we develop these days, and everything is just isolated on our local laptop, especially we talk about cloud a lot on this podcast and a lot of apps now go way beyond just I'm running a process on my machine and I'm connecting to data on my machine.There are local emulators you could use for some of these services, but most of them are inferior. And if you're using SQS or using any other, like, cloud-based service, you're usually, as a developer, connecting to some version of that and if you're disconnected anyway, you're not productive either. And so, I find that it's just like an irrelevant conversation in this new world. And that the way we've developed traditionally has not followed along with this view of I need to pile everything in on my laptop, to be able to develop and be productive has not, like, followed along with the trend that moved into the cloud.Corey: Right. The big problem for a long time has been, how do I make this Mac or Windows laptop look a lot like Linux EC2 instance? And there have been a bunch of challenges and incompatibility issues and the rest, and from my perspective, I like to develop in an environment that at least vaguely resembles the production environment it's going to run in, which in AWS's case, of course, comes down to expensive. Bu-dum-tss.Mike: Yeah, it's a really big challenge. It's been a challenge, right? When you've worked with coworkers that were on a Windows machine and you were on a Mac machine, and you had the one person on their Linux machine forever, and we all struggled with trying to mimic these development environments that were representative, ultimately, of what we would run in production. And if you're counting costs, we can count the cost of those cloud resources, we can count the cost of those laptops, but we also need to count the cost of the people who are using those laptops and how inefficient and how much churn they have, and how… I don't know, there was for years of my career, someone would show up every morning to the stand-up meeting and say, it's like, “Well, I wasted all afternoon yesterday trying to work out my, you know, issues with my development environment.” And it's, like, “I hope I get that sorted out later today and I hope someone can help me.”And so, I think cost is one thing. I think that there's a lot of inconsistencies that lead to a lot of inefficiencies and churn. And I think that, regardless of where you're developing, the more that you can make your environments more consistent and sound, not for you, but for your own team and have those be more representative of what you are running in production, the better.Corey: We should disambiguate here because I fear this is one of the areas where my use case tends to veer off into the trees, which is I tend to operate largely in isolation, from a development point of view. I build small, micro things that wind up doing one thing, poorly. And that is, like, what I do is a proof of concept, or to be funny, or to kick the tires on a new technology. I'll also run a bunch of random things I find off of JIF-ub—yes, that's how I pronounce GitHub. And that's great, but it also feels like I'm learning as a result, every stack, and every language, in every various version that it has, and very few of the cloud development environments that I've seen, really seems to cater to the idea that simultaneously, I want to have certain affordances in my shell environment set up the way that I want them, tab complete this particular suite of tools generically across the board, but then reset to that baseline and go in a bunch of different directions of, today, it's Python in this version and tomorrow, it's Node in this other version, and three, what is a Typescript anyway, and so on and so forth.It feels like it's either, in most cases, you either get this generic, one-size-fits-everyone in this company, for this project, approach, or it's, here's a very baseline untuned thing that does not have any of your dependencies installed. Start from scratch every time. And it's like, feels like there are two paths, and they both suck. Where are you folks at these days on that spectrum?Mike: Yeah, I think that, you know, one, if you do all of that development across all these different libraries and technology stacks and you're downloading all these repos from JIF-hub—I say it right—and you're experimenting, you tend to have a lot of just collision of things. Like if you're using Python, it's, like, really a pain to maintain isolation across projects and not have—like, your environment is, like, one big bucket of things on your laptop and it's very easy to get that into a state where things aren't working, and then you're struggling. There's no big reset on your laptop. I mean, there is but it takes—it's a full reset of everything that you have.And I think the thing that's interesting to me about cloud development environments is I could spin one of these up, I could trash it to all hell and just throw it away and get another one. And I could get another one of those at a base of which has been tuned for whatever project or technology I'm working on. So, I could take—you know, do the effort to pre-setup environments, one that is set up with all of my, like, Python tooling, and another one that's set up with all my, like, Go or Rust tooling, or our front-end development, even as a base repo for what I tend to do or might tend to experiment with. What we find is that, whether you're working alone or you're working with coworkers, that setting up a project and all the resources and the modules and the libraries and the dependencies that you have, like, someone has to do that work to wire that up together and the fact that you could just get an environment and get another one and another one, we use this analogy of, like, tissue boxes where, like, you should just be able to pull a new dev environment out of a tissue box and use it and throw it away and pull as many tissues out of the box as you want. And they should be, like, cheap and ephemeral because—and they shouldn't be long-lived because they shouldn't be able to drift.And whether you're working alone or you're working in a team, it's the same value. The fact that, like, I could pull on these out, I have it. I'm confident in it of what I got. Like for example, ideally, you would just start a dev environment, it's available instantly, and you're ready to code. You're in this project with—and maybe it's a project you've never developed on. Maybe it's an open-source project.This is where I think it really improves the sort of equitability of being able to develop, whether it's in open-source, whether it's inner-source in companies, being able to approach any project with a click of a button and get the same environment that the tech lead on the project who started it five years ago has, and then I don't need to worry about that and I get the same environment. And I think that's the value. And so, whether you're individual or you're on a team, you want to be able to experiment and thrash and do things and be able to throw it away and start over again, and not have to—like for example, maybe you're doing that on your machine and you're working on this thing and then you actually have to do some real work, and then now that you've done something that conflicts with the thing that you're working on and you're just kind of caught in this tangled mess, where it's like, you should just be able to leave that experiment there and just go work on the thing you need to work on. And why can't you have multiples of these things at any given time?Corey: Right. One of the things I loved about EC2 dev environments has been that I can just spin stuff up and okay, great, it's time for a new project. Spin up another one and turn it off when I'm done using it—which is the lie we always tell ourselves in cloud and get charged for things we forget to turn off. But then, okay, I need an Intel box one day. Done. Great, awesome. I don't have any of those lying around here anymore but clickety, clickety, and now I do.It's nice being able to have that flexibility, but it's also sometimes disconcerting when I'm trying to figure out what machine I was on when I was building things and the rest, and having unified stories around this becomes super helpful. I'm also finding that my overpowered desktop is far more cost-efficient when I need to compile something challenging, as opposed to finding a big, beefy, EC2 box for that thing as well. So, much of the time, what my remote system is doing is sitting there bored. Even when I'm developing on it, it doesn't take a lot of modern computer resources to basically handle a text editor. Unless it's Emacs, in which case, that's neither here nor there.Mike: [laugh]. I think that the thing that becomes costly, especially when using cloud development environments, is when you have to continue to run them even when you're not using them for the sake of convenience because you're not done with it, you're in the middle of doing some work and it still has to run or you forget to shut it off. If you are going to just spin up a really beefy EC2 instance for an hour to do that big compile and it costs you 78 cents. That's one thing. I mean, I guess that adds up over time and yes, if you've already bought that Mac Studio that's sitting under your desk, humming, it's going to be more cost-efficient to use that thing.But there's, like, an element of convenience here that, like, what if I haven't bought the Mac Studio, but I still need to do that big beefy compilation? And maybe it's not on a project I work on every single day; maybe it's the one that I'm just trying to help out with or just starting to contribute to. And so, I think that we need to get better about, and something that we're very focused on at JIT-pod, is—Gitpod—is—Corey: [laugh]. I'm going to get you in trouble at this rate.Mike: —[laugh]—is really to optimize that underlying runtime environment so that we can optimize the resources that you're using only when you're using it, but also provide a great user experience. Which is, for me, as someone who's responsible for the product at Gitpod, the thing I want to get to is that you never have to think about a machine. You're not thinking about this dev environment as something that lives somewhere, that you're paying for, that there's a meter spinning that if you forget it, that you're like, ah, it's going to cost me a lot of money, that I have to worry about ever losing it. And really, I just want to be able to get a new environment, have one, use it, come back to it when I need it, have it not cost me a lot of money, and be able to have five or ten of those at a time because I'm not as worried about what it's going to cost me. And I'm sure it'll cost something, but the convenience factor of being able to get one instantly and have it and not have to worry about it ultimately saves me a lot of time and aggravation and improves my ability to focus and get work done.And right now, we're still in this mode where we're still thinking about, is it on my laptop? Is it remote? Is it on this EC2 instance or that EC2 instance? Or is this thing started or stopped? And I think we need to move beyond that and be able to just think of these things as development environments that I use and need and they're there when I want to, when I need to work on them, and I don't have to tend to them like cattle.Corey: Speaking of tending large things in herds—I guess that's sort of for the most tortured analogy slash segway I've come up with recently—you folks have a conference coming up soon in San Francisco. What's the deal with that? And I'll point out, it's all on-site, locally, not in the cloud. So, hmm…Mike: Yeah, so we have a local conference environment, a local conference that we're hosting in San Francisco called CDE Universe on June 1st and 2nd, and we are assembling all the thought leaders in the industry who want to get together and talk about where not just cloud development is going, but really where development is going. And so, there's us, there's a lot of companies that have done this themselves. Like, before I joined Gitpod, I was at Slack for four years and I got to see the transition of a, sort of, remote development hosted on EC2 instances transition and how that really empowered our team of hundreds of engineers to be able to contribute and like work together better, more efficiently, to run this giant app that you can't run just alone on your laptop. And so, Slack is going to be there, they're going to be talking about their transition to cloud development. The Uber team is going to be there, there's going to be some other companies.So, Nathan who's building Zed, he was the one that originally built Adam at GitHub is now building Zed, which is a new IDE, is going to be there. And I can't mention all the speakers, but there's going to be a lot of people that are really looking at how do we drive forward development and development environments. And that experience can get a lot better. So, if you're interested in that, if you're going to be in San Francisco on June 1st and 2nd and want to talk to these people, learn from them, and help us drive this vision forward for just a better development experience, come hang out with us.Corey: I'm a big fan of collaborating with folks and figuring out what tricks and tips they've picked up along the way. And this is coming from the perspective of someone who acts as a solo developer in many cases. But it always drove me a little nuts when you see people spending weeks of their lives configuring their text editor—VIM in my case because I'm no better than these people; I am one of them—and getting it all setup and dialed in. It's, how much productivity you gaining versus how much time are you spending getting there?And then when all was said and done a few years ago, I found myself switching to VS Code for most of what I do, and—because it's great—and suddenly the world's shifting on its axis again. At some point, you want to get away from focusing on productivity on an individualized basis. Now, the rules change when you're talking about large teams where everyone needs a copy of this running locally or in their dev environment, wherever happens to be, and you're right, often the first two weeks of a new software engineering job are, you're now responsible for updating the onboarding docs because it's been ten minutes since the last time someone went through it. And oh, the versions bumped again of what we would have [unintelligible 00:16:44] brew install on a Mac and suddenly everything's broken. Yay. I don't miss those days.Mike: Yeah, the new, like, ARM-based Macs came out and then you were—now all of a sudden, all your builds are broken. We hear that a lot.Corey: Oh, what I love now is that, in many cases, I'm still in a process of, okay, I'm developing locally on an ARM-based Mac and I'm deploying it to a Graviton2-based Lambda or instance, but the CI/CD builder is going to run on Intel, so it's one of those, what is going on here? Like, there's a toolchain lag of round embracing ARM as an architecture. That's mostly been taken care of as things have evolved, but it's gotten pretty amusing at some point, just as quickly that baseline architecture has shifted for some workloads. And for some companies.Mike: Yeah, and things just seem to be getting more [laugh] and more complicated not less complicated, and so I think the more that we can—Corey: Oh, you noticed?Mike: Try to simplify build abstractions [laugh], you know, the better. But I think in those cases where, I think it's actually good for people to struggle with setting up their environment sometime, with caring about the tools that they use and their experience developing. I think there has to be some ROI with that. If it's like a chronic thing that you have to continue to try to fix and make better, it's one thing, but if you spend a whole day improving the tools that you use to make you a better developer later, I think there's a ton of value in that. I think we should care a lot about the tools we use.However, that's not something we want to do every day. I mean, ultimately, I know I don't build software for the sake of building software. I want to create something. I want to create some value, some change in the world. There's some product ultimately that I'm trying to build.And, you know, early on, I've done a lot of work in my career on, like, workflow-type builders and visual builders and I had this incorrect assumption somewhere along the way—and this came around, like, sort of the maker movement, when everybody was talking about everybody should learn how to code, and I made this assumption that everybody really wants to create; everybody wants to be a creator, and if given the opportunity, they will. And I think what I finally learned is that, actually most people don't like to create. A lot of people just want to be served; like, they just want to consume and they don't want the hassle of it. Some people do, if they have the opportunity and the skillsets, too, but it's also similar to, like, if I'm a professional developer, I need to get my work done. I'm not measured on how well my local tooling is set up; I'm sort of measured on my output and the impact that I have in the organization.I tend to think about, like, chefs. If I'm a chef and I work 60 hours in a restaurant, 70 hours in a restaurant, the last thing I want to do is come home and cook myself a meal. And most of the chefs I know actually don't have really nice kitchens at home. They, like, tend to, they want other people to cook for them. And so, I think, like, there's a place in professional setting where you just need to get the work done and you don't want to worry about all the meta things and the time that you could waste on it.And so, I feel like there's a happy medium there. I think it's good for people to care about the tools that they use the environment that they develop in, to really care for that and to curate it and make it better, but there's got to be some ROI and it's got to have value to you. You have to enjoy that. Otherwise, you know, what's the point of it in the first place?Corey: One thing that I used to think about was that if you're working in regulated industries, as I tended to a fair bit, there's something very nice about not having any of the data or IP or anything like that locally. Your laptop effectively just becomes a thin client to something that's already controlled by the existing security and compliance apparatus. That's very nice, where suddenly it's all someone steals my iPad, or I drop it into the bay, it's locked, it's encrypted. Cool, I go to the store, get myself a new one, restore a backup from iCloud, and I'm up and running again in a very short period of time as if nothing had ever changed. Whereas when I was doing a lot of local development and had bad hard drive issues in the earlier part of my career, well, there goes that month.Mike: Yeah, it's a really good point. I think that we're all walking around with these laptops with really sensitive IP on it and that those are in bars and restaurants. And maybe your drives are encrypted, but there's a lot of additional risks, including, you know, everything that is going over the network, whether I'm on a local coffee shop, and you know, the latest vulnerability that, an update I have to do on my Mac if I'm behind. And there's actually a lot of risk and having all that just sort of thrown to the wind and spread across the world and there's a lot of value in having that in a very safe place. And what we've even found that, at Gitpod now, like, the latest product we're working on is one that we called Gitpod Dedicated, which gives you the ability to run inside your own cloud perimeter. And we're doing that on AWS first, and so we can set up and manage an installation of Gitpod inside your own AWS account.And the reason that became important to us is that a lot of companies, a lot of our customers, treat their source code as their most sensitive intellectual property. And they won't allow it to leave their perimeter, like, they may run in AWS, but they have this concept of, sort of like, our perimeter and you're either inside of that and outside of it. And I think this speaks a little bit to a blog post that you wrote a few months ago about the lagging adoption of remote development environments. I think one of those aspects is, sort of, convenience and the user experience, but the other is that you can't use them very well with your stack and all the tools and resources that you need to use if they're not running, sort of, close within your perimeter. And so, you know, we're finding that companies have this need to be able to have greater control, and now with the, sort of, trends around, like, coding assistance and generative AI and it's even the perfect storm of not only am I like sending my source code from my editor out into some [LM 00:22:36], but I also have the risk of an LM that might be compromised, that's injecting code and I'm committing on my behalf that may be introducing vulnerabilities. And so, I think, like, getting that off to a secure space that is consistent and sound and can be monitored, to be kept up-to-date, I think it has the ability to, sort of, greatly increase a customer's security posture.Corey: While we're here kicking the beehive, for lack of a better term, your support for multiple editors in Gitpod the product, I assumed that most people would go with VS Code because I tend to see it everywhere, and I couldn't help but notice that neither VI nor Emacs is one of the options, the last time I checked. What are you seeing as far as popularity contests go? And that might be a dangerous question because I'm not suggesting you alienate many of the other vendors who are available, but in the world I live in, it's pretty clear where the zeitgeist of my subculture is going.Mike: Yeah, I mean, VS Code is definitely the most popular IDE. The majority of people that use Gitpod—and especially we have a, like, a pretty heavy free usage tier—uses it in the browser, just for the convenience of having that in the browser and having many environments in the browser. We tend to find more professional developers use VS Code desktop or the JetBrains suite of IDEs.Corey: Yeah, JetBrains I'm seeing a fair bit of in a bunch of different ways and I think that's actually most of what your other options are. I feel like people have either gone down the JetBrains path or they haven't and it seems like it's very, people who are into it are really into it and people who are not are just, never touch it.Mike: Yeah, and we want to provide the options for people to use the tools that they want to use and feel comfortable on. And we also want to provide a platform for the next generation of IDEs to be able to build on and support and to be able to support this concept of cloud or remote development more natively. So, like I mentioned, Nathan Sobo at Zed, I met up with him last week—I'm in Denver; he's in Boulder—and we were talking about this and he's interested in Zed working in the browser, and he's talked about this publicly. And for us, it's really interesting because, like, IDEs working in the browser is, like, a really great convenience. It's not the perfect way to work, necessarily, in all circumstances.There's some challenges with, like, all this tab sprawl and stuff, but it gives us the opportunity, if we can make Zed work really well in for Gitpod—or anybody else building an IDE—for that to work in the browser. Ultimately what we want is that if you want to use a terminal, we want to create a great experience for you for that. And so, we're working on this ability in Gitpod to be able to effectively, like, bring your own IDE, if you're building on that, and to be able to offer it and distribute on Gitpod, to be able to create a new developer tool and make it so that anybody in their Gitpod workspace can launch that as part of their workspace, part of their tool. And we want to see developer tools and IDEs flourish on top of this platform that is cloud development because we want to give people choice. Like, at Gitpod, we're not building our own IDE anymore.The team started to. They created Theia, which was one of the original cloud, sort of, web-based IDEs that now has been handed over to the Eclipse Foundation. But we moved to VS Code because we found that that's where the ecosystem were. That's where our users were, and our customers, and what they wanted to use. But we want to expand beyond that and give people the ability to choose, not only the options that are available today but the options that should be available in the future. And we think that choice is really important.Corey: When you see people kicking the tires on Gitpod for the first time, where does the bulk of their hesitancy come from? Like, what is it where—people, in my experience, don't love to embrace change. So, it's always this thing, “This thing sucks,” is sort of the default response to anything that requires them to change their philosophy on something. So okay, great. That is a thing that happens. We'll see what people say or do. But are they basing it on anything beyond just familiarity and comfort with the old way of doing things or are there certain areas that you're finding the new customers are having a hard time wrapping their head around?Mike: There's a couple of things. I think one thing is just habit. People have habits and preferences, which are really valuable because it's the way that they've learned to be successful in their careers and the way that they expect things. Sometimes people have these preferences that are fairly well ingrained that maybe are irrational or rational. And so, one thing is just people's force of habit.And then getting used to this idea that if it's not on my laptop, it means—like what you mentioned before, it's always what-ifs of, like, “What if I'm on a plane?” Or like, “What if I'm at the airport in a hurricane?” “What if I'm on a train with a spotty internet connection?” And so, there's all these sort of what-if situations. And once people get past that and they start actually using Gitpod and trying to set their projects up, the other limiting factor we have is just connectivity.And that's, like, connectivity to the other resources that you use to develop. So, whether that's, you know, package or module repositories or that some internal services or a database that might be running behind a firewall, it's like getting connectivity to those things. And that's where the dedicated deployment model that I talked about, running inside of your perimeter on our network, they have control over, kind of helps, and that's why we're trying to overcome that. Or if you're using our SaaS product, using something like Tailscale or a more modern VPN that way. But those are the two main things.It's like familiarity, this comfort for how to work, sort of, in this new world and not having this level of comfort of, like, it's running on this thing I can hold, as well as connectivity. And then there is some cost associated with people now paying for this infrastructure they didn't have to pay for before. And I think it's a, you know, it's a mistake to say that we're going to offset the cost of laptops. Like, that shouldn't be how you justify a cloud development environment. Like—Corey: Yeah, I feel like people are not requesting under-specced laptops much these days anymore.Mike: It's just like, I want to use a good laptop; I want to use a really nice laptop with good hardware and that shouldn't be the cost. The proposition shouldn't be, it's like, “Save a thousand dollars on every developer's laptop by moving this off to the cloud.” It's really the time savings. It's the focus. It's the, you know, removing all of that drift and creating these consistent environments that are more secure, and effectively, like, automating your development environment that's the same for everybody.But that's the—I think habits are the big thing. And there is, you know, I talked about a little bit that element of, like, we still have this concept of, like, I have this environment and I start it and it's there, and I pay for it while it's there and I have to clean it up or I have to make sure it stopped. I think that still exists and it creates a lot of sort of cognitive overhead of things that I have to manage that I didn't have to manage before. And I think that we have to—Gitpod needs to be better there and so does everybody else in the industry—about removing that completely. Like, there's one of the things that I really love that I learned from, like, Stewart Butterfield when I was at Slack was, he always brought up this concept called the convenience threshold.And it was just the idea that when a certain threshold of convenience is met, people's behavior suddenly changes. And as we thought about products and, like, the availability of features, that it really drove how we thought about even how to think about you know, adoption or, like, what is the threshold, what would it take? And, like, a good example of this is even, like, the way we just use credit cards now or debit cards to pay for things all the time, where we're used to carry cash. And in the beginning, when it was kind of novel that you could use a credit card to pay for things, like even pay for gas, you always had to have cash because you didn't know if it'd be accepted. And so, you still had to have cash, you still had to have it on hand, you still had to get it from the ATM, you still have to worry about, like, what if I get there and they don't accept my cards and how much money is it going to be, so I need to make sure I have enough of it.But the convenience of having this card where I don't have to carry cash is I don't have to worry about that anymore, as long as they have money in my bank account. And it wasn't until those cards were accepted more broadly that I could actually rely on having that card and not having the cash. It's similar when it comes to cloud development environments. It needs to be more convenient than my local development environment. It needs to be—it's kind of like early—I remember when laptops became more common, I was used to developing on a desktop, and people were like, nobody's ever going to develop on a laptop, it's not powerful enough, the battery runs out, I have to you know, when I close the lid, when you open the lid, it used to take, like, five minutes before, like, it would resume an unhibernate and stuff, and it was amazing where you could just close it and open it and get back to where you were.But like, that's the case where, like, laptops weren't convenient as desktops were because they were always plugged in, powered on, you can leave them and you can effectively just come back and sit down and pick up where you left off. And so, I think that this is another moment where we need to make these cloud development environments more convenient to be able to use and ultimately better. And part of that convenience is to make it so that you don't have to think about all these parts of them of whether they're running, not running, how much they cost, whether you're going to be there [unintelligible 00:31:35] or lose their data. Like, that should be the value of it that I don't have to think about any of that stuff.Corey: So, my last question for you is, when you take a look at people who have migrated to using Gitpod, specifically from the corporate perspective, what are their realizations after the fact—I mean, assuming they still take your phone calls because that's sort of feedback of a different sort—but what have they realized has worked well? What keeps them happy and coming back and taking your calls?Mike: Yeah, our customers could focus on their business instead of focusing on all the issues that they have with configuring development environments, everything that could go wrong. And so, a good example of this is a customer they have, Quizlet, Quizlet saw a 45-point increase in developer satisfaction and a 60% reduction in incidents, and the time that it takes to onboard new engineers went down to ten minutes. So, we have some customers that we talk to that come to us and say, “It takes us 20 days to onboard an engineer because of all the access they need and everything you need to set up and credentials and things, and now we could boil that down to a button click.” And that's the thing that we tend to hear from people is that, like, they just don't have to worry about this anymore and they tend to be able to focus on their business and what the developers are actually trying to do, which is build their product.And in Quizlet's example, it was really cool to see them mention in one of the recent OpenAI announcements around GPT4 and plugins is they were one of the early customers that built GPT4 plugins, or ChatGPT, and they mentioned that they were sharing a lot of Gitpod URLs around when we reached out to congratulate them. And the thing that was great about that, for us is, like, they were talking about their business and what they were developing and how they were being successful. And we'd rather see Gitpod in your development environment just sort of disappear into the background. We'd actually like to not hear from customers because it's just working so well from them. So, that's what we found is that customers are just able to get to this point where they could just focus on their business and focus on what they're trying to develop and focus on making their customers successful and not have to worry about infrastructure for development.Corey: I think that really says it all. On some level, when you have customers who are happy with what's happening and how they're approaching this, that really is the best marketing story I can think of because you can say anything you want about it, but when customers will go out and say, “Yeah, this has made our lives better; please keep doing what you're doing,” it counts for a lot.Mike: Yeah, I agree. And that's what we're trying to do. You know, we're not trying to win, sort of, a tab versus spaces debate here around local or cloud or—I actually just want to enable customers to be able to do their work of their business and develop software better. We want to try to provide a method and a platform that's extensible and customizable and gives them all the power they need to be able to just be ready to code, to get to work as soon as they can.Corey: I really want to thank you for being so generous with your time. If people want to learn more, where's the best place for them to find you, other than at your conference in San Francisco in a few weeks?Mike: [laugh]. Yeah, thank you. I really appreciate the banter back and forth. And I hope to see you there at our conference. You should come. Consider this an invite for June 1st and 2nd in San Francisco at CDE Universe.Corey: Of course. And we will put links to this in the [show notes 00:34:53]. Thank you so much for being so generous with your time. I appreciate it.Mike: Thanks, Corey. That was really fun.Corey: Mike Brevoort, Chief Product Officer at Gitpod. I'm Cloud Economist Corey Quinn and this is Screaming in the Cloud. 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 an angry comment detailing exactly why cloud development is not the future, but then lose your content halfway through because your hard drive crashed.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.

It's FRIIIIIDAAAAYYYY and we're swinging for the fence as we talk about GM joining an open source foundation. We also talk about a creative EV use for school buses, as well as new opportunities for soon-to-be vacated Bed Bath and Beyond Stores. GM is taking another step toward software-defined vehicle development by joining the Eclipse Foundation, a global association promoting open-source software. GM aims to facilitate industry-wide standardization for building and connecting applications that connect vehicles to cloud and mobile devices through contributing its proprietary uProtocol technology.Frank Ghenassia, GM's executive chief architect of software-defined vehicles, says a standard software foundation to simplify and expedite development and connectivity. Ghenassia states, "rather than reinvent or try to apply the traditional automotive model that's been successful for hardware-driven features and try to apply that to software development."Let's remember Automakers have a history of joining forces to create innovative platforms and vehicles more efficiently.Toyota and Subaru developed the Toyota 86 and Subaru BRZ Ford and Volkswagen collaborated on electric vehicles and autonomous driving technologies. In 2013, BMW and Toyota announced a partnership to develop hydrogen fuel cell systems, sports car platforms, and lightweight technologiesA new partnership in Prince Edward Island in Canada will leverage EV technology in school buses to also provide emergency power. Quebec based Lion Electric is a Canadian-based electric medium- and heavy-duty vehicle manufacturer that produces the nostalgic North American yellow school bus. Last year, the tail end of Hurricane Fiona hit Prince Edward Island with winds of up to 93 mph, knocking out power for almost everyone. The province setup "warming centers" for food, shelter, and phone charging using diesel generators.2 of these busses would have been able to power the center for 3 daysModel 3 (57kwh) F150 Lightning (130) these buses (210) 200 busses have been ordered and 82 will be in service next monthOne company's loss is often another's opportunity. Bed Bath & Beyond's recent bankruptcy and store closures open the door for a retail land grab. With nearly 500 potential spaces nationwide up for grabs, demand for these off-mall locations is high. Deborah Weinswig, CEO of retail real estate industry Coresight Research, says, "I'm not worried at this point because of the fact you've had this tremendous change in terms of demand for physical spaces."Vacancy rates for shopping centers have fallen to a record low, with dollar stores, off-price retailers, and traditional mall players competing for space.Some experts suggest that the easily adaptable spaces could become doctors offices for the quickly expanding medical care businesses of CVS and WalgreensGet the Daily Push Back email at https://www.asotu.com/ JOIN the conversation on LinkedIn at: https://www.linkedin.com/company/asotu/ Read our most recent email at: https://www.asotu.com/media/push-back-email ASOTU Instagram: https://www.instagram.com/automotivestateoftheunion

"What's going on with forming the Cyber Resilience Act in Europe has the potential to do enormous harm to the open source movement and to the future prosperity of the entire human race," says Milinkovich of the Eclipse Foundation, this week's guest on FLOSS Weekly. The Cyber Resilience Act (CRA) is an important topic to discuss in open source. Doc Searls and Jonathan Bennett speak with Milinkovich about this important matter. Hosts: Doc Searls and Jonathan Bennett Guest: Mike Milinkovich Download or subscribe to this show at https://twit.tv/shows/floss-weekly Think your open source project should be on FLOSS Weekly? Email floss@twit.tv. Thanks to Lullabot's Jeff Robbins, web designer and musician, for our theme music. Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit

"What's going on with forming the Cyber Resilience Act in Europe has the potential to do enormous harm to the open source movement and to the future prosperity of the entire human race," says Milinkovich of the Eclipse Foundation, this week's guest on FLOSS Weekly. The Cyber Resilience Act (CRA) is an important topic to discuss in open source. Doc Searls and Jonathan Bennett speak with Milinkovich about this important matter. Hosts: Doc Searls and Jonathan Bennett Guest: Mike Milinkovich Download or subscribe to this show at https://twit.tv/shows/floss-weekly Think your open source project should be on FLOSS Weekly? Email floss@twit.tv. Thanks to Lullabot's Jeff Robbins, web designer and musician, for our theme music. Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit

"What's going on with forming the Cyber Resilience Act in Europe has the potential to do enormous harm to the open source movement and to the future prosperity of the entire human race," says Milinkovich of the Eclipse Foundation, this week's guest on FLOSS Weekly. The Cyber Resilience Act (CRA) is an important topic to discuss in open source. Doc Searls and Jonathan Bennett speak with Milinkovich about this important matter. Hosts: Doc Searls and Jonathan Bennett Guest: Mike Milinkovich Download or subscribe to this show at https://twit.tv/shows/floss-weekly Think your open source project should be on FLOSS Weekly? Email floss@twit.tv. Thanks to Lullabot's Jeff Robbins, web designer and musician, for our theme music. Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit

"What's going on with forming the Cyber Resilience Act in Europe has the potential to do enormous harm to the open source movement and to the future prosperity of the entire human race," says Milinkovich of the Eclipse Foundation, this week's guest on FLOSS Weekly. The Cyber Resilience Act (CRA) is an important topic to discuss in open source. Doc Searls and Jonathan Bennett speak with Milinkovich about this important matter. Hosts: Doc Searls and Jonathan Bennett Guest: Mike Milinkovich Download or subscribe to this show at https://twit.tv/shows/floss-weekly Think your open source project should be on FLOSS Weekly? Email floss@twit.tv. Thanks to Lullabot's Jeff Robbins, web designer and musician, for our theme music. Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit

Stai ascoltando un estratto gratuito di Ninja PRO, la selezione quotidiana di notizie per i professionisti del digital business. Con Ninja PRO puoi avere ogni giorno marketing insight, social media update, tech news, business events e una selezione di articoli di approfondimento dagli esperti della Redazione Ninja. Vai su www.ninja.it/ninjapro per abbonarti al servizio.Cyber Resilience Act, le organizzazioni Open Source chiedono all'Ue di riconsiderare alcuni aspetti. Tredici organizzazioni, tra cui la Eclipse Foundation, la Linux Foundation Europe e l'Open Source Initiative (OSI), osservano che il Cyber Resilience Act, così come è stato scritto, "pone un inutile rischio economico e tecnologico all'UE" e chiedono di avere maggiore voce in capitolo nell'iter legislativo. Presentato per la prima volta in bozza a settembre, il CRA si propone di codificare in legge le migliori pratiche di cybersecurity per i prodotti connessi venduti in Europa. Il software open source rappresenta oltre il 70% del software presente nei prodotti con elementi digitali, sottolineano le organizzazioni. Il CEO di Google mette in guardia sull'AI. In un'intervista alla CBS andata in onda domenica scorsa e riportata da CNBC, Sundar Pichai ha lasciato intendere che la società non è preparata al rapido avanzamento dell'intelligenza artificiale. Pichai ha affermato che le leggi che regolano i progressi dell'AI "non possono essere decise solo da un'azienda". Mettendo in guardia dalle conseguenze di questa nuova tecnologia, ha anche detto che l'IA avrà un impatto su "ogni prodotto di ogni azienda". Fotografia creata dall'intelligenza artificiale vince ai Sony World Photography Awards. L'artista tedesco Boris Eldagsen si è aggiudicato la categoria "creatività" della sezione Open. Il fotografo ha quindi dichiarato che l'immagine è stata realizzata dal'AI e per questo di non poter accettare il riconoscimento. L'opera, ha spiegato Eldagsen, era stata creata proprio per generare un dibattito, non per vincere un premio.

The Cloud Native Computing Foundation (CNCF) is the home of the most prominent open source projects used today, such as Kubernetes, Prometheus, ArgoCD, Linkerd and more. These projects fuel today's cloud native architectures and software release pipelines. With its immense growth, it has become difficult to keep tabs on the hundreds of new and evolving projects and specifications, the different working groups and technical advisory groups, the different community forums and events, and to see where it's all heading. I invited Chris Aniszczyk, CTO of the CNCF, to join me on this episode, to help us understand the CNCF landscape and evolution. We will also discuss the trends in observability and in the open source realm in general. Chris also has some interesting predictions to share.  Chris Aniszczyk is an open source executive and engineer with a passion for building a better world through open collaboration. He's currently a CTO at the Linux Foundation focused on developer relations and running the Open Container Initiative (OCI) / Cloud Native Computing Foundation (CNCF). Furthermore, he's a partner at Capital Factory where he focuses on mentoring, advising and investing in open source and infrastructure focused startups. At Twitter, he created their open source program and led their open source efforts. For many years he served on the Eclipse Foundation's Board of Directors representing the committer community and the Java Community Process (JCP) Executive Committee. In a previous life, he bootstrapped a consulting company, made many mistakes, lead and hacked on many eclipse.org and Linux related projects. The episode was live-streamed on 15 March 2023 and the video is available at https://www.youtube.com/live/lMUFGmNploc OpenObservability Talks episodes are released monthly, on the last Thursday of each month and are available for listening on your favorite podcast app and on YouTube. We live-stream the episodes on Twitch and YouTube Live - tune in to see us live, and chime in with your comments and questions on the live chat. https://www.twitch.tv/openobservability https://www.youtube.com/@openobservabilitytalks   Have you got an interesting topic you'd like to share in an episode? Reach out to us and submit your proposal at https://openobservability.io/ Show Notes: Day in a life of CNCF CTO open source sustainability how to navigate the CNCF landscape how to get started with cloud native is Kubernetes spreading too broad to lose focus? OpenTelemetry project journey report sneak peak open observability stack convergence OpenFeature feature flagging OSS CNCF investing in more regional activity CNCF investing in security relicensing and OSS citizenship issues CNCF project health dashboard KubeCon sneak peak Resources: https://landscape.cncf.io/guide https://github.com/cncf/toc/blob/main/PRINCIPLES.md#no-kingmakers--one-size-does-not-fit-all https://projecthealth.cncf.io  https://www.linkedin.com/pulse/cloud-native-predictions-2023-chris-aniszczyk/?trackingId=QHkYlzDhTniN3sgLSRCOtQ%3D%3D Socials: Twitter: https://twitter.com/OpenObserv Twitch: https://www.twitch.tv/openobservability YouTube: https://www.youtube.com/@openobservabilitytalks Dotan Horovits ============ Twitter: https://twitter.com/horovits  LinkedIn: https://www.linkedin.com/in/horovits/  Mastodon: @horovits@fosstodon Chris Aniszczyk =============== Twitter: @cra LinkedIn: https://www.linkedin.com/in/caniszczyk/ Mastodon: @cra@macaw.social

Nesse episódio trouxemos as notícias e novidades do mundo da programação que nos chamaram atenção dos dias 11/03 a 17/03!

Nesse episódio trouxemos as notícias e novidades do mundo da programação que nos chamaram atenção dos dias 11/03 a 17/03!

Frederic Desbiens, program manager for IoT and edge computing, Eclipse Foundation, returns to the show to talk with Peggy about a new survey focusing on IoT adoption and edge computing. He says there was an acceleration of IoT adoption in 2022, citing specific statistics. They also discuss: If at some point there won't be an IoT deployment without edge computing. The role of open-source technologies and the main benefits. The workforce shortage and common operational challenges. iot.eclipse.org  (2/28/23 - 811) IoT, Internet of Things, Peggy Smedley, artificial intelligence, machine learning, big data, digital transformation, cybersecurity, blockchain, 5G, cloud, sustainability, future of work, podcast, Frederic Desbiens, Eclipse Foundation This episode is available on all major streaming platforms. If you enjoyed this segment, please consider leaving a review on Apple Podcasts.

Frederic Desbiens, program manager for IoT and edge computing, Eclipse Foundation, returns to the show to talk with Peggy about a new survey focusing on IoT adoption and edge computing. He says there was an acceleration of IoT adoption in 2022, citing specific statistics. They also discuss: If at some point there won't be an IoT deployment without edge computing. The role of open-source technologies and the main benefits. The workforce shortage and common operational challenges. iot.eclipse.org  (2/28/23 - 811) IoT, Internet of Things, Peggy Smedley, artificial intelligence, machine learning, big data, digital transformation, cybersecurity, blockchain, 5G, cloud, sustainability, future of work, podcast, Frederic Desbiens, Eclipse Foundation This episode is available on all major streaming platforms. If you enjoyed this segment, please consider leaving a review on Apple Podcasts.

About AndiAndi Gutmans is the General Manager and Vice President for Databases at Google. Andi's focus is on building, managing and scaling the most innovative database services to deliver the industry's leading data platform for businesses. Before joining Google, Andi was VP Analytics at AWS running services such as Amazon Redshift. Before his tenure at AWS, Andi served as CEO and co-founder of Zend Technologies, the commercial backer of open-source PHP.Andi has over 20 years of experience as an open source contributor and leader. He co-authored open source PHP. He is an emeritus member of the Apache Software Foundation and served on the Eclipse Foundation's board of directors. He holds a bachelor's degree in Computer Science from the Technion, Israel Institute of Technology.Links Referenced: LinkedIn: https://www.linkedin.com/in/andigutmans/ Twitter: https://twitter.com/andigutmans 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: This episode is sponsored in part by our friends at Sysdig. Sysdig secures your cloud from source to run. They believe, as do I, that DevOps and security are inextricably linked. If you wanna learn more about how they view this, check out their blog, it's definitely worth the read. To learn more about how they are absolutely getting it right from where I sit, visit Sysdig.com and tell them that I sent you. That's S Y S D I G.com. And my thanks to them for their continued support of this ridiculous nonsense.Corey: Welcome to Screaming in the Cloud. I'm Corey Quinn. This promoted episode is brought to us by our friends at Google Cloud, and in so doing, they have gotten a guest to appear on this show that I have been low-key trying to get here for a number of years. Andi Gutmans is VP and GM of Databases at Google Cloud. Andi, thank you for joining me.Andi: Corey, thanks so much for having me.Corey: I have to begin with the obvious. Given that one of my personal passion projects is misusing every cloud service I possibly can as a database, where do you start and where do you stop as far as saying, “Yes, that's a database,” so it rolls up to me and, “No, that's not a database, so someone else can deal with the nonsense?”Andi: I'm in charge of the operational databases, so that includes both the managed third-party databases such as MySQL, Postgres, SQL Server, and then also the cloud-first databases, such as Spanner, Big Table, Firestore, and AlloyDB. So, I suggest that's where you start because those are all awesome services. And then what doesn't fall underneath, kind of, that purview are things like BigQuery, which is an analytics, you know, data warehouse, and other analytics engines. And of course, there's always folks who bring in their favorite, maybe, lesser-known or less popular database and self-manage it on GCE, on Compute.Corey: Before you wound up at Google Cloud, you spent roughly four years at AWS as VP of Analytics, which is, again, one of those very hazy type of things. Where does it start? Where does it stop? It's not at all clear from the outside. But even before that, you were, I guess, something of a legendary figure, which I know is always a weird thing for people to hear.But you were partially at least responsible for the Zend Framework in the PHP world, which I didn't realize what the heck that was, despite supporting it in production at a couple of jobs, until after I, for better or worse, was no longer trusted to support production environments anymore. Which, honestly, if you can get out, I'm a big proponent of doing that. You sleep so much better without a pager. How did you go from programming languages all the way on over to databases? It just seems like a very odd mix.Andi: Yeah. No, that's a great question. So, I was one of the core developers of PHP, and you know, I had been in the PHP community for quite some time. I also helped ideate. The Zend Framework, which was the company that, you know, I co-founded Zend Technologies was kind of the company behind PHP.So, like Red Hat supports Linux commercially, we supported PHP. And I was very much focused on developers, programming languages, frameworks, IDEs, and that was, you know, really exciting. I had also done quite a bit of work on interoperability with databases, right, because behind every application, there's a database, and so a lot of what we focused on is a great connectivity to MySQL, to Postgres, to other databases, and I got to kind of learn the database world from the outside from the application builders. We sold our company in I think it was 2015 and so I had to kind of figure out what's next. And so, one option would have been, hey, stay in programming languages, but what I learned over the many years that I worked with application developers is that there's a huge amount of value in data.And frankly, I'm a very curious person; I always like to learn, so there was this opportunity to join Amazon, to join the non-relational database side, and take myself completely out of my comfort zone. And actually, I joined AWS to help build the graph database Amazon Neptune, which was even more out of my comfort zone than even probably a relational database. So, I kind of like to do different things and so I joined and I had to learn, you know how to build a database pretty much from the ground up. I mean, of course, I didn't do the coding, but I had to learn enough to be dangerous, and so I worked on a bunch of non-relational databases there such as, you know, Neptune, Redis, Elasticsearch, DynamoDB Accelerator. And then there was the opportunity for me to actually move over from non-relational databases to analytics, which was another way to get myself out of my comfort zone.And so, I moved to run the analytic space, which included services like Redshift, like EMR, Athena, you name it. So, that was just a great experience for me where I got to work with a lot of awesome people and learn a lot. And then the opportunity arose to join Google and actually run the Google transactional databases including their older relational databases. And by the way, my job actually have two jobs. One job is running Spanner and Big Table for Google itself—meaning, you know, search ads and YouTube and everything runs on these databases—and then the second job is actually running external-facing databases for external customers.Corey: How alike are those two? Is it effectively the exact same thing, just with different API endpoints? Are they two completely separate universes? It's always unclear from the outside when looking at large companies that effectively eat versions of their own dog food, where their internal usage of these things starts and stops.Andi: So, great question. So, Cloud Spanner and Cloud Big Table do actually use the internal Spanner and Big Table. So, at the core, it's exactly the same engine, the same runtime, same storage, and everything. However, you know, kind of, internally, the way we built the database APIs was kind of good for scrappy, you know, Google engineers, and you know, folks are kind of are okay, learning how to fit into the Google ecosystem, but when we needed to make this work for enterprise customers, we needed a cleaner APIs, we needed authentication that was an external, right, and so on, so forth. So, think about we had to add an additional set of APIs on top of it, and management, right, to really make these engines accessible to the external world.So, it's running the same engine under the hood, but it is a different set of APIs, and a big part of our focus is continuing to expose to enterprise customers all the goodness that we have on the internal system. So, it's really about taking these very, very unique differentiated databases and democratizing access to them to anyone who wants to.Corey: I'm curious to get your position on the idea that seems to be playing it's—I guess, a battle that's been playing itself out in a number of different customer conversations. And that is, I guess, the theoretical decision between, do we go towards general-purpose databases and more or less treat every problem as a nail in search of a hammer or do you decide that every workload gets its own custom database that aligns the best with that particular workload? There are trade-offs in either direction, but I'm curious where you land on that given that you tend to see a lot more of it than I do.Andi: No, that's a great question. And you know, just for the viewers who maybe aren't aware, there's kind of two extreme points of view, right? There's one point of view that says, purpose-built for everything, like, every specific pattern, like, build bespoke databases, it's kind of a best-of-breed approach. The problem with that approach is it becomes extremely complex for customers, right? Extremely complex to decide what to use, they might need to use multiple for the same application, and so that can be a bit daunting as a customer. And frankly, there's kind of a law of diminishing returns at some point.Corey: Absolutely. I don't know what the DBA role of the future is, but I don't think anyone really wants it to be, “Oh, yeah. We're deciding which one of these three dozen manage database services is the exact right fit for each and every individual workload.” I mean, at some point it feels like certain cloud providers believe that not only every workload should have its own database, but almost every workload should have its own database service. It's at some point, you're allowed to say no and stop building these completely, what feel like to me, Byzantine, esoteric database engines that don't seem to have broad applicability to a whole lot of problems.Andi: Exactly, exactly. And maybe the other extreme is what folks often talk about as multi-model where you say, like, “Hey, I'm going to have a single storage engine and then map onto that the relational model, the document model, the graph model, and so on.” I think what we tend to see is if you go too generic, you also start having performance issues, you may not be getting the right level of abilities and trade-offs around consistency, and replication, and so on. So, I would say Google, like, we're taking a very pragmatic approach where we're saying, “You know what? We're not going to solve all of customer problems with a single database, but we're also not going to have two dozen.” Right?So, we're basically saying, “Hey, let's understand that the main characteristics of the workloads that our customers need to address, build the best services around those.” You know, obviously, over time, we continue to enhance what we have to fit additional models. And then frankly, we have a really awesome partner ecosystem on Google Cloud where if someone really wants a very specialized database, you know, we also have great partners that they can use on Google Cloud and get great support and, you know, get the rest of the benefits of the platform.Corey: I'm very curious to get your take on a pattern that I've seen alluded to by basically every vendor out there except the couple of very obvious ones for whom it does not serve their particular vested interests, which is that there's a recurring narrative that customers are demanding open-source databases for their workloads. And when you hear that, at least, people who came up the way that I did, spending entirely too much time on Freenode, back when that was not a deeply problematic statement in and of itself, where, yes, we're open-source, I guess, zealots is probably the best terminology, and yeah, businesses are demanding to participate in the open-source ecosystem. Here in reality, what I see is not ideological purity or anything like that and much more to do with, “Yeah, we don't like having a single commercial vendor for our databases that basically plays the insert quarter to continue dance whenever we're trying to wind up doing something new. We want the ability to not have licensing constraints around when, where, how, and how quickly we can run databases.” That's what I hear when customers are actually talking about open-source versus proprietary databases. Is that what you see or do you think that plays out differently? Because let's be clear, you do have a number of database services that you offer that are not open-source, but are also absolutely not tied to weird licensing restrictions either?Andi: That's a great question, and I think for years now, customers have been in a difficult spot because the legacy proprietary database vendors, you know, knew how sticky the database is, and so as a result, you know, the prices often went up and was not easy for customers to kind of manage costs and agility and so on. But I would say that's always been somewhat of a concern. I think what I'm seeing changing and happening differently now is as customers are moving into the cloud and they want to run hybrid cloud, they want to run multi-cloud, they need to prove to their regulator that it can do a stressed exit, right, open-source is not just about reducing cost, it's really about flexibility and kind of being in control of when and where you can run the workloads. So, I think what we're really seeing now is a significant surge of customers who are trying to get off legacy proprietary database and really kind of move to open APIs, right, because they need that freedom. And that freedom is far more important to them than even the cost element.And what's really interesting is, you know, a lot of these are the decision-makers in these enterprises, not just the technical folks. Like, to your point, it's not just open-source advocates, right? It's really the business people who understand they need the flexibility. And by the way, even the regulators are asking them to show that they can flexibly move their workloads as they need to. So, we're seeing a huge interest there and, as you said, like, some of our services, you know, are open-source-based services, some of them are not.Like, take Spanner, as an example, it is heavily tied to how we build our infrastructure and how we build our systems. Like, I would say, it's almost impossible to open-source Spanner, but what we've done is we've basically embraced open APIs and made sure if a customer uses these systems, we're giving them control of when and where they want to run their workloads. So, for example, Big Table has an HBase API; Spanner now has a Postgres interface. So, our goal is really to give customers as much flexibility and also not lock them into Google Cloud. Like, we want them to be able to move out of Google Cloud so they have control of their destiny.Corey: I'm curious to know what you see happening in the real world because I can sit here and come up with a bunch of very well-thought-out logical reasons to go towards or away from certain patterns, but I spent years building things myself. I know how it works, you grab the closest thing handy and throw it in and we all know that there is nothing so permanent as a temporary fix. Like, that thing is load-bearing and you'll retire with that thing still in place. In the idealized world, I don't think that I would want to take a dependency on something like—easy example—Spanner or AlloyDB because despite the fact that they have Postgres-squeal—yes, that's how I pronounce it—compatibility, the capabilities of what they're able to do under the hood far exceed and outstrip whatever you're going to be able to build yourself or get anywhere else. So, there's a dataflow architectural dependency lock-in, despite the fact that it is at least on its face, Postgres compatible. Counterpoint, does that actually matter to customers in what you are seeing?Andi: I think it's a great question. I'll give you a couple of data points. I mean, first of all, even if you take a complete open-source product, right, running them in different clouds, different on-premises environments, and so on, fundamentally, you will have some differences in performance characteristics, availability characteristics, and so on. So, the truth is, even if you use open-source, right, you're not going to get a hundred percent of the same characteristics where you run that. But that said, you still have the freedom of movement, and with I would say and not a huge amount of engineering investment, right, you're going to make sure you can run that workload elsewhere.I kind of think of Spanner in the similar way where yes, I mean, you're going to get all those benefits of Spanner that you can't get anywhere else, like unlimited scale, global consistency, right, no maintenance downtime, five-nines availability, like, you can't really get that anywhere else. That said, not every application necessarily needs it. And you still have that option, right, that if you need to, or want to, or we're not giving you a reasonable price or reasonable price performance, but we're starting to neglect you as a customer—which of course we wouldn't, but let's just say hypothetically, that you know, that could happen—that you still had a way to basically go and run this elsewhere. Now, I'd also want to talk about some of the upsides something like Spanner gives you. Because you talked about, you want to be able to just grab a few things, build something quickly, and then, you know, you don't want to be stuck.The counterpoint to that is with Spanner, you can start really, really small, and then let's say you're a gaming studio, you know, you're building ten titles hoping that one of them is going to take off. So, you can build ten of those, you know, with very minimal spend on Spanner and if one takes off overnight, it's really only the database where you don't have to go and re-architect the application; it's going to scale as big as you need it to. And so, it does enable a lot of this innovation and a lot of cost management as you try to get to that overnight success.Corey: Yeah, overnight success. I always love that approach. It's one of those, “Yeah, I became an overnight success after only ten short years.” It becomes this idea people believe it's in fits and starts, but then you see, I guess, on some level, the other side of it where it's a lot of showing up and doing the work. I have to confess, I didn't do a whole lot of admin work in my production years that touched databases because I have an aura and I'm unlucky, and it turns out that when you blow away some web servers, everyone can laugh and we'll reprovision stateless things.Get too close to the data warehouse, for example, and you don't really have a company left anymore. And of course, in the world of finance that I came out of, transactional integrity is also very much a thing. A question that I had [centers 00:17:51] really around one of the predictions you gave recently at Google Cloud Next, which is your prediction for the future is that transactional and analytical workloads from a database perspective will converge. What's that based on?Andi: You know, I think we're really moving from a world where customers are trying to make real-time decisions, right? If there's model drift from an AI and ML perspective, want to be able to retrain their models as quickly as possible. So, everything is fast moving into streaming. And I think what you're starting to see is, you know, customers don't have that time to wait for analyzing their transactional data. Like in the past, you do a batch job, you know, once a day or once an hour, you know, move the data from your transactional system to analytical system, but that's just not how it is always-on businesses run anymore, and they want to have those real-time insights.So, I do think that what you're going to see is transactional systems more and more building analytical capabilities, analytical systems building, and more transactional, and then ultimately, cloud platform providers like us helping fill that gap and really making data movement seamless across transactional analytical, and even AI and ML workloads. And so, that's an area that I think is a big opportunity. I also think that Google is best positioned to solve that problem.Corey: Forget everything you know about SSH and try Tailscale. Imagine if you didn't need to manage PKI or rotate SSH keys every time someone leaves. That'd be pretty sweet, wouldn't it? With Tailscale SSH, you can do exactly that. Tailscale gives each server and user device a node key to connect to its VPN, and it uses the same node key to authorize and authenticate SSH.Basically you're SSHing the same way you manage access to your app. What's the benefit here? Built-in key rotation, permissions as code, connectivity between any two devices, reduce latency, and there's a lot more, but there's a time limit here. You can also ask users to reauthenticate for that extra bit of security. Sounds expensive?Nope, I wish it were. Tailscale is completely free for personal use on up to 20 devices. To learn more, visit snark.cloud/tailscale. Again, that's snark.cloud/tailscaleCorey: On some level, I've found that, at least in my own work, that once I wind up using a database for something, I'm inclined to try and stuff as many other things into that database as I possibly can just because getting a whole second data store, taking a dependency on it for any given workload tends to be a little bit on the, I guess, challenging side. Easy example of this. I've talked about it previously in various places, but I was talking to one of your colleagues, [Sarah Ellis 00:19:48], who wound up at one point making a joke that I, of course, took way too far. Long story short, I built a Twitter bot on top of Google Cloud Functions that every time the Azure brand account tweets, it simply quote-tweets that translates their tweet into all caps, and then puts a boomer-style statement in front of it if there's room. This account is @cloudboomer.Now, the hard part that I had while doing this is everything stateless works super well. Where do I wind up storing the ID of the last tweet that it saw on his previous run? And I was fourth and inches from just saying, “Well, I'm already using Twitter so why don't we use Twitter as a database?” Because everything's a database if you're either good enough or bad enough at programming. And instead, I decided, okay, we'll try this Firebase thing first.And I don't know if it's Firestore, or Datastore or whatever it's called these days, but once I wrap my head around it incredibly effective, very fast to get up and running, and I feel like I made at least a good decision, for once in my life, involving something touching databases. But it's hard. I feel like I'm consistently drawn toward the thing I'm already using as a default database. I can't shake the feeling that that's the wrong direction.Andi: I don't think it's necessarily wrong. I mean, I think, you know, with Firebase and Firestore, that combination is just extremely easy and quick to build awesome mobile applications. And actually, you can build mobile applications without a middle tier which is probably what attracted you to that. So, we just see, you know, huge amount of developers and applications. We have over 4 million databases in Firestore with just developers building these applications, especially mobile-first applications. So, I think, you know, if you can get your job done and get it done effectively, absolutely stick to them.And by the way, one thing a lot of people don't know about Firestore is it's actually running on Spanner infrastructure, so Firestore has the same five-nines availability, no maintenance downtime, and so on, that has Spanner, and the same kind of ability to scale. So, it's not just that it's quick, it will actually scale as much as you need it to and be as available as you need it to. So, that's on that piece. I think, though, to the same point, you know, there's other databases that we're then trying to make sure kind of also extend their usage beyond what they've traditionally done. So, you know, for example, we announced AlloyDB, which I kind of call it Postgres on steroids, we added analytical capabilities to this transactional database so that as customers do have more data in their transactional database, as opposed to having to go somewhere else to analyze it, they can actually do real-time analytics within that same database and it can actually do up to 100 times faster analytics than open-source Postgres.So, I would say both Firestore and AlloyDB, are kind of good examples of if it works for you, right, we'll also continue to make investments so the amount of use cases you can use these databases for continues to expand over time.Corey: One of the weird things that I noticed just looking around this entire ecosystem of databases—and you've been in this space long enough to, presumably, have seen the same type of evolution—back when I was transiting between different companies a fair bit, sometimes because I was consulting and other times because I'm one of the greatest in the world at getting myself fired from jobs based upon my personality, I found that the default standard was always, “Oh, whatever the database is going to be, it started off as MySQL and then eventually pivots into something else when that starts falling down.” These days, I can't shake the feeling that almost everywhere I look, Postgres is the answer instead. What changed? What did I miss in the ecosystem that's driving that renaissance, for lack of a better term?Andi: That's a great question. And, you know, I have been involved in—I'm going to date myself a bit—but in PHP since 1997, pretty much, and one of the things we kind of did is we build a really good connector to MySQL—and you know, I don't know if you remember, before MySQL, there was MS SQL. So, the MySQL API actually came from MS SQL—and we bundled the MySQL driver with PHP. And so, kind of that LAMP stack really took off. And kind of to your point, you know, the default in the web, right, was like, you're going to start with MySQL because it was super easy to use, just fun to use.By the way, I actually wrote—co-authored—the tab completion in the MySQL client. So like, a lot of these kinds of, you know, fun, simple ways of using MySQL were there, and frankly, was super fast, right? And so, kind of those fast reads and everything, it just was great for web and for content. And at the time, Postgres kind of came across more like a science project. Like the folks who were using Postgres were kind of the outliers, right, you know, the less pragmatic folks.I think, what's changed over the past, how many years has it been now, 25 years—I'm definitely dating myself—is a few things: one, MySQL is still awesome, but it didn't kind of go in the direction of really, kind of, trying to catch up with the legacy proprietary databases on features and functions. Part of that may just be that from a roadmap perspective, that's not where the owner wanted it to go. So, MySQL today is still great, but it didn't go into that direction. In parallel, right, customers wanting to move more to open-source. And so, what they found this, the thing that actually looks and smells more like legacy proprietary databases is actually Postgres, plus you saw an increase of investment in the Postgres ecosystem, also very liberal license.So, you have lots of other databases including commercial ones that have been built off the Postgres core. And so, I think you are today in a place where, for mainstream enterprise, Postgres is it because that is the thing that has all the features that the enterprise customer is used to. MySQL is still very popular, especially in, like, content and web, and mobile applications, but I would say that Postgres has really become kind of that de facto standard API that's replacing the legacy proprietary databases.Corey: I've been on the record way too much as saying, with some justification, that the best database in the world that should be used for everything is Route 53, specifically, TXT records. It's a key-value store and then anyone who's deep enough into DNS or databases generally gets a slightly greenish tinge and feels ill. That is my simultaneous best and worst database. I'm curious as to what your most controversial opinion is about the worst database in the world that you've ever seen.Andi: This is the worst database? Or—Corey: Yeah. What is the worst database that you've ever seen? I know, at some level, since you manage all things database, I'm asking you to pick your least favorite child, but here we are.Andi: Oh, that's a really good question. No, I would say probably the, “Worst database,” double-quotes is just the file system, right? When folks are basically using the file system as regular database. And that can work for, you know, really simple apps, but as apps get more complicated, that's not going to work. So, I've definitely seen some of that.I would say the most awesome database that is also file system-based kind of embedded, I think was actually SQLite, you know? And SQLite is actually still very, very popular. I think it sits on every mobile device pretty much on the planet. So, I actually think it's awesome, but it's, you know, it's on a database server. It's kind of an embedded database, but it's something that I, you know, I've always been pretty excited about. And, you know, their stuff [unintelligible 00:27:43] kind of new, interesting databases emerging that are also embedded, like DuckDB is quite interesting. You know, it's kind of the SQLite for analytics.Corey: We've been using it for a few things around a bill analysis ourselves. It's impressive. I've also got to say, people think that we had something to do with it because we're The Duckbill Group, and it's DuckDB. “Have you done anything with this?” And the answer is always, “Would you trust me with a database? I didn't think so.” So no, it's just a weird coincidence. But I liked that a lot.It's also counterintuitive from where I sit because I'm old enough to remember when Microsoft was teasing the idea of WinFS where they teased a future file system that fundamentally was a database—I believe it's an index or journal for all of that—and I don't believe anything ever came of it. But ugh, that felt like a really weird alternate world we could have lived in.Andi: Yeah. Well, that's a good point. And by the way, you know, if I actually take a step back, right, and I kind of half-jokingly said, you know, file system and obviously, you know, all the popular databases persist on the file system. But if you look at what's different in cloud-first databases, right, like, if you look at legacy proprietary databases, the typical setup is wright to the local disk and then do asynchronous replication with some kind of bounded replication lag to somewhere else, to a different region, or so on. If you actually start to look at what the cloud-first databases look like, they actually write the data in multiple data centers at the same time.And so, kind of joke aside, as you start to think about, “Hey, how do I build the next generation of applications and how do I really make sure I get the resiliency and the durability that the cloud can offer,” it really does take a new architecture. And so, that's where things like, you know, Spanner and Big Table, and kind of, AlloyDB databases are truly architected for the cloud. That's where they actually think very differently about durability and replication, and what it really takes to provide the highest level of availability and durability.Corey: On some level, I think one of the key things for me to realize was that in my own experiments, whenever I wind up doing something that is either for fun or I just want see how it works in what's possible, the scale of what I'm building is always inherently a toy problem. It's like the old line that if it fits in RAM, you don't have a big data problem. And then I'm looking at things these days that are having most of a petabyte's worth of RAM sometimes it's okay, that definition continues to extend and get ridiculous. But I still find that most of what I do in a database context can be done with almost any database. There's no reason for me not to, for example, uses a SQLite file or to use an object store—just there's a little latency, but whatever—or even a text file on disk.The challenge I find is that as you start scaling and growing these things, you start to run into limitations left and right, and only then it's one of those, oh, I should have made different choices or I should have built-in abstractions. But so many of these things comes to nothing; it just feels like extra work. What guidance do you have for people who are trying to figure out how much effort to put in upfront when they're just more or less puttering around to see what comes out of it?Andi: You know, we like to think about ourselves at Google Cloud as really having a unique value proposition that really helps you future-proof your development. You know, if I look at both Spanner and I look at BigQuery, you can actually start with a very, very low cost. And frankly, not every application has to scale. So, you can start at low cost, you can have a small application, but everyone wants two things: one is availability because you don't want your application to be down, and number two is if you have to scale you want to be able to without having to rewrite your application. And so, I think this is where we have a very unique value proposition, both in how we built Spanner and then also how we build BigQuery is that you can actually start small, and for example, on Spanner, you can go from one-tenth of what we call an instance, like, a small instance, that is, you know, under $65 a month, you can go to a petabyte scale OLTP environment with thousands of instances in Spanner, with zero downtime.And so, I think that is really the unique value proposition. We're basically saying you can hold the stick at both ends: you can basically start small and then if that application doesn't need to scale, does need to grow, you're not reengineering your application and you're not taking any downtime for reprovisioning. So, I think that's—if I had to give folks, kind of, advice, I say, “Look, what's done is done. You have workloads on MySQL, Postgres, and so on. That's great.”Like, they're awesome databases, keep on using them. But if you're truly building a new app, and you're hoping that app is going to be successful at some point, whether it's, like you said, all overnight successes take at least ten years, at least you built in on something like Spanner, you don't actually have to think about that anymore or worry about it, right? It will scale when you need it to scale and you're not going to have to take any downtime for it to scale. So, that's how we see a lot of these industries that have these potential spikes, like gaming, retail, also some use cases in financial services, they basically gravitate towards these databases.Corey: I really want to thank you for taking so much time out of your day to talk with me about databases and your perspective on them, especially given my profound level of ignorance around so many of them. If people want to learn more about how you view these things, where's the best place to find you?Andi: Follow me on LinkedIn. I tend to post quite a bit on LinkedIn, I still post a bit on Twitter, but frankly, I've moved more of my activity to LinkedIn now. I find it's—Corey: That is such a good decision. I envy you.Andi: It's a more curated [laugh], you know, audience and so on. And then also, you know, we just had Google Cloud Next. I recorded a session there that kind of talks about database and just some of the things that are new in database-land at Google Cloud. So, that's another thing that if folks more interested to get more information, that may be something that could be appealing to you.Corey: We will, of course, put links to all of this in the [show notes 00:34:03]. Thank you so much for your time. I really appreciate it.Andi: Great. Corey, thanks so much for having me.Corey: Andi Gutmans, VP and GM of Databases at Google Cloud. I'm Cloud Economist Corey Quinn and this is Screaming in the Cloud. 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 an angry, insulting comment, then I'm going to collect all of those angry, insulting comments and use them as a database.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.Announcer: This has been a HumblePod production. Stay humble.

Das Versprechen: IEC 61499 definiert eine domänenspezifische Modellierungssprache für die Entwicklung verteilter industrieller Steuerungslösungen. IEC 61499 erweitert die IEC 61131-1 durch die Verbesserung der Kapselung von Softwarekomponenten für eine verbesserte Wiederverwendbarkeit, die Bereitstellung eines herstellerunabhängigen Formats und die Vereinfachung der Unterstützung für die Kommunikation zwischen den Steuerungen. Seine Verteilungsfunktionalität und die inhärente Unterstützung für dynamische Rekonfiguration bieten die erforderliche Infrastruktur für Industrie 4.0 und industrielle IoT-Anwendungen.

Kito, Danno, and Josh welcome special guest Holly Cummins, Senior Principal Software Engineer on the Quarkus team at Red Hat and fellow Java Champion, to talk about Quarkus, working at IBM and Red Hat, Kotlin, ktor, contract testing, JHipster, Broadcom buying VMWare, and much more. We Thank DataDog for sponsoring this podcast! https://www.pubhouse.net/datadog *UI / Web* Ktor 2.0.0 and 2.0.1 https://ktor.io/changelog/2.0/ Quinoa - A Quarkus extension to create Modern UI with no hassle https://quarkus.io/blog/quinoa-modern-ui-with-no-hassle/ *Server Side Java* Getting Really Close to Jakarta EE 10! | The Eclipse Foundation (some specs can be reviewed/tested now) https://jakarta.ee/news/getting-really-close-jakarta-ee-10/ Quarkus CLI tool from SDKMAN: https://sdkman.io/sdks#quarkus https://sdkman.io/sdks#quarkus Installing JHipster Quarkus https://www.jhipster.tech/blueprints/quarkus/001_installing_jhipster_quarkus.html *IDEs and Tools* Kotlin 1.7.0 https://blog.jetbrains.com/kotlin/2022/05/kotlin-1-7-0-beta/ Quarkus IDE Support https://quarkus.io/guides/ide-tooling *Other * Holly's site https://hollycummins.com/ Why You Can't Buy Cloud Native talk https://hollycummins.com/why-you-cant-buy-cloud-native-codecamp/ OH! PROJECT LOOM OUT IN NEXT RELEASE  https://openjdk.java.net/jeps/425 Broadcom buys VMWare https://www.cnbc.com/2022/05/26/broadcom-announces-plans-to-buy-vmware.html Sip of Java: Scripting w Java https://inside.java/2022/05/23/sip052/ *Picks* Rocket XTRM-Q External SSD http://sabrent.com/products/sb-xtmq-4tb Podman https://podman.io/ Rancher Desktop https://rancherdesktop.io/ Gitpod.io  https://gitpod.io/ Pact (Contract Testing)  https://docs.pact.io/ *Other Pubhouse Network podcasts* Breaking into Open Source https://www.pubhouse.net/breaking-into-open-source OffHeap https://www.javaoffheap.com/ Java Pubhouse https://www.javapubhouse.com/ Events Agile2022 - July 18-20, 2022 - Nashville, TN , USA https://www.agilealliance.org/agile2022/ NFJS - USA https://nofluffjuststuff.com/ Great Lakes Software Symposium June 10 - 12, 2022 https://nofluffjuststuff.com/chicago ÜberConf July 12 - 15, 2022 https://uberconf.com/ KCDC https://www.kcdc.info/ August 8-10,  2022 https://www.kcdc.info/ JAVA ONE IS BACK: JavaOne is coming to Las Vegas in October 2022  October 16 to October 22, 2022.  https://blogs.oracle.com/javamagazine/post/javaone-2022 JCON Online 2022 - Sept 20-23 - Online https://2022.jcon.one/ connect.tech - Nov 8-10 - Atlanta, GA https://2021.connect.tech/ Java Summit IL - November 21 - Tel Aviv, Israel https://www.javasummitil.com/ SpringOne - Dec 6-8 (CFP Open) San Francisco or online https://springone.io/  

Bryan berichtet über die Pläne der chinesischen Foundation, die Rolle von Open Source in der Industrie, warum sich westliche Entwickler und chinesische Kolleginnen und Kollegen in der Zusammenarbeit schwer tun und welche Rolle Diversity bei der Entwicklung spielt.

Peggy and Frederic Desbiens, program manager for IoT and edge computing, Eclipse Foundation, talk about the organization. He says it is an open-source organization, a non-profit, and it is the home to more than 400 open-source projects, delivering services. They also discuss: The importance of open source. The importance of partnerships, relationships, and collaboration. Unique findings as a result of COVID. iot.eclipse.org (2/15/22 - 758) IoT, Internet of Things, Peggy Smedley, artificial intelligence, machine learning, big data, digital transformation, cybersecurity, blockchain, 5G, cloud, sustainability, future of work, podcast, Frederic Desbiens, Eclipse Foundation This episode is available on all major streaming platforms. If you enjoyed this segment, please consider leaving a review on Apple Podcasts.

Peggy and Frederic Desbiens, program manager for IoT and edge computing, Eclipse Foundation, talk about the organization. He says it is an open-source organization, a non-profit, and it is the home to more than 400 open-source projects, delivering services. They also discuss: The importance of open source. The importance of partnerships, relationships, and collaboration. Unique findings as a result of COVID. iot.eclipse.org (2/15/22 - 758) IoT, Internet of Things, Peggy Smedley, artificial intelligence, machine learning, big data, digital transformation, cybersecurity, blockchain, 5G, cloud, sustainability, future of work, podcast, Frederic Desbiens, Eclipse Foundation This episode is available on all major streaming platforms. If you enjoyed this segment, please consider leaving a review on Apple Podcasts.

Michael ist Ecosystem Development Director at Eclipse Foundation. Was er den ganzen Tag macht und warum auch die Plattform Industrie 4.0 mit ihm zusammenarbeitet, erklärt er im Podcast. Und Julian muss sein Vorurteil gegenüber der Foundations als Beamtenstube korrigieren.

Inside Living on the Edge episode 14, Jason and Dan discuss BT's public cloud strategy, new LEO and MNO partnerships and what's needed for edge native services and applications.

What is Jetty?Today, our guests share their extensive experience with Jetty. Greg Wilkins is the original software engineer for Jetty and Simone Bordet is a Jetty Committer. Jetty itself is an HTTP server and container for deploying Java servlets that run on HTTP, and it was also the first Java application server to be deployed as a clickable JAR file. Jetty started as a small open source project, and then moved to the Eclipse Foundation in 2009, where it still finds its home today.Greg adds, “Jetty is actually a lot more than an HTTP server. Over the years, the way we've developed the software is rather than being an application container, Jetty is a good software component first that can be used to make an application server, but it can also be used to make embedded applications and various other things.” Who uses Jetty?Jetty has a 25-year history with clients big and small, commercial and open source, from SaaS products to PaaS services. As Simone puts it, “Jetty is deeply battle-tested.” What do clients like about Jetty? It is:Highly extensible, flexible, and pluggableHighly scalable for large loadsCan be scaled down for smaller deploymentsWhat's ahead for Jetty?The new Jetty comes with significant improvements in performance and documentation, new features, and upgrades to Java 11 and Jakarta EE 9. Moving forward, Simone and Greg have plenty more they'd like to explore. “In the future, I'd like to see the standard support a good, reactive and/or asynchronous, scalable HTTP protocol and all the protocol features, and then have the application features layered on top of that,” says Greg. After working on Jetty for so long, Greg says it is just as relevant as it ever was. “It is amazing to keep doing it and to see the way Jetty keeps developing. What happens above us and the way people use the web changes all the time, but they still need this HTTP protocol.” Try out Jetty on Platform.sh: https://github.com/platformsh-templat... Platform.shLearn more about us.Get started with a free trial.Have a question? Get in touch!Platform.sh on social mediaTwitter @platformshTwitter (France): @platformsh_frLinkedIn: Platform.shLinkedIn (France): Platform.shFacebook: Platform.shWatch, listen, subscribe to the Platform.sh Deploy Friday podcast:YouTubeApple PodcastsBuzzsproutPlatform.sh is a robust, reliable hosting platform that gives development teams the tools to build and scale applications efficiently. Whether you run one or one thousand websites, you can focus on creating features and functionality with your favorite tech stack.

Foojay community members discuss the modernization of Jakarta EE applications from the older Java EE form, including backwards-compatibility, as well as forwards-excitement about cool new developments like Microprofile.Guests:Rudy De Busscher, product manager of Payara and EE contributor.Josh Juneau, consultant and author of Jakarta EE Recipes.Ivar Grimstad, Jakarta EE Advocate for the Eclipse Foundation.Erik Costlow, Developer Relations for Contrast Security to secure Java/Jakarta EE applications.

In this episode, we discuss the Eclipse Foundation's recently published IoT and Edge commercial adoption survey, which is released every two years. We explored edge computing adoption trends, future investment plans, common implementation challenges and changing perspectives on the dynamics between edge and cloud.  Our guest today is Frederic Desbiens, program manager of IoT and edge computing at the Eclipse Foundation. The Eclipse Foundation provides a mature, scalable and business friendly environment for over 375 open source projects, including frameworks for edge and cloud applications, IoT and AI. IoT ONE is an IoT focused research and advisory firm. We provide research to enable you to grow in the digital age. Our services include market research, competitor information, customer research, market entry, partner scouting, and innovation programs. For more information, please visit iotone.com

The Eclipse Foundation recently conducted a survey that focuses on IoT and Edge solutions. When I saw the results, I thought some sort of explanation was required, and that's exactly what I got from Frederic Desbiens, Program Manager for IoT & Edge at the Eclipse Foundation in this week's Embedded Executives podcast.

Projections indicate that 40% of organizations expect to increase Internet of Things (IoT) spending in the next fiscal year. This tells us that it's quickly becoming a crucial component within the industrial machinery industry. Knowing that this is a clear path for companies who want to accelerate their own digital transformation, getting started can seem daunting. Where should an organization even begin?Understanding the benefits to production capacity and the reduction of energy consumption is a good start. Taking small steps along the road like incrementally increasing machine connectivity serves as a motivating and daily reminder of the benefits business can leverage to their advantage. Within the collection of so much data lies limitless potential.In today's episode, Jörg Ludwig continues the conversation with Heiko Dickas, team leader of the digitalization team, and Sebastian Oeder, the head of the production unit main motors, both from Siemens Bad Neustadt, an electric motor factory in Bad Neustadt an der Saale, Germany. Also with us today are Portfolio Development Manager, Colm Gavin, and Head of PreSales and Solution Design, Matthias Lutz.Today's discussion centers around how the industrial IoT can help companies with today's complex challenges within manufacturing. You'll hear why getting started is less about fancy analytics and more about machine connectivity, and how we can ensure customers that their data is not only safe, but remains confidential.Some Questions Asked:Where should companies start with digitalization? (2:22)What are the differences between an edge implementation and doing so on the cloud? (6:10)How has industrial IoT improved your factory? (13:38)What You Will Learn:A common misconception about implementing digitalization (3:47)The surprising amount of data that you could be collecting (7:37)What customers really mean when they talk about security (10:00)Resources:Survey: Foundation, Eclipse. “The Eclipse Foundation Releases IoT Commercial Adoption Survey Results.” The Eclipse Foundation, www.eclipse.org/org/press-release/20200310-iot-commercial-adoption-survey-2019.php. Article: “Digital Transformation at Scale for Industrial Products.” IBM, www.ibm.com/thought-leadership/institute-business-value/report/transformation-industrial-products. Connect with Heiko Dickas:LinkedInConnect with Sebastian Oeder:LinkedInConnect with Colm Gavin:LinkedInConnect with Matthias Lutz:LinkedInConnect with Jörg Ludwig:LinkedIn See acast.com/privacy for privacy and opt-out information.

Нас конечно долго не было, но это все для того чтобы скопить побольше сил и продолжать делать для вас клевые выпуски. Сегодня мы будем много говорить о мире, в который боятся заходить современные Spring разработчики. Он повергает их в трепет и ужас и имя ему - Jakarta EE. Для уверенного погружения в эту тему мы позвали Митю Александрова, который много и подробно рассказал, как обстоят дела в этом мире и рассказал о Project Helidon, который всех победит. Если вы хотите поделиться своими впечатлениями от выпуска или задать свои вопросы - у нас есть телеграмм канал: http://t.me/javahutpodcast и твиттер! https://twitter.com/JavaHutPodcast! Мы ждём ваших подписок и лайков! Ваши комментарии, пожелания и предложения мы с удовольствием принимаем в наши почты и в телеграмм канале. Немного полезностей и годноты: 25 Июня состоится конфереция jLove: https://jlove.konfy.care/ У нас есть на нее промокод! Конференция бесплатная, но есть возможность купить доступ к видеозаписям и лайв QA сессиям с 50% скидкой Промокод: JAVAHUT Если вам интересны конкретные темы - мы приготовили для вас таймкоды, которые помогут вам их найти: 00:01:40 Кто такой Java Champion и что это дает кроме халявной Idea 00:04:47 О том как создавался болгарский JUG и почему делиться знаниями это круто 00:12:04 Как последний год отразился на комьюнити и что будет дальше 00:19:20 Как проходит подготовка к конференциям и как ребята готовят спикеров 00:25:00 О Jakarta EE и как у неё дела 00:28:42 Почему то что происходит с Jakarta важно для всех 00:31:00 О мире Springa и есть ли у Jakarta EE план 00:38:10 О том что изменилось с переходом под Eclipse Foundation и стало ли лучше 00:41:15 Про бюрократию и какой путь у новых фич в Jakarta EE 00:45:23 О том почему Jakarta EE не гонится за последними версиями Java SE и нужно ли это фреймворкам 00:53:00 Helidon - что это и зачем оно надо 01:04:00 Зачем нужен ещё один фреймворк для написания микросервисов и какие уроки Helidon вынес из соседних кейсов 01:08:55 О том будет ли скоро все Java приложения native 01:16:05 Про то почему бы программистам не объединиться и не сделать один хороший фреймворк, вместо 10 конкурирующих В выпуске мы обсуждаем ряд материалов и думаем будет полезным собрать все эти ссылки вместе тут: Доклад Дмитрия Корнилова про путь от Java EE к Jakarta EE: https://www.youtube.com/watch?v=Ndn6eGCCK0w&ab_channel=JakartaEE Ведущие: Рома Меерсон twitter: @Homich1991 Женя Никифоров twitter: @Baron_Oren Гость: Дмитрий Александров twitter: @bercut2000 Music: https://www.purple-planet.com

In this episode of ShipTalk, we are joined by Tracy Miranda who is the Executive Director of the Continuous Delivery Foundation which is part of the Linux Foundation. Tracy has been leading open source communities prior to her time at the CDF at Cloudbees and has spent time on the governing board of the Eclipse Foundation. Tracy chats through her experience creating thriving open source communities and practices from inception to maturity. Open source projects especially at their inception run like a start-up. Learn in this episode how to build a sustainable, robust, and inclusive community and more from Tracy. 

Migrating Java applications to the cloudJava is a popular framework that’s been a foundation for many enterprise applications for over 20 years. But lately, those enterprises have run into trouble: moving their applications to the cloud. This migration promises more security, reliability, and easier scaling, but it can be daunting with an older framework like Java. The host, Robert Douglass of Platform.sh, asks,“With all these older versions of applications floating around in this huge plethora of runtimes and variants, does that make it harder for organizations to “lift and shift”, or to adopt cloud native philosophies?” Speakers from Red Hat, the Eclipse Foundation, and Paerra address the Java toolbox that can help ease this transition.Java toolbox for developersJlink -- A command-line utility which helps modularize your application and makes it possible to build your own JVM Graal.vm -- A compiler that helps existing Java applications run faster, provide extensibility with scripting languages, and create ahead-of-time or just-in-time compiled native imagesTransformer -- An Eclipse project that takes your application to the Jakarta EE namespace so you don’t have to recompileJakarta EE -- The new name and face of Java EE, with all the same benefits: maturity, reliability, stability, and large community. Jakarta EE is a more enterprise-ready, cloud-ready, and microservice-ready version of Java.What should hype up developers about working with Jakarta EE? Ivar Grimstad of the Eclipse Foundation says, “If you want to be future-proof and to be productive right away, you can write less code, less configuration, and less boilerplate to get up and running using Jakarta EE than any other framework.”Make your life easier with Java toolsLaunching Java-built applications to the cloud can be difficult, but developers can minimize bumps by putting tools like Jlink, Graal.vm, Transformer, and Jakarta EE to work. Robert Douglass sums it up: “Stability, backwards compatibility, safety, and boringness are the hallmarks of the Java ecosystem these days, and they are really attractive features when the very act of software development is so fraught with risk.”Launch Java applications from these Platform.sh templates today.Platform.shLearn more about us.Get started with a free trial.Have a question? Get in touch!Platform.sh on social mediaTwitter: @platformshTwitter (France): @platformsh_frLinkedIn: Platform.shLinkedIn (France): Platform.shFacebook: Platform.shWatch, listen, and subscribe to the Platform.sh Deploy Friday podcast:YouTubeApple PodcastsBuzzsproutPlatform.sh is a robust, reliable hosting platform that gives development teams the tools to build and scale applications efficiently. Whether you run one or one thousand websites, you can focus on creating features and functionality with your favorite tech stack and leave managing infrastructure and processes to us.

In this episode of ShipTalk, we are joined by Tracy Ragan who is the CEO of DeployHub. Tracy is no stranger to open source communities spending time with the Eclipse Foundation and Continuous Delivery Foundation [part of the Linux Foundation].  A software and open source community is more than just a place to get free software, the community aspect is crucial. Especially during the COVID pandemic, the human element is key to furthering the software engineering craft.  Tracy talks about her career and community journey and why it is important to find your tribe.  At a bonus at the end, a joint perplexity around the rise of YAML.

So JDK 16 is rolling out, and keeping with the new six month cadence, we are getting new toys at least twice a year! We also have Microprofile 4 being released. In addition, we see the Eclipse Foundation getting bigger and bigger as it welcomes the OSGi alliance (how big will it become?) Lastly we talk about backdoor encryption requests, and the Case that will never die... Google V Oracle API Copyrights. Covering it all in our brand new OffHeap Episode! We thank DataDogHQ for sponsoring this podcast episode DO follow us on twitter @offheap JDK 16 JEPs rolling in: https://openjdk.java.net/projects/jdk/16/ Payara releases Jakarta EE 9 compatible container: https://www.javacodegeeks.com/2020/10/kicking-the-tires-of-jakarta-ee-9-with-payara.html Eclipse Transformer (discuss?): https://projects.eclipse.org/proposals/eclipse-transformer MicroProfile 4.0: https://projects.eclipse.org/projects/technology.microprofile/releases/microprofile-4.0 OSGi Alliance to Eclipse https://blog.osgi.org/2020/10/announcement-of-transition-to-eclipse.html?m=1 Backdoor encryption Access https://www.theverge.com/2020/10/12/21513212/backdoor-encryption-access-us-canada-australia-new-zealand-uk-india-japan Google AntiTrust Suit https://apnews.com/article/google-justice-department-antitrust-0510e8f9047956254455ec5d4db06044 Google Oracle Supreme Court - https://www.c-span.org/video/?469263-1/google-v-oracle-america-oral-argument#

In this episode of Modern Enterprise Podcast, we talk with Ian Skerrett, formerly VP of Marketing at Eclipse Foundation, on the role of open source in the cloud, the role of open source foundations and how open source can shape Edge Computing and IoT --- Support this podcast: https://anchor.fm/modernenterprise/support

An airhacks.fm conversation with Kevin Sutter (@kwsutter) about: working on Jakarta EE 9 and MicroProfile, IBM is supporting the Jakarta EE programming model, Oracle participates productively in Jakarta EE development, the developer and vendor view on Jakarta EE and MicroProfile, Jakarta EE and MicroProfile separation, one release of Jakarta EE per year is likely, Jakarta MVC and NoSQL could become part of Jakarta EE 9, should MicroProfile Configuration move to Jakarta EE?, thinking about MicroProfile working group, MicroProfile focusses on cloud specs, Jakarta EE is provides the stable infrastructure, "political is legal", successful opensource projects are like big companies, the Eclipse Foundation specification process will work fine for MicroProfile, Jakarta EE 9 big features, the Eclipse Transformer, Eclipse Transformer was used to transform the Jakarta EE TCK, Eclipse Transformer is used on application servers, but could also be used for applications, after 20 years of compatibility a breaking change is o.k., cleanup happens in Jakarta EE 9, XML-related services in Jakarta EE 9 are going to be listed as "optional", microservices and the trend towards monoliths, micro is not that micro any more, smallrye becomes the common implementation repository for MicroProfile, MicroProfile reactive messaging and MicroProfile GraphQL are not a part of MicroProfile platform yet, Kevin Sutter on twitter: @kwsutter

An airhacks.fm conversation with John Clingan (@jclingan) about: Redhat Summit Virtual Experience, Redhat Runtimes Quarkus Support, Senior Principal Manager of Next Generation Platforms, like Quarkus, MicroProfile is a major task, the MicroProfile IP flow, the formal stuff for a working group at Eclipse Foundation, tracking the MicroProfile progress: https://github.com/eclipse/microprofile/issues, the working group draft - what does it mean to be a MicroProfile working group, the MicroProfile politics, the goal of MicroProfile was to build specifications for development of microservices, MicroProfile began as crippled Jakarta EE, MicroProfile extends right now Jakarta EE with added value, fixing potential MicroProfile incompatibilities is less problematic and takes less energy to fix, Jakarta EE is a collection of specifications with a platform spec on top, helidon and quarkus are moving faster, because they are new, quarkus and helidon follow opposite philosophies, Quarkus Panache is proprietary but useful, Quarkus comes with 220 extensions, a half is camel related, Quarkus Vodafone Greece session at Red Hat Summit, Quarkus extension enable the integration of external configuration to configuration subsystem of quarkus, parsing XML at build time to save resources at runtime, Quarkus supports YAML - but keep it secret, Bruno Borges loves yaml, MicroProfile config is fully supported by Quarkus, Quarkus configuration is more than MicroProfile config, Quarkus Summit sessions, RedHat is a bottom-up organization, Quarkus is an integration point of various teams like e.g. Jakarta EE, MicroProfile, Vert.x, Camel, all Quarkus extensions have to run in dev mode and be compilable into GraalVM native mode, Quarkus is also driven by community feedback, with Quarkus you can get the niceness of Jakarta EE again, from 12 replicas to 2-4 replicas to serve the same traffic, startup time and memory utilization matter a lot in the context of kubernetes, the costs of running microservices in the clouds, for every microservice in production you get seven instances in staging environments, with quarkus you can build the perfect monolith, most of customers are building microliths, the microprofile hangouts, John Clingan on twitter: @jclingan, John's blog

A new report from Synopsys analyzes the use of open source components in commercial software, GitHub's fundraising program is now available for teams and projects, Mozilla appoints Adam Seligman as its new COO, Harbor becomes the first OCI-compliant container registry with its 2.0 release, and the Eclipse Foundation is moving to Belgium.

A new report from Synopsys analyzes the use of open source components in commercial software, GitHub's fundraising program is now available for teams and projects, Mozilla appoints Adam Seligman as its new COO, Harbor becomes the first OCI-compliant container registry with its 2.0 release, and the Eclipse Foundation is moving to Belgium.

An airhacks.fm conversation with Markus Karg (@mkarg) about: What is HeadCrashing? JavaMagazin, IX and Java Aktuell, the first JAX-RS contributions, extending JAX-RS via official API, you are not a spec lead, an airhacks.fm episode about Eclipse Foundation: From Java EE over EE4j to Jakarta EE, no political powers, APIs and SPIs are decoupled at Jakarta EE, Jersey is only "an" implementation of the spec, not "the'" implementation, Eclipse Foundation runs their own infrastructure, make JAX-RS more usable, Java SE bootstrap API for JAX-RS, it is impossible to write a spec without code, in future there is no room for coders, contract first is problematic, it will take more time to design the spec than to write the implementation, hundreds of microscopic services, with helidon there is less coupling to the proprietary implementation, building dependencies from source, relaxing drones, use cases for JAX-RS client-side caching, modular JAX-RS, new features in Jakarta EE 9, Jakarta EE 9 earth quake is enough, the JAX-RS roadmap, aligning JAX-RS with CDI, support for Java Platform Module System, JPMS modules in JAX-RS,Jersey is a framework, not a product, JPMS modules could provide new JAX-RS features, using JAX-RS client for testing, testing on kubernetes level, functional probes, project vs. product business, thoughts on odata, select * and everything stops, being more generic for CRUD and stuff which does not matter, accessing a database via excel, prepared interviews are not fun, Markus Karg on twitter: @mkarg, and Markus' blog: https://headcrashing.wordpress.com/

For more episodes listen here: https://thenewstack.io/podcasts/ Welcome to The New Stack Context, a podcast where we discuss the latest news and perspectives in the world of cloud native computing. For this week's episode, we spoke with a couple of folks from cloud workload protection platform provider Rezilion: CEO Liran Tancman, and Chief Marketing Officer Tal Klein. We discuss how current best practices in security are actually outdated and how they think companies should be approaching security practices in the age of DevOps. TNS editorial and marketing director Libby Clark hosted this episode, alongside founder and TNS publisher Alex Williams and TNS managing editor Joab Jackson. Klein wrote a contributed article for TNS on “Why Vulnerability Management Needs a Patch,” where he argues that current best practices and tools around security patching, such as the CVSS system for rating vulnerabilities, are outdated, particularly for modern DevOps shops. As Klein says in the interview: When you've got vulnerabilities, it's very tough to figure out which ones to fix first, and the fact is that more and more vulnerabilities are discovered every year. So there's, there's a greater amount of things to patch and if you don't know which ones to patch first, you're never going to be able to address the full patching needs of your organization. And that's been a cat and mouse game for a long time. Then later in the show, we discuss some of our top podcasts and stories of the week. Our sister podcast, The New Stack Makers, posted an interview with DevRel trailblazer (and Coder-Twitter celeb) Cassidy Williams, on building software communities. COVID-19 continues to tear through the IT community, and so we look at the shifting network traffic patterns that have come about from the pandemic, as well as the additional babysitting duties that many IT professionals have to now mix into their daily work from home routines. Finally, we discuss The Eclipse Foundation's Theia code editor, which has been billed as “a true open source alternative to Visual Studio Code.”

For more episodes listen here: https://thenewstack.io/podcasts/ Welcome to The New Stack Context, a podcast where we discuss the latest news and perspectives in the world of cloud native computing. For this week's episode, we spoke with a couple of folks from cloud workload protection platform provider Rezilion: CEO Liran Tancman, and Chief Marketing Officer Tal Klein. We discuss how current best practices in security are actually outdated and how they think companies should be approaching security practices in the age of DevOps. TNS editorial and marketing director Libby Clark hosted this episode, alongside founder and TNS publisher Alex Williams and TNS managing editor Joab Jackson. Klein wrote a contributed article for TNS on “Why Vulnerability Management Needs a Patch,” where he argues that current best practices and tools around security patching, such as the CVSS system for rating vulnerabilities, are outdated, particularly for modern DevOps shops. As Klein says in the interview: When you've got vulnerabilities, it's very tough to figure out which ones to fix first, and the fact is that more and more vulnerabilities are discovered every year. So there's, there's a greater amount of things to patch and if you don't know which ones to patch first, you're never going to be able to address the full patching needs of your organization. And that's been a cat and mouse game for a long time. Then later in the show, we discuss some of our top podcasts and stories of the week. Our sister podcast, The New Stack Makers, posted an interview with DevRel trailblazer (and Coder-Twitter celeb) Cassidy Williams, on building software communities. COVID-19 continues to tear through the IT community, and so we look at the shifting network traffic patterns that have come about from the pandemic, as well as the additional babysitting duties that many IT professionals have to now mix into their daily work from home routines. Finally, we discuss The Eclipse Foundation's Theia code editor, which has been billed as “a true open source alternative to Visual Studio Code.”

In episode 29 of Women in WP, we talk to Christie Witt, a WordPress designer, developer, and part-time comedian! Note: This episode was recorded during the very early days of the coronavirus pandemic, prior to the rapid spread across the world. About Christie Witt: Christie Witt is the Creative Specialist at Eclipse Foundation. Christie develops […]

An airhacks.fm conversation with Tanja Obradovic (@TanjaEclipse) about: The amazing rainbow wires, obsessed with tetris, programming: seeing immediate results is great, basic, pascal, fortran, c, c++ and FoxPro, Smalltalk in Canada, exposed to programming, pascal did more than basic, SmallTalk is clean and logical, object oriented programming was hyped, The Object People, programming over electronics, using TopLink to access databases, messaging between object was a challenge for a C++ programmer, objects talk like people, there are no blocks in Java, meta inheritance in SmallTalk and Java, business driven decisions matter, it is easier for C and C++ programmers to learn Java, than SmallTalk, working with TopLink as consultant, the acquisition of the consulting The Object People by BEA, the TopLink product was acquired by WebGain, Oracle acquired WebGain, Oracle acquired BEA, TopLink was migrated to Java by the Object People, enjoying to work as team lead, now its time to start programming again with MicroProfile and Jakarta EE, joining Eclipse Foundation, preparing Jakarta EE for the cloud era, Jakarta EE is a huge amount of work, starting to work on Jakarta EE 9, the big bang move to jakarta.* namespace, identifying the priorities was a major challenge, addressing one problem a time with more frequent Jakarta EE releases is the preferred approach, Jakarta EE and Java EE were synonyms for complexity, the Jakarta ONE livestream, Tanja Obradovic on twitter: @TanjaEclipse, Tanja's blog: https://blogs.eclipse.org/blogs/tanja-obradovic

Travis Cox and Arlen Nipper take a deep dive into the world of Digital Transformation and IIoT. They discuss the success of the MQTT protocol, the importance of education in continuing adoption of MQTT, the hurdles companies face when approaching the Digital Transformation, and how a strong ecosystem can achieve a solid IIoT infrastructure. They also touch upon the importance of the Eclipse Foundation, Sparkplug Working Group and much more. Learn more at inductiveautomation.com

Ah, we got together with our usual suspects, and while our local Curmudgeon was enjoying his Old-fashioned, I was enjoying Cold Medicine. Even so, we went through the biggest events that happened this year, including the Oracle v Google debacle, The new copy-and-kill strategies from cloud providers, the proliferation of Java implementations, the re-emergence of Eclipse Foundation as a home for standards, and of course, the Java EE (reincarnated as Jakarta EE) saga. It has been a great year, and we couldn't have made it with our listeners. Thanks for listening to our podcasts. We have expanded our OffHeap family, so don't forget to check all of our podcasts. And you can always drop off a line @offheap (https://twitter.com/offheap) Java Pub House (https://www.javapubhouse.com) Breaking into Open Source (https://www.pubhouse.net/breaking-into-open-source) Stackd, formally Enterprise Java News(http://enterprisejavanews.com/) And more coming on 2020! We thank DataDogHQ for sponsoring this podcast episode DO follow us on twitter @offheap Oracle moving OpenWorld from San Francisco to Las Vegas Caesars Forum Quarkus 1.1 CR JUnit 4.13 DevNexus (We'll be there!) Dev Dot Next (Bob and I will be presenting there!)

The Eclipse Foundation recently launched a new working group for Edge Native (https://edgenative.eclipse.org/). The mission is to deliver open source edge platforms now. I had a chance to sit down with the guests highlighted below to discuss. Enjoy. Mike Milinkovich, Executive Director, Eclipse Foundation Mike serves as the executive editor for the Eclipse Foundation. An influential voice in the open source and Java communities, Mike has worked tirelessly over the last two decades to help establish the open source model for software development. Outside of work, Mike's passions are his family, the family cottage and hockey (as a coach, player and fan) in pretty much that order. When he's not working, or traveling for work, you will probably find him involved in one of those three things. Kilton Hopkins, CEO and co-founder, Edgeworx Kilton started programming computers when he was 8 years old. That was 1986. He started a software company a few years later. The world is very different than it was back then, but Kilton is still bringing new tech companies to life. He currently serves as the Co-Founder and Chief Executive Officer of Edgeworx, which provides the world with an open-source universal edge computing platform called Eclipse ioFog. Kilton lives in Berkeley, California. He received his MBA from The University of Chicago Booth School of Business in 2010. He likes to meditate, make music, and read about everything scientific.

Microsoft releases Teams for Linux, SiFive enters the education market, the Eclipse Foundation champions open source on edge computing, and xs:code wants to help improve open source funding models.

Microsoft releases Teams for Linux, SiFive enters the education market, the Eclipse Foundation champions open source on edge computing, and xs:code wants to help improve open source funding models.

Java is owned by Oracle. Oracle has assigned Eclipse Foundation to handle Java Enterprise Edition, but they are not allowed to use the name Java (owned by Oracle). So JEE has been renamed to Jakarta Enterprise Edition. But this in not just about a name change, it can cause a whole range of challenges. Listen to Pontus Ullgren, Johan Carlsson and Tomas Ljunggren elaborating the subject.

An airhacks.fm conversation with Michael Bolz (@onemibo ) about: The first line of Turbo Pascal in 1992, 286 Compaq with a Turbo button, writing an installer for friends, C64 vs. PC, Jump and Run without jumping, writing some HTML code with DreamWeaver, What You See is NOT what you get, studying at the University of Applied Sciences in Karlsruhe, building web based applications with Struts, Java is easier to learn than C/C++, starting with "public static void main", then managing students with Java, writing UI tools in Swing / AWT for applying patches in CMS, JSF vs. Struts, the steinbeis foundation system migration from EJB 2.1 to EJB 3.1 in 2008, EJB 2.1 required code generation with xdoclet - and EJB 3.1 was nice, Heidelberg is nicer than Karlsruhe, the JAX 2012 meeting with JMS expert Ruediger zu Dohna, simplifications with JMS 2.X, copying museum code from the internet, copy and paste oriented programming, working for SAP, opensource at SAP, starting Apache Olingo, the ODATA specification for accessing backends, backend for frontends, ODATA is queryable database, ODATA exposes CRUD+ operations as standardised REST interface, Olingo is ODATA implementation for Java, Olingo is a raccoon, Olingo team started with 4 developers, ODATA v4 is an OASIS standard, ODATA v4 is mostly based on JSON, 2 developers are currently maintaining Olingo, JPA extension only exists for the Olingo v2 and not v4, most SAP services are available as ODATA endpoints, SAP's UI5 components can be also bound to ODATA, SAP UI5 widgets are also available as SAP ui5 WebComponents, MaxDB, teaching ABAP developers Java, nightly conversations about the R3 VM, in ThinWARs there is nothing to scan, removing unwanted dependencies is a good idea, Vulnerability Assessment Tool (Vulas) by SAP research, Vulas is going to be donated to Eclipse Foundation, Vulas scans transitive dependencies as well as the source code of the dependencies, SAP runs a lot of Java apps internally, Olingo comprises two parts - the metadata and the execution part, Olingo v2 comes with JPA extension and a Servlet as entry point, Microsoft contributed the Olingo client, Java Annotation extension for Apache Olingo V2, Olingo is open for contributions, it is a good idea to discuss new features on the mailing list first, new Olingo features must be backward compatible, this podcast episode was triggered by 66th airhacks.tv Q&A, Michael Bolz on twitter: @onemibo

Chris Aniszczyk is the CTO of the CNCF. We discuss how he got into open source, what it's like to work at Twitter and how he helped start the CNCF. Plus, Chris gives us an overview of the different kinds of CNCF projects and offers advice on how to get started with Kubernetes. Show links: Hatching Twitter (https://www.amazon.com/Hatching-Twitter-Story-Friendship-Betrayal/dp/1591847087) GORILLA.BAS (https://en.wikipedia.org/wiki/Gorillas_video_game) IBM Extreme Blue (https://www.ibm.com/employment/extremeblue/) Eclipse Marketplace (https://marketplace.eclipse.org/) Eclipse Foundation (https://www.eclipse.org/org/workinggroups/explore.php) CNCF Charter (https://github.com/cncf/foundation/blob/master/charter.md) The universal data plane API (https://blog.envoyproxy.io/the-universal-data-plane-api-d15cec7a) Universal Data Plane API Working Group (https://docs.google.com/document/d/1y-H-pQ2mmhBPX_U9pP3mMMUbEpZskxBdEbwd5KlivY4/edit#heading=h.hphw9gdcmb90) Contact Chris: @cra (https://twitter.com/cra) LinkedIn (https://www.linkedin.com/in/caniszczyk/) More Software Defined Talk Subscribe to Software Defined Interviews Podcast (https://www.softwaredefinedinterviews.com/) Subscribe to Software Defined Talk Podcast (https://www.softwaredefinedtalk.com/) Follow @SoftwareDefTalk on Twitter (https://twitter.com/SoftwareDefTalk) Send your postal address to stickers@softwaredefinedtalk.com (mailto:stickers@softwaredefinedtalk.com) and we will send you free laptop stickers! Join us in Slack (http://www.softwaredefinedtalk.com/slack). Special Guest: Chris Aniszczyk.

Chris Aniszczyk is the CTO of the CNCF. We discuss how he got into open source, what it's like to work at Twitter and how he helped start the CNCF. Plus, Chris gives us an overview of the different kinds of CNCF projects and offers advice on how to get started with Kubernetes. Show links: Hatching Twitter (https://www.amazon.com/Hatching-Twitter-Story-Friendship-Betrayal/dp/1591847087) GORILLA.BAS (https://en.wikipedia.org/wiki/Gorillas_video_game) IBM Extreme Blue (https://www.ibm.com/employment/extremeblue/) Eclipse Marketplace (https://marketplace.eclipse.org/) Eclipse Foundation (https://www.eclipse.org/org/workinggroups/explore.php) CNCF Charter (https://github.com/cncf/foundation/blob/master/charter.md) The universal data plane API (https://blog.envoyproxy.io/the-universal-data-plane-api-d15cec7a) Universal Data Plane API Working Group (https://docs.google.com/document/d/1y-H-pQ2mmhBPX_U9pP3mMMUbEpZskxBdEbwd5KlivY4/edit#heading=h.hphw9gdcmb90) Contact Chris: @cra (https://twitter.com/cra) LinkedIn (https://www.linkedin.com/in/caniszczyk/) More Software Defined Talk Subscribe to Software Defined Interviews Podcast (https://www.softwaredefinedinterviews.com/) Subscribe to Software Defined Talk Podcast (https://www.softwaredefinedtalk.com/) Follow @SoftwareDefTalk on Twitter (https://twitter.com/SoftwareDefTalk) Send your postal address to stickers@softwaredefinedtalk.com (mailto:stickers@softwaredefinedtalk.com) and we will send you free laptop stickers! Join us in Slack (http://www.softwaredefinedtalk.com/slack). Special Guest: Chris Aniszczyk.

Chris Aniszczyk is the CTO of the CNCF. We discuss how he got into open source, what it's like to work at Twitter and how he helped start the CNCF. Plus, Chris gives us an overview of the different kinds of CNCF projects and offers advice on how to get started with Kubernetes. Show links: Hatching Twitter (https://www.amazon.com/Hatching-Twitter-Story-Friendship-Betrayal/dp/1591847087) GORILLA.BAS (https://en.wikipedia.org/wiki/Gorillas_video_game) IBM Extreme Blue (https://www.ibm.com/employment/extremeblue/) Eclipse Marketplace (https://marketplace.eclipse.org/) Eclipse Foundation (https://www.eclipse.org/org/workinggroups/explore.php) CNCF Charter (https://github.com/cncf/foundation/blob/master/charter.md) The universal data plane API (https://blog.envoyproxy.io/the-universal-data-plane-api-d15cec7a) Universal Data Plane API Working Group (https://docs.google.com/document/d/1y-H-pQ2mmhBPX_U9pP3mMMUbEpZskxBdEbwd5KlivY4/edit#heading=h.hphw9gdcmb90) Contact Chris: @cra (https://twitter.com/cra) LinkedIn (https://www.linkedin.com/in/caniszczyk/) More Software Defined Talk Subscribe to Software Defined Interviews Podcast (https://www.softwaredefinedinterviews.com/) Subscribe to Software Defined Talk Podcast (https://www.softwaredefinedtalk.com/) Follow @SoftwareDefTalk on Twitter (https://twitter.com/SoftwareDefTalk) Send your postal address to stickers@softwaredefinedtalk.com (mailto:stickers@softwaredefinedtalk.com) and we will send you free laptop stickers! Join us in Slack (http://www.softwaredefinedtalk.com/slack). Special Guest: Chris Aniszczyk.

Today on the podcast, Wes talks with Mike Milinkovich, Executive Director of the Eclipse Foundation. The Eclipse Foundation was chosen to govern the evolution of Oracle’s Java EE to Jakarta EE. The two discuss the project, the recent news about issues with the javax namespace, the challenges around bundling a Java Runtime with Eclipse, and the path forward for Jakarta EE 9 and beyond. Why listen to this podcast: - Java EE, unlikely Java SE, has always been a multi-vendor ecosystem. It made sense for everyone for Oracle to invite their partners to be involved in the governance of the specification for Java EE for it to continue moving forward. This is the reason for moving Java EE into the Eclipse Foundation as Jakarta EE. - The current plan is for the Eclipse Foundation to get a copyright license to evolve the text of the specification and not a license to the trademarks of Java EE itself. - The javax namespace must remain as is. For it to be evolved, a different namespace must be used. The javax namespace is a trademark of Oracle. Because of this, there are quality controls that Oracle required for its evolution. Ultimately because of those controls, the Eclipse Foundation felt it was better to branch javax into a different namespace and evolve it separately solely under Jakarta EE governance. - Jakarta EE 8 is targeted to be released around Oracle Code ONE. Jakarta EE 8 will be exactly the same as Java EE 8. * The only difference is it will be licensed from Jakarta, not Oracle and only requires membership in the Working Group. - Beyond EE 8, the release cycle, the plan for moving the javax namespace (and keeping compatibility with both the old javax namespace and the new namespace), and new specifications for inclusion into Jakarta EE are still active areas of discussion. - Unrelated to the discussion of Jakarta EE (but discussed in the same board meeting), an attempt to bundle OpenJ9 with the Eclipse IDE failed because of licensing restrictions around a certified Java Runtime. OpenJ9 is certified when acquired through an IBM channel, but not when downloaded directly for us. More on this: Quick scan our curated show notes on InfoQ https://bit.ly/2HSfcfM You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVq Subscribe: www.youtube.com/infoq Like InfoQ on Facebook: bit.ly/2jmlyG8 Follow on Twitter: twitter.com/InfoQ Follow on LinkedIn: www.linkedin.com/company/infoq Check the landing page on InfoQ: https://bit.ly/2HSfcfM

There seems to be a foundation/association for just about everything in our space these days. Are such institutions necessary? Do they wear out their usefulness? I asked that question of Mike Milinkovich, the Executive Director of the Eclipse Foundation. Of course, he defended his group, but his reasoning was quite interesting. Check out this week’s Five Minutes With…discussion.

There seems to be a foundation/association for just about everything in our space these days. Are such institutions necessary? Do they wear out their usefulness? I asked that question of Mike Milinkovich, the Executive Director of the Eclipse Foundation. Of course, he defended his group, but his reasoning was quite interesting. Check out this week’s Five Minutes With…discussion.

The Embedded Insiders briefly review the results of an IoT developer survey from the Eclipse Foundation, which found that two-thirds of engineers are currently or plan to launch an IoT project in the next 18 months (https://iot.eclipse.org/iot-developer-surveys/). Given the pervasiveness of IoT, does that even mean anything anymore?Afterward, the Insiders slide into a discussion of wide-area networks prompted by Alix Paultre's recent engagements with The Things Network. Do recent announcements in 5G have any impact on the advancement of LoRa-based technologies such as those developed by The Things Network, or is there still ample market opportunity? Will Semtech's LoRa monopoly stifle the industry, or help it grow sustainably? Tune in to find out more.

Bradley and Karen discuss and critique the new initiative by the Linux Foundation called CommunityBridge. The podcast includes various analysis that expands upon their blog post about Linux Foundation's CommunityBridge. Show Notes: Segment 0 (00:36) Conservancy helped Free Software Foundation and GNOME Foundation begin fiscal sponsorship work. (07:50) Conservancy has always been very coordinated with Software in the Public Interest, which is a FOSS fiscal sponsor that predates Conservancy. (08:26) Conservancy helped NumFocus get started as a fiscal sponsor by providing advice. (08:53) The above are all 501(c)(3) charities, but there are also 501(c)(6) fiscal sponsors, such as Linux Foundation and Eclipse Foundation. (10:00) Bradley mentioned that projects that are forks can end up in different fiscal sponsors, such as Hudson being in Eclipse Foundation, and Jenkins being associated with a Linux Foundation sub-org. (10:30) Bradley mentioned that any project — be it SourceForge, GitHub, or Community Bridge — that attempts to convince FOSS developers to use proprietary software for their projects is immediately suspect (12:00) Open Collective, a for-profit company seeking to do fiscal sponsorship (but attempting to release their code for it) is likely under the worst “competitive” threat from this initiative. (19:50) Segment 1 (21:23) Projects that use CommunityBridge are required to act in the common business interest of the Linux Foundation members. (27:30) Board of Directors seats at the Linux Foundation are for sale, according to their by-laws. (28:50) Bradley advises that you should not put anything copylefted into CommunityBridge — given Linux Foundation's position on copyleft and citing the ArduPilot/DroneCode example. (29:50) CommunityBridge appears to only allow governance based on the “benevolent dictator for life model” (31:40), at least with regard to who controls the money (34:30) Bradley mentioned the LWN article about Community Bridge. (33:22) Segment 2 (36:54) Karen mentioned that CommunityBridge also purports to address diversity and security issues for FOSS projects. (37:00) Bradley mentioned the code hosted on k.sfconservancy.org and also the Reimbursenator project that PSU students wrote. (42:00) Segment 3 (42:44) Bradley and Karen discuss (or, possibly don't) discuss what's coming up on the next episode. Fact of the matter is that this announcement wasn't written yet when we recorded this episode and we weren't sure if 0x65 would be released before or after that announcement was released. We'll be discussing that topic on 0x66. Send feedback and comments on the cast to . You can keep in touch with Free as in Freedom on our IRC channel, #faif on irc.freenode.net, and by following Conservancy on identi.ca and and Twitter. Free as in Freedom is produced by Dan Lynch of danlynch.org. Theme music written and performed by Mike Tarantino with Charlie Paxson on drums. The content of this audcast, and the accompanying show notes and music are licensed under the Creative Commons Attribution-Share-Alike 4.0 license (CC BY-SA 4.0).

Bradley and Karen discuss and critique the new initiative by the Linux Foundation called CommunityBridge. The podcast includes various analysis that expands upon their blog post about Linux Foundation's CommunityBridge. Show Notes: Segment 0 (00:36) Conservancy helped Free Software Foundation and GNOME Foundation begin fiscal sponsorship work. (07:50) Conservancy has always been very coordinated with Software in the Public Interest, which is a FOSS fiscal sponsor that predates Conservancy. (08:26) Conservancy helped NumFocus get started as a fiscal sponsor by providing advice. (08:53) The above are all 501(c)(3) charities, but there are also 501(c)(6) fiscal sponsors, such as Linux Foundation and Eclipse Foundation. (10:00) Bradley mentioned that projects that are forks can end up in different fiscal sponsors, such as Hudson being in Eclipse Foundation, and Jenkins being associated with a Linux Foundation sub-org. (10:30) Bradley mentioned that any project — be it SourceForge, GitHub, or Community Bridge — that attempts to convince FOSS developers to use proprietary software for their projects is immediately suspect (12:00) Open Collective, a for-profit company seeking to do fiscal sponsorship (but attempting to release their code for it) is likely under the worst “competitive” threat from this initiative. (19:50) Segment 1 (21:23) Projects that use CommunityBridge are required to act in the common business interest of the Linux Foundation members. (27:30) Board of Directors seats at the Linux Foundation are for sale, according to their by-laws. (28:50) Bradley advises that you should not put anything copylefted into CommunityBridge — given Linux Foundation's position on copyleft and citing the ArduPilot/DroneCode example. (29:50) CommunityBridge appears to only allow governance based on the “benevolent dictator for life model” (31:40), at least with regard to who controls the money (34:30) Bradley mentioned the LWN article about Community Bridge. (33:22) Segment 2 (36:54) Karen mentioned that CommunityBridge also purports to address diversity and security issues for FOSS projects. (37:00) Bradley mentioned the code hosted on k.sfconservancy.org and also the Reimbursenator project that PSU students wrote. (42:00) Segment 3 (42:44) Bradley and Karen discuss (or, possibly don't) discuss what's coming up on the next episode. Fact of the matter is that this announcement wasn't written yet when we recorded this episode and we weren't sure if 0x65 would be released before or after that announcement was released. We'll be discussing that topic on 0x66. Send feedback and comments on the cast to . You can keep in touch with Free as in Freedom on our IRC channel, #faif on irc.freenode.net, and by following Conservancy on on Twitter and and FaiF on Twitter. Free as in Freedom is produced by Dan Lynch of danlynch.org. Theme music written and performed by Mike Tarantino with Charlie Paxson on drums. The content of this audcast, and the accompanying show notes and music are licensed under the Creative Commons Attribution-Share-Alike 4.0 license (CC BY-SA 4.0).

Episode 43. JCP: Hold my (white) Wine. The JCP welcomes the competition of Eclipse Foundation on spec creation + A recap on Reactive. Ah, DevNexus 2019! One of the better conferences to attend in the U.S. We ended up running our yearly offheap show in...

Episode 43. JCP: Hold my (white) Wine. The JCP welcomes the competition of Eclipse Foundation on spec creation + A recap on Reactive. Ah, DevNexus 2019! One of the better conferences to attend in the U.S. We ended up running our yearly offheap show in there with special guests Heather VanCura, and Ben Hale! We went through the deep questions on the role of JCP (now that Eclipse Foundation Spec Process is in town), and Heather replied that the JCP is agile, knows what they've been doing for a while, and that is still THE Source for Java Spec creation! Indeed, these are intertesting times! We also dove deeply on the current state of Reactive (and what Pivotal is doing to make it easier for everyone to embrace it). We got to hear about R2DBC, when to go Reactive, and what is a good criteria for adoption (hint: Don't go and rewrite your large app in reactive just because). To top it off, we ended up with a "Who wants to be a millionaire quiz" where we pitted our guests against our (somewhat tricky) quiz questions. All for the privilege of winning an OffHeap Mug!. In all, a great episode, with tons of information and interesting guests! We thank DataDogHQ for sponsoring this podcast episode We also thank OverOps for sponsoring this podcast episode   DO follow us on twitter @offheap Heather VanCura (JCP Chair) Ben Hale (Cloud Foundry Java Lead, Pivotal) Redis Labs gets a new License Age Discrimination only for employees SAP Machine Java Distribution

An interview with Eclipse Foundation's Mike Milinkovich

Episode 42. Move over JCP! There's a new Specs Maintaining Organization in town with Eclipse Foundation Spec Process. Oh goody, this episode is special in many ways! First, I got to travel to Chicago, and meet in-person with our usual suspects. We went to the bar where everything started, and we recorded our 42th episode in-person! (very Douglas Adams). But aside from the reminiscing, we actually got the Executive Director of The Eclipse Foundation to go on the record on what's happening with Eclipse Foundation and Jakarta EE! We went into what does it mean to have the Eclipse Foundation Spec Process (and how is that affect the JCP), and dove into maintainers, and the future of Jakarta EE (Glassfish is released!). All in all, an incredible episode, with "you-heard-it-here-first" content. Go ahead an play. Also, a big shoutout to Dr. Heinz Kabutz who plugged our podcast in his newsletter. If you haven't subscribed to it, you definitively should! His Java newsletter is unparalleled and is always full of excelent topics and Java tips/trick. A must for every Java developer. We thank DataDogHQ for sponsoring this podcast episode   DO follow us on twitter @offheap Red Hat Launches CodeReady Workspaces Kubernetes IDE Corretto 11 is out! Java SE 8 End of Public Updates Microprofile Starter Launched Splunk stop selling its product in Russia Micronaut 1.1 Milestone 1 Released Jakarta EE Working Group Jakarta EE Github

In dieser Episode geht es wieder weg von den Apple Themen der letzten Zeit hin zu Developer Themen und DevOps. Tom erzählt über seine Erfahrungen mit Security Issues und seiner Evaluierung von Google Cloud. Danach geht es weiter mit ein paar Facts zur neuen Spring Boot 2.1.0 Version die vorige Woche released wurde. Zu guter Letzt erzählt André von Eclipse Che, einem interessanten Projekt der Eclipse Foundation das eine Cloud IDE auf Basis von Docker als Ziel hat.

A conversation with Elder Moraes (@elderjava) about Java EE at JavaONE, why Java EE at all, enjoying boring stuff, Java EE for pet projects, thinking freely about business problems, no distractions, servlets and JSPs, Java as career choice, Jakarta EE opinions, Oracle's Java EE stewardship, Java EE 8 being late, Jakarta EE should remain boring, Jakarta EE and profiles, an idea for a Jakarta EE profile creation process, Eclipse Foundation and agility, the pace of MicroProfile, thoughts on Cloud Native, Java EE in Cloud Native environments, Sebastian Daschner and successful Java EE careers, Java EE impact on startups, ES 6, TypeScript, thoughts on serverless, future of Jakarta EE, JVM overhead and microservices, GraalVM and Nashorn, JavaONE vs Oracle Code, Java EE 8 recipes in the Java EE 8 Cookbook. Checkout: eldermoraes.com, Elder Moraes and @elderjava.

A conversation with Mike Milinkovich @mmilinkov, about Cobol, APL, Smalltalk, Visual Age for Java, WebGain, TopLink, "The Object People". Canadians run the Java World, Eclipse, plugins and OSGi, pragmatic modularization, the First Executive Eclipse Director, Mark's Cavage role in opensourcing Java EE ee4j name confusion, the Jakarta EE brand and logo, the migration from Java EE to Jakarta EE, why it is not possible to rename ee4j to Jakarta EE, working 50% on Jakarta EE, working with Oracle lawyers, why not all JSR specs can not be contributed by Oracle, dealing with old specifications, how to contribute to Jakarta EE project, how to become a Jakarta EE committer, the difference between Eclipse Foundation agreements and other foundations, becoming an Eclipse member, becoming a member steering committee, hacking the Jakarta EE process by becoming a member without paying money, the Jakarta EE release cadence, different cadences between ee4j and Jakarta EE, who decides what at Jakarta EE / Eclipse, specs become opensource projects, committer based merocratacy, how to start a new Jakarta EE subproject, Jakarta EE is "code first", Microsoft joins Jakarta EE, the dangers of profiles, no politics, the specification Jakarta EE committee decides about profiles.

Oh my, there are so much news going on. Starting with a weird string concat bug in Java 9 and 10. We also see that Serializable is going to be removed (and hopefully there is an alternative for it), and we also dive into the ethics of Google as it turns down military contracts they are uncomfortable with. We also see Mission Control being open sourced and explore what that means (an opportunity for growth or a death knell for the product?). Lastly we dive into a bit of a news where Oracle will retain the description of the EE specs and not transfer it to the Eclipse Foundation. What does that mean for Jakarta? All this and more in the full-to-the-brim episode!   We thank DataDogHQ for sponsoring this podcast episode   DO follow us on twitter @offheap Java 9 Bug Github is aquired by Microsoft Google not renewing military contract Java Mission Control Open Sourced EE Spec Docs discussion

Lightbend CEO Mark Brewer discusses what joining the Eclipse Foundation as a founding member of the Jakarta EE Working Group means for bringing Reactive closer to the traditional Java enterprise landscape.

What an eventful time for being a Softare developer. We got a Meltdown, and a Spectre in our field to begin with, and we also have some interesting news brewing from Payara. But most importantly we secured an interview with no other than Eclipse Foundation's own Executive Director Mike Milinkovich! He takes us into an inner tour of what's going on with JavaEE (and the handoff between Oracle and the Eclipse Foundation). We talked on all topics EE, including namespaces, future names, clarifications on what is being open sourced and the relevancy of the JCP in today's climate. In all, even if you think you don't use Java EE (hint...you are probably using specs that are surviving under the EE umbrella...Json much?) you should take a listen!   DO follow us on twitter @offheap EE4J: Current Status and What's Next Meltdown

In this episode we explore the new brand selection for the Java EE Platform now that the umbrella specification is moving from Oracle Corporation to the Eclipse Foundation

After the JavaOne 2017 conference and Oracle's announcement to move the umbrella specification, tools compatibility kit and the verification and trade marks to the Eclipse Foundation, we look at the concerns, the advantages and disadvantages to the community of engineers worldwide. We also consider the implications to business. Retro edited in December 2017

Oh my gosh! When it rain it pours. We have tons of news for this podcast, starting with the actual release of Java 9 (wow, it is finally OUT!). And on the toes of that we have the news that Java EE is going to be moving to the Eclipse Foundation (and...

Oh my gosh! When it rain it pours. We have tons of news for this podcast, starting with the actual release of Java 9 (wow, it is finally OUT!). And on the toes of that we have the news that Java EE is going to be moving to the Eclipse Foundation (and outside the JCP)! Lastly we dive into the big Equifax vulnerability (and see what was the vulnerability about). In all, an exciting episode on which we make predictions to the uncharted territory Java is heading towards!   DO follow us on twitter @offheap MicroProfile 1.2 is out Oracle to keep control of the Java name Struts/Equifax breach Analysis of the Equifax Vulnerability

The DevOps kids have decided to come up with a new term “observability.” We get to the bottom of the WTF barrel on what that is - it sounds like a good word-project. Also, there’s a spate of kubernetes news, as always, and some interesting acquisitions. Plus, a micro-iOS 11 review. Meta, follow-up, etc. Patreon (https://www.patreon.com/sdt) - like anyone who starts these things, I have no idea WTF it is, if it’s a good idea, or if I should be ashamed. Need some product/market fit. Check out the Software Defined Talk Members Only White-Paper Exiguous podcast over there. Join us all in the SDT Slack (http://www.softwaredefinedtalk.com/slack). Is “observability” just “instrumentation”? Write-up (https://medium.com/@copyconstruct/monitoring-and-observability-8417d1952e1c) from Cindy Sridharan. This guy (https://medium.com/@steve.mushero/observability-vs-monitoring-is-it-about-active-vs-passive-or-dev-vs-ops-14b24ddf182f): “Thinking directionally, Monitoring is the passive collection of Metrics, logs, etc. about a system, while Observability is the active dissemination of information from the system. Looking at it another way, from the external ‘supervisor’ perspective, I monitor you, but you make yourself Observable.” So, yes: if developers actually make their code monitorable and manageable…easy street! It’s a good detailing of that important part of DevOps. Cloud Native Java (http://amzn.to/2jPJHcv) has a good example with the default “observability” attributes for apps, and then an overview of Zipkin tracing. Weekly k8s News Heptio gets funding (https://www.geekwire.com/2017/heptio-raises-25m-series-b-funding-round-kubernetes-takes-world/), now “has raised $33.5 million in funding to date.” I think we’ll cover this press release in a WP episode. Also, something called “StackPointCloud” now with the Istio (https://thenewstack.io/stackpointcloud-drops-istio-service-mesh-integration/). Mesosphere adding K8s support (https://techcrunch.com/2017/09/06/mesosphere-says-its-not-bowing-to-kubernetes/) - “Guagenti also noted that he believes that Mesosphere is currently a leader in the container space, both in terms of the number of containers its users run in production and in terms of revenue (though the company sadly didn’t share any numbers).” "I think it’s fair to call Kubernetes the de facto standard for how enterprises will do container orchestration,” Derrick Harris (http://news.architecht.io/issues/with-oracle-on-board-kubernetes-has-to-be-the-de-facto-standard-for-container-orchestration-73880). Is Kubernetes Repeating OpenStack’s Mistakes? (https://www.mirantis.com/blog/is-kubernetes-repeating-openstacks-mistakes/) - Boris throwing bombs Meanwhile, an abstract of a containers penetration study (https://redmonk.com/fryan/2017/09/10/cloud-native-technologies-in-the-fortune-100/), from RedMonk: "Docker, is running at 71% across Fortune 100 companies. Kubernetes usage is running in some form at 54%, and Cloud Foundry usage is at 50%” This update from the Cloud Foundry Foundation (https://www.cloudfoundry.org/update-containers-2017-research-shows/) is a little more, er, “responsible” in pointing out flaws. Instead it just says there’s lots of growth and tire-kicking: 2016/2017 y/y shows those evaluating containers went up from 31% to 42%, while “using” ticked up a tad from 22% to 25%, n=540. Oracle’s in the CNCF (https://techcrunch.com/2017/09/13/oracle-joins-the-cloud-native-computing-foundation-as-a-platinum-member/) club! K8s on Oracle Linux, K8s for Oracle Public Cloud. “At this point, there really can’t be any doubt that Kubernetes is winning the container orchestration wars, given that virtually every major player is now backing the project, both financially and with code contributions.” James checks in on Red Hat (http://redmonk.com/jgovernor/2017/09/21/red-hat-is-pretty-good-at-being-red-hat/). (https://techcrunch.com/2017/09/13/oracle-joins-the-cloud-native-computing-foundation-as-a-platinum-member/) Acquisitions & more! Rackspace acquires Datapipe (https://techcrunch.com/2017/09/11/rackspace-acquires-datapipe-as-it-looks-to-expand-its-managed-cloud-business/) “The reason we’re buying them is that we want to extend our leadership in multi-cloud services,” Rackspace chief strategy officer Matt Bradley told me. “It’s a sign and signal that we’re going for it.” Bradley expects that the combined company will make Rackspace the largest private cloud player and the largest managed hosting service. Datadog acquires Logmatic.io to add log management to its cloud monitoring platform (https://techcrunch.com/2017/09/07/datadog-acquires-logmatic-io-to-add-log-management-to-its-cloud-monitoring-platform/) Puppet Acquires Distelli (https://www.geekwire.com/2017/puppet-acquires-distelli-bolster-cloud-computing-automation-platform/), known for their Kubernetes dashboard. Jay Lyman at 451 (https://451research.com/report-short?entityId=93381). Sizing Puppet: “The company has grown to more than 500 employees, and has estimated annual revenue in the $100m range.” Coverage from Susan Hall: “What we haven’t had up to this point is all the requisite automation for moving infrastructure code and application code through any kind of automated delivery lifecycle” and now they gots that. https://thenewstack.io/puppet-will-extend-infrastructure-automation-capabilities-distelli-acquisition/ “In May, the company launched its Kubernetes dashboard K8S. It allows users to connect repositories, build images from source, then deploy them to that Kubernetes cluster. You can also set up automated pipelines to push images from one cluster to another, promote software from test/dev to prod, quickly roll back and do all this in the context of one or more Kubernetes clusters… The Kubernetes service is offered as a hosted service or in an on-prem version. It provides notifications through Slack.” Google pays $1.1 billion for HTC team and non-exclusive IP license (https://www.axios.com/login-2487682498.html?rebelltitem=2&utm_medium=linkshare&utm_campaign=organic#rebelltitem2) Security Corner The Apple Effect? — Why BMW might get rid of car keys (http://www.autonews.com/article/20170915/OEM06/170919789/why-bmw-might-get-rid-of-car-keys) Don’t blame Apache — EQUIFAX OFFICIALLY HAS NO EXCUSE (https://www.wired.com/story/equifax-breach-no-excuse/) Is there anything to do here? Setup layers of credit cards? Require Touch ID (etc.) approval of all financial decisions and transactions in your “account”? Food & Safety like inspectors for security? Hackers respond to Face ID on the iPhone X (http://bgr.com/2017/09/21/iphone-x-release-date-soon-hackers-eye-face-id/) iOS 11 Coté has been running the beta. It seems fine. There’s the usual Re-arrangement of how some gestures work that’s jarring at first, but after using it for awhile, you forget what they even are. The extra control center stuff is nice. The Files.app is interesting, but not too featureful. The new photo formats are annoying because, you know, non-Apple things need to support it (which they seem to?) Bonus Links Coté gives up on defining DevOps, and more Interview about DevOpsDays Auckland (https://www.infoq.com/news/2017/09/michael-cote-devops-days-nz). (https://techcrunch.com/2017/09/13/oracle-joins-the-cloud-native-computing-foundation-as-a-platinum-member/) Is Solaris dead yet? Strongly confirmed rumors that Oracle is shutting it down (http://www.zdnet.com/article/sun-set-oracle-closes-down-last-sun-product-lines/). This guy has written a big Solaris-brain to Linux-brain manifesto/guide (http://www.brendangregg.com/blog/2017-09-05/solaris-to-linux-2017.html), plus: “[n]owadays, Sun is a cobweb-covered sign at the Facebook Menlo Park campus, kept as a warning to the next generation.” SICK BURN! Layoffs and more (http://dtrace.org/blogs/bmc/2017/09/04/the-sudden-death-and-eternal-life-of-solaris/): “In particular, that employees who had given their careers to the company were told of their termination via a pre-recorded call — “robo-RIF’d” in the words of one employee — is both despicable and cowardly.” HPE We Can See The New Hewlett Clearly Now, Says CEO Whitman (http://blogs.barrons.com/techtraderdaily/2017/09/05/hpe-we-can-see-the-new-hewlett-clearly-now-says-ceo-whitman/?mod=BOLBlog) - AI in storage arrays, Docker in OneView. Clearly (http://www.marketwatch.com/story/hp-enterprise-has-yet-another-confusing-plan-to-simplify-itself-2017-09-05)? Making money (https://www.cnbc.com/2017/09/05/hpe-earnings-q3-2017.html). They bought CTP!? (https://www.cloudtp.com/doppler/hewlett-packard-enterprise-to-acquire-cloud-technology-partners/) Selling hardware to cloud providers is rough (https://www.nextplatform.com/2017/09/06/prospects-leaner-meaner-hpe/). Huawei New board (http://talkincloud.com/cloud-services/chinas-huawei-braces-board-revamp-western-markets-beckon). Microsoft app support. We can all agree on food Someone has to pay attention to this real world stuff (http://www.nationalgeographic.com/magazine/2017/09/holland-agriculture-sustainable-farming/). This Tiny Country Feeds the World More on VMware/AWS The possible failures in the partnership (https://www.bloomberg.com/news/articles/2017-09-01/how-vmware-s-partnership-with-amazon-could-end-up-backfiring) - sort of an odd article in that the larger point is “maybe it won’t work.” Meanwhile, Matt Asay does some loopty-loops on it all (https://www.theregister.co.uk/2017/09/11/kubernetes_envy/). JEE Code put in github (http://go.theregister.com/feed/www.theregister.co.uk/2017/09/06/oracle_java_ee_java_se_github/). They’re giving it over to the Eclipse Foundation (https://blogs.oracle.com/theaquarium/opening-up-ee-update). Probably a good idea. VMware’s OpenStack Little report form 451 (https://451research.com/report-short?entityId=93303&type=mis&alertid=693&contactid=0033200001wgKCKAA2&utm_source=sendgrid&utm_medium=email&utm_campaign=market-insight&utm_content=newsletter&utm_term=93303-VMware+sheds+free+version+of+its+OpenStack+distribution). “Going forward, users pay a onetime $995-per-CPU socket license fee, in addition to ongoing support.” Recommendations Brandon: Prophets of Rage (http://prophetsofrage.com/). Matt: American Gods (https://en.wikipedia.org/wiki/American_Gods_(TV_series)), the TV show. Zero History (https://www.amazon.com/Zero-History-Blue-William-Gibson-ebook/dp/B003YL4AGC/): finale(?) to William Gibson’s Blue Ant trilogy LOT (https://www.lot2046.com/): a subscription-based service which distributes a basic set of clothing, footwear, essential self-care products, accessories, and media content. Engineering the End of Fashion (https://www.ssense.com/en-gb/editorial/fashion/engineering-the-end-of-fashion) Coté: Rick & Morty (http://amzn.to/2xrHo3L). These cultural guides (http://www.commisceo-global.com/country-guides) are fucking awesome! See America (http://www.commisceo-global.com/country-guides/usa-guide), Australia (http://www.commisceo-global.com/country-guides/australia-guide), and Latvia (http://www.commisceo-global.com/country-guides/latvia-guide) (no one sang at the meals I was at!). Cardenal Mendoza (https://www.thewhiskyexchange.com/p/996/cardenal-mendoza-brandy-solera-gran-reserva), brandy de jerez (https://en.wikipedia.org/wiki/Brandy_de_Jerez). And, you know, cognac/brandy in general - be a fucking adult already, you damn kids.

Severe security vulnerability found in Apache Struts using lgtm.com (CVE-2017-9805) XML? Be cautious! The Backdoor Threat Java News Moving Java Forward - 6 month release cycle, breaking changes.  3 yearly LTS versions Java 9 will NOT be an LTS release Module Hell - java.ee not in base ( easy to fix, but ack ) O'Reily Java 9 Modularity published Use Stream API simpler ( or don't use it at all ) Kevlin Henny JavaZone talk/video: Paradigms Lost, Paradigms Regained: Programming with Objects and Functions and More Jitwatch Project Home IntelliJ Plugin Video demo of Jitwatch/IntelliJ Plugin at the JVM Language Summit Using GraphQL? Why Facebook Now Owns You Java EE moves to the Eclipse Foundation  

In today’s episode we talk with Chris Aniszczyk. Chris is the COO of the Cloud Native Computing Foundation, aka the CNCF. We spoke with Chris on site at DockerCon 2017 in Austin, TX earlier this year about the CNCF Master Program. CNCF is part of the Linux Foundation, of which he is a VP, and a home to many projects, including Kubernetes. Kubernetes is one of the fastest growing open source projects. We had a very interesting talk with Chris on how the ambassador programs of both the CNCF and Linux mirror other types of open source contributions, where participants themselves often have day jobs and work with commercial products based on open source projects. Chris also shares with us about open source culture and his extremely impressive involvement with CNCF, Linux and Twitter. The ambassador program at CNCF seeks to cultivate a worldwide community of people interested in spreading the notion of Cloud Native Computing. About our guest Chris Aniszczyk is an engineer by trade with a passion for open source and building communities. At Twitter, he created their open source program and led their open source efforts. For many years he served on the Eclipse Foundation’s Board of Directors representing the committer community and the Java Community Process Executive Committee. In a previous life, he bootstrapped a consulting company, made many mistakes, lead and hacked on many eclipse.org and Linux related projects. He is now the COO of the Cloud Native Computing Foundation and VP of Developer Programs at The Linux Foundation. Mentioned In This Episode John’s Twitter: @JTroyer Kathleen’s Twitter: @DailyKat To Join the IMC or for more information: info@influencemarketingcouncil.com DockerCon Cloud Native Computing Foundation CNCF Ambassadors Chris Aniszczyk’s Twitter — @CRA The Linux Foundation MeetUp Lanyrd.com Kubernetes The Apache Foundation   The Influence Marketing Podcast, a podcast brought to you by the Influence Marketing Council, an industry council for B2B brands who innovate in influencer, advocacy, and community marketing. Your hosts, John Mark Troyer and Kathleen Nelson Troyer, are co-founders of the IMC. The Influence Marketing Podcast is part of the research program of the IMC. For more information, go to influencemarketingcouncil.com.

In dieser Episode spricht Till Schulte-Coerne mit Stefan Bodewig über die Apache Software Foundation (ASF), eine Organisation zur Förderung von Open Source-Software, in der sich Entwickler vorwiegend ehrenamtlich betätigen. Stefan ist seit vielen Jahren Mitglied der ASF. Er berichtet über ihre Strukturen, die Unterschiede zu anderen Organisationen wie der Eclipse Foundation, die Arbeit in den einzelnen Apache-Projekten und von seinem Alltag als Committer und Vice President.

In this episode Scott discusses Eclipse, Open Source and both the history and future of software with Bjorn Freeman-Benson. Bjorn is the Technical Director for Open Source Process and Infrastructure for the Eclipse Foundation.

Ward and I talk about his new position as the Director of Committer Community Development at Eclipse.  He discusses the release of Callisto by the Eclipse foundation, it’s Agile roots and other fun tool related topics.-bob