z3rOR0ne

Same. Best Game Series and storytelling Telltale has ever done.

Just use firejail to sandbox it and find out.

Damn…this looks really good actually. I’m sad to day I never heard of cohost until now. But I’ll admit I just identify with the founder’s sentiments around the tech industry, and their strict adherence to moral values around how a platform like that should interact with their users. I wish their developers all the best in looking for new work.

Xenogears for the PS1 had one of the best combat systems I’ve ever played. Tied with Star Ocean 2 for the PS1. There’s a remake which I think they overhauled the combat system, so I’m not sure if it still is as good as the first edition, but the customizability was amazing.

After that Grandia was fun, but I played it far less than the aforementioned, so have less to say. Chrono Trigger was very good for what it was, and IMHO was only matched by FF6 in that category (heavy turn based combat systems). Chrono Cross is an honorable mention in that category as well.

Lastly, very recently the Sea of Stars game had a very good combat system.

Ultimately these games have great stories, and that’s all I really cared about, but the combat systems could either make or break the monotonous grind to get to the plot points, so they had to be at least decent to make the games playable.

I highly recommend any of these games. Chrono Trigger in particular is highly regarded as possibly the greatest JRPG of all time, and personally I’d put Xenogears at 2nd place, with Star Ocean 2 at 3rd. But I might just be nostalgic.

Tell that to Linus Torvalds.

Lol. Emphasis on the H in IMHO. I meant no offense, it’s a valid point.

I have about 25 or so shell scripts I use somewhat regularly and well over 300 aliases. I actually specifically don’t wrap package manager related scripts for no reason in particular, but many often do.

My rule for an alias is if the amount of custom flags gets lengthy, and I use it often, yeah it gets an alias. Here’s an example of using yt-dlp:

alias ytdl='yt-dlp --sponsorblock-remove all --write-auto-sub -f "bestvideo\*+bestaudio[ext=m4a]/best" -f mp4'

For shell scripts, my rule goes that it should probably have multiple features related around a single idea, that way you can use getopts to create custom flags. For example, I have a script that wraps very basic, but commonly used, git commands, chaining the classic add, commit -m, and push behind a series of read prompts, it has -h flags for help -l for a minimal log output, -i to initialize a new repository (even using github api token to remotely create the repo if you want to use github), and -r to revert back changes to a specified commit.

Generally speaking aliases will get you what you need most of the time in a pinch, but shell scripting is more powerful, versatile, but potentially more time consuming.

Others have rightly pointed out that these abstractions can sometimes negatively impact muscle memory, but IMHO this only really applies if you work as devops or sysadmin, where you are often responsible for running many different Linux servers, but usually this isn’t an issue if you have access to the internet and can see your saved aliases and/or scripts (but yeah, instant recall of native commands trumps notes every time).

Additionally, another mentioned using git to keep track of your aliases, which I totally agree with. Whatever you do, back up your aliases and shell scripts, ideally with a git repo of some kind. This not only allows you to take your new scripts/aliases with you wherever you go, but also reference them later in case it’s not possible to use them on not your machine.

Hope this helps. Bash can be crazy powerful if you take the time to learn it, and aliases are a great entry point to recognizing that potential. Here’s one of my favorites that combines mkdir with cd:

alias mkcd='{ IFS= read -r d && mkdir "$d" && cd "$d"; } <<<' 

Good luck, and have fun.

On Android, from FDroid you can install an app called Seal, which is a minimal frontend for yt-dlp. I discovered it while trying to circumvent issues Newpipe was having with some update to the YouTube API.

Unlike Newpipe forks, which can use the sponsor block API but not when downloading the video directly to your device, Seal allows you to input the custom flags available from the yt-dlp cli, so you can automatically skip annoying sponsor mentions even on your downloaded videos.

Everyone remember to pollute your answers wherever you post them at least once a day.

Honestly my first olkb was the Planck from DROP. A 40% keyboard where the numbers and symbols are each on their own separate layer. The defaults on the Voyager were very clunky IMHO, so I simply switched them to the defaults of the Planck, including moving the home row up one whole row. This left a few spare keys as the Voyager is a 55 key, so I simply added two Super keys instead of one as well as a few other duplicates.

I’ve also heard of some interesting workarounds for using Vim with Colemack/Dvorak. It is funny, when I first discovered OLKBs, I kept encouraging people to use them, and I still do. Same with Vim. But ultimately I get why people don’t. I’m so used to this workflow now, going back to a standard keyboard feels clunky and slow, and I’d imagine my setup feels awkward and alien to most if not all other people.

But it’s uniquely mine and I can type 100wpm if I am on a roll with his setup.

The clamps are a hilarious accident that happened to work for me. I was experimenting with different ways to get that near 90° angle shoulder width apart, and this was the3 soluuon I haphazardly stumbled on.

Glad you like it/find it entertaining! I wish you well in finding what works for you! ✌️

Lol, yeah I know it’s definitely not for everybody.

Nah, didn’t go that far (yet), just heavily edited a qmk_firmware configuration. So yeah, I’ll admit I didn’t exactly write my own keyboard firmware.

I have the soldering tools ready for when I have time to learn. Sadly I only have time for software lately, and hardware/firmware has had to take a back seat.

Customizing your workflow around the keyboard is a helluva drug though! If it weren’t for Vim being configured for QWERTY out of the box, I’d probably configure a COLEMAK or DVORAK setup as well.

I’d encourage you to go as far down the rabbit hole as you’re comfortable, the learning curve can slow you down initially, but the dividends pay off in the long run imho.

