It’s basically ThunderBolt 3 without the licensing.
It’s basically ThunderBolt 3 without the licensing.
Several comments specifically talked about VMs for the various apps. And frankly I’m not super familiar with the limitations of containerizing apps either. That’s part of why I was looking for an immutable os + flatpacks / snaps - it’s much more similar to a normal linux system just organized in a way to not break shit.
Is there a performance impact on the jellyfin server by having the NAS on a separate machine? How long does it take to serve a 20gb rip of a bluray?
Honestly I had never built an NAS and installed an OS on it before. I’ve only ever used the junk that ASUSTOR puts out and I want to have control over things. So a good part of the reason I asked on here was to see what other people had done and why.
Oh I like the look of that.
It’s mostly for running media servers like jellyfin.
I want immutability because I come from a the debian world where everything just works. But I want the benefits of using modern versions of packages.
Yeah but it was an unsecure piece of shit for more than the past decade
Yeah that’s the case with programming… well anything. This at least gives you a way to automatically receive all of that data from any app without excessive prior knowledge. With a small amount of info you can filter for specific events and create all kinds of robust functionality. That’s the power of a set protocol - it is to make things widely compatible with one another by only depending on the dbus protocol and app name. Otherwise you may need to depend on some shared objects which makes deployment and maintenance a total clusterfuck.
https://en.wikipedia.org/wiki/Coupling_(computer_programming)
It’s much easier to understand how dbus works once than to understand how every daemon you connect to works every time you interface with a new daemon.
I used to love Thinkpad laptops up until Lenovo bought the line - build quality dropped off a cliff after that. I’ve avoided them since then so I can’t comment on their current build qualities except to say they used to be built stronger than those toughbooks with handles.
Yeah but how is the experience? While I’m not a fan of MacOS the polish and integration with the hardware is excellent. Hmm… I may need to see if I can dual boot this machine and check it out myself.
When I originally typed it, I made a function for string reversal and called that. But I didn’t include it since I didn’t want to define that too.
Honestly… this wiki has a seriously difficult path ahead of it. I mean - it’d be fantastic if it did simplify things like that to let you write simple, elegant, and easy to read functions while linking to other functions.
But it’d also have to lint those and make sure that contributors don’t implement recursive dependencies.
I think you’re absolutely correct about them choosing those awful identifiers so the functions are not language specific. It just hurts to read and thoroughly makes it harder to understand because my brain doesn’t tokenize “Z10096” and “Z10096K1”.
Neat. I don’t like that the implementations have to name the function by some cryptic identifier, though. Real words matter in source code.
Who can tell me what this function is?
def Z10096(Z10096K1):
return Z10096K1 == Z10096K1[::-1]
How about this?
def isPalimdrone(myString):
return myString == myString[::-1]
That’s true for cable, but I haven’t found it to be possible with fiber.
They’re also engineered with the assumption that there is nothing within a 6 in radius and it is kept in a 70F room. Those are assumptions that often aren’t true and lead to them overheating all the dang time.
They downvote you, but after spending time writing powershell scripts, I can confirm that I absolutely fucking loathe microsoft products now.
Mine doesn’t require photos - it just does a series of weird sounds like I am at the audiologist.
The reason they moved back is because Excel.