Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)UR
Posts
1
Comments
378
Joined
2 yr. ago

  • Overall, I think I prefer elixir, but is probably choose go as well.

    Not just ease and performance but popularity. I could be happy in only go for the rest of my life. Currently a Rust dev and I don't know if I can spend the rest of my life with lifetimes. They are an emotional challenge..

  • It's only worth it if you're planning to work in Java or one of the other JVM languages.

    If that's what you are striving for, is worth it to spend the effort ahead of time. If your goal is more agnostic to tech stack, learning Spring Boot won't be worth it until you land a role that uses it.

    It might be worth dipping your toes in the water anyways. But frameworks like that shouldn't be bothered with without inherent interest or need.

    Personally, I've no interest in working in Java, Scala, or Kotlin so I'll skip it.

  • I think Chrome OS did an excellent job of achieving what it set out to do. Which was be a low profile closed ecosystem meant for people who just need to surf the web.

    I won a Chromebook in a drawing and used it fairly regularly until my wife co-opted it as her own.

  • This was my thought. Bethesda games are considered great because of the modability. Until the tools are released it seems like a hassle to do anything more than simple. Especially knowing that it will just be replaced when the tools come out.

  • I figured it was something like that. I don't think anybody in the industry believes kubernetes is even close to a great solution (it is a good one, just not great), but it's mature enough that it solves most business needs well and there aren't any good alternatives that I've seen.

  • It's not that an Amazon instance can be a docker container. It was more that the behavior you are describing is extremely odd for a full Linux environment but normal for a docker container.

    If you created the instance, it isn't likely a container. But it also sounds like the base image might be poorly set up

  • Well, the docker command wouldn't exist inside of a container. You could use uname to check the system info.

    How is it you don't know this information about a system you've connected to?