Three IOS apps and a Web App that might interest you -
Live Loop - apps.apple.com/us/app/live-l…
StreamPilot - apps.apple.com/us/app/stream…
City Discoverer - apps.apple.com/us/app/city-d…
And
EventLoop - web.live-loop.live
41
Two IOS apps and a Web App that might interest you -
Live Loop - apps.apple.com/us/app/live-l…
StreamPilot - apps.apple.com/us/app/stream…
And
EventLoop - web.live-loop.live/
18
Two IOS apps and a Web App that might interest you -
Live Loop - apps.apple.com/us/app/live-l…
StreamPilot - apps.apple.com/us/app/stream…
And
EventLoop - web.live-loop.live/
79
Jun 11
🚀 Day 29 — Restarting My Full-Stack Journey
Today I went deeper into Node.js and learned what actually happens behind the scenes when JavaScript runs outside the browser.
This was one of those topics where understanding the internals made many previously confusing concepts finally click.
📚 What I learned today:
✅ How JavaScript Runs in Browsers vs Node.js
* Browsers provide Web APIs
* Node.js provides Node APIs
* Both use JavaScript but have different runtime environments
✅ Understanding Node.js Architecture
* V8 JavaScript Engine
* Node.js APIs
* C/C Bindings
* libuv
* Event Loop
Understanding how all these components work together to execute JavaScript outside the browser.
✅ Node.js Process Lifecycle
Learned what happens when we run:
```bash
node index.js
```
* A Node.js process is created
* A main thread is allocated
* Top-level code starts executing
* Modules are loaded
* Event callbacks are registered
* Event loop starts processing tasks
✅ Event Loop Deep Dive
Explored major event loop phases:
* Timers
* I/O Poll Phase
* `setImmediate()`
* Close Callbacks
And how Node.js decides when to continue or exit the process.
✅ Main Thread vs Thread Pool
Learned:
* JavaScript runs on the main thread
* CPU-blocking code can freeze execution
* libuv uses a thread pool for certain expensive operations
* Why blocking code like `while(true)` should be avoided
✅ Understanding Asynchronous Execution
Practiced examples using:
* `console.log()`
* `setTimeout()`
* Event Loop execution order
And understood why asynchronous callbacks execute after synchronous code completes.
🛠️ Practice:
* Explored Node.js execution flow
* Tested event loop behavior using timers
* Experimented with callback execution order
* Learned how blocking code impacts application performance
💡 Biggest takeaway:
Before today, I knew that Node.js was "single-threaded."
Now I understand what that actually means.
Learning about the event loop, libuv, the main thread, and asynchronous execution helped me understand how Node.js handles thousands of operations efficiently without blocking the application.
The deeper I go into backend development, the more fascinating it becomes 🚀
#100DaysOfCode #FullStackDevelopment #BackendDevelopment #NodeJS #JavaScript #EventLoop #WebDevelopment #LearningInPublic #ChaiCode #dayxwebtoon #TrendingforPavel #100DaysOfSilence #DAY29
@Hiteshdotcom @nirudhuuu @yntpdotme @ChaiCodeHQ @surajtwt_ @codedailybot @_100DaysOfCode @100days
Jun 10
🚀 Day 28 - Restarting My Full-Stack Journey
Today was another exciting backend day as I moved beyond theory and started understanding how web servers, Express.js, TypeScript tooling, and backend project workflows work together.
I also built my first basic backend Todo CRUD application to put these concepts into practice.
📚 What I learned today:
✅ Understanding Web Servers
* How clients and servers communicate
* Ports and server processes
* Why servers continuously listen for incoming requests
✅ Node.js HTTP Module
* Creating a basic web server using the built-in `http` module
* Understanding:
* Request (`req`)
* Response (`res`)
* Handling different routes and HTTP methods manually
✅ Dependency Management
* Understanding:
* `node_modules`
* Dependency trees
* `package-lock.json`
* Why dependency locking is important for consistent environments
✅ Introduction to Express.js
* Creating APIs with Express
* Routing using:
* `app.get()`
* `app.post()`
* Parsing JSON using:
* `express.json()`
✅ TypeScript Project Setup
* `tsconfig.json`
* `rootDir`
* `outDir`
* Compiling TypeScript into JavaScript
✅ Development Workflow Improvements
* Local TypeScript installation
* `tsc-watch`
* Auto compilation and server restart during development
✅ Type Definitions
* Understanding `@types/*`
* Installing:
* `@types/node`
* Express type definitions
* Better IntelliSense and type safety
✅ Runtime Validation
* Introduction to Zod
* Understanding why TypeScript alone is not enough for validating external inputs
🛠️ Practical Work
Built a basic Todo CRUD API using:
* Node.js
* Express.js
* TypeScript
Implemented:
✅ Create Todo
✅ Read Todos
✅ Update Todo
✅ Delete Todo
This was my first step toward building real backend applications.
💡 Biggest takeaway:
Frontend taught me how users interact with applications.
Backend is teaching me how applications actually process requests, manage data, and communicate with clients behind the scenes.
Building my first CRUD API made the client-server relationship much clearer and made backend development feel far less intimidating.
Excited to keep moving deeper into Node.js, Express, APIs, validation, and databases 🚀
#100DaysOfCode #FullStackDevelopment #BackendDevelopment #NodeJS #ExpressJS #TypeScript #WebDevelopment #LearningInPublic #ChaiCode #DaysCount #DAY1 #DAY28 #trendingsongs #100daysofadam
@Hiteshdotcom @piyushgarg_dev @nirudhuuu @surajtwt_ @yntpdotme
53
shower thought
In gateway scenarios, if io_uring submits mostly happen on the EventLoop, maybe IoOps can be reused to avoid one extra object allocation.
probably not a huge performance win, but jfr objectSample events might be a bit happier
1
1
6
314
Jun 3
🔥 How Netty's EventLoop actually works (and why it handles 10K connections on few threads)Netty's secret? Non-blocking I/O with a Boss-Worker model:• BossGroup → 1 thread that only accepts incoming connections • WorkerGroup → N threads that handle actual I/O read/write • Each EventLoop = 1 thread handling MANY channelsInside each EventLoop, it runs this infinite cycle:1️⃣ Select → poll for ready I/O events (epoll/kqueue) 2️⃣ Process I/O → handle read/write on ready channels 3️⃣ Run tasks → execute queued tasks 4️⃣ Run scheduled → fire timed/delayed tasks ↻ RepeatWhy this is powerful:• No thread-per-connection (1 thread → 1000s of channels) • Thread affinity — a Channel stays bound to one EventLoop forever (no locking needed) • Zero context switching for a given connection • Everything is non-blocking — thread never waits idleThis is why Netty powers Kafka, gRPC, Elasticsearch, Zuul, and most high-perf Java servers.#Java #Netty #SystemDesign #Backend
1
53
Jun 3
What is the Event Loop?
A little helper that keeps things moving, one at a time
open.substack.com/pub/aamira…
#JavaScript
#Coding
#Learn
#EventLoop
#Tech
2
2
29
Jun 2
Learning backend engineering concept after work: Explaining Event loops after I just learnt it.
#backenddeveloper #programmer #backendengineer #eventloop
May 30
It's time to really challenge myself.
I feel like a total beginner.
#100DaysOfBackendMastery
2
4
30
1,533
Day 01/60
Exploring Nodejs Internal Architecture In depth
- Event loop
- Event Queue
- Thread Pool
@lftechnology
#60DaysOfLearning #Backend #NodeJS #Architecture #EventLoop
23
Jun 1
21/
That is the Event Loop.
Completely.
From why it exists,
to how it works internally,
to what breaks it,
to how to fix it.
Save tweet 1 of this thread.
Come back to it when you need it.
If this helped you understand something that was confusing before,
repost it so other devs see it too.
Follow for more Node.js and backend content in plain language.
#NodeJS #JavaScript #BackendDev #WebDev #EventLoop #LearnToCode #Programming
22
我找到了一种办法不需要patch netty而是从eventloop入手把阻塞native transport挂到master poller上
虽然还是有一点点反射…要是iohandler可以暴露内部fd或许就不需要了…
1
1
77
May 28
ฝันที่เกินฝัน! กับการเห็น Stage ที่ “BAMBAM-JEFF SATUR-PP -TIMETHAI” มาแสดงด้วยกัน! เห็นมีหลุดสปอยล์มีการใช้สลิงโหนใดใด แล้วอยากดูสุดๆ
.
ใครยังไม่มีบัตร ยังเปิดขายที่ EVENTLOOP แล้วเจอกัน 20-21 มิ.ย. นี้ ที่ศูนย์ประชุมสิริกิตต์
#YOU2PLAY #THETITANSCONCERT2026
211
222
3,276
99% of JS devs get this wrong.
Nested setTimeout Promise chains. What's the output?
If you can nail this without running it, you truly understand the Event Loop.
#JavaScript #EventLoop #SDE1 #WebDev #100DaysOfCode
1
13
May 20
Looking like the NodeJS version of Promises/Microtask explosion starving the eventloop 😂😂
1
1
126
May 17
Most event-driven systems scatter state across queues, caches, and threads. “The Event Loop as a Single Source of Truth” argues for one clear authority instead.
Read More: zalt.me/blog/2026/05/event-l…
#eventdriven #architecture #eventloop #concurrency
110
May 17
Honestly, nothing good. JSC is horrible in a server setting. It's GC is crap. You'll see horrible spikes if running for a long time.
And libuv is unbeatable. No matter whatever eventloop they come up with another shiny language, libuv would always outperform, it's just too good
1
303
