Domain: torun.pl
Stories and comments across the archive that link to torun.pl.
Comments · 7
-
expect the unexpected
Gee, we would have missed out on Anomalous acceleration if we had pulled the plug the first time they wanted to. (Have they adequately explained that yet?)
-
Re:Math and CS are different things
I'd like to see a winbox perform a simulation of a noncompressible fluid with vorticity confinement and added force for convection. Sounds physical, but it's 7000 lines of code (including a model editor and a visualisation module) and solving thousands of linear differential equations within minutes, all done by 5 students in 4 months to pass a subject called Team Programming.
Looks like this.
They use the same differential equations in computer graphics, like the simmulated water in Ant Z. -
Re:Ok, now this just pissess me offOkay, I was gonna let your post go until I saw that little gem... 50MHz system bus? -- The fastest the 486 line's bus got was 33MHz, and they went back to 25MHz system bus for the DX2 (50MHz CPU clock) and DX4 lines
The 486DX/50 (note, not the 486DX2/50) ran on a 50Mhz system bus (or "Front Side Bus" for the young'uns). At the time, this caused hardware developers massive headaches because it was a nightmare trying to build a motherboard that could keep up. VLB (VESA Local Bus) machines, in particular, were the worst as only one (of usually 2 or sometimes 3) slots could run at 50Mhz without adding an extra wait state. Indeed, most VLB 486 boards at the time had a specific jumper to use if you had a 486DX/50 with more than one VLB slot in use that added an extra wait state to keep the system stable.
Here are some websites that confirm this. Alternatively, if you want to trawl through google groups there should be literally hundreds of "DX/50 vs DX2/66" threads arguing about how the DX/50's higher bus speed makes up for the DX2/66's higher clock speed (like this one). Also, if you can get hold of a 486 board, pretty much anything with VLB on it should have a bus speed setting for 50Mhz and another jumper to add a wait state to the VLB. Or, if you're feeling particularly adventurous, Intel's design docs for the 486 should provide the information - although you may have trouble finding info on something so old, the DX/50s were never common because they were quite expensive.
As someone who owned (still do, it's just packed away in a cupboard) a very expensive (at the time) 486DX/50 system, I take offence at you implying my old workhorse doesn't exist !
:). Heck, in the closing days of the 486, there were even a few DX4 chips that could be coaxed into running at 3x50=150Mhz, if you could keep them cool enough.Sure. But what exactly is waiting on the memory? Your joystick?
The point is if there's wait states there it's the fault of slow memory, not the CPU. Your DX/25 might have been faster than a slow-memory crippled DX/33, but that was because of the memory, not the CPU - and I'd be highly sceptical of even such a crippled DX/50 or DX2/66 being slower at anything except a few corner-cases. The other thing to consider, of course, was those were back in the days where the market was rife with people selling motherboards that didn't have any - or fake, nonfunctional - L2 cache. A decent 386 would probably be faster than a 486/33 without any L2 cache., so if the machine you were comparing to was hamstrung like that, it would also have been (*much*) slower.
-
you are an Apple marketing victimjust think about where the computer industry would be without Apple to do the R&D?
Let's look at some of your claims:
3) GUI with the Lisa,
Xerox PARC did the R&D for modern GUIs. The Lisa was Apple's first attempt to copy the Xerox PARC GUI work, and it failed. Then, Apple tried again with Macintosh, and by cutting a lot of corners made the system cheap enough to make it a success.
7) First to develop the laser printer and postscript printing with the Laserwriter,
The laser printer was developed at Xerox PARC. Postscript was developed at Adobe, based on a more complicated PDL developed at Xerox PARC. Apple just happened to create a successful product based on those technologies.
8) First to develop the PDA with the Newton,
The Psion predates the Apple Newton by nearly a decade, and I think it wasn't the first PDA either.
9) First to develop the laptop form factor as we know it with the Powerbook,
Not even close; you can find the history of the laptop here. In fact, the idea goes back to Alan Kay's work on Dynapad--late 1960's or early 1970's.
11) First speech technology with the Apple ][,
The Apple II was irrelevant to speech recognition research and development.
14) First company to ship a consumer digital camera with the Quicktake,
Not even close.
You other examples either refer to system integration issues (e.g., supposed first use of a 3 1/2" floppy--developed by Sony), or are vague and meaningless from a technological point of view.
For a few years, Apple had an R&D department that actually published a little and was fairly high quality. However, I can't think of any fundamental breakthroughs that came out of that, and they disappeared again in the mid-1990's.
In addition to demonstrating your ignorance, I find your posting just offensive: I actually know some of the people who developed the technologies you talk about and I assure you that they didn't work at Apple when they did it. For their own financial gain, Apple has deliberately created the impression that they invented a lot of things that they didn't invent at all--and you fell for that dishonest marketing. Read up on the history of computing--you'll be surprised what you find. -
Re:what about mirrors?
Wow? You've proven this? And all this time I thought it was an assumption that had partial experimental evidence. When do you get your nobel?
-
Re: simpl redirector [was: Wonder ...]
Only one person decided to report a problem with redirurl to me (thanks).
I have decided to disable the cgi program, that you post as an example of the boards-killer (http://www.klaban.torun.pl/prog/redirurl/)
BTW: IE has hundrets bugs, and hundrets would be found in the future. IE bugs should be corrected by Microsoft.
Problems with redirurl:
1. it was placed on the web for public use
2. it does not check if the URL is proper URL, and it does not escape HTML entities on the "warning" page
ad. 1. it was a mistake
ad. 2. it is just a simple redirector, that has been made just for hidding Referrer.
Referrer is logged to local web logs, but is unknown to the target web server.
-
Re:Wonder if that works deeper in a page
You mean this will kill IE?