Comments by "Charles M." (@charlesm.2604) on "Godot in 100 Seconds" video.

@igorthelight bash
4
@gokudomatic Ultimately it doesn't really matter what language is better for game dev, there are objectively more game dev who are used to C# and C++ and we should make Godot a welcoming community to them.
4
@Spartan322 "Devs who get into Godot do not work in C# or C++." Don't get surprised when those who do work in C# and C++ are favoriting alternative engines with first class support for them. I'm not saying GDScript is bad (in fact it has been a real advantage for beginners to get into game dev), I'm saying it makes no sense to enforce its use to people who prefer other languages. As far as funding goes, I agree, Godot isn't going to run off of financial support. But it's very hard for professionnals to trust a FOSS project. If we want professional adoption we need an income-bringing activity. It's a tough problem to tackle and it needs to be discussed as a community because it could change the direction the project is trying to take. Some of my ideas: - Asset library fees. - Working with a hosting platform to offer multiplayer infrastructure and SDK. - Godot Ads. - Premium support. Thanks for reading and please be informed my intent isn't to detract Godot, the core team or anyone working on the project. It's to help them.
2
@Magnumsrt Callback lambda functions are so confusing to write and read. Class properties/constructors in the class declaration, really ? You end up with a bunch of files with a one liner data class. Let's not even talk about their implementation of coroutines which make asynchronous a bigger struggle than old JavaScript's Promises. And on top of that JetBrains is turning the ecosystem into .NET, a bunch of confusion because of legacy projects, reusing names, etc... Don't get me wrong I'll write in Kotlin before Java in day of the week but let's not act like it's a good designed language. It's just the better of 2 bad options.
1
@Mechite Exactly. My reply wasn't about Java, it was about Kotlin. Kotlin is a badly designed language. The only good part about Kotlin's abstraction are the top-level functions, which save space and avoid classes with static methods when not needed (utils and whatnot). But under the hood Kotlin is turning those to traditional Java class during compilation so you don't end up with anything different running on the JVM during runtime. I think the reason why people have such an unhealthy love for Kotlin is because of all the years devs have complained about Java. What they fail to realize is that Java receives updates to address those issues. They heard a senior dev angry about how difficult coding his his prehistoric Spring applet 20 years ago and they see it as a red flag. Sheeps i guess.
1
@Mechite True that. I think that was what Jetbrains tried to address when it comes to the ecosystem, they made out of-the-box compatibility with Java packages. They knew nobody would migrate and leave the Java ecosystem otherwise, it's rich, it's mature, it's the biggest community in the industry, it would make no sense to leave the ecosystem and build everything from the ground up again. But honestly at this point Kotlin is becoming much more of a toolkit than a Java alternative. Sure, you can transpile Kotlin codebases to Java classes to compile them to JVM bytecode but that's not the main interest. It would just be the same results with extra steps. What Jetbrains is turning Kotlin into is more of toolkit with "cross-compilation targets" (Kotlin Native, JavaScript, DOM, etc...). And they are also building Kotlin as a DSL power house, people are creating bindings for pretty much any language under the sun. That's an interesting direction, especially with the other projects Jetbrains is working on (Compose for Web mainly). This might be the reason why I would see true value in Kotlin in the future, it could become a true "write once run everywhere" language which would be accessible to Java devs (so any dev with experience with C-inspired languages).
1