Migrate development environment from Windows to macOS and continue project updates

- Shifted primary development environment from Windows to macOS to ensure better performance, stability, and streamlined workflow for Java development.
- Removed OS-specific metadata and ensured platform-agnostic project compatibility.
- Normalized line endings to LF for cross-platform consistency.
- Verified and adjusted file paths, permissions, and encoding settings to suit macOS environment.
- Cleaned up unnecessary Windows-generated files and updated Git configuration accordingly.
- Future commits and development will now be
managed entirely from macOS.

This migration ensures a cleaner, more consistent
setup moving forward and prepares the project for
scalable development across Unix-based systems.

Future development will continue on macOS for a
smoother, Unix-based experience.

Signed-off-by: Someshdiwan <[email protected]>

Author: Someshdiwan

JavaEvolution-Learning-Growing-Mastering.iml

@@ -0,0 +1,13 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<module type="JAVA_MODULE" version="4">
+  <component name="NewModuleRootManager" inherit-compiler-output="true">
+    <exclude-output />
+    <content url="file://$MODULE_DIR$">
+      <sourceFolder url="file://$MODULE_DIR$/Section27NetworkProgramming" isTestSource="false" />
+      <sourceFolder url="file://$MODULE_DIR$/src" isTestSource="false" />
+      <sourceFolder url="file://$MODULE_DIR$/JAVA8" isTestSource="false" />
+    </content>
+    <orderEntry type="inheritedJdk" />
+    <orderEntry type="sourceFolder" forTests="false" />
+  </component>
+</module>

Popular interview question What is.txt

@@ -0,0 +1,31 @@
+Popular interview question: What is the difference between Process and Thread?
+
+To better understand this question, let’s first take a look at what is a Program. A Program is an executable file containing a set of instructions and passively stored on disk. One program can have multiple processes. For example, the Chrome browser creates a different process for every single tab.
+
+A Process means a program is in execution. When a program is loaded into the memory and becomes active, the program becomes a process. The process requires some essential resources such as registers, program counter, and stack.
+
+A Thread is the smallest unit of execution within a process.
+
+The following process explains the relationship between program, process, and thread.
+
+The program contains a set of instructions.
+
+The program is loaded into memory. It becomes one or more running processes.
+
+When a process starts, it is assigned memory and resources. A process can have one or more threads. For example, in the Microsoft Word app, a thread might be responsible for spelling checking and the other thread for inserting text into the doc.
+
+Main differences between process and thread:
+
+Processes are usually independent, while threads exist as subsets of a process.
+
+Each process has its own memory space. Threads that belong to the same process share the same memory.
+
+A process is a heavyweight operation. It takes more time to create and terminate.
+
+Context switching is more expensive between processes.
+
+Inter-thread communication is faster for threads.
+
+Over to you:
+
+Some programming languages support coroutine. What is the difference between coroutine and thread?

Process vs Thread.gif

@@ -0,0 +1,82 @@
+Absolutely! The `sw.js` file (short for **Service Worker**) is the **brain behind a Progressive Web App (PWA)**. It's a JavaScript file that your browser runs in the background — separate from the main page — and gives your site **offline capabilities, background sync, and faster performance through caching**.
+
+---
+
+## 🧠 In Simple Terms:
+Think of `sw.js` as your site’s **“offline assistant”**.  
+Even if your user loses internet, the service worker helps show pre-cached pages and assets.
+
+---
+
+## 🔧 What `sw.js` Typically Does:
+
+| Function | Description |
+|---------|-------------|
+| **Install** | Runs once when the service worker is registered. It's used to cache important assets. |
+| **Activate** | Cleans up old caches and takes control of pages. |
+| **Fetch** | Intercepts network requests and serves from cache (if available), otherwise from network. |
+| **Sync** *(optional)* | Used for background syncing when a user goes offline and comes back later. |
+| **Push** *(optional)* | Handles push notifications if integrated with a backend/server. |
+
+---
+
+## 🛠️ Example Use Cases:
+
+1. **Offline Support**  
+   - Cache HTML, CSS, JS, and images.
+   - When offline, the service worker can show cached content.
+
+2. **Speed Boost**  
+   - Load from cache instead of waiting for the network = faster performance.
+
+3. **App Shell Model**  
+   - Load static parts of the site immediately, then fetch dynamic parts.
+
+---
+
+## ✍️ Your current `sw.js` (simplified):
+
+```js
+self.addEventListener("install", function (e) {
+  console.log("Service Worker Installed");
+});
+
+self.addEventListener("fetch", function (e) {
+  // Just lets all requests go through as normal (no caching yet)
+});
+```
+
+This just logs install and allows fetch requests.  
+→ No caching or offline functionality yet.
+
+/*
+const cacheName = 'java-evolution-cache-v1';
+const assetsToCache = [
+  '/',
+  '/JavaEvolution-Learning-Growing-Mastering/index.html',
+  '/JavaEvolution-Learning-Growing-Mastering/assets/style.css',
+  '/JavaEvolution-Learning-Growing-Mastering/assets/script.js',
+  // Add more files as needed
+];
+
+self.addEventListener("install", (event) => {
+  event.waitUntil(
+    caches.open(cacheName).then((cache) => cache.addAll(assetsToCache))
+  );
+});
+
+self.addEventListener("fetch", (event) => {
+  event.respondWith(
+    caches.match(event.request).then((response) => response || fetch(event.request))
+  );
+});
+*/
+
+/*
+self.addEventListener("install", function (e) {
+  console.log("Service Worker Installed");
+});
+
+self.addEventListener("fetch", function (e) {
+  // Just let requests pass through for now
+});*/

