15:58:12 From Erin RobotZwrrl to Everyone:
	Hello! 🙂
	
16:07:15 From Tom to Everyone:
	Jeff's talk on QP mentioned he tended to use more active objects than he would traditional tasks. Is there any stack optimization inherent in AO's or sizing techniques to keep those stacks as small as necessary?
	
16:07:25 From Eric Habets to Everyone:
	@Erin RobotZwrrl OT: Do these robot butterflies in the background really fly?
	
16:07:31 From Quantum Leaps to Everyone:
	QP-nano framework supports 8-bit AVR
	
16:09:18 From Quantum Leaps to Everyone:
	The native real-time kernels in QP (non-preemptive QV and preemptive QK) use only a single stack for all Active Objects. That's why the RAM use tends to be low, even when many AOs are used.
	
16:09:40 From ts to Everyone:
	I heard FreeRTOS, Zephyr, Nuttx, … Does anyone still use a commercial RTOS? I’m aware of Jacob’s work for some stats, although that changes really fast.
	
16:09:45 From Viktor to Everyone:
	Hello! Tank you for great talks!
	Question for Erin : in the demo you used FreeRTOS to build the Butterfly Robot. What was your criteria for choosing RTOS? Did you try other options (Zephyr, NuttX, others)?
	
16:09:52 From Erin RobotZwrrl to Everyone:
	Replying to "@Erin RobotZwrrl OT: Do these robot butterflies in...":
	Thanks for the question! They can “fly” on the second half of a parabolic trajectory. However, I would not recommend that 😄  The IMU is a MPU6050, so it can measure the free fall and force of impact
	
16:10:22 From Tom to Everyone:
	@Jacob Beningo Miro addressed my question in chat.
	
16:12:23 From Germán Castro to Everyone:
	Hi Miro @Quantum Leaps , could you see Jeff's presentation? I would like to ask about it and I'm sure you can answer
	
16:12:54 From Quantum Leaps to Everyone:
	Thanks for interest in QP. Yes, I watched Jeff'
	
16:12:59 From Rumman to Everyone:
	I'm interested in adopting Zephyr for my projects, but I've found that the framework's heavy reliance on C macros is problematic due to the inherent issues with macro-based development such as debugging challenges, limited IDE support, and potential maintenance problems. Could you share any recommendations for working effectively with this aspect of Zephyr, or discuss if there are any ongoing initiatives within the project to transition toward more modern approaches that rely less on preprocessor macros?
	
16:14:01 From Quantum Leaps to Everyone:
	I watched Jeff's presentation and liked it a lot. Some more details are in my comment that I posted online.
	
16:18:55 From Viktor to Everyone:
	Contiki was quite popular RTOS in past. But now it seems to be dead. Why an Open Source OS can suddenly die? And how can we prevent current RTOSs from dying?
	
16:18:59 From Kate Stewart to Everyone:
	Replying to "I'm interested in adopting Zephyr for my projects,...":
	There are some good tutorials on working with the Macros effectively in the community - in particular Marti’s talk from 2022 is popular for helping understand how to be effective.  https://www.youtube.com/watch?v=w8GgP3h0M8M
	
16:19:24 From SteveM to Everyone:
	Replying to "QP-nano framework supports 8-bit AVR":
	Thank you, I didn't realize that existed. I will look into it.
	
16:21:27 From Rumman to Everyone:
	Replying to "I'm interested in adopting Zephyr for my projects,...":
	Thank you :)
	
16:25:26 From Quantum Leaps to Everyone:
	Replying to "QP-nano framework supports 8-bit AVR":
	https://github.com/QuantumLeaps/qpn
	
16:27:44 From Robert Hancock to Everyone:
	Some of the other RTOSses out there are controlled by a single company which tends to discourage contributors as people feel like they're just donating their work to that company (who might be a competitor).
	
16:29:08 From Germán Castro to Everyone:
	Miro, as a follow-up, I was surprised that Jeff didn't even mention orthogonal component pattern when talking about device drivers. Would you say that is because it is not the best option to develop them?
	
16:30:21 From John.Singleton to Everyone:
	Are any of the major industries that make the news doing the most to support/interact with Zephyr on safety, etc.?
	
16:31:20 From Otzen to Everyone:
	Maybe a little off topic. I have almost only worked with baremetal systems for the last 10-15 years, so my knowledge is a bit outdated on RTOS'es. But many years back I worked with eCos ( I was a eCosmunaut 😉), eCos was also very unix inspiret. 
	With a map with freeRtos, Zephyr and Linux on it, if anyone can remember eCos, where would you place eCos on that map?
	
16:31:43 From Quantum Leaps to Everyone:
	Replying to "Miro, as a follow-up, I was surprised that Jeff di...":
	Jeff had to carefully choose the features to cover.
	
16:32:27 From Quantum Leaps to Everyone:
	Now we also have a huge copyright-infringement machine called... AI
	
16:32:55 From Robert Hancock to Everyone:
	Replying to "Some of the other RTOSses out there are controlled...":
	As Kate mentioned, retaining copyright is also helpful. At the very least avoids extra paperwork for getting your company to sign off assigning copyright to another company.
	
16:34:42 From Germán Castro to Everyone:
	Replying to "Miro, as a follow-up, I was surprised that Jeff di...":
	Makes sense. I believe he chose the most relevant or suitable for developing device drivers
	
16:36:05 From John.Singleton to Everyone:
	That's good. Thank you, Kate!
	
16:37:14 From Rumman to Everyone:
	This week is 10 years since Rust 1.0 so I figured I should ask a Rust question. What do you think about the state of RTOS in the Rust world?
	
16:37:26 From Otzen to Everyone:
	Grat answer thanks
	
16:37:44 From Edwin Estep to Everyone:
	🦀🦀🦀
	
16:41:59 From John.Singleton to Everyone:
	Beginner RTOS question: I noticed that, by default, the RTOS embOS uses static memory allocation by default, whereas FreeRTOS uses dynamic memory allocation by default. Why the difference? Is it about targeting resource-constrained environments?
	
16:44:46 From Quantum Leaps to Everyone:
	Replying to "Beginner RTOS question: I noticed that, by default...":
	Dynamic memory might be unsafe. Therefore most functional safety standards highly recommend to use static memory only. FreeRTOS started with heap-1, heap-2, and heap-3 memory allocation policies, but then added static option.
	
16:47:24 From Quantum Leaps to Everyone:
	Replying to "Beginner RTOS question: I noticed that, by default...":
	Please check out: https://www.state-machine.com/heap-of-problems
	
16:48:26 From John.Singleton to Everyone:
	Ah! Thank you taking the time to answer this!
	
16:48:43 From Keith J to Everyone:
	Thanks everyone!
	
16:49:02 From John.Singleton to Everyone:
	Thank you!
	
16:49:14 From Raul Pando to Everyone:
	It's being great. Thank you all!
	
16:49:37 From Immanuel to Everyone:
	Thank you. Interisting insights
	
16:49:50 From ts to Everyone:
	Thank you so much! Great Panel discussions.
	
16:49:53 From Rumman to Everyone:
	Thank you
	
16:49:55 From Edwin Estep to Everyone:
	Thanks!
	
16:49:58 From Viktor to Everyone:
	Thank you!