So what IS the point? If you can't code or if you can't use a compiler you might make bloated programs? Surprise, surprise.
..
It happens by default with famous PC compilers. Looks like you replied to this message without reading the entire posting since what you argued against initially was answered later.
>No, size doesn't necessarily have direct correlation with speed unless you count the loading time from the disk or stream the content.
The anim files decompress on the fly-- no streaming or disk reads.
>I never said your bootblock stuff doesn't, but you'll have a pretty frustrating experience watching OCS and ECS demos or games without soft kicking or using WHDLoad.
But Amiga has the edge since if you use OCS standard hardware, it works across the board on all Amigas and you don't have to use APIs.
>That is after the OS loads. Yes, interfacing with "any" soundcard on a PC relies on standard APIs. That's definitely a difference from the "standard" Amiga, but in most regards it's not a short-coming, which is why abstraction layers like RTG and AHI exist.
I'm glad you agree on something.
>Probably not often in DOS demos, but it's definitely possible to support adlib compatible cards in 1k.
Adlib is not supported by all audio cards and even those it's supported on don't use the same I/O port.
>Yes, and a change in sound can happen over an infinitesimal amount of time. It doesn't mean that it's particularily important for our hearing.
In sound, 44Khz..48Khz is enough but in the case of joysticks, IT CAN make a difference. It all depends on how fast the software is sampling the joystick and WHEN it samples. Anyway, your point that humans can't react that fast is false since you can produce millisecond accurate state changes in the joystick that are not NOISE.
>How often do you think the game itself is checking the state? Show me a game that utilizes the superior Amiga joystick port to its full potential!
I can say the same for Audio.
>PS2 as in Playstation 2, not PS/2. I have an adapter to connect two PS2 compatible controllers to one USB port.
So, how does that make it faster than Amigas I/O port access like MOVE.W $DFF00A,D0.
>No. There is nothing to catch up to. Having a joystick port on a computer is totally redundant when you have universal serial interfaces.
It has catching up to do until you prove that you have faster joystick interface that people are using out there right now.
>No. Unless you've been living under a rock for the past 15 years you know that software developers are trying to move further AWAY from the hardware. Transparency, modularity, uniformity, and in the end, system stability, at the expense of exact control...
Believe it or not, people still access hardware I/O ports on PCs in kernel drivers. I write some of these so I know.
>PC:s may very well be (and are) used in low latency/real-time applications.
But PC has catching up to do in regards to Amiga's real-time set-up.
>Given the average life length of a typical PC game pad I'm pretty sure that there are more USB sticks in use. "There are millions of game ports"... How many USB ports do you think there are?
Not ports, USB joysticks that are faster than Amiga's joystick interface.
>The joypads I use have two separate analog joysticks, a directional pad and ten buttons ergonomically laid out.
Analog sticks suck and 10+ button joysticks suck as well. I rather have a one or two button joystick rather than complicate things for kids playing games with 10+ joysticks. "Sorry you pressed Select instead of A". "Sorry you pressed Start although it's labeled as Select." "Sorry you pressed the right white button instead of left black one." Now take this into context of a fast shoot-em up game.
>They work as respond as instantly as necessary for fast shooters as well as old platform games, even if my computer might not be able to sample them at 1000Hz (which I don't know since there are no games that do).
They can all seem instantaneous, but there's factually some time they take.
>There really isn't anything like it for Amiga.
Complete bullcrap.
>On some OS:s I'm sure it's possible. If you need to have timing that tight (i e for timing some sort of serial communication) in any of the mainstream general purpose OS:s you can often outsource the time critical stuff to a $1 PIC.
That's your worst argument so far. Use a piece of hardware. As I stated before, if I use hardware, anything can be done on any computer.
