As I relayed in an earlier post about the soon availability of Axum, well, today is the day. I noted before that Microsoft has still not decided whether to release this as a real project, and needs feedback from users like yourself. On the Axum site there is a great video on how to build your first Axum application. Over time, I hope to add a few to the picture myself as actor model concurrency to me is highly interesting for many problems in today’s environment. You can read more of the announcement at the Axum Team Blog.
Josh Phillips, the PM of the Axum team has asked for pointed feedback for this release. These include:
- Learning curve: How complex do you find it to do simple things in Axum? Do you think the value it provides is worth the investment in learning and understanding the language?
- Form: Do you think that Axum is better off as a language or would you be just as happy with a library-based solution?
- Interop: How hard was it to consume objects that were created in other .NET languages? Was it easy to place isolation guarantees on these objects? If not, how would you change the process?
- Async pattern: What do you think of asynchronous methods? Do they make the APM pattern easier?
- Legacy: What issues are there with porting legacy applications? Any blockers or things we could do to make it easier?
- Platform fit: How does Axum fit in with the rest of .NET? For graphical applications, did you face any challenges with the UI?
- Scalability: Were you able to easily write applications that scale from cores to the cluster to the cloud? Is the unified model all it’s cracked up to be?
- Tools: What kind of tools (compile-time, run-time, post-run) would make you a more productive Axum programmer?
- Love/Hate: What’s the one thing about Axum that frustrates you to no end? What’s the thing you love most about it?
Download it, use it in anger, and give the team feedback!