this post was submitted on 31 Aug 2024
879 points (98.6% liked)

196

16436 readers
2212 users here now

Be sure to follow the rule before you head out.

Rule: You must post before you leave.

^other^ ^rules^

founded 1 year ago
MODERATORS
moss@lemmy.blahaj.zone
greembow@lemmy.blahaj.zone
moss@lemmy.world
queue@beehaw.org
funky_rodent@lemmy.blahaj.zone
PeachyMcPeachface@lemmy.blahaj.zone
threegnomes@lemmy.blahaj.zone
greembow@lemmy.world
remotelove@lemmy.ca
Roflmasterbigpimp@feddit.de
qaz@lemmy.world
A_Very_Big_Fan@lemm.ee
qaz@lemmy.blahaj.zone
qaz@lemmy.ca
A_Very_Big_Fan@lemmy.world
qaz@lemmy.dbzer0.com
Qaz@lemmy.ml
qaz@sh.itjust.works
qaz@lemmy.sdf.org
879
AI Rule (lemmy.world)
submitted 2 months ago by seaQueue@lemmy.world to c/196@lemmy.blahaj.zone
81 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] Daxtron2@startrek.website 6 points 2 months ago (1 children)

Canvas code can get out of hand very quickly if not done right

[–] TootSweet@lemmy.world 1 points 2 months ago (2 children)

I've made exactly two projects that utilized canvas, both of which I "released" in a sense. One contains 248kb of JS code and the other contains 246kb. That's before it's minified.

So I guess that means I did my canvas code right. Lol.

(Unless you meant 3d canvas or WebGL stuff with which I haven't played.)

[–] thanks_shakey_snake@lemmy.ca 6 points 2 months ago

I think they're referring to the memory footprint, not the source code file size.

[–] Daxtron2@startrek.website 2 points 2 months ago

Code size isn't really related to how much graphics data you're throwing in RAM