Is GLFW "open loop" versus glutMainLoop?

After "using glut " for less then a weak I realized that “glutMainLoop” is difficult to control eternally. I call it “closed loop”.
My very first question to the forum , before I ditch “glut” -
Does GLFW runs “closed loop” AKA not user friendly to eternal events?
By events i do not mean keyboard , mouse ect.

For example - can I SIMPLY change window text after I get data via socket ?
Can I run my application independently of GLFW “updating (graphics) window contents”?

Here’s a link to a simple GLFW example.

As you can see unlike GLUT you have complete over flow control. You can register callbacks for events but GLFW leaves the main loop to the developer to implement.