@teppa Interface between chiplets still introduces latency. Perhaps photonics will eventually overcome this but it is currently an issue with chiplet designs.
@cm0002 This site, friendica.eskimo.com/, is running on an 18 core 36 thread CPU clocked at 4.5Ghz with 256GB of RAM, the CPU itself cost me less than $400, can't find anything close in that price range from AMD and sure as hell not Crapple.
@cm0002 You know about one cookie / two cookie children, those who are willing to delay gratification for a larger long term reward? Intel has always been a two cookie company, their investment in high numerical aperture extreme ultra violate fabs being a case in point. This is going to make them competitive with ASML and domestically to boot which means if China does take over Taiwan they'll be in an extra good place, not that I believe this is likely. But I believe this investment will serve them well in the long term even if it means some short term pain.
@cm0002 Running 6.15.5 self compiled kernel, had some stability issues in 6.14 that didn't resolve even up to end of life, but have not had this issue with 6.15.
@cm0002 All of the Redhat derivatives, including Alma dropped NIS support after 8, which is why my Alma server is still at Alma 8. They expect us to "upgrade" into LDAP but LDAP makes things unnecessarily complicated, like changing login shells, so a no go.
@ruffsl I have no bandwidth quota on my vps's, only memory and disk. See eskimo.com/services/virtual-pr… further our shared hosting is extremely robust, this friendica site runs on it, friendica.eskimo.com/ and runs around 7-16 hits/second (between slow and peak times) and response time is generally between 240-500ms which is better than most major providers. It is doable, for me the big issue is you are proxying https, is that data getting un-encrypted / re-encrypted in the chain? If so do you really want them looking at all of your traffic?
@heleos Linux will do fine too.
@teppa Interface between chiplets still introduces latency. Perhaps photonics will eventually overcome this but it is currently an issue with chiplet designs.
@Cris_Color Everybody makes it out like Intel is doomed. It will do fine.
@cm0002 This site, friendica.eskimo.com/, is running on an 18 core 36 thread CPU clocked at 4.5Ghz with 256GB of RAM, the CPU itself cost me less than $400, can't find anything close in that price range from AMD and sure as hell not Crapple.
@cm0002 You know about one cookie / two cookie children, those who are willing to delay gratification for a larger long term reward? Intel has always been a two cookie company, their investment in high numerical aperture extreme ultra violate fabs being a case in point. This is going to make them competitive with ASML and domestically to boot which means if China does take over Taiwan they'll be in an extra good place, not that I believe this is likely. But I believe this investment will serve them well in the long term even if it means some short term pain.
@just_another_person I hate to state the obvious but Happy Days was FICTION.
@srasmus Live a lazy life, get lazy rewards.
@cm0002 I notice this has the same remote ID format as AnyDesk, are these in anyway interoperable?
@just_another_person Erase your history then repeat it's painful lessons.
@cm0002 Running 6.15.5 self compiled kernel, had some stability issues in 6.14 that didn't resolve even up to end of life, but have not had this issue with 6.15.
@cm0002 All of the Redhat derivatives, including Alma dropped NIS support after 8, which is why my Alma server is still at Alma 8. They expect us to "upgrade" into LDAP but LDAP makes things unnecessarily complicated, like changing login shells, so a no go.
@ruffsl I have no bandwidth quota on my vps's, only memory and disk. See eskimo.com/services/virtual-pr… further our shared hosting is extremely robust, this friendica site runs on it, friendica.eskimo.com/ and runs around 7-16 hits/second (between slow and peak times) and response time is generally between 240-500ms which is better than most major providers. It is doable, for me the big issue is you are proxying https, is that data getting un-encrypted / re-encrypted in the chain? If so do you really want them looking at all of your traffic?
@ruffsl I see no desirability to putting a man-in-the-middle of a web connection. Cloud flare = cloud censor and spy.