Their success was largely down to their very low price point (clever cost-shaving engineering) at a time when there was a huge untapped public interest in computers.
9,912 karma · joined February 2, 2008
Their success was largely down to their very low price point (clever cost-shaving engineering) at a time when there was a huge untapped public interest in computers.
What was very common on those devices was using the "poke" command in BASIC to change a handful of values, but while it was possible to change code in this way it was much more common to be changing the value of variables - things corresponding to "number of lives left" and the like. Not all that different.
Fairly quickly, though, the games were entirely in machine code and used fancy loaders (still from tape mostly) so you didn't get access to BASIC. This created a market for devices that let you get at a monitor program - the "Multiface" series of addons². They had at least three generations of that device, but the company slightly weirdly evolved into a music production company³ after that, which is kind of cool.
Er, ok, I'll stop now while I still can...
Edit: PS - you should ask him about it. Tell him another former ZX81 owner says "Hi" and that my fingers still ache from that keyboard. Although I sneer a bit at its capabilities, it kicked off an interest in computing that's still paying the bills 40 something years later...
----
¹ https://spectrumcomputing.co.uk/entry/2000265/Book/Not_Only_...
Edit: ...or was it the ukulele?
:)
> I’d recommend you go to the show if you haven’t already, but that’s not really the point of this post.
So while I agree that it is good to contemplate why you like things, that wasn't the topic of the post at all.
The author quite explicitly say so.
I know I'd get used to them, but the key combos used by tmux seem very odd choices, even to someone who used to code on a real glass tty!
https://strangestloop.io/essays/things-that-arent-doing-the-...
Fair if you mean me - I've at most toyed with it, but the shim stuff was off-putting.
I'm a backender though, I don't pretend my opinion is of any consequence here.
> Personally I'm not a fan of this
You make it sound like the shim layer is actively desirable - why is that?
To a very casual observer (me) it seems like it ought to be simple, but I expect there are good reasons why it isn't.
Quality varies, but I think it's only the super small outfits where I've been expected to just wing it.
"The term blob was first used in database management systems to describe a collection of binary data stored as a single entity."
So I guess I'm not any clearer on this point.
edit: If I had to bet on it then I'd put money on the theory that "blob" became "BLOB" to sound more technical though...
Currently in a brief macos phase before I can be issued my Linux laptop at work. It's so clunky. A major annoyance for me right now is the lack of MST multi-screen over USB which means my nice daisy-chained home setup is fine on my near-decade-old Dell but doesn't work at all on the fancy Macbook. They have the hardware to support it, they just don't.
Generally the hardware with Apple is amazing but I'll take the hit on that and things like battery life just to get an OS that feels like it's on my side.
I'd maybe consider Asahi for home use but I'd be wary of it for work. Perhaps in a few years.
Edit: and I'm not btw - for all I know BLOB in DB land might be backronym from blob in the common usage.
Some people get their egoes attached to their choices (for or against Rust).
Also there's a time and a place for all criticism. If the conversation is not fundamentally about language choice then it's very irritating to have it brought up.
This is practically the elevator pitch of the language :) and I speak as one who likes it a lot!
Rust's culture of pushing things into type checking does eliminate a huge swathe of bugs and I wouldn't be surprised if it was the majority.
The hurdle of negotiating translation between filesystem strings and unicode strings strikes me as a good example of a place where most languages don't protect you from bugs and a strongly typed one does. The downside, of course, is that you have to handle these cases (even if it's to explicitly say "I don't care").
I still create dumbass bugs in Rust, but they are usually simple logical errors that are pretty obvious when debugging.