Clients, Servers & Scripts…Oh My!

In my programming tasks, I utilize JavaScript a ton, but how does JavaScript fit into the world around us, the web world and our various applications? In the past, there were people that were web designers and there were web developers. The two did not ‘speak the same language’. Those days are long gone. To be a good designer, you have to understand development and vice versa. For example, if a web designer is creating a modern interface, it is not uncommon to utilize a JavaScript UI library (jQuery UI, Script.aculo.us, etc.) to provide a rich internet application (RIA). If you do not have a solid understanding of JavaScript, you will run into difficulties in attempting to use these resources. 

So where does JavaScript fit into the puzzle? JavaScript has been around a long time and is a mature language. It is an interpreted language. What that means is each browser has a JS Interpreter built in. When the browser hits JS code, it asks the interpreter to take over and tell the browser what it means. This is different than a compiled language, such as C# or Java. These languages are compiled into packages before their code can be executed.

JavaScript is traditionally a client-side language. What that means is the code is read on the end user’s machine within their browser, not on the web server. I say traditionally, because over the past several years, there has been a growth in server-side/enterprise JS and JS libraries (Node, Dart, TypeScript). Let’s stick with the traditional usage, however. So, on the client-side, we use the browser, which combines our content (HTML), style/layout (CSS) and our functionality (JS) to provide the web site experience. I call this the ‘three-legged stool’ of a web app.

In my programming, I have typically found that the more I do on the client-side, the better my application performs. This is due, in part, because we do not have to go across the network of the internet. This does not de-value the need of a server-side language component. In fact, all of my applications have a server-side component that provides the business logic. 

I hope this high-level look at JS and the role it plays in the web space helps clarify things for you. If you have any questions, let me know.

Happy Coding!

Clay Hess

More To Explore

computer, laptop, work place-2982270.jpg
Code

Unlocking Wireless Communication: A Dive into the Bluetooth API

Wireless communication has become an integral part of our daily lives, and Bluetooth technology is at the forefront of this revolution, enabling devices to exchange data over short distances and creating a world more interconnected than ever before. At the heart of this technology lies the Bluetooth Application Programming Interface (API), a powerful tool for developers looking to harness the capabilities of Bluetooth in their applications. In this blog post, we’ll explore what the Bluetooth API is, how it works, and the possibilities it opens up for innovation in wireless communication.

lighthouse, beacon, atlantic-8578318.jpg
Code

Understanding the Beacon API: Simplifying Asynchronous Data Transfers

In today’s data-driven world, web applications often need to send data back to the server. Traditionally, this has been done using AJAX requests or similar methods. However, these techniques can come with a cost, especially when dealing with data that needs to be sent during the unload phase of a document, such as tracking and diagnostic data. This is where the Beacon API shines by allowing developers to send data to a server more reliably and efficiently.

Share This Post

small_c_popup.png

Need help?

Let's have a chat...


Login

Jump Back In!

Here at Webolution Designs, we love to learn. This includes sharing things we have learned with you. 

Register

Begin Your Learning Journey Today!

Come back inside to continue your learning journey.