I do know some enterprises that still run JBoss so it’s not entirely like no one would use this. However, they are all in the process of refactoring for the cloud off of JBoss JEE.
5,056 karma · joined March 2, 2020
I do know some enterprises that still run JBoss so it’s not entirely like no one would use this. However, they are all in the process of refactoring for the cloud off of JBoss JEE.
>” From time to time, a complex algorithm will lead to a longer routine, and in those circumstances, the routine should be allowed to grow organically up to 100-200 lines. (A line is a noncomment, nonblank line of source code.) Decades of evidence say that routines of such length are no more error prone than shorter routines. Let issues such as depth of nesting, number of variables, and other complexity-related considerations dictate the length of the routine rather than imposing a length restriction per se.
If you want to write routines longer than about 200 lines, be careful. None of the studies that reported decreased cost, decreased error rates, or both with larger routines distinguished among sizes larger than 200 lines, and you’re bound to run into an upper limit of understandability as you pass 200 lines of code.”
[0] https://books.google.co.in/books?id=LpVCAwAAQBAJ&pg=PA174
Isn’t that the fucking point? Having a 2000 line function is a code smell so bad, I don’t care how well the function works. It’s an automatic review fail in my book. Abstractions, closures, scope, and most importantly - docs to make sure others use your functions the way you intended them. Jesus.
This is the same as someone arguing for scrolls when books with table of contents and appendices are far superior.
Every store requires work on the devs part, Unity’s doesn’t (or extremely little).
I also don’t want to give Unity any more money so buying assets from them and porting them isn’t my idea of a good time.
If that’s your requirements, use my engine Reactor3D.
Like a C++ developer crying foul because inheritance doesn’t exist in YAML.