Mono relicensed under MIT - C# for UE4 can come back?

[miketgv]

@ambershee;575069

Here’s the first function that stared at me when I opened visual studio today:

AUniFacilityFurnishing::AUniFacilityFurnishing()
{
 	// Set this actor to call Tick() every frame.  You can turn this off to improve performance if you don't need it.
	PrimaryActorTick.bCanEverTick = true;
	USceneComponent* MyRoot = CreateDefaultSubobject<USceneComponent>(TEXT("Root"));
	RootComponent = MyRoot;

	Collider = CreateDefaultSubobject<UBoxComponent>(TEXT("Collider"));
	Collider->AttachTo(RootComponent);

	RotatorWidget = CreateDefaultSubobject<UStaticMeshComponent>(TEXT("RotatorWidget"));
	RotatorWidget->AttachTo(RootComponent);
}

Here’s an approximation of what it would probably look like if it were implemented in C#:

class AUniFacilityFurnishing
{
	 AUniFacilityFurnishing()
	{
 		// Set this actor to call Tick() every frame.  You can turn this off to improve performance if you don't need it.
		PrimaryActorTick.bCanEverTick = true;
		USceneComponent MyRoot = CreateDefaultSubobject<USceneComponent>(TEXT("Root"));
		RootComponent = MyRoot;

		Collider = CreateDefaultSubobject<UBoxComponent>(TEXT("Collider"));
		Collider.AttachTo(RootComponent);
	
		RotatorWidget = CreateDefaultSubobject<UStaticMeshComponent>(TEXT("RotatorWidget"));
		RotatorWidget.AttachTo(RootComponent);
	}
}

Truly terrifyingly different. I don’t know how C# programmers would ever be expected to adapt

FRunnable / FRunnableThread. Honestly, I don’t think it would be all that hard. There’s a little legwork to get yourself started but it’s almost all in the organisation of your thread management, not fighting with the language.

So… where’s the header of your example?
In my point of view the complexity of c++ is not that difficult to pass over. But the thing that I don’t like at c++ is the lack of intelisense ( who says it has, he didn’t programmed in c#) and the extra information you type in .h files witch it’s writing the same thing twice and on top of that the compilation errors are too generic and it takes time to find the culprit. All of this combined takes a lot of extra time that is so precious for one like me (i have a daily job and a family) so for the time being I do all the programming using blueprints and only specific complex code in c++. We leave in a era of speed and c++ it’s not the fastest way to develop (no offence to anyone).