

Agreed and I have domicile in a country that provides improved, though not perfect, protections. But it still tempers my views of the organization.


Agreed and I have domicile in a country that provides improved, though not perfect, protections. But it still tempers my views of the organization.


It is quite good and hopefully one of the privacy forks will rise victorious. But yeah, nothing will ever topple neovim and emacs.


I have found a few communities on Matrix that fit that bill to some extent. For some reason they don’t devolve to “general chat” as quickly as most software related Discord servers do, in my experience.


Ha. I still have an open PR on that.
Not at all. Tongue was firmly in cheek. I work with jvm professionally. I was specifically trying to clarify that I find the beam vm exciting but not jvm and was therefore just kidding around when I made the first comment. Not gate keeping at all. Like whatever you please.
I won’t argue that isn’t true. I’m just saying beam is a value prop that speaks to me. Jvm isn’t, but objectively is for sure.
At least there is a good reason to use elixir. Beam.


What funny is it is Mozilla giving away free cookies with a sign that says, “Only accept my cookies”.


Actually going this year. Have wanted to for many. Really looking forward to it.
Modelling how you want to handle trust in your architecture doesn’t have a best answer really. Many ways to pet a cat, and all that jazz. Some prefer to trust only end to end, meaning not just establishing trust at the API entry, but all the way to the backend. There are arguments to be made for doing it either way. As long as your services behind the API gateway are in a private network, it is maybe okay to establish complete trust here and you could even terminate TLS and use clear communications. Another more secure pattern is to authenticate the call to the API, authorize which backends can be called, then verify the source caller in the backend as well.
There are many public sector organizations that need programming done. There are also organizations that back FOSS work. However, if it can’t involve devops, cloud, or containers, I don’t know how much will be left for you to do. There are tasks that don’t involve those, but they’re few and far between. And anybody who said those aren’t part of “REAL programming” wouldn’t get a second listen from me in a hiring scenario.


Might want to check out !fedigrow@lemmy.zip. They link to some resources for sharing this or growing the new community.
I think most communication errors are on behalf of the speaker, so that’s on me. Rereading, I can see how it would come off that way, but it wasn’t intended.
There are only a few communities where the sum total of several instances of saving a few keystrokes would be appreciated candidly. A bunch of nerds talking about code sharing are the vim golfers of the world.
I was being completely genuine. That was just pure gratitude.
Thank you. I knew there was a better way. At first I just put code_review@programming.dev, which of course wanted to be a mailto:. This is the kind of optimization I seek. You save us 2 keystrokes, and this is the sort of community that appreciates that.
There is a community /c/code_review@programming.dev. It isn’t busy, but it should be. But posting stuff here will get far more eyes.


How about you do experimentation, then share anything to support your claim.
I suspect they draw a distinction between using their built binary and logged in services like collaboration from the editor code itself, but iinal.