Actual Problem: C → Segmentation Fault
Actual Problem: C → Segmentation Fault
My system was configured perfectly one day, then I started vi and now I can’t exit. Send help.
Honestly, vscode opens in a split second for me, faster than I can react and start typing. For all intents and purposes it is instantaneous. Granted my setup is extremely clean and I only have the barest extensions installed for my workflow. The performance is consistent in my Windows, macOS and Linux machines.
I can’t imagine it running slow at all (perhaps someone with hundreds or thousands of extensions would). The last two editors I could recall that took the whole of eternity in the time space continuum to load were Eclipse and Atom. And those were slowass right out of the gate with zero extensions or plugins.
Best I can do is a JPEG of a goat, but singular. One goat.
This man is too dangerous to be left alive.
If it fits you must acquit!
+1 for bottom, I aliased top to it.
But are you even a real programmer if you don’t test in production?
If it’s not Hannah Montana Linux, I don’t want to hear another word of this.
A man after my own heart.
I had a whole bunch of machines and I just realised I haven’t booted Windows on any of them for a couple of weeks. I daily drive Tumbleweed when I don’t need any advanced Adobe features or play games that run on Windows only.
I wouldn’t go as far as to say I will ditch Windows completely, but it is nice to have options.
I’m impressed there isn’t yet anyone who’s suggesting arch btw and dead serious about it.
But Pop!_OS without a doubt.
At this stage I suspect its just 3 kids in a trenchcoat.
I hate this aspect of Linux. I spent countless days trying to figure this shit out on Tumbleweed. Turns out you have to manually install codecs. https://en.opensuse.org/SDB:Installing_codecs_from_Packman_repositories
You wouldn’t know this because it really isn’t hinted anywhere until you notice your CPU going into overdrive when you play a 4K video on YouTube.
I don’t know how to explain this to any regular m$ user that this is a thing they need to do because reasons.
Fake news!!1!!1!
Those are UDP packets.
Blasphemy. Hannah Montana is a god.
Anyone who doesn’t use standardized libraries for tz should be summarily tried.
I have had some success in the past with Rustdesk, which works alright amongst all the other options I’ve tried. However, one word of caution is to temper your expectations on the performance side of things. Visually, it is nowhere near a native experience regardless of software or protocols I’ve tried.
It’s unfortunate that Parsec still doesn’t support hosting on Linux. It is the best implementation of Remote Desktops I’ve used so far, and I tried almost all of them.
It’s first-class in every metric, except it doesn’t host Linux (only as clients), sadly.
Great find! Thanks, this is new to me. I would have taken this out for a whirl immediately but I just read the docs and sadly it doesn’t support my 3000 series nvidia card. Team Green is seriously getting on my nerves for their anti consumer practices, enough for me to go all in into Team Red or Intel for my next GPU.
At this point, Intel (if you’re listening), the single most important feature you can implement to get an immediate buy from me, is SR-IOV on your Arc cards. I will probably buy a few of them for each of my PCs as well.
I first beheld the glory of the cube in 2009. It was transcendental. I almost felt my soul leaving my body and ascending to a higher plane of consciousness, where few have treaded and those that truly grasp its majesty, yet fewer still. I was swept up in the spiritual, yet fleeting, ephemeral, and mercurial experience that was like no other. We were no more than ants trying to understand Einstein’s Relativity, or dung beetles oblivious to the sonorous rapture of Mozart.
I flipped the cube for a couple more times to show it to my unimpressed wife, and promptly never booted into Ubuntu since.