HNHacker News
TopNewBestAskShowJobs

jdswain

389 karma · joined May 5, 2011

Remote Software Architect.

[ my public key: https://keybase.io/jds; my proof: https://keybase.io/jds/sigs/JuHXXIhuefdZjpeFytCS4YvxdoIa6SnkDjV3wcoAB9c ]

submissionscomments
jdswain··on Why Does the U.S. Have Three Electrical Grids?
Wouldn't a better solution be to make them all in phase with each other? Then there wouldn't need to be any HVDC interconnect.
jdswain··on The Sac State 8008: The First Full-Fledged Microcomputer (2008)
The details always matter in these kinds of statements, and I guess there is often exaggeration in a lot of claims to have designed things. Someone that made a one sentence comment on a design then claims to be the one that actually made it work. It’s clear that Woz was a uniquely talented hardware designer, but he also wasn’t living in isolation (although imagine what it would have been like if he had the internet).

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.

jdswain··on Compaq and Coronavirus
The article does have two good topics, and I can see the connection, but it does detract from the message. There are some very important things said about Coronavirus, and USA should be taking notice of this right now, but unfortunately if I forward the article on to someone, the first thing they will read will be some PC industry history.
jdswain··on Ask HN: Who wants to be hired? (March 2020)
Location: New Zealand (timezone quite good for most of US)

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.

jdswain··on Larry Tesler Has Died
I was thinking of Eric Schmidt. A quick check shows a net worth of $14.7 billion.
jdswain··on Larry Tesler Has Died
I think he did, as a consultant. The main reference I found was an article in MacTech, written by an Apple employee:

"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...

jdswain··on Apple's long processor journey
And quite a bit of MacOS was ported back to the IIgs, most notably QuickDraw. The IIgs had ADB before the Mac, and colour QuickDraw years before the Mac had colour graphics.

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.

jdswain··on Fax on the beach: The audacious, visionary, calamitous iPad of the 90s
And the iPad of the 80's would be the Apple //c as featured in the movie 2010. It was seen being used on a beach, complete with LCD screen, and this was 1984.

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.

jdswain··on What is wrong with all those AArch64 desktops?
Which would look a lot like an Apple TV but running macOS.
jdswain··on Steve Jobs: Out for Revenge (1989)
Yep, that was what finally made him a billionaire. Probably Apple phase 2 well surpassed that by the end, but I think the first fortune is the most important Apple 1. Millionaire by 21 I think.
jdswain··on Tony Brooker, creator of Mark 1 Autocode, has died
Mainly because the assembler I knew I had on my computer was the GNU assembler and it uses that syntax. I did quickly try the .intel_syntax directive but it was just easier to change it around as the code was so short.

Most of my assembler experience is with 6502 or ARM.

jdswain··on Having Kids
For the first few years I spent more time thinking about projects rather than actually implementing them. Often this pays of in the long run as you have a much better design by the end and save all that wasted time when you change part way through a project. Plus it made me feel better.
jdswain··on Having Kids
And it’s important for kids to learn to entertain themselves. In this time of YouTube and social media and all the other things that are trying to grab kids time, they still need to learn how to be at peace with themselves.
jdswain··on Having Kids
I always thought it would be incredibly hard to have a child with difficulties like yours. I teach a gymnastics club once a week and have an autistic kid there and instead of being problem she is one of the most rewarding ones to teach (in the limited time I have to spend with her). I’m not in any way a good teacher, but I’m learning a lot from her and actually get a lot out of it myself. I’m sure it’s much harder full time, but in the end it’s just the same challenge all parents have, to try and prepare your kids for life and hopefully give them a happy life.
jdswain··on Tony Brooker, creator of Mark 1 Autocode, has died
Always stayed away from Intel assembly, but thought I'd have a go at running this. First issue was this is I think, Intel format, whereas I was using GNU as, so I had to make a few changes:

  .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.out
jdswain··on Steve Jobs: Out for Revenge (1989)
Depending on how you measure it, it could be up to 4 fortunes:

Founding 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.

jdswain··on Apple’s Use of Swift in iOS 13
Objective-C was designed by adding objects to C. So the base syntax is C. Then the idea was that the object-oriented bits were inside [], and the named arguments or message syntax came from smalltalk and was designed to make the language easer to read. Named arguments are very verbose, but they make the code much more readable.

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.

jdswain··on People Simply Empty Out (1986)
Your SO is very lucky to have your understanding. While personal torment in a situation like this is probably the biggest issue, the fear of others judgement is a very real problem to deal with. So many things that people say are just wrong in these situations, things that are well meaning but misguided. So having the support and understanding of a partner is a great thing, and probably a rare thing. From your comment you appear to have a good understanding of what your SO is going through and that will help keep your relationship strong.
jdswain··on The not so hidden cost of sharing code between iOS and Android
It's mainly because I'm trying to write everything in Swift now rather than Objective-C. I still think Objective-C is a great language, but Swift is the future of iOS development.

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.

jdswain··on The not so hidden cost of sharing code between iOS and Android
I've been using C++ to share code between iOS and Android for years and have come to the same conclusion. I developed the C++ code on desktop operating systems which was easier to debug, but once you move it to mobile then the debugging gets a lot harder (on Android at least).

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).

