You're talking about something else with a remote control. When you're streaming, the device you're streaming to has control of the audio level, display ratio, and what you are watching, not the server. The remote device becomes the remote control. You're talking about a smart TV or a console system you attach to a TV. Streaming is a different thing.
Apache will stream your stupid 75GB BluRay files without any need to re-encode, and you can watch it remotely so long as the client device can decode it, even across a 10kbit connection, so you go ahead and enjoy your wasted processor cycles and higher electric bill, oh, and watching your content at a lower bit rate and resolution. I'll just stream the large media as is at full quality without compromise.
You have to work really really very hard to get Apache not to just work, and it takes a slashdot-level event to get it to stop working.
Meanwhile, whatever thing you bought will be abandonware in less than 2 years. And chances are about equal your thing is just running a crappy wrapper and gui for Apache anyway. So the business end of your thing is probably free, yet you paid for it anyway.
I feel like you're intentionally missing the point.
Your "dump all your videos into a big directory and Ctrl-F the Apache directory index" workflow will necessarily limit you to watching on devices that can navigate to arbitrary URLs and play videos from them. This will, in most cases, limit you to a computer (built-in browsers in "smart" devices, be they TVs, consoles, or purpose-built streaming boxes, will often play videos only grudgingly), and I don't know about you, but I don't want to sit and watch TV episodes or an entire movie at my computer desk with its relatively tiny monitor and relatively shitty speakers. I want to watch them on my big TV with the fancy sound system in the living room. So what would you suggest for this use case? Connect my computer to the TV? OK, great, but the video card won't output surround sound over HDMI, so now I have to futz with a bunch of other connections if I want more than just stereo sound. And once that that's sorted, how am I supposed to pause the movie when I have to get up to piss, because the TV remote can't control my computer?
> Apache will stream your stupid 75GB BluRay files without any need to re-encode, so long as the client device can decode it, even across a 10kbit connection, so you go ahead and enjoy your wasted processor cycles and higher electric bill.
Again, missing the point. Yes, Apache will happily squirt those bytes at whatever requests them, but that will not produce an enjoyable user experience (i.e., one where I can WATCH THE FUCKING MOVIE) over a sufficiently slow connection, and I'm not going to re-encode every file I have at a low bitrate on the off chance I want to watch it away from home.
> Meanwhile, whatever thing you bought will be abandonware in less than 2 years. And chances are about equal your thing is just running a crappy wrapper and gui for Apache anyway.
My Apple TV HD in my bedroom is still receiving updates seven years after it was originally released. The Apple TV 4K in the living room is still receiving updates five years after it was originally released. I run Plex to stream my local media to local (and my own remote) clients, and it is still actively maintained after 14 years--and if if Plex, Inc. should go under, there are plenty of alternatives that won't necessitate me regressing back to a computer connected to the TV.
Dude. I get it. It's HTTP all the way down. I know that; I'm a professional software developer and have been Into Computers since I was old enough to read. That's also how I know that "just dump your video files into a directory and let Apache serve them and watch them on a computer"--or, yes, "just connect your computer with the directory full of video files directly to the TV"--is a shitty user experience, which is the point you seem bound and determined not to concede, since you are instead laser-focusing on the literal reading of statements like "I'm not going to re-encode every single video file I have on the off chance I want to watch them away from home" (obviously I meant I'm not going to do that AHEAD OF TIME versus letting my Plex server do it on-demand and stream it to me when I'm using a device not on my local network), or splitting hairs about binaural hearing and the utility of surround sound.
In any case, I yield; you have Won the Conversation; congratulations. I'd give you a gold star, but I don't think HN allows emoji in comments.
Whatever works for you. If you have some aversion to hotlinked directory listings and need to see a glitzed up array of tiny movie posters, go with God. I'm glad your stuff works, if it does, and I cry with you if it doesn't.
Apache will stream your stupid 75GB BluRay files without any need to re-encode, and you can watch it remotely so long as the client device can decode it, even across a 10kbit connection, so you go ahead and enjoy your wasted processor cycles and higher electric bill, oh, and watching your content at a lower bit rate and resolution. I'll just stream the large media as is at full quality without compromise.
You have to work really really very hard to get Apache not to just work, and it takes a slashdot-level event to get it to stop working.
Meanwhile, whatever thing you bought will be abandonware in less than 2 years. And chances are about equal your thing is just running a crappy wrapper and gui for Apache anyway. So the business end of your thing is probably free, yet you paid for it anyway.