Observability is a capability my last employer really fucked up. I would have loved this power.
Trying to figure out wtf is going on with database locks, or celery tasks you can't find in the dashboard, was like blindfold surgery.
Fat chance that team would use elixir, though. Nothing more esoteric than python.
Second draw.io - I've done lots of diagrams with VSCode and the draw.io plugin
Excellent - I'm about to install it for my aged mother, because windows keeps moving her cheese.
I want something that doesn't change the workflows once she's learned how to do a task, and that local techs can help her with, and that I can VNC to when I have to.
I used a Sidewinder keyboard for years with programmable macros.
Yeah, I had my password as a macro.
Dick move on my part as the macro, I'm fairly sure, is stored in plaintext on the PC. But the convenience was great. I don't do that any more.
I'm a native English speaker. I can't understand your comment. I sense that you have a useful perspective, could you rephrase it so it's understandable?
Think of the lexiconsequences
Maybe not. But that was before he was president for four years - fuck, it's still crazy to think that happened - and really forced people to acknowledge that yeah, he is a pathological liar who doesn't give a shit about the country.
A lot of people still suck on the tit. But a lot of others recognise that the hot pain comes from getting burned.
You had all the tea party nutters for years - but none of them became president.
The bit about "secret" whatsapp messages is alarming.
when Steve Jobs built the first Apple computers in his garage
Just erase Wozniak from history huh
the translation step from binary (program) -> text (SQL) -> binary (server)
Your concern about this is misguided. Inter-process communication always has to cross a barrier, by definition.
I take it http also feels wrong to you?
Binary protocols do exist, e.g. gRPC, but they incur costs of their own.
Shame I had to scroll this far to find PRQL
No! Bad dev! No biscuit!
Never merge master into a feature branch. It's called a "wrong-way" merge and it makes the history fucking awful.
You shit in the face of project maintainers when you do this.
You may not care, in fact many don't. Also people buy timeshares, read celebrity gossip magazines, and vote for scumbags. They are fucking idiots who don't know what they are doing. So are people who leave wrong-way merges in shared history.
In fact, wrong-way mergers are worse, because you can't just ignore them - git blame rubs your face in their shit, so they shit in your face forever.
Just don't fucking do it, OK? Or I will hit you in the throat with a cricket bat soaked in wasps. As a first warning.
You are correct, it's a warm and helpful community... except for the people who like the smell of their own farts.
Lemmy is better. But reddit is lousy with ignorant twats saying bullshit like "Linux is just a superior philosophy", but who have never written a line of C or C++ in their lives. They know nothing about system design or computing history. They make claims about windows that apply equally to linux, or vice versa. They use terminology in a nonsensical context. In short, smug fools. It's not unwelcoming so much as unappealing.
The best thing about Windows is that no-one is smug about using it.