p5v

It's one thing having to download this monstrosity, and a whole other, having to use it daily to write code.

Before you answer with a loud "No," this isn't a question that asks for facts. Of course, it didn't. But also, we also know that the underlying theories behind LLMs and other artificial intelligence techniques are not new; some date back to much earlier. Plus, there were efforts on both sides of the Cold War sectrum to build a supercomputer "to rule them all."

Thus, if we imagine that the scope of my question is in the context of a parallel reality hard-sci-fi story, how plausible would it have been for any side to advance over the other with any form of artifical intelligence (as rudimentary as it may have been)?

This is something I’ve been asking myself a lot lately. When you look at the 80s, particularly in Europe, you see much of the same conflict between generations, a Cold War threatening to wipe out the world at the push of a button, Chernobyl, the beginning of people’s realization that yeah, maybe the climate is not doing well.

So, the youth protested. Much like it does today, but it seemed more hopeful about the future.

So, I’m wondering what parallels and lessons a young person from the 80s can draw to a Gen-Z-er.

For context, I am talking about Red Hat's Quarkus framework - the one that Red Hat famously markets as the future of cloud-native Java microservices. My experience suggests that Quarkus is just as capable for building good old monolithic web apps, the way Spring Boot famously does. Perhaps, even better, thanks to the thousands of tiny performance optimizations.

Last year, I took Quarkus for a spin, and built https://feedle.world/ pretty much in one go. The experience was great, and I didn't feel like I was missing much from Spring Boot. Qute is a fantastic templating language tailor-made for Quarkus, and combined with some HTMX and Alpine.js, it's a combo made in heaven.

I was wondering if anyone is using Quarkus to build (predominantly, non-microservice) web apps. Feel free to showcase them here and share your experience.

As someone who has spent the better part of the last 5 years working with Go, I can't help but notice the waning enthusiasm in considering it for new non-cloud projects. There was a time when people would get excited about choosing Go for a new project, regardless of it being a CLI tool, a Web application, or some system-level infrastructure. Looks like all three are getting well-covered by Rust these days. On the other hand, good old stacks like Java and .NET are not sleeping either, and improving all the time.

All of this makes me wonder - where is Go actually heading? Not now, but in like 5 or 10 years? Will people be as excited in building new applications with it, or will it niche itself into "that cloud and microservice thing" made by Google that we have to maintain, because a few large projects decided to use it a decade ago?

What do you think? Do you see a bright future for Go, or is it more like "it's going to be more of the same"?