- Jun 12, 2001
- 8,758
- 43
- 91
When you watch or listen to things delivered by the HTPC, how are you doing so? Through a visual interface like HULU, KODI, or Plex?
You know those interfaces are essentially a web browser in kiosk mode? You are not really using an application on the system but viewing it remotely with the essential computational power being devoted to audio and visual drivers.
Does that really mean you really just need a system that is a NIC+GPU configuration?
Here is my supporting evidence to my thesis:
So basically, the best HTPC system should look something like a Raspberry Pi with a nVidia GTX 1080 and an Gigabit Ethernet (or best wireless) card.
What do y'all think?
You know those interfaces are essentially a web browser in kiosk mode? You are not really using an application on the system but viewing it remotely with the essential computational power being devoted to audio and visual drivers.
Does that really mean you really just need a system that is a NIC+GPU configuration?
Here is my supporting evidence to my thesis:
- Computational power to open, run the browser container is negligible
- All modern web browsers (oops, except IE 11 and below) contain W3/Apache standards for:
- Audio recording and speech comprehension
- Computerized Speech
- Load drivers (mouse, keyboard, scanner, etc) to the system through JSON, as needed/required by JavaScript
- IFTTT-like scripting, contained in resident memory
- time shift caching (like being able to store a video in cache memory)
- Computational requirements are on the server system and then delivered to client
- Client computations are for screen (redraw, paint, move within the browser boundary) and audio processing
So basically, the best HTPC system should look something like a Raspberry Pi with a nVidia GTX 1080 and an Gigabit Ethernet (or best wireless) card.
What do y'all think?