??Log 1: How I developed SRON?

Saksham Rapid Object Notation, a high-level, procedural, dynamically typed and compiled + interpreted programming language which provides easy and expressive syntax along with insane speed surpassing Java, Python, C#, JavaScript and even C in many cases.

I, Saksham Joshi, the developer of this amazing programming language, am going to reveal the secrets of becoming a proficient developer. So, let's start...

As I had much experience in developing mini projects, I know some practices to develop projects that are easy to maintain and are optimized.

I got the idea for SRON when I was getting bored during a lecture in my bachelor's classes. At that time, I just decided to make it an interpreted programming language with a syntax similar to JSON. Getting such a crazy idea, which is beyond anyone's expectations, is exciting. I would say that due to daily meditation & yoga and a disciplined life, I got such an idea.

On September 5, 2023, I started working on SRON, but before writing code, I had to decide on a name for it. I decided to put my name "Saksham" in it, and I wanted to make it fast, so it took the word "Rapid". Because I took inspiration from the syntax of JSON (JavaScript Object Notation), "Object Notation" came from that, and that's how SRON got its name.

During October 2023, on someday suddenly my laptop stopped working properly. The screen would get stuck, and then the blue screen error would show up, displaying that it was a KMODE_EXCEPTION, and then even the blue screen would stick. I was completely stunned by what had suddenly happened.

I took my laptop to the Official Service Centre of Asus in Haldwani (Uttarakhand, India), and they fixed it, but my laptop started doing that again. I felt so bad because this was just the start of SRON's journey, and I wasn't able to work.

Then, I actively researched on the internet about this problem and came to know that this was happening due to some hardware failure. I didn't open my laptop for 20 days, and then I somehow gathered the courage and opened it in safe mode. I downgraded Windows 11 to Windows 10.

Suddenly, I got the intuition that this error must be happening due to the graphics card because displays and graphics are handled by it, so it must be a hardware failure of the graphics card. I turned off the automatic update of all the drivers, uninstalled Nvidia's graphics driver, and installed Intel's basic graphics driver, which uses the processor to load and refresh graphics on the monitor.

Guess what? This actually worked, and now my laptop was working fine. Then I took a break from programming and refreshed my mind by visiting my home and spending some good time with my family. Along with this, I always brainstorm on how I could develop it and what features it must have.

Initially, I decided to make it statically typed and interpreted, but during development, I realized that making it statically typed would result in extensive type checking at runtime, increasing memory and power usage on a whole other level. Then, I made the big decision to make it dynamically typed.

After my exams, on January 11, 2024, I started working again on SRON with a clear mind. Then the hardest journey started!

How did I implement datatypes like Any, Int, Double, Char, String, and List? Why did I make it compiled + interpreted rather than interpreted only? Why SRON is so fast? You will get answers to these questions in the next newsletter, publishing on June 30, 2024 (Sunday).

Thanks for reading this Newsletter! Make sure to subscribe this newsletter and download SRON from bit.ly/SR_ON. Follow and connect with me for more such interesting and knowledgeable content.