3 ms·

> I think the best way is probably to check out the CVS repo on your machine, then run cvs log, and cvs diff. I've used cvs a bit recently. It's amazing how p

by mlyle 2y ago

> I think the best way is probably to check out the CVS repo on your machine, then run cvs log, and cvs diff. I've used cvs a bit recently. It's amazing how poor the performance is on large repositories, even on modern machines. I can't figure out how I put up with this 20 years ago.

asveikau 2y ago
I remember following the openbsd stable branch about 20 years ago and it was indeed very slow to simply check out and update. Svn felt much better even though it wasn't a revolutionary improvement. I guess that's why the errata page has source patches. It's also great that they have syspatch now for fast binary patches
toyg 2y ago
Everything was slower back then; we just worked at a slower pace and "disconnected". Turn on the PC, and go make coffee; start a build, and go over notes and comments again; start a download, and clean up the desk or go for a drink at the cooler; launch a big report, and make a phone call. Now we're so completely absorbed by the screen for so long, we get irritated by any perceived delay.
- Bagged2347 2y ago
  I want to work in the world you described. I'm 28 and irritated by the pace of modern work, but I have nothing to compare it to and your comment made me ponder. I feel as if there's no room to breathe. Do you have any stories to share?
  - anthk 2y ago
    Get an Usenet account at https://www.eternal-september.org https://www.eternal-september.org, roam around the comp.lang.* groups, setup slrn to fetch news offline and answer to the groups in 'batch' mode, there's slrnpull for that. Learn the basics of C and Perl for automation, Perl can do tons of *unix stuff (awk/sed... but better). Mark Burguess has books on Perl/C (ANSI C and GNU C) and the basics of C++ with systems' programming. I know today Golang would be more apt but if you know how the things work under the shiny stuff, you will apply most of the knowledge from Unix systems' programming to Go in a breeze. Once you begin to automate scripting, testing and repetitive stuff, you will spend less time with computers.
  - toyg 2y ago
    I should say that that type of forced context switching could be very irritating too. It was a joyous time when laptops started booting in seconds... This said, you can and should slow it down if you feel overwhelmed, generally speaking. Use reminders to break every 45 minutes or so, then stand up and walk around. Take longer lunches. Generally speaking, lower expectations about your productivity - which, in itself, should not be a life goal. The cult of productivity helps capital, not people. We should be kinder to ourselves.
- Muromec 2y ago
  Now it’s just running that jenkins pipeline, which takes 40 minutes and requires a manual confirmation in the middle .

by mlyle 2y ago

asveikau 2y ago

I remember following the openbsd stable branch about 20 years ago and it was indeed very slow to simply check out and update. Svn felt much better even though it wasn't a revolutionary improvement. I guess that's why the errata page has source patches. It's also great that they have syspatch now for fast binary patches

toyg 2y ago

Everything was slower back then; we just worked at a slower pace and "disconnected". Turn on the PC, and go make coffee; start a build, and go over notes and comments again; start a download, and clean up the desk or go for a drink at the cooler; launch a big report, and make a phone call. Now we're so completely absorbed by the screen for so long, we get irritated by any perceived delay.

Bagged2347 2y ago
I want to work in the world you described. I'm 28 and irritated by the pace of modern work, but I have nothing to compare it to and your comment made me ponder. I feel as if there's no room to breathe. Do you have any stories to share?
- anthk 2y ago
  Get an Usenet account at https://www.eternal-september.org https://www.eternal-september.org, roam around the comp.lang.* groups, setup slrn to fetch news offline and answer to the groups in 'batch' mode, there's slrnpull for that. Learn the basics of C and Perl for automation, Perl can do tons of *unix stuff (awk/sed... but better). Mark Burguess has books on Perl/C (ANSI C and GNU C) and the basics of C++ with systems' programming. I know today Golang would be more apt but if you know how the things work under the shiny stuff, you will apply most of the knowledge from Unix systems' programming to Go in a breeze. Once you begin to automate scripting, testing and repetitive stuff, you will spend less time with computers.
- toyg 2y ago
  I should say that that type of forced context switching could be very irritating too. It was a joyous time when laptops started booting in seconds... This said, you can and should slow it down if you feel overwhelmed, generally speaking. Use reminders to break every 45 minutes or so, then stand up and walk around. Take longer lunches. Generally speaking, lower expectations about your productivity - which, in itself, should not be a life goal. The cult of productivity helps capital, not people. We should be kinder to ourselves.
Muromec 2y ago
Now it’s just running that jenkins pipeline, which takes 40 minutes and requires a manual confirmation in the middle .