jdswain··on Have Disneyland fans finally reached their limit?
Theres some simple economics in this. If visitor numbers are down 3%, and say prices are up 5% then total profit is also up, variable costs are down, and parks are less crowded so everyone has a better time.
jdswain··on A photo history of Frog, the company that designed the original Mac
And the Mac SE wasn't introduced in 1984 as the article says, the original Macintosh (128) was introduced then, designed by Jerry Manock as the parent says. The Mac SE and Mac II were introduced in 1987, after the 512, Plus and 512Ke.
jdswain··on Rich Felker of musl libc comments on Google's LLVM libc proposal
In my experience NDK development is quite painful now. Most of my NDK work is a little old now but I found the debugging process quite painful. This was for C++ code that was running on other platforms so almost all of the debugging was due to platform incompatibilities or bugs.

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.

jdswain··on “Origins of the Apple human interface” lecture – an annotated transcription
Regarding the foil reference, it’s actually a reference to something that technology has made obsolete. Back then people used to use overhead projectors for presentations, and the sheets of transparent film were called foils. There were sometimes hand drawn with markers, people could have used LisaDraw to print foils. Later on programs like Aldus Persuasion and Microsoft PowerPoint were used, but for a long time their output was printed rather than used directly like most people know today.
jdswain··on Get Started with 6502 Assembly Programming on Atari Lynx
There is an INC A instruction on the 65C02 and 65816, so this is better if you have anything newer than the NMOS 6502:

  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.
jdswain··on Ask HN: How to get started developing with FPGA?
The books by Pong Chu are really good. You can choose either VHDL or Verilog and then the FPGA you are getting started with. I went through 'FPGA Prototyping by Verilog Examples' as my first starting point with Verilog and it was very easy to follow. This will give you a basic level of understanding of FPGA development, from there you can study more specific topics.

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.

http://zipcpu.com/dsp/2017/08/30/cordic.html

jdswain··on UCSD Pascal pioneer Ken Bowles has died
Bill Atkinson ported UCSD Pascal to the Apple ][, and he was one of the very core Mac developers. Apple Pascal was probably one of the very few software systems that spanned all of Apple's computers at the time. The Apple /// made heavy use of it and had the benefit of a lot more RAM. Then the Lisa Monitor used the same menus as earlier Apple Pascals. I think the Lisa Pascal was licensed from another company and wasn't a port of UCSD Pascal though. One of the first pieces of code for the Mac was a port of the Lisa Monitor, so those Pascal menus were probably the first menu bar on the Macintosh. The Macintosh Toolbox, while written mostly in assembly language had Pascal bindings and much of it was originally written in Pascal before being rewritten in assembly, QuickDraw was based on LisaGraf which was written in Pascal.

https://www.folklore.org/StoryView.py?project=Macintosh&stor...

jdswain··on New Research Finds that Caravaggio Died of Sepsis, Not Syphilis
Simon Schama’s Power of Art series starts with an episode on Caravaggio. The series is well worth watching and explains a lot about the artists lives.

https://en.m.wikipedia.org/wiki/Simon_Schama%27s_Power_of_Ar...

jdswain··on Ask HN: Better tools for the software requirements / scoping phase?
There is a class of tools for this called Requirements Management. They tend to be expensive and clunky tools in my experience, but I haven't used one for quite a few years. Ones I have used are Rational Requisite Pro (IBM) and Doors, which is now apparently an IBM Rational product too. I've worked on a project that used Doors for requirements management but also requirements traceability, a somewhat tedious task that would let us look from a requirement and identify all development documentation that implemented that requirement and eventually to code if required.

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.

jdswain··on Steve Jobs licensed Amazon’s one-click patent for $1M in one phone call
Like this? NeXTstep NextStep NEXTstep...
← PreviousPage 4 of 7Next →