konsuko

A while ago I ported my indie game Penko Park to Nintendo Switch, and the process turned out to be much bumpier and more challenging than I anticipated. There were unexpected technical hurdles, weird edge cases, and moments where I genuinely wondered if it would ever get finished.

I wrote a detailed breakdown of the whole journey – the good, the bad, and the ugly.

For those of you who have done console ports before: What was the biggest headache you ran into?

Would love to hear other devs’ experiences.

Hey everyone! I just wrote a blog post about the (very bumpy) journey of porting Penko Park to Nintendo Switch.

I’m curious: Have you done any console ports yourself? What was your biggest surprise or pain point? Was it all worth it in your opinion, after you launched?

I’d love to hear other devs’ experiences (good and bad)!

Jai is an amazing language to work with, I highly recommend checking it out once it becomes publicly released. It's elegant, simple, performant, takes all the best parts of Zig minus the annoying parts (like errors on unused local variables) and adds a bunch of super useful game development libraries as well as a built-in string type (which I really missed in Zig).

Oh, and the compile times are just a joy, almost no other language even comes close to the speed of iteration that's possible with Jai, which is another great reason to use it for games and prototyping in general.

The new multi-object for loop syntax is such an improvement. Hoping for many more small QoL features like this until Zig hits 1.0.

No, it's not fine. It's broken on Chrome for macOS and freezes on startup for about 10-20 seconds. Has nothing to do with C#, this happens with GDScript, too. It's a known issue, has been discussed at length on Github (by myself as well) and there is no fix in sight at the moment.

I would consider that broken.

They have to use Mono. New .NET Core Runtime does not yet support all platforms that Mono used to support, and won't for a while.

It has been excellent, best browser game engine imo - however as of Godot 4, the web export is completely broken, unfortunately. Godot with C# straight up has no web export and no mobile export atm, just desktop.

This library is probably the most full-featured, well-documented open source PDF libraries I ever came across. Implementing it right now for a small app I'm building and it's simple & fun to use.

Can't believe it's developed by one single dev and it's MIT-licensed. Really happy this exists, as before this there were almost only paid/commercial PDF libraries in the .NET ecosystem.

> but if you want to cause a so called "paradigm shift" then you'll need to understand where the progress is happening and what kinds of opportunities it creates.

This is the most Hacker News thing I read all year. What are you talking about? Where did he say anything about wanting to cause a paradigm shift?

I can definitely say that for me, this is the straw that breaks the camel's back. I am turning my back on the .NET ecosystem, after having written C# for 7 years. The `dotnet watch` debacle from last year, still having key parts like the debugger closed-source and now again with this: It's just too much.

I do not want to build anything of value on top of such a shady platform that's completely controlled by one Megacorporation. It's too big of a risk.

No matter how many MVPs tout "MS <3 Open Source", how can anyone still believe them after these repeated violations?