You can stop reading when you find the answers to the requested questions.

Eh no not necessarily. This depends on the type of audit and the questions specifically, but should never be a default stance if you want to provide a full report. Moreover, if you are learning to do software audits, it would be beneficial to check everything because experience is key to know what you are looking for

I think you might have a point there. I for one was not aware of the gay frog situation before that whole drama and I’m grateful it was brought to my attention

This article talks about galaxy formations and stars bursting, curious how you jump to “life” from that?

Its important to understand that:

• JavaScript is typescript
• Typescript is JavaScript with types

When you are writing typescript, you are writing JavaScript but have additional syntax to help support type safety and structure. If you are creating a function that does x, it should very much be the same in JS and TS, just in TS it has extra syntax

TS doesn’t modify the way JS works, its one of the stated needs for the tooling.

In TS, for example, I can denote an object as

const x: Record = {}

In JS it would be

const x = {}

It’s still nothing but an object. TS doesn’t change the functionality, it just adds typing and checks that you are using that object properly as static build step.

Typescript doesn’t really remove anything you learn in JavaScript. Like at all. It’s not really a library as such. It adds ways to enhance your JavaScript, with typing, structure, and tooling

Learn JavaScript as much as possible. Every bit you learn will benefit you with typescript

It is, the one that starts with lower case is called camel case. As in camelCase has a “hump”