prollyanotherlurker
kiwifarms.net
- Joined
- Apr 1, 2024
Don't expect to be going back to Windows again ever then. Because it's only downhill from here.
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Don't worry, I am aware. One look at the Windows 11 trailer was enough for me to never look back at Windows. Doing stuff on it at my workplace is no fun and makes me glad I switched early.Don't expect to be going back to Windows again ever then. Because it's only downhill from here.
I get you don't want to learn about things you think are unnecessary. But learning how the underlying stuff works. I'm not even talking about writing bash scripts, or moving to a window manager. Just learning the basics of how unix, specifically linux does things. Makes using it a lot easier. There really isn't much I can think of, where that wouldn't end up being a pretty big benefit at some point. And make linux a more effective tool.Don't worry, I am aware. One look at the Windows 11 trailer was enough for me to never look back at Windows. Doing stuff on it at my workplace is no fun and makes me glad I switched early.
Thankfully my needs are met nicely with Linux (especially the fantastic KDE tools) and honestly its better then modern Windows, it is the right tool for the job for me. I'm still not a huge fan of Unix stuff but I am also aware that I used Windows for much longer then I have used Linux for, so I am probably still more used to Windows. Although I find Windows harder and harder to use by the year at this point.
On a desktop I will just have interfaces.d set up to do the normal thing- bring up the ethernet interface with DHCP, which then just launches dhclient to pull down a (coincidentally static) address for the LAN. No need for NM. I don't bother to get rid of NM. But everything just works without thinking which is nice.These days, there's no real reason not to use NM, even if you don't need all its functionality, like on a Desktop solely using Ethernet. Its basically expected at this point as a Linux standard (which is a good thing). Other stuff still exists but configuring networking manually was something I never want to do again after doing it on BSD systems.
I've already been through a Gentoo + bspwm optimisation phase, which really did help a lot to get me to understand some basic Unix/Linux concepts. Probably a lot further then most are willing to go. But these days I just want something practical, so a vanilla KDE setup (funnily enough its set up just like Windows) is the best for me.I get you don't want to learn about things you think are unnecessary. But learning how the underlying stuff works. I'm not even talking about writing bash scripts, or moving to a window manager. Just learning the basics of how unix, specifically linux does things. Makes using it a lot easier. There really isn't much I can think of, where that wouldn't end up being a pretty big benefit at some point. And make linux a more effective tool.
Funnily enough, learning the terminal on Linux actually helped me out a lot on Windows, as I was actually able to use a bit of PowerShell (which is lovely to use aside from the weird syntax) to make my life easier.Being able to use some kind of terminal editor
Maybe it's a huge problem for me only now because currently I keep setting up and knocking down my SUSE installs to properly figure out how they work.didn't even notice, but I'm not constantly changing loads of packages.
it's like the booting times meme, if it takes longer it just means I can enjoy my coffee more ¯\_(ツ)_/¯
Yeah it's a travesty really. I daily Win10 and I have Win11 on my laptop and they don't get in my way, at all. Thing is, when I start off fresh, I need to go through multiple hoops to trim down all the annoying and unnecessary bullshit Microsoft puts on top of what's still a solid NT base. Disable mouse acceleration, run WinUtil, run WinAero Tweaker, do some extra manual tweaking like disabling animations, setting Registry tweaks, installing software like Windhawk and so on. I had to do a bit of extra work on Win11 as well due to them fucking up the taskbar and adding the new shitty right click menu, after that I basically got fancier Win10.I would still use Windows, but Microsoft has shit it up so much that Linux is the best choice for me at this point.
IMO PowerShell is great and Bash purists hate it because it's Microsoft. It's object oriented scripting is actually very neat once you get the hang of the basic aspects. Thing is, you don't want to use PS as a shell to send one-liners from memory, you want to use it as a scripting language first and foremost. That's when it's at it's best and it's Verb-Noun ceases to be an issue.Funnily enough, learning the terminal on Linux actually helped me out a lot on Windows, as I was actually able to use a bit of PowerShell (which is lovely to use aside from the weird syntax) to make my life easier.
Get-NetIPAddress -InterfaceIndex (Get-NetAdapter -Physical | % ifIndex) | ? AddressFamily -eq "IPv4" | % IPAddress
promptCouldn't be able to do the same with Batch or Bash.
{
"presets": [
{
"name": "Best Audio",
"options": ["-f", "bestaudio", "--extract-audio", "--audio-format", "mp3"]
},
{
"name": "Best Video",
"options": ["-f", "best"]
},
{
"name": "Custom Format",
"options": ["-f", "bestvideo[ext=mp4]+bestaudio[ext=m4a]/mp4"]
}
]
}
#!/bin/bash
CONFIG_FILE="config.json"
# Check for jq
if ! command -v jq &>/dev/null; then
echo "jq is required. Please install it first."
exit 1
fi
# Check for yt-dlp
if ! command -v yt-dlp &>/dev/null; then
echo "yt-dlp is required. Please install it first."
exit 1
fi
# Load preset names into a menu
preset_names=($(jq -r '.presets[].name' "$CONFIG_FILE"))
echo "Choose a preset:"
select preset in "${preset_names[@]}"; do
if [[ -n "$preset" ]]; then
break
else
echo "Invalid choice, try again."
fi
done
# Extract options for selected preset
index=$(jq --arg name "$preset" '.presets | map(.name) | index($name)' "$CONFIG_FILE")
options=($(jq -r ".presets[$index].options[]" "$CONFIG_FILE"))
# Prompt for URL
read -p "Enter the URL to download: " url
# Combine command and run
echo "Running: yt-dlp ${options[*]} \"$url\""
yt-dlp "${options[@]}" "$url"
chmod +x yt-menu.sh
./yt-menu.sh
Choose a preset:
1) Best Audio
2) Best Video
3) Custom Format
#? 1
Enter the URL to download: https://www.youtube.com/watch?v=dQw4w9WgXcQ
Running: yt-dlp -f bestaudio --extract-audio --audio-format mp3 "https://www.youtube.com/watch?v=dQw4w9WgXcQ"
So, an external dependency. PowerShell relies on it's own methods so you won't run into issues that a script won't work on another machine because it misses a dependency that you'd then have to install just for the script to work. This is why PowerShell is very handy for sysadmins as they can write a single script, run it on any machine and it will behave the same way as long as it has PowerShell 7, which is a single dependency. Also, my menu is nested and relies on a single JSON for all positions, but I can use an LLM too so don't bother. And stop using this video link, I recognize that ID instantly.
"Do one thing and do it well" is never going to be outdated as a principle, no matter how many jack-of-all-trades tools exist.The Unix philosophy is outdated.
The "do it well" part is the problem. And didn't an entire development system implode because a developer pulled a program for left aligning text because he was forced to pull an app because kik wanted the name?"Do one thing and do it well" is never going to be outdated as a principle, no matter how many jack-of-all-trades tools exist.
That was an npm lib. npm being shit is not an argument.The "do it well" part is the problem. And didn't an entire development system implode because a developer pulled a program for left aligning text because he was forced to pull an app because kik wanted the name?
And "keep it simple stupid" will always be the superior principle. Needing multiple unrelated packages to accomplish the same task a single package can do is the antithesis of the KISS principle."Do one thing and do it well" is never going to be outdated as a principle, no matter how many jack-of-all-trades tools exist.
And xz is not an argument because...?npm being shit is not an argument
Indeed. I used to run Windows 7, and had a Zune!I forgot how nice Windows used to be OOTB until I installed Win7 on my old PC recently for a test.
Say what you want about Ballmer, but under his tenure we got both Windows XP and Windows 7. Windows 10 and 11 are all the result of Satya Nadella.
Good news is that with the release of PowerShell 7 it's now multi-platform, so you can write scripts in PowerShell on Linux as well. I like PowerShell. PowerShell's nice. Just because the code is long doesn't mean it's not performant. But I guess being able to crash your system with thirteen characters makes Bash superior since Linux users don't enjoy having working systems.
Since Ballmer left, that's been their specialty. Sad to see.Microsoft has a good thing going and they can't help but fuck it up at times.
Since Ballmer left, that's been their specialty. Sad to see.
It doesn't have to be, but I would rather a huge monolithic program that does 1000 things that sucks vs 1000 programs that do one thing but all suck (such is the case on 100% of modern Unix systems). Especially with how bad programmers seem to be compared to the time around Unix's conception.The Unix philosophy is outdated