Scratch wants people to shift away from it for some reason…. there's been 117 bugs that have been posted in github that are open right now, but scratch NEVER listens… and dont pull that “THE SCRATCH TEAM HAS LOTS OF WORK” because they have lots of people who are willing to help out, tell them what to do, but…. NO.

1THEKINGBOB3 wrote:

Scratch wants people to shift away from it for some reason…. there's been 117 bugs that have been posted in github that are open right now, but scratch NEVER listens… and dont pull that “THE SCRATCH TEAM HAS LOTS OF WORK” because they have lots of people who are willing to help out, tell them what to do, but…. NO.

IDK where exactly you got that number from (edit, it was here), but the editor alone has > 3x what you said:


Though not all of these are real - a ton are just complaints about intended features.

This absolutely NEEDS to be implemented. The reason that Godot, an open source game engine, has so many features is that they actually have an active GitHub community offering to code new features for it. Big support.

AHypnoman wrote:

(#47)

1THEKINGBOB3 wrote:

Scratch wants people to shift away from it for some reason…. there's been 117 bugs that have been posted in github that are open right now, but scratch NEVER listens… and dont pull that “THE SCRATCH TEAM HAS LOTS OF WORK” because they have lots of people who are willing to help out, tell them what to do, but…. NO.

IDK where exactly you got that number from, […]

It seems to come from https://github.com/scratchfoundation/scratch-blocks/issues?q=label%3Abug+is%3Aissue+is%3Aopen.

just found out in GitHub last scratch blocks change was six months ago (bug change)

1THEKINGBOB3 wrote:

just found out in GitHub last scratch blocks change was six months ago (bug change)

I mean, scratch-blocks doesn't need that many updates (realistically it'd only be updated if a big revamp of the codebase, some breaking change is introduced, a new block is implemented, a vulnerability is fixed, a bug etc.)

josueart wrote:

1THEKINGBOB3 wrote:

just found out in GitHub last scratch blocks change was six months ago (bug change)

I mean, scratch-blocks doesn't need that many updates (realistically it'd only be updated if a big revamp of the codebase, some breaking change is introduced, a new block is implemented, a vulnerability is fixed, a bug etc.)

the scratch.vm was even later…. (thats the main website)

1THEKINGBOB3 wrote:

josueart wrote:

1THEKINGBOB3 wrote:

just found out in GitHub last scratch blocks change was six months ago (bug change)

I mean, scratch-blocks doesn't need that many updates (realistically it'd only be updated if a big revamp of the codebase, some breaking change is introduced, a new block is implemented, a vulnerability is fixed, a bug etc.)

the scratch.vm was even later…. (thats the main website)

No - the main website frontend is under scratch-www

Hopefully this gets merged: https://github.com/scratchfoundation/scratch-www/pull/9106

Support because Gamepads need to be added to extensions and this would make that process go faster.