dyingkneepad

> hard things

How about consistently competing at fighting video-games at the highest level in the world for more than 30 years?

"The Will to Keep Winning", by Daigo Umehara. He was the first Street Fighter 2 player to reach the top (being considered either the best player or top 3), and he was able to stay at the stop since then. No other video-game player has ever been so consistently good as Daigo. He may not have won many EVO or Capcom Cup titles, but he has always stayed at the top. And he's the protagonist of Evo Moment 37.

Also, his story is good. The book may make you cry. And it's a very short book.

I'm planning to learn how to find time to learn anything at all.

Just normal work and family stuff consumes 100% of my energies, whenever it's 9pm and I have time to actually try to learn anything or do anything productive, I'm usually so tired that I can't do anything that engages my brain.

Thanks a lot for the link! That solves my questions!

Maybe I'll join.... (but still: which server!?)

> > Does this affect search and discoverability in between servers?

> A little.

Can you please elaborate on that?

Thanks for the answers!

I'm not the person you're asking to, but I failed at the "choose a server" part. I started having a bunch of questions over the choice of server and then gave up from analysis paralysis.

What are the implications of choosing one server over the other? Does this affect search and discoverability in between servers? If I really like Baking and really like Fencing as well, should I join the "Matodon Baking" server, the "Fencing fans" server of a neutral one? If I choose the Fencing server, will the people on the Baking server start seeing me as some sort of outsider since I'm not originally from the Baking server? Will they even be able to organically find me? How does the algorithm evaluate these choices? Can I restrict/split my posts between Baking, Fencing and general? And so on...

It seems to me that the market is kinda segmented between "people who read mostly physical books" and "people who read mostly ebooks", with some people consuming both, but usually doing some kind of segmentation for them as well (e.g., fiction vs technical).

I only want physical books. For me, book time is away-from-screen time. So: any book I may want to read?

Just remember: whenever IT doesn't deliver a workable solution, Shadow IT does.

This channel has the best Linear Algebra explanations I've ever seen, and it also explains the basics of AI really well.

Performance will be significantly better. Power consumption will be way way way better. Integrated graphics (Intel) will be extremely better than 2019. Just check the benchmarks. Your drivers will still be supported for years by all vendors (even on Linux that matters somewhat: although everything is always supported, vendors tend to put most of their resources on the newer stuff).

Also, you'll have USB-C ports, the newer hard drive standards, memory, latest wifi protocols (I don't know if there is one, to be honest), etc etc.

Why slimy? They asked a question and you answered without charging for it. It's not their fault.

Choose 3 countries. Live 121.6 days of the year in each. Don't pay any taxes because you're not a fiscal resident anywhere.

Thank not only these people but also their employers for funding the work.

I always see people claiming they use this strategy, but I never ever ever see people blaming services saying "this and this company sold my data to spammers". Where are the name-and-shame people? Have you ever caught anybody doing anything?

> the video encode and decode blocks were on an entirely different piece of silicon from the GPU.

As far as I understand this is not true. It's a different engine within the graphics device, and it shares the execution units.

When I can't find something on Google I may ask ChatGPT, read its answer and then we talk about it.

X11 is just a network protocol that specifies how a client (e.g., your browser) can send messages to a server (e.g., /usr/bin/Xorg) so the server will draw stuff on the screen. A complicated part of this process is the decision of where each client windows will be shown on the screen, so in X11 we have a special client that is the "window manager" (WM), which does stuff like drawing maximize/minimize buttons everywhere, coordinating which apps are being shown, and, these days, also compositing (which is a more complicated version of what I just said, except the apps don't even know where they are on the screen or if they are being displayed). The fact that the WM/compositor is just a client and not a server creates all sorts of problems, especially in the security area, but also synchronization. The protocol was created in the early 1980's so there are all sorts of insecure design decisions and other decisions that made a lot more sense at that time.

Since then, the X11 protocol got extended and extended, but the "core protocol" is not allowed to change (by design). There are a zillion instructions on how applications can tell the server how to draw stuff, but basically none of these are used anymore.

These days, when it comes to drawing, what the clients want to do is very different than the traditional X11 network protocol model. Clients want to create themselves the buffers, draw on them (using GL/Vulkan), and just be able to tell the compositor: "hey, I finish drawing on my buffer, please display it on the screen", without even having to send pixels over the network. This is accomplished by the DRI and Composite extensions (and a lot of glue everywhere) and these clients are able to not make use of a vast part of the X11 protocol.

So based on all that, Wayland's idea is to promote that new model to be the base level. Wayland is also a protocol, but there are no protocol calls such as "draw this line from x:20,y:20 to x:40,y:20". The operations match the new model: "hey, I just finished drawing on my window that has handle 0x30984, can you please display it for me?" (well, actually, it's more like: "when syncobj handle 234 gets signaled, the buffer is yours to display"). The big difference here is that instead of having a server, a client and a WM/compositor, there is just a client and a server/WM/compositor. This simplifies a lot of things, allows more security, but creates the problem that, well, Gnome wants its compositor to behave in some way, but KDE wants its compositor to behave in another way, so each one will have to be a whole Server and not just an application anymore. And that causes the fragmentation that has been haunting us a lot.

