4 ms·

People used 50Mhz SPARC systems to do real work, and the peripherals were all a lot slower (10mbps Ethernet, slower SCSI drives) with less and slower RAM. But i

People used 50Mhz SPARC systems to do real work, and the peripherals were all a lot slower (10mbps Ethernet, slower SCSI drives) with less and slower RAM. But it might take a week to compile everything you wanted, I agree; of course there is always cross-compiling as well.

bitcompost 2y ago
Oh I believe in theory a 50Mhz CPU is capable of doing almost everything I need, but it just lacks the software optimized for it. I think a week to compile everything is too optimistic.
- kwhitefoot 2y ago
  I did valuable work on a 2 MHz Apple II with a 4 MHz Z80 add-on running CP/M that I used to write the documentation. The documentation part was just as fast forty years ago as it is now but assembling the code was glacially slow. The 6502 macro assembler running on the Apple too forty minutes to assemble code that filled an 8 k EPROM.
  - musicale 2y ago
    6502 assemblers are amazingly fast on more recent hardware. Something like 60-70ms to run a script to assemble and link an a version of msbasic (AppleSoft) on my old laptop. https://github.com/mist64/msbasic https://github.com/mist64/msbasic
    - musicale 2y ago
      I usually only notice typos after hn has disabled editing... ;-(
- musicale 2y ago
  Old compilers/IDEs like Turbo Pascal or Think C were/are usably fast on single-digit MHz machines and emulators. And even if the CPU is 50 MHz, modern DRAM and NVMe flash are very fast compared to memory and storage on 1990s (or older) machines. Older versions of Microsoft Office (etc.) ran about the same on 50 MHz systems as Office 365 runs today.
RobotToaster 2y ago
That was before everything became a snap package in a docker image.
- musicale 2y ago
  > That was before everything became a snap package in a docker image. A modern app should consist of dozens of of docker images in k8s on remote cloud infrastructure, all running "serverless" microservices in optimized python*, connected via REST* APIs to a javascript front-end and/or electron "desktop" app, with extensive telemetry and analytics subsystems connected to a prometheus/grafana dashboard. That is ignoring the ML/LLM components, of course. If all of this is running reliably, and the network isn't broken again, then you may be able to share notepad pages between your laptop and smartphone. *possibly golang/protobufs if your name happens to be google and if pytorch and tensorflow haven't been invented yet

bitcompost 2y ago

Oh I believe in theory a 50Mhz CPU is capable of doing almost everything I need, but it just lacks the software optimized for it. I think a week to compile everything is too optimistic.

kwhitefoot 2y ago
I did valuable work on a 2 MHz Apple II with a 4 MHz Z80 add-on running CP/M that I used to write the documentation. The documentation part was just as fast forty years ago as it is now but assembling the code was glacially slow. The 6502 macro assembler running on the Apple too forty minutes to assemble code that filled an 8 k EPROM.
- musicale 2y ago
  6502 assemblers are amazingly fast on more recent hardware. Something like 60-70ms to run a script to assemble and link an a version of msbasic (AppleSoft) on my old laptop. https://github.com/mist64/msbasic https://github.com/mist64/msbasic
  - musicale 2y ago
    I usually only notice typos after hn has disabled editing... ;-(
musicale 2y ago
Old compilers/IDEs like Turbo Pascal or Think C were/are usably fast on single-digit MHz machines and emulators. And even if the CPU is 50 MHz, modern DRAM and NVMe flash are very fast compared to memory and storage on 1990s (or older) machines. Older versions of Microsoft Office (etc.) ran about the same on 50 MHz systems as Office 365 runs today.

RobotToaster 2y ago

That was before everything became a snap package in a docker image.

musicale 2y ago
> That was before everything became a snap package in a docker image. A modern app should consist of dozens of of docker images in k8s on remote cloud infrastructure, all running "serverless" microservices in optimized python*, connected via REST* APIs to a javascript front-end and/or electron "desktop" app, with extensive telemetry and analytics subsystems connected to a prometheus/grafana dashboard. That is ignoring the ML/LLM components, of course. If all of this is running reliably, and the network isn't broken again, then you may be able to share notepad pages between your laptop and smartphone. *possibly golang/protobufs if your name happens to be google and if pytorch and tensorflow haven't been invented yet