Skip to main content

Java is dead?

During my college days, I had a gut feeling that Java would die pretty soon, but it wasn't. My reasons were:

  1. Java was locking me down on unnecessary OOP
  2. Too lengthy programming as in C++
  3. Slow JVM
After long time, my gut feeling is becoming true with reason #2 mentioned above. This space is now getting bitten by:
  1. Scala (pronounced skaa-lah or skey-lah)
  2. Clojure (pronounced closure)

Comments

Popular posts from this blog

Madurai food Vs Nagercoil food

There's huge cry that Madurai idlis are best. Having stayed in Madurai for 7-years, I can give assurance that they're crap. Madurai foods (especially available in hotels) are of poor hygiene and poor in taste. But, I always like the people--they're friendly and helping. My favorite is always Azad Hotel's (Nagercoil, near Tower Junction) chicken kothu parotta . Nagercoil food like aviyal , samba (red) rice , etc are always good and healthy as they're cooked in coconut oil and with high hygiene--even in hotels.

Solved: "Ports" Tab Not Visible in VS Code (WSL2)

None of the solutions I found on Reddit or GitHub worked, and most of the related GitHub issues were locked. So I'm documenting this here for future reference. Problem When using WSL2 in Visual Studio Code, the Ports tab—needed to access your application in Windows browsers like Chrome or Edge—doesn't appear. Even the Ports-related options are missing from the Command Palette. Solution After a lot of trial and error, here's what worked: Run npx serve in the VS Code terminal. It will output a URL such as http://localhost:3000/ . Click the link (or use the Follow Link option). This will open the app in your default browser. You may notice that it opens on a different port (for example, http://localhost:64198 ). At this point, the Ports tab becomes available in VS Code. After this initial trigger, the Ports tab seems to remain available in future VS Code...