It turns out that this is all standard IEEE 754, which gives a maximum relative rounding error of about 1.11e-16.
In JavaScript, when you compare 100 == 99.99999999999999, it evaluates to false because the precision of the number representation can lead to small inaccuracies. The value 99.99999999999999 is slightly less than 100, causing the comparison to fail.
On the other hand, 100 == 99.999999999999999 evaluates to true because this number is represented in a way that is close enough to 100 within the limits of the floating-point precision defined by IEEE 754. In this case, the tiny difference falls within the acceptable error margin, and thus the two values are considered equal by JavaScript.
This illustrates how floating-point arithmetic can lead to unexpected results in programming!
In JavaScript, when you compare 100 == 99.99999999999999, it evaluates to false because the precision of the number representation can lead to small inaccuracies. The value 99.99999999999999 is slightly less than 100, causing the comparison to fail.
On the other hand, 100 == 99.999999999999999 evaluates to true because this number is represented in a way that is close enough to 100 within the limits of the floating-point precision defined by IEEE 754. In this case, the tiny difference falls within the acceptable error margin, and thus the two values are considered equal by JavaScript.
This illustrates how floating-point arithmetic can lead to unexpected results in programming!
https://blog.angulartraining.com/how-to-run-repeated-http-requests-with-angular-signals-5f66f8db73f8
#angular #signals #rxjs #easy
#angular #signals #rxjs #easy
Medium
How to run repeated HTTP requests with Angular Signals?
A few years ago, I published a tutorial on how to do polling with RxJs and Angular. The goal was to illustrate how to retrieve and render…
🎉 It's that time again! The 2024 Annual Anonymous Salary Survey for Tech Professionals in Germany 🇩🇪 is now live!
It takes just 3 minutes to share your input and help create valuable insights into tech salaries across Germany.
Take the survey and feel free to share it with your colleagues and friends:
👉 https://airtable.com/appbmmHgUzFU3Qres/pagxOj4KVV2pJ7YUZ/form
⏳ Deadline: before 2025 rolls in. Results, along with highlights from 2024, will be shared in January 2025.
In the meantime, check out last year’s analysis: https://ksyula.github.io/Salary-report/
Your participation makes a difference — thank you for contributing to this community effort! Wishing you a joyful holiday season 🎄 and a great start to 2025!
(c) Ksenia Legostay
It takes just 3 minutes to share your input and help create valuable insights into tech salaries across Germany.
Take the survey and feel free to share it with your colleagues and friends:
👉 https://airtable.com/appbmmHgUzFU3Qres/pagxOj4KVV2pJ7YUZ/form
⏳ Deadline: before 2025 rolls in. Results, along with highlights from 2024, will be shared in January 2025.
In the meantime, check out last year’s analysis: https://ksyula.github.io/Salary-report/
Your participation makes a difference — thank you for contributing to this community effort! Wishing you a joyful holiday season 🎄 and a great start to 2025!
(c) Ksenia Legostay
A gentle reminder for software engineers (you'll be thankful):
• Learn SQL before ORM.
• Learn Git before Jenkins.
• Learn SQL before NoSQL.
• Learn CSS before Tailwind.
• Learn Linux before Docker.
• Learn English before Python.
• Learn REST before GraphQL.
• Learn JavaScript before React.
• Learn HTML before JavaScript.
• Learn Containers before Kubernetes.
• Learn Monolith before Microservices.
• Learn Data Structures before Leetcode.
• Learn Server Management before Serverless.
• Learn to ask the Right Questions before ChatGPT.
The bottom line: Learn fundamentals before going deep.
What else would you add?
• Learn SQL before ORM.
• Learn Git before Jenkins.
• Learn SQL before NoSQL.
• Learn CSS before Tailwind.
• Learn Linux before Docker.
• Learn English before Python.
• Learn REST before GraphQL.
• Learn JavaScript before React.
• Learn HTML before JavaScript.
• Learn Containers before Kubernetes.
• Learn Monolith before Microservices.
• Learn Data Structures before Leetcode.
• Learn Server Management before Serverless.
• Learn to ask the Right Questions before ChatGPT.
The bottom line: Learn fundamentals before going deep.
What else would you add?
Hey ppl! I need you! :-)
he-he... I thought, that "ngx-translate" was a long time dead... =) And many devs switched to "transloco"...
What you think... What should I choose @2025 for my "ng new mew"?
he-he... I thought, that "ngx-translate" was a long time dead... =) And many devs switched to "transloco"...
What you think... What should I choose @2025 for my "ng new mew"?
A pattern in a lot of #Angular code bases
❌ mixing of imperative and declarative code
❌ unnecessary boilerplate
❌ updating data from another source creates more mess and hard to follow code
💡How would you improve it?
#interview
❌ mixing of imperative and declarative code
❌ unnecessary boilerplate
❌ updating data from another source creates more mess and hard to follow code
💡How would you improve it?
#interview
@angular/material version 19 improves the developer experience to define custom themes with a new theming-api!
Also overriding styles on specific material components get easier
#angularMaterial #ng19
Also overriding styles on specific material components get easier
#angularMaterial #ng19
Happy browser choice day to those in Europe who celebrate! This is a second attempt to get it right. Brought to you by the iOS 18.2 update and the fine folks from https://open-web-advocacy.org/
This media is not supported in your browser
VIEW IN TELEGRAM
Long awaited feature in Angular Material: Time Picker component shipped with @angular/material 19!
#ng19 #angular19 #ngMaterial
Fully aware of locales
#ng19 #angular19 #ngMaterial