ما تو پروژه مون که یه وب اپلیکیشن هستش تو بخش اصلیش از setTimeOut و setInterVal استفاده میکنیم برای کنترل کامپوننت و ریکوئست هایی که به سرور میزنه ولی یه چیزی بود که مشکل بزرگی رو برامون ایجاد میکرد اونم این بود که وقتی شما میرفتی یه تب دیگه از مرورگر و مدتی بعد برمیگشتی
این setTimeOut و setInterVal ها اون پشت اجرا نمیشدن و باعث میشد کامپوننت مون باگ بخوره و کار نکنه برای حل این مشکل اومدیم از پکیج HackTimer استفاده کردیم این پکیج میاد یسری web worker راه اندازی میکنه که تو background این تایمر هارو اجرا میکنه و این باعث میشه که
شما اگه رفتی یه تب دیگه این تایمر ها اون پشت کار کنن و کامپوننت بتونه به درستی و سر موقع ریکوئست هاشو بزنه
#javascript
#npm
#reactjs
https://www.npmjs.com/package/hacktimer

cool

Node.js Helps NASA Keep Astronauts Safe and Data Accessible

🔆 Why Node.js?
For starters, Estes’ team was already writing JavaScript-heavy applications. “When we selected
Node.js, one of our selling points was centering around a single platform,” he said.
Some other key reasons NASA choose Node.js were:
🔸 • The relative ease of developing data transfer applications with JavaScript, and the
familiarity across the organization with the programming language, which keeps
development time and costs low.
🔸 • Node.js’ asynchronous event loop for I/O operations makes it the perfect solution for a cloudbased
database system that sees queries from dozens of users who need data immediately.
🔸 • The Node.js package manager, npm, pairs incredibly well with Docker to create a
microservices architecture that allows each API, function and application to operate smoothly
and independently. This encourages each of the three legacy database systems to play nice
with each other while the data is transferred to the cloud.

https://foundation.nodejs.org/wp-content/uploads/sites/50/2017/09/Node_CaseStudy_Nasa_FNL.pdf

If I was an astronaut and I knew my protection relies on npm packages and safety of JS, I would have taken a space walk without being attached to ISS

Node is basically a V8 engine that is not sandboxed and has a few extra APIs and functions and things like libuv attached to it.

That means it has exactly the same APIs for debugging that the V8 has and you can simply configure things like attach in flags.

I said all of that to point out that you don’t need an extra hassle to configure chrome and debug your node apps from there. You can simply do it in your text editor of choice. More powerful text editors that let you set breakpoints and custom watches and stuff are even easier to do so:

https://code.visualstudio.com/docs/nodejs/nodejs-debugging

Portable Cloud Programming with Go Cloud:
the Go team at Google is releasing a new open source project, Go Cloud, a library and tools for developing on the open cloud

https://blog.golang.org/go-cloud

@go_lang