article, chore, fix: (allying the enemy), (remove overflow from pre), (em to **)

4 files changed, 63 insertions, 5 deletions

diff --git a/articles/2020-05-15-debugging-the-installer.md b/articles/2020-05-15-debugging-the-installer.md
index 1f1c1e7..5c25a17 100644
--- a/articles/2020-05-15-debugging-the-installer.md
+++ b/articles/2020-05-15-debugging-the-installer.md
@@ -13,7 +13,7 @@ Paraphrasing from the repository's README;
 1. Clone repository.
 2. Install Luvit."
 
-Personally, I had some issues during the process of <em>attempting</em> to install Luvit. For whatever reason, when trying to install it via CMD, Powershell, or Bash, all had their fair share of problems. Eventually, the way I ended up installing it is opening the Powershell script which handles the installation process, inspecting what was going on, and manually stepping through it.
+Personally, I had some issues during the process of *attempting* to install Luvit. For whatever reason, when trying to install it via CMD, Powershell, or Bash, all had their fair share of problems. Eventually, the way I ended up installing it is opening the Powershell script which handles the installation process, inspecting what was going on, and manually stepping through it.
 
 First, when looking into the `get-lit.ps1` script which in itself, is the installer, the versions of Luvi and Lit look to be declared in variables, at the time, the versions were **2.10.1** and **3.8.1** respectively, this will come in handy later.
 ```ps
@@ -47,7 +47,7 @@ Finally, some of the last few steps seem to be performing a couple of Powershell
 
 I only can assume that by now, they have managed to fix this error, as I can't be the only one getting it, on that note, if you would like to install Luvit as well, please visit https://luvit.io/install.html and complete the installation process according to your operating system.
 
-<em>Continuing on the usage steps...;</em>
+*Continuing on the usage steps...;*
 3. Add the installed Luvit's binary directory to your PATH
 4. Install the [Discordia]() library via `lit install SinisterRectus/discordia` inside the cloned repository's directory...
 5. Replace the `PUT_TOKEN_HERE` field at the end of the file with your Discord application's bot token.
diff --git a/articles/2020-11-06-welcome.md b/articles/2020-11-06-welcome.md
index 7611cca..45296dd 100644
--- a/articles/2020-11-06-welcome.md
+++ b/articles/2020-11-06-welcome.md
@@ -5,6 +5,6 @@ date: 2020-11-06
 description: Welcome, read some, stay for more, struggle along side me.
 ---
 
-You're probably wondering what this is, well, quite honestly, I don't really know. I've been told that I tell good stories, by this, I think people actually mean to say <em>"I love to read through your struggles that you put in your source code."</em>... Oh, I couldn't agree more...
+You're probably wondering what this is, well, quite honestly, I don't really know. I've been told that I tell good stories, by this, I think people actually mean to say *"I love to read through your struggles that you put in your source code."*... Oh, I couldn't agree more...
 
-Well, if you want more of that but minus the <em>"having to sift through your source code"</em> part, stay for more!
+Well, if you want more of that but minus the *"having to sift through your source code"* part, stay for more!
diff --git a/articles/2020-11-11-allying-the-enemy.md b/articles/2020-11-11-allying-the-enemy.md
new file mode 100644
index 0000000..c63fecd
--- /dev/null
+++ b/articles/2020-11-11-allying-the-enemy.md
@@ -0,0 +1,58 @@
+---
+title: Allying the enemy
+route: /allying-the-enemy
+date: 2020-11-11
+description: Why I've decided to finally pickup <b>REDACTED</b> and some of thoughts and things that I'm looking forward to (and not so much looking forward to).
+---
+
+Here we are, me, finally letting in...
+
+For quite a while now, I've been a hardcore [React](https://reactjs.org/) junkie, not giving a single chance to the competition. But at last, I've given in.
+
+I say this with zero regrets, I will be spending the next few weeks learning Angular. Yes, [Angular](https://angular.io/), the most dreaded framework of all.
+
+# Here are a couple reasons for my decision, just to name a few;
+
+1. Angular is a **framework**, meaning that almost everything I will *probably* need to start out a production application should already come with the Angular framework, it just makes it seem cozy and prepared. Now I know that you are going to mention that due to the amount of features that come with Angular, there will be bigger bundle sizes, and from what I've researched, it doesn't make as big of an impact that people make it out to have.
+
+2. The Google ecosystem! (No political or ethical comments will be found here...) Google has everything you would ever need to ship a production application; the Google Cloud Platform, Firebase Analytics, and more! Angular easily integrates into the Google ecosystem and has a few Google specific goodies.
+
+3. [TypeScript](https://www.typescriptlang.org/)... the best thing to happen to JavaScript since [jQuery](https://jquery.com/) (subjective). Me, having come from declarative, statically typed languages, having a static typing system and conventions for JavaScript is amazing and makes me feel at home. A typing system which resembles Rust, a Java-like class system are a couple of the things that stand out to me.
+
+4. THE ANGULAR CLI!!! This tool is amazing, it is was React is missing in my opinion. Yeah there's create-react-app, but it's not the same in any comparable way other than the initial creation of the project files. The Angular CLI handles making new components, serving, building, and more. It's truly amazing.
+
+# Now, for some of the things that I will be missing from React;
+
+1. The simplest templating system of all the libraries/ frameworks. Of the UI libraries and frameworks I've ever taken a look at, React takes the cake when it comes to simplicity in the re-usability and templating aspect. For example, lets say I make a component which has a paragraph tag that just displays "Hello, world!";
+```jsx
+import { Component } from "react";
+export default class HelloWorld extends Component {
+    return <p>Hello, world!</p>;
+}
+```
+To use this in another component/ view, all I would have to do is import it and use it as if it a was a standard HTML element;
+```jsx
+import HelloWorld from "../components/HelloWorld";
+export default class App extends Component {
+    render() {
+      return(
+        <HelloWorld />
+      )
+    }
+}
+```
+As you can see, it is dead simple to reuse components wherever you want. In Angular, it's still *relatively **not super complicated***, but it was definitely a bit weirder if you are coming from React.
+
+2. Passing data between components. I still don't get this...
+
+3. Huge project directories. This is definitely a little scary if you are comparing it too a React directory, but I hope I'll get used to it. I mean, everything must have a reason right?
+
+# What I'm looking forward to?
+
+1. Learning about PWAs and the creation of them using Angular. Somewhat in reference to my first point of where I explained why I made my decision, Angular is a huge framework, and having PWA support basically out of the box is pretty nice.
+
+2. [AngularDart](https://github.com/dart-lang/angular). Though I don't typically use Dart, I have fun messing about with it, and I await to see how Angular and Dart can play together.
+
+3. Just all out, the process of learning Angular. Learning a new framework can always be a little daunting, but seen as there's so many resources out there for Angular, hopefully it'll be a breeze.
+
+Well, I hope you enjoyed my little update, hopefully, like I was, maybe this might inspire you React elitists to get up and try something new!
\ No newline at end of file
diff --git a/public/css/style.css b/public/css/style.css
index d1f1837..38923b9 100644
--- a/public/css/style.css
+++ b/public/css/style.css
@@ -103,7 +103,7 @@ pre {
   position: relative;
   left: -20px;
   padding-left: 20px;
-  overflow-x: scroll;
+  /* overflow-x: scroll; */
 }
 
 pre code {