3 ms·
bebox, what the macs could have been if jobs wasn't so hellbent on getting back to apple, had a CPU port. it was pretty much a north bridge socket/plug to the
by xhcxjkhchxjk 4y ago
bebox, what the macs could have been if jobs wasn't so hellbent on getting back to apple, had a CPU port.
it was pretty much a north bridge socket/plug to the cpu from outside of the case.
haven't seen anything close to that. also the design of the pseudo realtime os would be killer on today's multicores. not to mention the bekernel c api instead of the osx side-step-patents-above-all-else-api of their bastard bsd. glad my livelihood doesn't depend on osx/ios client side applications
- lob_it 4y agoI'm silly enough to think having a 12u rack in the mancave is better than a keg setup. https://ltsp.org/ https://ltsp.org/ http://www.porteus.org/ http://www.porteus.org/ I've done a few personal projects with LTSP and think PXE booting is the bee's knees for some uses (obviously not as portable as a laptop running porteus). Booting remotely was not a priority, but OS exploration has always been exciting. With more devices (laptops, SBC's, etc) getting HDMI-In ports, running a compute stick, sbc/PI or other devices externally is also a cool feature. I like KVM's, so if they integrate a K/M protocol to HDMI-In port at somepoint, its back to plug and play designs, instead of RDP, SSH, etc for the external devices. Though on this post, cramming a SOC with the kitchen sink on it, it seems like they could simplify that dilema with a deca-socket design, reserving the PCIe bus for traditional expansion. Even expanding memory channels per socket negates some of the penalties for performance under some conditions (bottlenecks can be moved easily and/or will still exist without the complexity of jamming everything on one CPU die.) That is cool though!