Hi Sandeep, I have been an early enthusiast of your community features. I keep coming back once a year or so. Last year I opened a dev.to account simply because of its popularity. I wanted to feel for myself. I quickly closed my account once I realized the exact fundamental difference you alluded to here. Why then do I login once a year then, you may ask. Well, I feel like it's a bit cliche, but if I could have my personal blog look like the Hashnode user profile page or the homepage itself, Hashnode's differentiation would be complete (in my opinion). Until then, I will keep checking in once a year. I like what you have done with the UI/UX.

Java or Kotlin sounds to me like the choice of a human language to, say, write a book. Personally I'm still a Java fan for the foreseeable future (at least until I'm affected by its limitations). Now... having said that, I know Oracle and Google had issues over the use of Java, which pushed Google to weigh its options. I tweeted that Google would unveil a new programming language. At the time what I didn't know was Kotlin having an existing and vibrant community in the JetBrains family of IDEs and developer tools for Android. But given that Kotlin, or Java, aren't the only choices for Android development in 2018 it makes perfect sense for Google to continue to look into their other options going forward. Ultimately the direction is dictated by the users themselves. Native vs Hybrid apps is the next tug-of-war.

@Job and @Dmitriy, after looking into issues on gitlab, kubernetes, and GCP online, I found out that after entering http://<cluster-IP>/ui in the browser it automatically resolves to https://<cluster-IP>/api/v1/namespaces/kube-system/services/kubernetes-dashboard/proxy ... And that's the error (at least for me). The fix is to edit the "proxy" at the end and place it here https://<cluster-IP>/api/v1/ proxy /namespaces/kube-system/services/kubernetes-dashboard/ . In a few words that's how I got it to work. After I was able to copy the ca.crt and token into my gitlab configuration. I can now breathe a little -staging passed, yay!... but I can't open the staging URL 😒. I guess I gotta figure out how to access the pods in the browser. From gitlab.com I am able to make a few edits from the staging terminal, but I can't temporarily view them in the browser using the generated URL. Any pointers?

Hey @Dmitriy... before I make another attempt, I gotta let you understand that GCP is deprecating the Kubernetes dashboard. So I access my secrets using kubectl CLI kubectl describe secret/<default-secret> -o yaml . How badly copied can it be?

Hey @Job, I'm working with the default ca.crt PEM in secrets. Is it self-signed? If yes, is that why staging is rejected? I don't mind filing an issue, but I also want to take this opportunity to have a real one-on-one on this live AMA.

I just created a fresh GCP cluster, successfully linked it to my gitlab.com project settings (under Kubernetes integrations) and now I'm a bit confused by a failing "staging" job that returns Unable to connect to the server: x509: certificate signed by unknown authority ERROR: Job failed: exit code 1. Btw, I'm following this tutorial ( https://www.youtube.com/watch?v=PoBaY_rqeKA ) and I can't go past editing the.gitlab-ci.yml config file KUBE_DOMAIN value which is the IP of my Kubernetes master. Any reaction is most welcome. And yes I did a kubectl describe -o yaml and copied the ca.crt and token values into the appropriate fields.

Thank you @lorthirk Turns out that group and version in the vector declaration are optional. I got this from the book "Gradle - Beyond the Basics" by Tim Berglund (on page 51).

I also do that a lot... it's a bit odd I think. Is there a more "intelligent" way?

EDIT March 1, 2020: A lot has changed since then... Go it is! JavaScript. Simple. If I was having this conversation with Marty McFly, I would tell him you can develop a full-stack with JS only. I think a lot of developers tend to take this awesomeness for granted. Just imagine Marty's face when I tell him...