Description:
I saw today Node 20 deprecation notice in our CI piplines.
To my surprise major Go CI action is using Typescript?
This is so strange. Why Go ecosystem that is notoriouslty does not even depend on libc to do syscalls now is depending on a dependency/security nightmare JS/Typescript ecosystem?
More to that. Since recently, Typescript itself uses Go. So to build a Go project we depend on something that is itself depends on Go itself to be built! Why we have this extra jump into Typescript land?
Go has notoriously high stability and security of its packages. Minimialism in dependencies.
Typescript/Node is notoriously nightmare. Fiasco after Fisasco. Every year something happens.
Why we are not utilising Go to build CI ecosystem for Go projects?
What are we even doing here.
Justification:
like cmon.
Are you willing to submit a PR?
Yes.
Description:
I saw today Node 20 deprecation notice in our CI piplines.
To my surprise major Go CI action is using Typescript?
This is so strange. Why Go ecosystem that is notoriouslty does not even depend on
libcto do syscalls now is depending on a dependency/security nightmare JS/Typescript ecosystem?More to that. Since recently, Typescript itself uses Go. So to build a Go project we depend on something that is itself depends on Go itself to be built! Why we have this extra jump into Typescript land?
Go has notoriously high stability and security of its packages. Minimialism in dependencies.
Typescript/Node is notoriously nightmare. Fiasco after Fisasco. Every year something happens.
Why we are not utilising Go to build CI ecosystem for Go projects?
What are we even doing here.
Justification:
like cmon.
Are you willing to submit a PR?
Yes.