Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Then why are developer tools for a MacBook the same size as the MacBook itself?


The days of tuning software have changed. In the past, these systems were indecipherable and had no good profiling or debugging tools, so they came with a lot of hardware connected which allowed you to profile and tune and debug.

If you wanted to profile PS2 code, for example, the way you did that was with a gigantic logic analyzer connected to various traces at Sony's labs. We used their Redwood City lab. You'd give Sony instrumented code, and they'd do some kind of secret magic on it and run it on this instrumented PS3, and a few days later, you get a profile! Downside, this thing is incredibly complex, but on the upside, you had little performance penalty for profiling. Later, these kinds of tools came built into dev kits.

For the PS3, programming the Cell was quite difficult and so you had to do lots of tuning. The single PPC core (called the PPU) was really slow, so you had to offload what you could to the SPE's, which were incredibly fast on floating point math, but it was on you to interleave DMA and computation in a way to get good utilization of them. The Dev kits had tools to give you visibility into this.

Programming on a laptop only requires the laptop, as you've got all the tools you need in the OS. Only apple does debugging at the board level.

It's fun to take a stroll down memory lane.


Because Apple don’t release low-level dev tools externally? I’m sure there are some wonderful frankensteins in their labs, but they have less of a need to release them externally.


An example of an internal Apple "devkit" for the original iPod Touch: https://www.youtube.com/watch?v=kg62JpqJGBg



What even is a developer MacBook? Any applied computer can be used




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: