That's been addressed, but wasn't easy and still isn't perfect. The results would only show up at the termination of the loop, when the system could breathe again. This could happen if you printed output in a tight loop. A prime feature being that the GUI console, but not the CLI console, didn't show output if the UI couldn't process events. For example, most people use the console (the REPL), so the fixes and improvements there are easy to see. Some of these are small, but important, others are headline-worthy some are deep voodoo and some visible to every Reducer (what we call Red users). Since our last blog post we've logged over 400 fixes and 100 features into Red itself. It's really exciting, and we'll talk more about that in a future blog post. One thing we can say right now is that the work on DiaGrammar led to a huge amount of work on a more general diagramming subsystem for Red. We'll probably announce what it will be in Q4. The first time you do something is the hardest, and we're excited to improve and learn more as we update DiaGrammar and work on our next product. We don't think about outreach, marketing, payments, support, upgrade processes for users, web site issues, announcements, and more.
As technologists, we're used to writing the code and maybe writing some docs to go with it. An important lesson is that the product itself is only half the work. We learned a lot from the process of creating a product, and will apply that experience moving forward. Truly, there is nothing else like it on the market. We are a team, but he really accepted ownership of the project and took it from an idea to a great product. Our thanks to Toomasv for his ingenuity and dedication in creating DiaGrammar. Our first product, DiaGrammar for Windows, was released in December 2020, and we've issued a number of updates to it since then. The commercial goal, starting out, is to focus on our core strengths and knowledge, building developer-centric tools. There's no need to comment on the exceptions to these cases, because they are exceptions. This is necessary for sustainability, because people don't pay for programming languages, and they don't pay for Open Source software. We had some team changes, and also split our focus into product development alongside core Red Language development. We were already a remote-only team, but the effect the pandemic had on the world, particularly travel, hit us too. Last year was a tough year all around, even for us. We know it's important, even if we have many other channels where people can get information. It's one of those things that falls off our radar without a person dedicated to it, and we run lean so don't have anyone filling that role right now. It's been almost a year since our last blog post.
0 kommentar(er)
