Exactly

lol

+1 lol

that is annoying asf

its not really funny because theres 500 other things about programming everyone assumes you know

Oh! Cool! I'm glad to be of help :)

Wow! Thanks, and yeah, I suppose so.

I appreciate the compliment, that is encouraging!

Haha, you're welcome.

Haha, thanks! I can't save your life, though, only Jesus Christ can do that.

Haha, you and me both; There are so many things that I don't fully understand.

Indeed, there are many, many things so that it can be easy to miss some basic things. I, too, have been thinking about web development lately and feeling I should probably learn some more of the basic things. I mean I literally don't even know how one typically sends an HTTP request back to the server that served the webpage in order to have some interplay between the webpage and the webserver. I mean, I realize it's probably extremely basic, and that I could probably even get away with simply running an HTTP server on a port and opening said port, and then sending requests to that open port, however something about that seems incorrect and there must be a "correct" and "professional" way of doing it! I must know! I also learned, recently, that one of the HUGE gaps in my understanding when I studied Computer Science at University (almost 10 years ago now) was simply that Java had already built a webserver & HTTP server program and the JSPs and JSFs of which I was learning was related completely and only to those particular Java programs that served your webpage; That is to say, I hadn't even learned what a "typical" webserver might be and I was already trying to grasp this "JSP, JSF" concept that was ONLY USED by this particular suite of Java server programs. Needless to say, I was completely confused, didn't understand ANY of it, and only recently did I even begin to grasp what a "webserver" program might even be considered. Now I also would like to learn more about Nginx and some of the other "professional" webserver programs out there as I would like to rectify my gross misunderstandings from nearly a decade ago.

You're welcome!

Hello! I'm glad that I could be of help. So as not to cause confusion, just about everything you'll encounter will have an OS sitting between the CPU and the code that you'd like to execute. Typically a cloud based service that you might "spin up" is running on some kind of virtualization software which is a fancy way of quickly installing and running another OS ontop of the OS that you already have running and installed. Virtualization is a pretty deep subject that's kind of new to me, but it's interesting. I hope that helps clarifies some things and answers your question!

I'm glad I could be of help!

Just had one question Nodejs or Golang

I'm glad! You're welcome!

Useful @ 2023

You're welcome!

You're welcome! Thanks for watching!

You're welcome! I'm glad that was helpful.

thank you so much 🤝, now i got clear picture

No, node is abstracted away from the browser. I think node is actually built from components that you would find in the browser. You can run javascript code outside (edit: the) browser on node, as if node was a "JRE" that consumes javascript code rather than java's bytecode. If you wanted to, you could run node completely on the backend / server. You could run it "where-ever you want", although that mostly means any where you can install node and boot it up.... so probably only your "backend".

Hahaha, how do you think I ended up here?

Haha, yessir. Clojurescript provides support for the Clojure programming language in the front-end / web browser (which is almost always written in Javascript). I think it would deserve it's own video to explain it a bit better, so in lieu of a more appropriate explanation I'll leave a link to their website. Interestingly enough, the Clojurescript website states that they do indeed use the CLOSURE Google compiler and library to optimize their trans-piled Clojure code. clojurescript.org/

That's a good question. I think someone wanted to run Javascript outside of the browser!

​@@hwilliampolenz6713 Sounds awful. Do you still use it? it seems to be heavily used and promoted. There must be some reason its used so much. I'm learning JavaScript as a necessary evil. I sure wouldn't want use it outside the browser where other things can be used.

@@lack76 Hmm.... interesting points. I use node in one project, however I haven't used a back-end / webserver framework yet for that project, but I probably will end up using some degree of Javascript on the back-end. Personally, most of the technology choices for me had more to do with ease and legacy code. For instance, since one project had originally been built with a mix of Python and Ruby for the back-end, I will probably continue to use those languages for the project as it's extra effort to switch to a different language and the associated libraries and frameworks. ...

@@lack76 ... I agree that you'll definitely want to learn Javascript for any kind of web-based or browser based application. You don't necessarily need to know it for the back-end, although in some sense it's easier as you won't need to learn another language to operate a back-end. You can just continue using Javascript with a node based back-end framework like Express or one of the others frameworks that you prefer. I think it's almost definitely necessary to learn Javascript for browser based applications and therefore the vast majority of developers will need to learn it and so consequently this same majority of developers can save some time if you don't need to learn yet another language to manipulate the back-end. I am guessing this is at least one of the impetuses for creating node.js and allowing Javascript to operate outside of the browser.