This is good general advice. If your software needs a "tour," that's a good indicator you should work on your UX instead. If you're just excited to tell the user about a new feature, they'll discover it when they need it.
Odin is not like JS or something where you'd need a VM or transpilation process to target an embedded system. It's just C with nicer syntax and modern data structures, there's no "squeezing" required. You just compile for the target you want to run on.
I don't believe Xtensa (ESP32) is supported yet, but people have been asking for it, so it may happen at some point. ARM is well supported now though, obviously.
I've been using Odin for about 6 months now, and to be honest, it's hard to find fault with it. I've used it for STM32 microcontroller firmware, web and desktop applications, and all are performant and compile quickly.
My one issue is (and I'm fully aware it will never happen) I do wish there was some sort of first-class solution to inheritance. I've grown to love procedural programming, but some problems really are just better solved with a more OOP approach. Just because classes exist does not mean they need to be used.
But as far as a language to "get stuff done" with as few tradeoffs as possible, Odin is about as good as I can imagine a language being.
And therein lies the rub. Unreal 5 is massive and complex, and there comes a point where it takes longer to understand how to layer on your own customizations than just to start from scratch. Especially for indie developers.
I wanted to make a little editor utility (the UE editor is built in UE) that changed the way viewport selection was handled. I think I got to 5 layers of abstraction before I gave up. 5 layers, for a left-click object select.
Can I ask a dumb question to those smarter than I: Is this way of visualizing temperature/pressure accurate, or is it an abstraction for convenience in the same way that depicting electrons "flowing through wires" is?
The key difference is the founder built a product in search of a problem to solve, rather than the other way around.
The "secret" is just to talk to people in the field they're trying to "revolutionize," and ideally observe them work. Often, people become blind to workflow problems and workarounds become normal process. They never even consider to look for a better way to do something. Those are the opportunities for founders to solve.
But what I've seen a lot is founders just arbitrarily coming up with an idea that sounds cool on paper, raising money, and only realizing too late that there is zero actual market fit.
When I was younger, I was always paranoid when I reached out to somebody and didn't hear back. Now that I'm older and busier, I totally get it. Clearly state who you are, what you want, and what your timeline is. It's far easier to reply to a message like that, than to parse paragraphs of fluffery looking for an ask.
I will say--as someone who has fielded late night troubleshooting calls--I totally understand OP's point of view. It's reasonable to expect that you will be able to answer questions about something that you ship, or brainstorm ways to solve a problem a customer is encountering while using something you provided them.
The obvious counterargument is "well, just ask the AI for those answers," but the AI lacks the context and experience that you have. Sometimes, genuinely, the user really is just "holding it wrong," but none of the current AI models would ever admit that, and you'd spend hours trying to solve an unsolvable problem.
Additionally, without the knowledge of how you got from A to B, you don't know what else is possible (or impossible.) In the process of doing something manually, you may stumble across a particular setting or effect that creates something you never even considered. And now, that is knowledge you can use on the next project.
I was going to say, I don't understand what this does that Revit doesn't already do better. I guess it's a fun demo, but I doubt this was a problem that needed solving.
Absolutely. One of the major purposes of art is as a way to communicate things that can not be put into words. And if that's the case, how could one ever hope to create it with a prompt?
The comment wasn't about CC specifically. If you rely (like, can't ship without it) on any model that you don't control, it's not really your product. If Dario decides to increase pricing 500% because it's Tuesday, and you can't work without CC, you really have no choice but to open your wallet.