Ah, Visual Studio Code—our trusty sidekick in the coding trenches. But wait, what's this? A delightful new feature designed to keep us on our toes: the 'Disable All Extensions for This Workspace' command. Because who doesn't love a good surprise, especially when it involves disabling all the tools we painstakingly set up?

Picture this: you're in the zone, about to format your document as usual. You hit Ctrl + Shift + P, type 'for', and expect the familiar 'Format Document' to greet you. But no! Instead, 'Disable All Extensions for This Workspace' has decided to make a guest appearance at the top of the list. How thoughtful! It's as if VS Code is saying, "Hey, let's make things interesting by turning off all your extensions without warning."

And the fun doesn't stop there. Once you've accidentally disabled all your extensions, there's no magical 'undo' button to save the day. Nope, you get the joy of manually sifting through your extensions list, re-enabling each one like it's 1999. And let's not forget the mandatory restarts—one to unload the extensions and another to load them back up. Because who doesn't love losing their undo history and breaking their workflow?

So, dear VS Code developers, thank you for adding a dash of unpredictability to our coding sessions. After all, who needs stability and consistency when we can have random command roulette?

Dear great ux lords at ms azure devops, could you make the whole freaking button clickable instead of just the text inside of the button?

Not sure if anyone appreciates but here are the new dR stats!

For more stats see comments.

Do you want to have your personal stats? Ask me, it's already generated. I only have to post it.

hitgub

Both suicidal children and children dying of cancer do the same thing from time to time: they mimic a bird’s last song. Three short whistles in rapid succession.
When I saw Marc for the last time, he was asleep. It seemed like I scared him: he woke up in panic, did the whistle thing, pulled the boomerang from under his pillow and started hitting that dark spot on his arm with it. The spot was melanoma, but he was too young to understand it.
He died three days later. Then, we found glass shards inside his stomach.

Well, shit is kinda hitting the fan literally.

Two of my four clients are closing down, and it all happened in a month.

Not really fearing for job security, but now I've scheduled an interview with nVidia that I dismissed two years ago. Let's see how it goes.

"AI coding tutor" is a real job. You're tutoring an AI. I think I'd rather go touch grass...

https://boards.greenhouse.io/xai/...

I don't know if AI makes people dumber. But it lends me to believe that people who swear by it might be dumber.

Time will tell how useful the code generators are.

I should go play with chatgpt today...

Currently having a stupid fight in my PR comments to remove dead code because I refuse to write a whole book to justify a cleanup commit.

WHY DID FEDORA REMOVE X11 !!! Really a bad decision from FESCO(fedora decision committee).
X11 is by a kilometer and a half (mile I think) away from Wayland and it's ugly do::from syntax that I always hated from CPP and RS.
X11 has simple basic functions and a good manual (https://tronche.com/gui/x/xlib/) well documented.

Functional programming in a one liner:

const value = (define_value, start) => value(define_value(start))

Alright, I've got a confesstion. It's a confession and a question, combined, get it?

Anyway, I've been a happy Linux user for over 20 years now, and I've used all kinds of graphical envs, from tiling wms like dwm and xmonad (I didn't care for hyprland, sorry if that's weird) to full DEs like kde, cinnamon, gnome, etc.

The "question" here is why do people hate Gnome so much? It's the one environment that I keep coming back to, especially now that my main machine is a beast, and RAM usage is nary a concern. Even then, my system is sipping RAM compared to KDE (running two docker dev environments, three browser windows with several tabs - one of which is streaming music, slack, and steam is sitting on the fourth virtual desktop, chilling), and I'm still at just over 18 GB of ram.Being able to push one single key/key combo, and type anything at all that is vaguely relevant to what you want to accomplish, and having that thing be instantly available (including searching for individual files) is super nice. Easy virtual and multi monitor switching is intuitive; little to no effort needed.

Even when I want to do other stuff, like play a game, or edit a photo, video, or some of my shitty musical-aspirational material - GNU+Linux with Gnome has been and continues to be the easiest, most neato way to get shit done.

Why the hate, gnome haters? Maybe you’re using it wrong?

I don't really understand all that love rust gets. It's syntax, better than C++'s, isn't better than C syntax.
You can make memory safe programs with C, just if you know how to manage memory, and you should only if you know how to. Bigger ecosystem for C/C++.
C23 waay better than any rs standard.

PS: I used both C/C++ and Rust

are there people that when you hang around them make you better in some way? which way and how?

Journalistic humour:

> "compensation is zero," the world's richest man wrote.

https://news.sky.com/story/...

City 17 is a joke compared to the amount of surveillance an average Android user is under every day.

Anyone in Arusha, Tanzania in Africa

We have a challenge project

I've only been using it for one day, but the most striking thing about going from VSCode to Neovim is the performance incrase.

VSCode has some noticeable input lag, but Neovim, even running in wsl2 (AN ENTIRE OPERATING SYSTEM VIRTUALIZED) has none.

That's sort of insane. An ENTIRE OPERATING SYSTEM is less heavy than a single instance of a bloated Electron app.

The absolute state of desktop development in 2024. Yes, VSCode is a fuckin amazing editor. But I can't help but think it's built like resources and performance were never truly a concern beyond "good enough".

Don't look too closely at the code for tools you use.

Its 50/50 great or garbage. Great way to accumulate side projects...

That moment when you spend hours debugging, only to realize... the bug wasn’t in your code but in your brain. Yup, I initialized the variable outside the loop and wondered why it wasn't updating. Classic me.

Moral of the story: Sleep is not optional, fellow devs. Also, coffee isn’t a fix for stupidity, but hey, it keeps us going! ☕