Here’s a pic of my current setup. The keyboard is prebuilt (Voyager ZSA), just with custom firmware. Couple clamps keep it vertical for ergonomics.

I’ve been on BSPWM for nearly 2 years now. Custom scripts and keybindings all over the place. My workflow is so customized and keyboard centric with this TWM. Vim bindings in the terminal, Vimium in the browser, and a heavily customized Neovim Text Editor with Espanso Text expander global keybindings every where… Not to mention a 55 key split Ortholinear Keyboard with custom firmware…yeah… My hands almost never touch my mouse except to game.

Yeah, Fedora has the closest I’ve seen to this, as they do a rolling release distribution cycle, but with a major update every year. It’s still too hands on for the average Windows user from what I’ve seen.

That said, in the particular case of the Fedora upgrade, I’ll admit I get lazy in the other direction. If I can accomplish a task from the terminal, 99.9% of the time, I’ll do it simply because it’s exponentially faster.

Yeah, I generally agree with all sentiments. TS is handy at times, but working with poorly written .d.ts types from 3rd party libs is Hell.

The MS acquisition of Github is sad imho. Using alternatives is nice. I’ll eventually get around to self hosting a Gitea or cgit instance.

Ubuntu, Mint, and PopOS are probably the closest to a mainstream Linux Desktop from what I’ve seen, and perhaps one day one of those really will take the mantle and push the Linux Desktop forward into the mainstream, but I just don’t see it. I do hope I’m wrong though.

Ah BSD, the OS that probably doesn’t have an NSA backdoor in it because it’s just not worth their time, lol.

deleted by creator

On X11, Nvidia is pretty close to plug n’play (unless you install multiple kernels, but even then it isn’t so bad). Wayland has been a stuttery mess for Nvidia for a while now and there’s a long standing issue up that hopefully will be resolved in 550 release.

That said, linux desktop environment developers will likely have to adjust a large amount of environment variables (more than they probably have already) that thus far have had to be set by the User by hand. One has only to look at the Hyprland docs on setting up Nvidia to see the extent to which the bulk of the configuration is set on the User as it stands right now.

There’s more than a few reasons why Linux can’t make the jump to holding a dominant position in the desktop market.

One is simply preinstallation. For companies (and therefore the general public) to adopt the Desktop Linux, they’d need it simply to be installed for them, with a Desktop Environment like Gnome or KDE.

Secondly is updates. As much as Linux users tout the control they have over when and how updates take place, and how much Windows users will always complain about having to update their systems, until system updates on Linux are made automatic (or at least given the option to be made automatic), there cannot be a mainstream Linux Desktop. This means updates that happen very much like Windows, no administrator/sudo password, just happens on reboot regularly.

The reason for this is mainly that the average user would never update unless forced, and then when something inevitably breaks, they are left, as always, frustrated that their computer just didn’t work as expected forever without any upkeep, understanding, or updates.

Lastly is support. And this is multifaceted. By support I mean software support by companies like Adobe. I also mean a much farther reaching swath of random devices that literally plug and play like on Windows.

As an aside, I’ll also say that since there is a move towards Wayland, there also needs to be a No Configuration Necessary way of running Nvidia on Wayland. This is less a Linux issue, and more a Nvidia one, but until pretty much any and all hardware works on Linux the way it just works on Windows, this sadly affects Linux Desktop adoption as more and more of the Linux Desktop ecosystem moves towards forcing Wayland adoption.

Finally I’ll say that the Microsoft corporation at large obviously relies mainly on Corporate Adoption of its products and services, and that the Windows Desktop is simply one part of that greater whole. Their approach to competing with Apple and their walled garden ecosystem has been to slowly but surely create their own, its just so much larger you forget there are walls. They have done this by absorbing more and more of the tech ecosystem either by acquisition, invention, or otherwise. Examples ot this include Bing and All Search Engines that Use it, the pushing of TypeScript into JavaScript Development, the predominance and proliferation of VSStudio/VSCode in modern software development, their heavy involvement with OpenAI and aggressive pushing of AI products/services, their acquisition of Github and subsequent further expansion of influence over software development and distribution, and much much more.

Despite the privacy invasion, enshittefication of the user experience, and their various other ways they have mistreated their users specifically via the direction they’ve taken Windows, Microsoft has established itself as THE Desktop, as THE Workstation, and as THE company that comes to mind when the average person mentions “computer”, and the majority of people associate computer related productivity and play with Windows.

For all the advances made to Desktop Linux, especially in recent years, it is unlikely that Linux Desktop adoption will ever proliferate to the kinds of mainstream adoption that its accolades desire. Until Linux (or at least a Linux distribution) can demonstrate what I’ve mentioned above (preinstallation, automatic/automated updates, and wide spread software/hardware support from various 3rd party vendors) along with demonstrating a work flow/user experience that is somehow both familiar to the user and also better than the experience on Windows, then the day of the Linux Desktop will never come.

This aforementioned demonstration, btw, would have to become obscenely apparent to the average every day computer user who just wants to get their work done, play a Video Game, and watch Netflix, all without having to ever even know what a terminal emulator is.

I love Linux, and I think the Linux Desktop is not only a superior user experience, but is just better in general than Windows. But the average user I’ve encountered generally hates their Computer if it doesn’t work as expected 110% of the time. Linux, and honestly computers, will never be able to do that, but the closer the Desktop (and user facing GUIs more broadly) get to creating that illusion of “it all just works all the time”, the more adoption you’ll see.

Her presentations are fun. Thanks! Great watch.