Tools we used to create a hit HTML5 game on Steam

Re:Tools we used to create a hit HTML5 game on Steam by shantly on Tuesday November 19, 2019 @03:25PM (#21577875)

They tend to use ~10x the memory that seems reasonable—generous, even—for what they're doing, and periodically misbehave and decide to eat tons of cycles continuously for no obvious reason, in a way native apps don't, or at least not so frequently and nigh-universally.

Sure, partial counterexample in VSCode, but then there's all the others.

[ Parent | on HN ]

Re:Tools we used to create a hit HTML5 game on Steam by IggleSniggle on Tuesday November 19, 2019 @06:36PM (#21579577)

I agree with what you are saying with regards to the tendency of the platform. But, aside from the weight of unnecessary/unused browser features, I think that has more to do with the needs of the developers attracted to the platform more than the platform itself.

"The needs" being a requirement to ship a MVP ASAP using developers that can agree on a lowest common denominator language of js.

[ Parent | on HN ]

Re:Tools we used to create a hit HTML5 game on Steam by stjohnswarts on Tuesday November 19, 2019 @07:18PM (#21579891)

I wonder if the VsCode coders don't share their SOP somewhere for us mere mortals to learn some techniques they use to keep electron under control.

[ Parent | on HN ]