IvanPM

With UE4 out, thought, I have the feeling that support for UDK will drop even lower than it has been since last year, leaving the toolchain in a buggy mess. I've heard of companies delegating a coder or two to work on porting the codebase to UE4, while the rest of the team works on the non-UE branch. I work as a programmer in UE4 in my full-time job and so far the "biggest problem" that I've experienced is migrating the codebase every time a new major version of the engine comes up (while the codebase itself is still being worked on) and is something that they might experience if they start porting the code just now. In that light, the "make everything in Blueprint and then port it over to C++" workflow, which has become somewhat popular in the UE4 community, could reduce the scale of that issue. There are options, but one thing is for sure - UE4 is quite powerful and I do hope they decide to switch. To add to the existing feature list, the backlog has loads of awesome features, which will be coming soon, if they ever decide to stop working on it - the source will be there for people to maintain and with it going free - bugfixes should increase dramatically.