41–50 of 265 posts
Is this Casio colocated in a Hetzner datacenter?
It is cheaper than AWS's Casio as a Service and for small sites you barely notice the difference.
this is like firing the death star at a plucky little pod racer
Hm, maybe posting this to HN wasn't the best idea...?
In case it completely dies there are archives now available: http://web.archive.org/web/20210712193555/http://fxip.as2034... https://archive.is/5a44i Or the whole thing is small enough to fit in a comment: > GET / HTTP/1.1 > Host: fxip.as203478.net > User-Agent: curl/7.76.1 > Accept: */* > * Mark bundle as not supporting multiuse * HTTP 1.0, assume close after body Casio fx-9750GII Webserver * { margin: 0; padding: 0…
Doesn't this run on one of the CPUs Sega used in the Saturn or Dreamcast?
Earlier quoted context omitted.
It is cheaper than AWS's Casio as a Service and for small sites you barely notice the difference.
Sure, but with fixed hardware resources you risk the site going down with traffic spikes like this, with AWS you have access to calculatorless options that can easily scale to handle increased request volume.
ERR_CONNECTION_TIMED_OUT
Doesn't this run on one of the CPUs Sega used in the Saturn or Dreamcast?
It was a fine CPU for the era with parallel instructions but also a fairly deep pipe compared to other contemporaries so it did best with a bit of hand tuning. (We worked on a DC game and Transform&Lighting loops needed hand optimizations iirc)