On top of all that, Input handling and Accessibility was sorta underestimated on the Wayland side, and things have been evolving rather slowly. A lot of stuff that is possible to accomplish these days with X11 is still not covered by Wayland. A lot of super-specialized X11 apps will never be ported to Wayland, and there is probably not even Wayland protocol in existence to support that. This is all, of course, a solvable problem: throw enough money at these issues and they will all disappear (but you may want to dedicate part of this money as bribes, because gathering consensus for some stuff without bribery may be impossible so your extension proposals may get stuck in limbo). For example: even a filthy rich behemoth such as Valve has been having problems merging extensions that will allow its games work better on Linux. Good luck with anything you may need.

I am also deeply disappointed that Wayland has been taking to much to develop, but I don't have anybody specifically to blame. I believe part of the issue is that more money should be thrown by I-dont-know-who at it. The Compositor fragmentation is also a painful issue, but going back to insecure X11 protocols doesn't seem like a good alternative. Anyway: I just don't know how to make things better. Let's just try not to blame the developers that have been doing herculean efforts to keep all these cards stacked on top of each other. Without them, perhaps we'd still be doing insecure inefficient 80's-style window drawing and wrapping, moving pixels all over network sockets.

I'd love to be corrected on my views by anybody on this forum.

Speaking from my own experience at work, for non-webdev, if the project is something I'll want to share with other people, there is a great incentive in just using Python. I can't seem to get people to be interested at all in my tools if they're in Ruby. When I write stuff in Python, people naturally read, use and contribute.

I believe both Gnome and KDE have native "share my desktop" options (if you have the right packages installed) that will in theory work out of the box even on Wayland. It does not work properly when you're running games (games are just black screens). The nice thing about this is that you can use the local machine to use/continue your session once you're physically present. It also uses your native graphics drivers so your desktop has all the X11, GL and Vulkan extensions available for whatever graphics card is attached to the machine.

TigerVNC is decent and I have used it in the past for cases where there is never a need to have a local session. It has the disadvantage of no native 3D rendering.

Intel AMT (that is not available in every processor, and a lot of people want to see dead) has a remote VNC thing that you can enable and allow you to even browse your BIOS and Grub with it: it covers more cases than any alternative, but it's not a software solution. It's the one I prefer when available.

I got a very similar thing: a legit email from PayPal, but it's an invoice and not a quote. And when you login to PayPal the website shows nothing.

And then some day someone will recognize you somewhere, tell your wife "hey, I saw reaperducer at the park today!", and then she will think you're cheating on her.

From non-university stuff, I did not read the book but I read the derivative works and applied it to my life: Getting Things Done. Specifically, Inbox Zero changed my life and made me a better programmer by having me become way more organized and on top of everything.

Only malicious foreign actors are encouraged to survey the security of systems of national interest, since they can't easily get prosecuted. Systems working as intended.

The the mandatory yearly corporate BS trainings.

Organize your inbox.

Do that one thing you've been wanting to but is lower priority, like learning a tool or working on a low priority bug.

Because the Jira deadline (or perhaps OKR deadline) or whatever other deadline set by a PM or a Manager or HR is Friday, and I have to mark the checkbox or move the ticket as done before the deadline so I can claim I finished stuff on time for the our support agreements on performance evaluation period or whatever.

"We recommend you try UBQTLONR this time!"

I have dual boot on my computer, but Steam on Linux has been getting so much better that I've been running stuff mostly on Linux. It's been a while I had to boot on Windows... But I also own a PS5 and prefer to game on it. Seriously, try gaming on Linux for a while!

I share my headphone and the monitor between the PC and the PS5, but the laptop has its own screen so I don't need to use the monitor all the time. The headphone is one of those wireless headsets that has a USB dongle, so I just need to unplug it form the console and plug it into the PC. No need to keep bluetooth pairing, and I don't suffer from latency issues as well.

As a bonus I can have my laptop open when I play the PS5 so I can see notes related to the game (e.g., combo lists).

Trying neovim has been on my TODO list for a while, but I never had an actual reason for it. What's better about it that will make me want to switch? I don't care about the fact that internally it's Lua instead of Vimscript: I'm not writing code in either. All that I can see is that I'm going to adapt to the differences, which is a downside.

As much as I admire the herculean efforts of the people involved to make these things work, my policy is to only ever use hardware where the drivers are actually supported/paid for by the hardware manufacturers.

I mean, even when using paid-for drivers we encounter a lot of trouble, I don't want to live in this world there the HW manufacturer doesn't care about my usage.

I'll stay with Intel Graphics. It works just fine. If I report bugs, someone who is getting paid to fix those bugs will read my report and try to address it.

For fiction books, I've heard of indie authors organizing groups where they read each other's books and write reviews. Some groups are more serious in that they actually analyze and suggest improvements to each others' work, but other groups work more as a "let's trade 5 star reviews" thing.

> My DS is rusty

What is DS?