2022 Update:
My concerns around immaturity have long since been addressed since the 1.0 release. While issues around arm32 builds might...
For further actions, you may consider blocking this person and/or reporting abuse
Every programming language is a Runtime, Python, JAVA, C#, and so on, so basically, everyone calling Node a JS runtime is right but it is also unnecessary, Theoretically, you can call Node a programming language because this is exactly how other languages are built, They are a Box/Program where they run.
Whaaat
What do you mean by "Runtime" exactly?
Java is not a Runtime!
Java is a runtime language it runs on a runtime.
Java compiler compiles
.java
code to "java byte code"Then JVM runs that byte codes.
Yes thats what I said, Java is a runtime language.
I haven't dabbled with Deno at all so far but I'm curious as to how people would tackle the missing script-section of the package.json.
For example I have a script:
Like you described we probably could setup some
.sh
or other centralized collection of scripts but ... aren't we just rebuilding the package.json at this point?Without any of those you probably end up noting all your possible scripts somewhere in your readme so other devs know what to execute? Sounds iffy. Am I missing the obvious solution to this problem?
Also, how would a typical CI like GitHub actions work out? Let's say we have a GitHub action running whenever someone wants to merge into our master-branch. What does the github action execute? The
.sh
? I'm really open for new things but I just don't see any gain from this :|Work for a DOMParser that will be integrated into Deno going on at github.com/b-fuze/deno-dom if anyone wants to contribute.
I actually linked it at the end! I’m familiar with the project and its contributors personally. I used it for a project of mine and I’m very happy it exists. It’s been making steady progress for a while now.
Ah, sorry. My eyes must've glazed over the difference in color. I even re-read the end twice searching for the link😂
Haha, not a problem! I didn't write anything to make you think it was different than the link previously in the article.
haha I enjoyed the part where package.json is effectively replaced by exports.ts! not trolling just mildly amused