Earlier quoted context omitted.
You're misremembering the young web.
Did you see any ads in 1993?
Hmm... Most pages that time were grey with very few images.
Ads were certainly very rare in 1993.
LT6502: A 6502-based homebrew laptop
221–226 of 226 posts
Re: LT6502: A 6502-based homebrew laptop
#222Earlier quoted context omitted.
> The Classic Mac OS model in general I think is the best that has been or ever will be in terms of sheer practical user power/control/customization A point for discussion is whether image-based systems are the same kind of thing as OSes where system and applications are separate things, but if we include them, Smalltalk-80 is better in that regard. It doesn’t require you to reboot to install a new version of your pa…
smalltalk missed the opportunity to incorporate more sophisticated versioning, including distributed versioning with current SotA ideas of course modern smalltalks or st-inspired systems could still incorporate these ideas
Perhaps decades ago there was "more sophisticated versioning" for Smalltalk implementations:
2001 "Mastering ENVY/Developer".
https://www.google.com/books/edition/Mastering_ENVY_Develope...
Re: LT6502: A 6502-based homebrew laptop
#223Earlier quoted context omitted.
I cannot recall crashes being a problem.
With Windows 9x, I recall the crashes being manageable, but it was advisable to give the system 15 minutes to settle down after rebooting. Windows would start multiple things at once on startup and it was a bit risky to overstress it. Windows NT 4 seemed OK, but a lot of software didn't run. By the time of Windows 2000 the tradeoff was much better. (Allowing a settle down time remained a good idea, in my experience.…
In 1997-8 I met the first person I knew to have a CD-R burner.
He dual-booted 98 and NT 4. He joked that NT was his 100+ MB CD burning software. He used 98 for almost everything else, but it couldn't keep that steady stream of data going.
Re: LT6502: A 6502-based homebrew laptop
#224Earlier quoted context omitted.
smalltalk missed the opportunity to incorporate more sophisticated versioning, including distributed versioning with current SotA ideas of course modern smalltalks or st-inspired systems could still incorporate these ideas
Perhaps decades ago there was "more sophisticated versioning" for Smalltalk implementations: 2001 "Mastering ENVY/Developer". https://www.google.com/books/edition/Mastering_ENVY_Develope...
ENVY suffered of a problem that many other Smalltalk technologies suffered: a conflict between a culture of proprietary zeal as a business model and powerful network effects of adoption. Visualage in general was plagued by this. I used to blame Microsoft and Apple successes for the pervasive push for lock-in and "integration" as a feature that defined the era so strongly.
You had on the one hand had a technology that desperately needed adoption to build a culture and best-practices documentation, and on the other hand you had short term profit motive seriously getting in the way, so what you had that was completely cutting edge for decades, eventually it wasn't anymore - or the world moved in another direction and your once revolutionary technology became an ill fit for it.
By the 2000s with monotone and darcs, but specially with the rise of git, other standards for versioning have superseded what could have been. Smalltalkers already by the 2010s should have been wise to try to incorporate what is clearly a standard now but instead a bunch of invented-here systems for versioning and repositories and hybrids have developed in its place. And by incorporate i don't mean "let's make X for ST" but making it core in their implementation so that the system itself is more easily understood and used, even if its to take pieces of it away and use them which is actually a strength and not a weakness! contrary to some brand of 90s-era beliefs.
Generally speaking, to this very day it's regarded as cool and as a feature in ST world that something is ST-only, conveniently "integrated" into the system as tightly as possible and, implicitly but insidiously and glaringly, near-impossible to use elsewhere except maybe as a concept and laundered of its origin.
Re: LT6502: A 6502-based homebrew laptop
#225Good timing. My current weekend project is constructing something similar to the the first third of Ben Eater's 6502 design (last weekend was the clock module plus some eccentricities). It occurred to me that given the 6502's predictable clock cycle timings it should be possible to create a realtime disassembler using e.g. an Arduino Mega 2560+character lcd display attached to the 6502's address/data/etc pins. Of cou…
I was recently using this project. It outputs over serial which is handy for capturing a longer stream. I’m working on a wire wrapped 6502 machine and was getting a weird issue where I could see via the Sync pin that it was mis-executing a byte of data as an instruction instead. The fix was to add another decoupling capacitor next to the CPU…
Re: LT6502: A 6502-based homebrew laptop
#226Good timing. My current weekend project is constructing something similar to the the first third of Ben Eater's 6502 design (last weekend was the clock module plus some eccentricities). It occurred to me that given the 6502's predictable clock cycle timings it should be possible to create a realtime disassembler using e.g. an Arduino Mega 2560+character lcd display attached to the 6502's address/data/etc pins. Of cou…
I was recently using this project. It outputs over serial which is handy for capturing a longer stream. I’m working on a wire wrapped 6502 machine and was getting a weird issue where I could see via the Sync pin that it was mis-executing a byte of data as an instruction instead. The fix was to add another decoupling capacitor next to the CPU… https://github.com/dpm-343/6502-monitor
Neat.