schlupa

5 ms·

1.
by schlupa 1y ago
The Mega ST keyboard is indeed the best keyboard of the whole Atari family. My TT keyboard has its rubber dome getting stiff with age. This said, the Mega ST keyboard has one big flaw, its plastic is getting extremely brittle and fragile wi
2.
by schlupa 1y ago
The expansion slot of Mega-ST is just 2 rows of 32 pins that are 1:1 connected to the CPU pins. Any extension that was supposed to be solderedon the CPU could be put in the slot with a simple adapter (see f.ex. the Volksfarben ISA slot adap
3.
by schlupa 1y ago
I bought a Mega ST2 because I studied CS and wanted to become a developper. I sold the Amiga 500 my father had bought me. The ST was cheaper for programming than the Amiga 500 as you would need to add, at least a second floppy and a lot of
4.
by schlupa 1y ago
The big advantage we had on Atari and Amiga was that the 68000 could address more than 640K without a sweat. PC's had this annoying limit up until the 90s and the complexity that it introduced was mind blowing (EMM, EMS, XMS etc.). In
5.
by schlupa 1y ago
OP's grievances are spot on for the period 1985 to 1990. After that, PC's did indeed gain enough power (386 were mass and 486 just came out), also VGA started to become. This means that your perception built especially after 1990
6.
by schlupa 1y ago
normal 720 K floppies were very generous with the sectors on a track. It was easy to format a floppy with 10 sectors per track even without reducing the gap between sectors. On Atari it was almost standard praxis which made that floppies ha
7.
by schlupa 2y ago
You're probably meaning the Belgian designed DAI computer that was developed for TI initially but was then refused in favor of the TI-99/4. From a corporate point of view it made sense as the DAI was architected around a Intel 808
8.
by schlupa 2y ago
One thing TI (Extended) Basic had for it that was almost unique among early home computers was its use of decimal floating point with 13 digits precision. It was so useful for maths. I used it a lot at that time in high school. When I switc
9.
by schlupa 2y ago
The fundamental issue with BASIC on the TI-99/4A, be it the regular BASIC or even the Extended BASIC, is that the program was stored in the video memory. This meant that you couldn't use all features of the VDP, you could only use
10.
by schlupa 2y ago
You can also visit one in Germany at the Technik Museum Sinsheim[1]. It has the advantage that it can be compared to the soviet counterpart Tupolev Tu-144 that is also exposed. [1] https://sinsheim.technik-museum.de/en/
11.
by schlupa 4y ago
Not many characters left in ASCII. Reuse of an existing operator almost required. Binary operators cannot be use as it would be grammatical ambiguous and would need resolution at the semantic pass which is a big no-no (that's why C++ i
12.
by schlupa 4y ago
Indeed. Watch Sina's youtube video on Ringo Starr where she explains the very special style he had and what makes his drumming stand out.
13.
by schlupa 5y ago
6502 is nice to program in assembler. For a compiler it is an atrocious platform to support. The limited stack, the 8 bit limit, the zero page idiosyncrasies, the page crossing bugs (some corrected in 65C02), etc. Z80, while also full of a
14.
by schlupa 5y ago
Yeah, I also always have the necessity to look what the compiler does with the code you through at it.
15.
by schlupa 5y ago
This was a real issue with the V2 rocket as related in Irving's book 'The Mare's Nest'.
16.
by schlupa 5y ago
You also have the best programming language in the world and a lot of people dispense only negativity about it.
17.
by schlupa 5y ago
There was Helios64 but unfortunately they went out of business. I have the predecessor system Helios4 and absolutely love it.
18.
by schlupa 5y ago
There's also sometimes the incentive to slow things down because if it is too fast, the client will perceive that he paid too much money for an operation that takes no time, i.e. it doesn't exists seems unimportant.
19.
by schlupa 5y ago
One funny anecdote about Zuse during the war was that he managed to save his Z4 because it was named as V4 in the paperwork. The wehrmacht officers thought it was one of these retaliation weapon V1, V2, V3 so V4 was very important and got h
20.
by schlupa 5y ago
Yes, I know. I just wanted to keep it at the simplest form.
21.
by schlupa 5y ago
That's not how you do it. git checkout master git pull => fetch and merge the new things on master git checkout develop => go back to your work branch git rebase master => simple rebase, n
22.
by schlupa 5y ago
Probably not. The free (as in speech) part of git is what made it usable for entities like google, Microsoft, github etc. If git had been released with the same license model of BitKeepr it NEVER would have taken off.
23.
by schlupa 5y ago
Mmmmh, AGC was not that low level. It was a 16 bit computer, running at 1Mhz with 72 Kb of ROM and 4 Kb of RAM.
24.
by schlupa 5y ago
That's similar to what I do on our translation memory at the Commission. The issue we have is that we search for sentences, not words and the medium length of sentences in the database is around 120 characters and we have around 1.5 bi
25.
by schlupa 5y ago
Yes, that one is especially nasty as &p->bar[0] is a constant expression completely solvable at compile time. It's equivalent to the offsetof() macro of stddef.h
26.
by schlupa 5y ago
That's exactly why X16 uses PC parts for that. The case is a micro-ATX case, the keyboard is a PC keyboard.
27.
by schlupa 5y ago
Mythbuster dispelled that the coating paint could have been the cause of the disaster. https://en.wikipedia.org/wiki/MythBusters_(2007_season)#Hind...
28.
by schlupa 5y ago
and the 911 planes were at best half full when they hit as they already had flown around half of their programmed flight distance.
29.
by schlupa 5y ago
The fundamental difference is that AMD respects exclusion domains even when speculating a thing intel is notorious for not doing. It's a fundamental difference. Intel: speculate without checking rights and crush afterward if a violatio
30.
by schlupa 5y ago
Epyc also has hyperthreading. Intel's security woes have more to do with a deep corporate philosophy than anything else. Meltdown happened because Intel works with the premise: you can cheat (not respect protection domains) if nobody s

More ›