Just my 2 cents, but I hope you realize no code editor (in one form or another) means no migration to Kinetic until there is one for 90% of our customers with UI customizations, not just “edge cases”… Kinetics in its current form is fine to add the random UD fields to a screen, but even in a web page, most code runs on client side, not on the server. You don’t want to call the server for every field validation, and you don’t necessarily want to wait for an update to validate the entire screen either.
Just put yourself in the shoes of a new Epicor customer who paid hundreds of thousands of dollars in the last 2-3 years to implement their very specific tailor made processes in Epicor. Kinetics comes along, and now they have to redo it all again. It gives them a nice opportunity to evaluate the competition, since either way they have to start over from scratch.
I don’t expect plug and play functionality with old code, but I DO expect 1:1 equivalent functionality before I can contemplate migrating any customer with any customization slightly more involved than adding a few fields. The customer having to adapt to a new UI is one thing, but having to adapt to new processes because we can no longer reproduce the old ones is quite another…
I don’t see the big difficulty either way, C# is defined as an ECMA script, and can be integrated directly in a web page… And even if it has to be JS, that’s fine too. The biggest difficulty is just the code framework around it.