JavaScript Ekosistemi: Deno, NestJS, Ondalık Sayılar, Beyin Sinyalleri ve Dahası

Summary

In this candid discussion, the speaker critiques the rise of Deno, expressing skepticism over its need and arguing that it doesn't offer significant improvements over Node.js. He also defends JavaScript's capabilities, especially in machine learning, against its critics. The speaker emphasizes the importance of understanding architecture and programming languages, sharing personal experiences in overcoming challenges with Node.js. He further highlights how JavaScript remains relevant and effective in various fields, while also questioning the rising popularity of other technologies like Deno, Rust, and NestJS. The conversation highlights the evolution and practical use of JavaScript in diverse applications.

Takeaways

• 😀 The speaker doesn't see Deno's release as beneficial and believes it was unnecessary. They feel if Node.js can do what Deno does, there's no need for an additional framework.
• 😀 The speaker criticizes the politics behind creating Deno, viewing it as divisive, and prefers solutions that don't promote unnecessary fragmentation in the development community.
• 😀 They mention that JavaScript has issues with floating-point numbers, but argue this is a common problem in all programming languages and can be solved using libraries.
• 😀 The speaker shares their experience of using JavaScript for machine learning and claims that JavaScript can handle such tasks despite the floating-point limitations.
• 😀 The speaker recounts a 2018 conference where they demonstrated using brain signals to control JavaScript, challenging claims that JavaScript isn't suitable for scientific tasks like machine learning.
• 😀 The speaker advocates for a scientific approach to problem-solving and emphasizes the importance of testing claims before making conclusions, particularly in programming and technology.
• 😀 The speaker expresses strong opinions about JavaScript frameworks, particularly their dislike for NestJS, stating that it reflects poor design choices and that simpler frameworks like Express should be used instead.
• 😀 They argue that a developer’s choice of technology is heavily influenced by the team's familiarity with certain languages and frameworks, and that transitioning between technologies requires substantial effort.
• 😀 The speaker believes in the adaptability of developers, claiming that one can write excellent software even in PHP, showing their broad experience with different programming languages.
• 😀 Despite criticisms of JavaScript, the speaker emphasizes its popularity and flexibility, noting that it continues to grow in importance, especially for browser-related tasks and machine learning.
• 😀 The speaker believes that while JavaScript may not be suitable for every task (like working directly with hardware), it can interact with native code through bindings and extensions, making it versatile in a variety of applications.

Q & A

What are the main criticisms the speaker has regarding Deno?

The speaker criticizes Deno for being unnecessary, stating that if Deno implements the features it claims to offer, it should simply merge with Node.js rather than exist as a separate entity. The speaker also dislikes the politics around Deno's introduction.

What is the speaker's opinion on Node.js and JavaScript?

The speaker is a strong proponent of Node.js and JavaScript, emphasizing their versatility, including their ability to perform tasks like machine learning. The speaker believes that JavaScript can handle tasks typically associated with other languages, and they dismiss criticisms of JavaScript's handling of floating-point numbers.

How does the speaker respond to criticisms about JavaScript's handling of floating-point numbers?

The speaker argues that the issue with floating-point numbers is not specific to JavaScript, but a general problem in many programming languages. They assert that this is a known standard and that JavaScript can still handle machine learning tasks despite the issue.

What was the speaker's experience with a conference presentation in 2018 related to JavaScript?

In 2018, the speaker presented a live demo at a conference where they demonstrated how JavaScript could be used to write text through brain signals. They also used the opportunity to refute criticisms of JavaScript and highlight its capabilities, including its potential for machine learning.

How does the speaker feel about frameworks like NestJS?

The speaker expresses a strong dislike for NestJS, stating that it is a poor design choice for Node.js and that anyone using it likely lacks knowledge of software design. The speaker prefers simpler frameworks like Express.

What is the speaker's view on using different programming languages depending on the team's expertise?

The speaker acknowledges that the choice of technology often depends on the expertise of the team. For example, if the team knows C# or .NET, they are likely to use .NET for backend development, while a team skilled in JavaScript would use Node.js.

Why does the speaker prefer JavaScript over other languages like Java?

The speaker prefers JavaScript for its high signal-to-noise ratio, which makes it easier to work with compared to languages like Java. They emphasize that JavaScript is easier to learn and use, which is crucial for both individual and team productivity.

What challenges does the speaker mention when writing a firewall in JavaScript?

The speaker notes that while it is possible to write a firewall in JavaScript, it would require dealing with network traffic, which JavaScript does not natively support. To handle this, they used C bindings to interface with hardware and manage the network traffic.

How does the speaker describe their experience in promoting Node.js in a work environment?

The speaker describes overcoming resistance to using Node.js in their workplace. After advocating for it and showing how it could be used effectively, they successfully convinced several teams to adopt Node.js.

What does the speaker think about JavaScript's future and popularity?

The speaker believes that JavaScript's popularity will continue to rise, particularly because it works seamlessly in browsers. They suggest that other languages, such as Rust, would need to support browser environments to gain similar traction.