Java is painful

[loftar]

You imply we somehow track versions, we don't, that's the problem. We have no indicator you went from Trees version 20 from 19 unless 20 causes crashes.

If that's the only problem, I don't see any obvious reason why you couldn't do that, though.

[Granger]

Also, as far as goes the Godot engine in its other aspects, the fact that they can't even present a "hello world" as one single and simple text-file, rather than as a whole tutorial that goes through eleventeen various levels of GUI for creating "projects" and whatnot rules it out for me right then and there. If that's the kind of stuff I wanted, I'd be using Visual Studio already.

Your loss, should you insist on not using the IDE that's coming with it... which you can if you want. What you do in the IDE ends up in mostly human read- and editable files in your project directory anyway, so basically nothing is stopping you from making your life harder than it needs to be. Clicking around in the GUI and looking at what's happening on the filesystem level might be a good way to speed up getting up to speed at the beginning.

https://docs.godotengine.org/en/3.1/get ... pting.html should answer your questions, also the one about performance of the different scripting options.

[Potjeh]

Let me guess, you use Vim because it's so simple and user friendly?

[shubla]

Let me guess, you use Vim because it's so simple and user friendly?

There is nothing wrong with Vim, it is a very good tool for editing any text files. I use it for everything else except java, mainly because java is only language for which good IDE's exist.

[Potjeh]

It's probably the most powerful text editor out there, but it's as far from intuitive as it gets.

[shubla]

It's probably the most powerful text editor out there, but it's as far from intuitive as it gets.

Sure you cannot use it without a manual, if you have no prior experience of such things. But default keybindings and core functionality are still very logical, even though you may have to read something first before knowing the exact keys. It's crazy how much efficiency people are ready to trade for saving 1 minute of time during the first use of the program

[loftar]

There is indeed a difference between "user-friendliness" and "shallow learning curve". I prefer the former.

I use Emacs, though.

[Astarisk]

Also, as far as goes the Godot engine in its other aspects, the fact that they can't even present a "hello world" as one single and simple text-file, rather than as a whole tutorial that goes through eleventeen various levels of GUI for creating "projects" and whatnot rules it out for me right then and there. If that's the kind of stuff I wanted, I'd be using Visual Studio already.

Your loss, should you insist on not using the IDE that's coming with it... which you can if you want. What you do in the IDE ends up in mostly human read- and editable files in your project directory anyway, so basically nothing is stopping you from making your life harder than it needs to be. Clicking around in the GUI and looking at what's happening on the filesystem level might be a good way to speed up getting up to speed at the beginning.

https://docs.godotengine.org/en/3.1/get ... pting.html should answer your questions, also the one about performance of the different scripting options.

Having messed with Godot a bit some time ago, I wouldn't touch any option but GDScript as you open up a headache in regards to compatibility for some platforms and frequent crashes in the editor in some of the others. The other languages they claim can be used are far more underdeveloped than their main one. That being said Godot would go against what Loftar likes in style (as he said himself). He'll need to learn just more than the scripting as he will need to learn to use the editor.

[Fostik]

Just found