Today I’ll be chatting all about Deno with my guest Andres Pirela, a 19 year old who’s working for a large company as a full stack software engineer using C#, Java, Typescript and Javascript. He’s been programming since the age of 9! Learn what Deno is all about, it’s great features, and it’s drawbacks!
*******************************
Questions Asked
*******************************
- How does a 19 year old work for a large company as a software engineer?
- How old where you when you first started programming?
- How and when did you learn C# and Java?
- What is Deno?
- Who created Deno?
- What is a web assembly?
- What are the three main reasons that Deno was created?
- What are some of Deno's security features?
- How are modules handled in Deno?
- How are modules cached?
- How do you distribute Deno projects and it's associated cache folder?
- Can the cache be configured on a per project basis?
- How are module dependencies handled by Deno?
- How are points of failure handled by Deno modules?
- Do you think Deno will end up using a centralized package manager?
- Why is a package manager being rejected by the Deno founders?
- Explain how Deno uses promises by default?
- How is callback hell avoided by Deno?
- Explain how you can use top level Await with Deno?
- Does Deno support Type Script and Javascript?
- How can people get started developing Deno apps?
- Is Deno ready for production?
*******************************
Reference Links
*******************************