Progressive Web App (PWA).txt

@@ -0,0 +1,89 @@
+
+/*
+const cacheName = 'java-evolution-cache-v1';
+const assetsToCache = [
+  '/',
+  '/JavaEvolution-Learning-Growing-Mastering/index.html',
+  '/JavaEvolution-Learning-Growing-Mastering/assets/style.css',
+  '/JavaEvolution-Learning-Growing-Mastering/assets/script.js',
+  // Add more files as needed
+];
+
+self.addEventListener("install", (event) => {
+  event.waitUntil(
+    caches.open(cacheName).then((cache) => cache.addAll(assetsToCache))
+  );
+});
+
+self.addEventListener("fetch", (event) => {
+  event.respondWith(
+    caches.match(event.request).then((response) => response || fetch(event.request))
+  );
+});
+*/
+
+/*
+self.addEventListener("install", function (e) {
+  console.log("Service Worker Installed");
+});
+
+self.addEventListener("fetch", function (e) {
+  // Just let requests pass through for now
+});*/
+
+
+
+Absolutely! The `sw.js` file (short for **Service Worker**) is the **brain behind a Progressive Web App (PWA)**. It's a JavaScript file that your browser runs in the background — separate from the main page — and gives your site **offline capabilities, background sync, and faster performance through caching**.
+
+---
+
+## 🧠 In Simple Terms:
+Think of `sw.js` as your site’s **“offline assistant”**.  
+Even if your user loses internet, the service worker helps show pre-cached pages and assets.
+
+---
+
+## 🔧 What `sw.js` Typically Does:
+
+| Function | Description |
+|---------|-------------|
+| **Install** | Runs once when the service worker is registered. It's used to cache important assets. |
+| **Activate** | Cleans up old caches and takes control of pages. |
+| **Fetch** | Intercepts network requests and serves from cache (if available), otherwise from network. |
+| **Sync** *(optional)* | Used for background syncing when a user goes offline and comes back later. |
+| **Push** *(optional)* | Handles push notifications if integrated with a backend/server. |
+
+---
+
+## 🛠️ Example Use Cases:
+
+1. **Offline Support**  
+   - Cache HTML, CSS, JS, and images.
+   - When offline, the service worker can show cached content.
+
+2. **Speed Boost**  
+   - Load from cache instead of waiting for the network = faster performance.
+
+3. **App Shell Model**  
+   - Load static parts of the site immediately, then fetch dynamic parts.
+
+---
+
+## ✍️ Your current `sw.js` (simplified):
+
+```js
+self.addEventListener("install", function (e) {
+  console.log("Service Worker Installed");
+});
+
+self.addEventListener("fetch", function (e) {
+  // Just lets all requests go through as normal (no caching yet)
+});
+```
+
+### 🔍 This just logs install and allows fetch requests.  
+→ **No caching or offline functionality yet.**
+
+---
+
+Let me know if you're ready to upgrade it to support **actual caching**, and I’ll guide you step by step or give you a clean caching-enabled version!