389 karma · joined May 5, 2011
[ my public key: https://keybase.io/jds; my proof: https://keybase.io/jds/sigs/JuHXXIhuefdZjpeFytCS4YvxdoIa6SnkDjV3wcoAB9c ]
In Chuck Peddles oral history at the Computer Museum he has this to say about Apple:
Peddle: Apple II. OK, so Apple I. Peter lived in the Bay Area, and he was my salesman for the Bay Area. So he was selling Atari and all that sort of stuff. And we went to two or three other of his customers and helped them with the ICE. And he called up and said, hey, we got these two young guys working on this computer in their garage, and they can't make it work. So Peter and I took the ICE down, and we made it work.
Peddle designed the 6502 and a lot of 6502 systems, he would have been a great person to have around to get your design going. And an ICE (In Circuit Emulator) would have helped too.
Remote: Yes
Willing to relocate: No
Technologies: iOS, Android, Swift, Objective-C, Kotlin, Java, C++, Embedded
Résumé/CV: Available on request
Email: Jason@1av.com
I've been living in UK for a long time and working on some very large projects, mostly at architecture level. Now I live in a small town and am looking for remote work. I have a lot of experience with iOS development, and a bit with Android. I've been working with Objective-C since 1991 on NeXT computers. Lately I've been doing contract app development but would like to work on larger and more challenging projects. I've also been doing some more diverse work lately, including a complete system including embedded development, LoRa radios, and a Web management console running on Raspberry-Pi. I've also built a lot of audio apps and know streaming technologies well.
"Object Pascal is an extension to the Pascal language that was developed at Apple in consultation with Niklaus Wirth, the inventor of Pascal."
http://preserve.mactech.com/articles/mactech/Vol.02/02.12/Ob...
At the time it looks like the 65816 was deliberately speed limited so as to not overshadow the Mac. Mac was 8MHz, IIgs was 2.8MHz, the 65816 eventually got to 14MHz+, if Apple released an 8MHz IIgs it would have compared very well against the Mac. Woz is even quoted as saying that.
Also, the Mac IIfx had two 10MHz 6502 based I/O processors to offload work from the main CPU.
There's a couple of issues though, the //c did not run off battery power, so you'd need a long cord, and the LCD was terrible, I don't think you'd be able to read it in direct sunlight. But if you have a long phone cable to go with the power cord, maybe you could have sent a fax? Or at least a telex.
Most of my assembler experience is with 6502 or ARM.
.global _start
.text
_start:
mov $1,%rax # write(
mov $1,%rdi # STDOUT,
mov $msg,%rsi # msg,
mov $len,%rdx # sizeof(msg)
syscall # );
mov $60,%rax # exit(
mov $0,%rdi # EXIT_SUCCESS
syscall # );
.data
msg: .ascii "RIP Tony, Father of Assembly Language\n"
len = . - msg
Then you can run with: gcc -c src.s && ld src.o && ./a.outFounding Apple. Pixar. NeXT? Apple the second time.
I'm not sure if you'd count NeXT as a fortune, it looks like he got something a little under $40m in Apple shares, still not bad.
Then much later Apple added the . syntax, which while more familiar to a lot of modern developers kind of broke the cleanliness that the syntax used to have.
It was easier in Objective-C as you could just rename your code file with an extension .mm rather than .m and that made it Objective-C++ and then you could import your C++ headers and use your library as you should. With Swift you don't have that option, and even the interface to C is more difficult.
Even with Objective-C there is still some work in converting data formats (NSString to std::string etc.) and you need to be careful of C++ exceptions and NSException.
The overhead of the JNI interface is quite a lot of work too. Luckily I had a UML model that I generated the interfaces out of, so adding JNI was just a matter of templating this out of the UML, but it was still quite a bit of work.
On iOS the situation has gotten worse in that the interface between Swift and C++ has to go through C, so if you are using C++ you need a special interface layer, which is almost like the JNI situation on Android.
So you have the trade-off of on one hand having two code bases (Swift, Kotlin) and the associated headache of keeping them in sync, versus the extra work of maintaining the C++ interface layers and testing and debugging on each platform. In the end I now believe that it is better to work with the platform native development tools rather than trying to share C++.
As far as finding developers goes, because of the rarity of using C++ on mobile there will not be a lot of developers with this experience. I work remotely and have found that any remote C++ work is very rare, Swift and Kotlin are a lot easier to find work with (it's still more difficult that you would think to get remote work of any type).
But I did notice in the linked article that they are only targeting x86_64, so I don't think this libc is targeted at Android.
EOR #255 ; Invert
INC A ; Add 1
It looks like the Lynx has a 65SC02 which is a 65C02 without the bit manipulation instructions, so it should have the INC A instruction.There was a good article yesterday on HN that went through the process of taking the Cordic algorithm and implementing it in Verilog, it's a good example of using FPGAs to implement a specific algorithm.
https://www.folklore.org/StoryView.py?project=Macintosh&stor...
https://en.m.wikipedia.org/wiki/Simon_Schama%27s_Power_of_Ar...
From an logical point of view I think it makes a lot of sense to start from clearly documented requirements, then work forward to design, implementation, and testing with links back to each requirement. I don't know how testing (higher level than unit testing) can really be effective unless they have requirements documents to use as their starting point. Use Cases go some of the way to providing this information but tend to be a bit less formal. Agile methodologies tend to be less formal than older methodologies that emphasised this kind of process more. A lot of Agile is good, but it does also tend to forget lessons from the past.