lavbublLvl 1
- Windows
what is this (edgy blood cat gore sscary aaaa screaming) https://studio.code.org/projects/gamelab/Rw-j-SkXSOP3U5mSQ0tfgimok7Qs69Q_WG_0ikFOuhY/view
what is this (edgy blood cat gore sscary aaaa screaming) https://studio.code.org/projects/gamelab/Rw-j-SkXSOP3U5mSQ0tfgimok7Qs69Q_WG_0ikFOuhY/view
Graycat
bruh
1000 support!!!!!
goofy ass lmaooo https://studio.code.org/projects/gamelab/ZU3eevTJ8nPV5_kyVSR1_Vhaz1w2QyDYPl2Ti06WHdE (that cat again) so i guess theyre on the forum
WE NOW HAVE 2000 SUPPORT ON THE ORIGINAL AND 1500 on the second one
A TURNING POINT IN CDO HISTORY
SUPPORT NOW
lavbubl
I think they got banned at some point
Idk I don’t want to wade through all the past discussions to find out
[WUT] Adam
Have you gotten permabanned from CDO yet?
ackvonhuelio it was a example I want to make a project listing like Locus
But why
KA, unlike CDO, has a built in projects list that can be sorted by hot, recent, and all time greatest
yeah but on the other hand, no key values
person that and harder to implement animations if not any at all, perhaps they allow sprite sheet load in but that's a whole load of other crap to look into even if they allow it, true CDO may be slower in some cases, but that's only if you don't know what your doing.... if it doesn't need to be drawn more than once then why do it? exactly it should just be rendered as an image rather than calling all of the draw calls again as far as I'm concerned everything has a learning curve, just because you can write it shittier and have it still work is not good practice especially if it's written to be unmaintainable (Yes, I'm referring to a chess game i found on khan) so while i can agree with @ackvonhuelio that it is a faster engine, it is by no means any better if (most) of the people aren't working on optimized solutions
Varrience
But the point is KA allows idiots like the bozo who made the unoptimized chess to still implement their ideas and have them work.
You can’t argue that it’s better to have worse performance, that’s just not how it works.
Plus KA has all the other benefits that I’m not going to go over again because it’ll turn this post into an essay
If you can’t make decent animations then just get better. KA has everything you need to make smooth, colorful animations.
ackvonhuelio well actually i can argue about having worse performance, it's literally the most basic principle of GIGO (Garbage In Garbage Out) if you write your program bad, it should suffer significantly that's what I'm arguing here. sure it may be good for people who may be starting out, but that can also be a bad thing since optimizing their code is no longer any priority, hence leading to possible bad practices if they continue doing stuff like that, having a limited program teaches you to be conscious on how much demand each process slows your program down rather than, oh i can probably optimize this and never do it
I just don’t see how you could possibly think that CDO is better than KA
If you say that CDO is better than KA because it has keyvalues, then I should tell you that KA does have local storage(see one of my previous posts for link to example) and that KA does also have HTTP request workarounds(also see previous post)
If you say that CDO is better than KA because it has sprites, then I should tell you that sprites are just any other constructor that you could remake if you’ve really become that dependent on sprites.
If you say that KA is bad because its fast performance promotes unoptimized programming, then you’d be wrong because eventually you will have to learn to optimize if you want to make big programs. I think that teaching optimization to beginners who are never gonna need to utilize it is a mistake, they should instead be taught how to take their dreams and ideas and bring them to life. Then, once they start making cooler, bigger, and more advanced programs, they will learn to code better and more efficiently.
I’ve honestly run out of false ideas to disprove
Give me your reasons against KA, and I’ll shoot them down with ease. I don’t know how to say it any other way, KA is just better than CDO.
ackvonhuelio I'm not disagreeing with you though, I am however arguing about principle KA has a lot more performance along with another learning curve, i am well aware... as for sprites (i am refering to animations the come pre fabbed with the frames already loaded in) thus making it much easier for a beginner to run a game with decent animations rather than having to go out of their way to make their own or load them in and format them seperately, sure keyvalues is another thing but it's not too bad since most games don't need to rely on such
As for my main point of principle of writing unmaintainable code or stuff that looks like literal spaghetti discourages me from actually figuring out how a cool program works, I won't argue that there isn't people who don't optimize their programs and there are even people on CDO who don't just saying that I've seen most people who were forced to make their programs better because their programs ran bad, I've even experienced this myself when working on faster programs and not optimize it because I don't have to
How about you, then?
Why would you, with your optimized code, prefer CDO?
tbh i dont thing lag is that much of a problem, my game retro world used the laggiest techniques and the lag is only noticeable while viewing the code lol