gnasher729
  • Member for 5 years, 7 months
  • Last seen more than a week ago
What aspect of portable floating point did Java back down on?
9 votes

The biggest problem was that on Intel CPUs with external floating point unit (80387 IIRC) all operations were done in extended precision, while Java required double precision. And due to “double ...

View answer
When did half-bad RAM chips stop being available?
3 votes

A slightly different situation, but you can buy a brand new MacBook Air right now where only seven out of eight GPUs are working, and save $50. And all new Macs with an M1 processor are sold with ...

View answer
Why user-assembled kits?
2 votes

In many cases, you can maximise profit by having one price for many people, and another price for a few - you just have to somehow achieve this. If you have one price, then the number of customers ...

View answer
Why did 8-bit Basic use 40-bit floating point?
7 votes

This all happened on an 8 bit computer. So the designer of the floating-point format was free to use 3, 4, 5, 6, 7, 8 or 9 bytes for floating-point numbers, there was no particular advantage of using ...

View answer
What "unusual" syntax assembly languages are/were there?
2 votes

Control Data had the only reasonable syntax I’ve ever seen in the COMPASS assembler for CDC 60 bit computers. Most instructions were one letter for the type of instruction, followed by the destination ...

View answer
How did dusty deck Fortran handle overflow?
4 votes

In my dusty memory, F77 on a CDC Cyber 175 would crash on floating-point overflow, and I would assume that applies from 6600 to 176 as well. That might have been due to local setup.

View answer
Was Objective-C really a hindrance to Apple software development?
4 votes

It's an excellent and extremely powerful language. The syntax needs a bit of time to get used to, but after a week or so you should have no problems whatsoever. Named arguments are the best ...

View answer