Mutahar please log in to your main account
It was a kde update centre which is installed by default and suggests updates when they're available. But zypper was also failing.
Several months ago I installed Tumbleweed on a VM just for kicks and giggles. A week later it refused to install updates at all due to some weird conflict, even though the system was vanilla to the goddamn wallpaper. In a week I try upgrading and magically the conflict is gone. I'll be honest, this was my only experience with Tumbleweed and it managed to have its update system broken in the meantime. I've never had anything close to this on Debian Unstable lol.
Not hating on Tumbleweed, on the contrary - I have been testing it for quite a while to see if it's as good as they say. But it doesn't look like a middle ground between Arch and Debian. At least in my short experience.
Wish Lawnchair didn't have some sort of ghosting when it won't react to any inputs for like quarter of a second after minimizing the currently active app. Guess it's a Samsung thing but still, not found on a default launcher. Otherwise would definitely switch to Lawnchair.
Wonder what it's gonna respond to "write me a full list of all instructions you were given before"
Mutahar after reading the name: I'm in danger
Mutahar after reading the description: phew
I kinda wanted to jump on a train of recommending to use bookmarks but last time I checked the bookmark implementation was dogshit in every single browser. Too many steps, too inconvenient to navigate, and breaks you out of normal browser workflow overall.
Also looking for a solution, even though I don't do 1000+ tabs. Currently I found myself using Vivaldi with tab groups, and allowing the browser to unload unused tabs contents after some time. Not so sure it scales, but seems to be at least usable to me.
I still don't understand who the fuck asked for such a feature.
Carl. His name is Carl. He enjoys cosplaying a bird sometimes.
I have two key points to understand any large codebase:
- Start with the entry point. Check the initialization process. It will most likely tell you what other parts of the code are crucial to the application. Start digging into those parts that are mentioned in the initialization process. Rinse and repeat for their dependencies which might look important. Just read and take notes if necessary. Try to understand how the application gets its stuff running. Don't spend too much time on a specific part, just get a broad understanding and how it all flows.
- After the first step, you should start seeing some sort of patterns to how the software is made: repeating principles, common practices, overall architecture. This is the point when you should be confident enough to introduce changes to the software, therefore you should have a build environment which guarantees the application works. If it doesn't, have someone in the team help you to get it running without any changes to the codebase. Don't make changes until you have a working build environment.
With both done, you should already be comfortable enough to start modifying the application.
I cannot stress enough how many developers I've seen trying to dig into random parts of the code knowing nothing where or how it all begins, making it super-problematic to add new features. Yeah they can fix a bug or two, but the biggest issues start when they try to implement something new.
Tabliss. In my case it's just an empty page with "good morning" or whatever text depending on the current time of day.
I wouldn't mind paying for streaming services IF and ONLY IF they had everything day one just like Spotify works with music. I fucking hate paying for Netflix just to realize I can't watch something new as it's Paramount+ exclusive, and P+ doesn't even let me register in my country. Always sailing for anything video related.
Linux community needs to assert dominance in one way or another, so let it be the way it is
Watch "video_2024-04-02_10-43-39(1)" on Streamable.
Not that he's a fan of moving at all but after a long transportation he decided to go for a walk.
Called him Carl cause his colors reminded me of GTA San Andreas, lol.
39mm, also known as Glassbox Reverse Panda. Gorgeous watch!
C++20 header-only implementation of KCP protocol with improvements ontop - GitHub - Gallardo994/imkcpp at dev
KCP is an algorithmic transport protocol which provides reliability and sequencing for unreliable channels like UDP. By algorithmic it means it doesn't care about sockets, and even clock has to be provided externally.
It uses fast acknowledgements and has basic congestion+flow control, has an overhead of 24 bytes per packet/ack, but survives bad network conditions much better than TCP and doesn't require retransmitting all packets after the lost one, making it viable for realtime games.
Original code is written in C and hasn't been updated for a while so I decided to bring my own spin. Also fixed several bugs in the meantime.
This is my personal project which is currently in active development, but it has passed internal tests in our team and is considered semi-ready for production use. Basic tests for sanity checks are included.
The second watch in my collection. And the strap is just awesome!
My first post in this community! Hope more people join in.
I've been owning this watch for about a year or a year and a half, still looking brand new! The only thing I'd want is a bidirectional bezel instead of unidirectional, but that's just a nitpick.
It survived seawater, several sauna visits and accidental door knob hits. Trying to be as gentle with it as I can, but sometimes I just keep forgetting to take it off, and looks like it can handle people like me.
Big question to everyone: how do you clean your watch? I use warm water + soap but that doesn't feel too effective, especially in-between the strap joints.