If 100MB of assets are taking 6-8 GB of memory to import, there's definitely Pajeetery at hand. Either they get put into memory over and over by multiple pieces of code or there's a misplaced memory allocation inside a loop where it should've been outside it. The guy said they started having problems with a large number of asset files, so it could be the latter.
I knew this for years but Godot is simply not a replacement for serious game engines and this is just one way this is made clear. During the Unity licensing drama people were advertising Godot to people who wanted to jump ship from Unity, I'm sure those were people who have never tried to develop a game in Godot. They're filling the engine with pointless bells and whistles while the core functionality is still unusable. The maintainers are asleep at the wheel, they don't know what an engine needs to have to be a serious contender.
i was recently decompiling a popular Godot game to look at some assets when i noticed it took a bunch of time more than it really should to import the assets. this is not an isolated issue; the engine fucking chugs at loading if you dare to work with an actual sufficiently large project.
[Citation Needed]
To be fair, that's not a phenomenon unique to godot. Not by a damn sight. It sure seems to be the standard operating procedure with more than a few. Okay. a lot.
Note how despite the bug reporter providing a minimal reproducible example you get multiple people, including a "Godot Senior" immediately being dismissive of the issue and asking "why would you have that many assets?", with a suggested workaround from said senior to be literally "keep restarting it until it works".
TeX is basically done which is why it's so good as an underlying; LaTeX will never be done (though it's now so ingrained into things it likely will never continue much further, either). There are simply too many LaTeX compatible weird packages on CTAN for anything else to really take off.
They tried to bully him into "GPL 2.0 or later" and he adamantly refused, and refuses to consider GPL 3. He likes exactly what GPL 2 is and does.
Rate me
all you want, this is a different statement than the statement:This statement implies that he didn't even want GPL at all, and only begrudgingly accepted GPL2, which I have seen no evidence for.
Yeah was agreeing - I’ve never heard he didn’t want GPL and only seen evidence that he wants GPL 2.0 only.
Godot maintainers do this all the time. If you report a bug, they'll tell you you're holding it wrong, or that there's already an annoying, bothersome workaround, so they're not going to fix it. Any feature request, even if you implement it yourself, is too complex to be added, can be confusing for newcomers, is out of scope, or would require too much maintenance (except their own retarded one-off shit like volumetric shading, or an entire movie editor - those are fine).
I have seen it speculated more than once that if BSD wasn't in the middle of legal troubles at the time, Linus Torvlads might have become a BSD kernel hacker.
s out there.
"BSD" was in nothing. BSDi was embroiled in a lawsuit over whether or not they'd misappropriated some code from AT&T Unix. All the PC-based forks of BSD derived from 386BSD which used precisely zero code from the original BSD, and hence was not party to the lawsuit whatsoever. However, there was so much bullshit flying around that people thought this meant BSD was encumbered and so it was avoided like the plague until after the lawsuit resolved by which time Linux was a thing. That would not, however, have stopped him from using the BSD or an MIT-style license if he wanted to. He chose to switch to the GPL because he liked it.
There was an interview in a contemporary issue of Wired from around the release of Linux 1.0 where he said he initially intended to release it into the public domain, but got very vocal feedback that he should go GPL instead, and that he basically gave in to pressure from the FSF crowd to go GNU instead of BSD or any other open source license because they were the most adamant.
TLDR, Linus is written by many authors, everyone owning a little bit of it. It can never switch to GPLv3 unless all authors agree.
A few years ago, I learned that PD is not recognized within EU jurisdictions, there HAS to be an owner, making it effectively proprietary due to unclear licensing terms. A WTFPL style license would have better legal standing.
IBM mentioned this decades ago, which is why the BSD licenses exist at all.
This is a really pedantic nitpick, but those tools have evolved I noticed, to support some flags for eliminating the ansi color codes from their output for use in scripts. And the cli tools try to be cute and detect when you're passing the output to a pipeline vs when it's getting sent properly to a tty. Which is really comfy when you're aware of what might be going on but if you aren't intimately familiar with these system calls and the byte streams they use for io, you're completely mystified when you get an incomprehensible spam of square brackets and other ansi nonsense.
