1. 28
  1.  

  2. 9

    While the SE/30 isn’t doing as much of the work here as I’d want it to… this is very cool! Nice job.

    I think the SE/30 is one of my favorite computers ever.

    And also, how are you getting cmake to build binaries for an SE/30? I really admire the twisted mind that came up with a way to do that. Well done (either to you or whatever project you pulled in to do that)!

    1. 1

      One of my friends in college had an SE/30, and it really was a great computer: monochrome graphics and classic Macintosh case, but inside, actually more powerful than most of the color Mac IIs that were around at the same time. I think my friend actually ended up running A/UX on it, which made it even more impressive.

      1. 3

        I worked in an apple repair shop for most of the 90s. We had an SE/30 running A/UX as a file server until about 1997. At which point we replaced it with an apple network server 700 running AIX right around the time they were discontinued and the sales group no longer felt the need to have one on hand for demos.

    2. 5

      This is really cool. I love how people go out of their way to express their fondness for the classic Mac era.

      1. 0

        The app is called MacPlayer and works thanks to the magic of Spotify Connect. The speaker itself streams and plays the music, and the Mac simply tells the speaker which song to play (as well as volume, current playlist, shuffle mode and other settings). Communication is over Wifi.

        So this is not an actual player which decodes the stream and plays it on Mac’s audio DMA, only the UI controller. It’s very annoying in such kind of projects these days, same for “Slack client on C64!!!!!” which is actually a VT100 telnet client communicating with actual Slack client on Raspberry Pi. And so on, in modern programming too (like, people call their borderlees website an “application”)…

        In other words, people want to be “cool” and shown like ultimate heroes, but they are scared about actual hard code and special challenges related to the platform they’re targeting, which is sad and most likely will turn out bad in the future.

        1. 13

          In other words, people want to be “cool” and shown like ultimate heroes, but they are scared about actual hard code and special challenges related to the platform they’re targeting, which is sad and most likely will turn out bad in the future.

          I’m disappointed by this. By the same logic, since all the playlists and music is stored on remote computers in the first place, the official Spotify players themselves aren’t really apps, just attempts to be “cool.”

          Older computers had many task-specific peripherals to get the job done. That’s why Apple IIs, early PCs, and even cheaper computers like the Commodore 64 had so many expansion ports. This to me feels very much in the spirit of how people programmed those computers. The C64 doesn’t have enough power to do speech synthesis? Fine, here’s a cartridge. Your PC can’t make real sound with just the PC speaker? Fine, here’s a Yamaha DSP. Or in this case, the Mac doesn’t have enough CPU to decode MP3s and handle the DRM and reencrypt to HTTPS? Fine, we’ll use a couple separate specialty components for those things.

          You’re both discounting what was accomplished here and being unrealistic about how it would’ve been done with an actual Mac SE back in the day. I’m sad to see such negativity here. This forum is usually much more appreciative of this kind of fun hack.

          1. 1

            I’m disappointed by this. By the same logic, since all the playlists and music is stored on remote computers in the first place, the official Spotify players themselves aren’t really apps, just attempts to be “cool.”

            It’s stored remotely, but it’s played locally. Just like you would use a regular player with, for example, an SMB share. Same thing on this particular Mac would be completely okay if you lack a harddisk.

            Older computers had many task-specific peripherals to get the job done. That’s why Apple IIs, early PCs, and even cheaper computers like the Commodore 64 had so many expansion ports. This to me feels very much in the spirit of how people programmed those computers. The C64 doesn’t have enough power to do speech synthesis? Fine, here’s a cartridge. Your PC can’t make real sound with just the PC speaker? Fine, here’s a Yamaha DSP. Or in this case, the Mac doesn’t have enough CPU to decode MP3s and handle the DRM and reencrypt to HTTPS? Fine, we’ll use a couple separate specialty components for those things.

            This isn’t correct at all. I mean, it is, but only in burger mentality where you don’t even try to work a bit harder on particular problem, but pay a slave worker to do this.

            The C64 doesn’t have enough power to do speech synthesis?

            Of course it does, and performs really well. The software is patched SAM & Reciter to work with Polish. The VIC-II is disabled during speech to free up DMA speed for cartridge access, but no one prevents you from precalculate speech sample and put it in RAM, like some games (remember Impossible Mission?) did at build time.

            Your PC can’t make real sound with just the PC speaker?

            Oh dude. There are numerous more and less creative ways to play regular PCM-based tunes on PC speaker and I didn’t even looked deeper than first YouTube link. Methods to achieve that are so diverse you can even play a sound using only an Atari XL/XE video output chip (GTIA, not to confuse with actual GPU, ANTIC) and fancy interrupt handling.

            Or in this case, the Mac doesn’t have enough CPU to decode MP3s and handle the DRM and reencrypt to HTTPS?

            This particular Mac SE/30 has a Motorola 68030@16MHz and 1 to 128 megs of RAM (I assume some modest quality of life upgrade, 4MB at least). It’s absolutely enough to decode MP3s (with some assumptions about buffer of course) and on Amiga it was even more than needed, leaving you with some cycles to do your office work.

            You might be right about HTTPS though - due to its recently increasing complexity because why the fuck no, everything beyond x86 at Pentium II grade is out of the league. On the other hand, the OpenSSH w/ SSH2 and recent ciphers works acceptable on Amigas with 68060 without blocking other tasks too much.

            So, some sort of ssl-stripping proxy in the middle would be accepted. But it’s no tied to this particular software and can be used with anything else. The software running on the Mac wouldn’t be tied to the outside bits of code, just requiring the HTTPS endpoint which you can provide however you want.

            You’re both discounting what was accomplished here

            Yes, because it’s just a mockup and requires actual modern machine to do all the stuff. In 90s, everyone would call this software a “lame” way. Huge expectations, little code, pretends to be something that it’s not.

            and being unrealistic about how it would’ve been done with an actual Mac SE back in the day.

            Absolutely no. 80% of regular Spotify client feature set could be done on that Mac (and even more on later 68k MacOS workstations). But it requires actual understanding of the target platform and - what’s seriously missing here - some bits of true love.

            You see, all that retrocomputing stuff isn’t about showing off and acting cool. It’s about these platforms. People are doing excellent things to prove their loved machines can still be relevant and do modern work without offloading it onto Raspberry Pi hidden under the table to gather internet points on reddit and orange site. People are dedicated to particular line or brand or model they used in the past, can utilize and show its unique features and don’t strip everything into least common denominator.

            I think this particular project, while “looking cool” is actually disrespectful to the Macs. This guy could do the same thing on PC, Amiga, C64, Atari or even a ZX Spectrum - requires only the monochrome bitmap graphics, keyboard and serial to communicate with ESP8266 (which even does HTTPS on its own).

          2. 3

            Pretty close to my reaction too. All the audio decoding and network streaming is handled by some very fancy speakers; http-based API auth delegated to a phone app. So, it’s mostly a visual gimmick… but still cool. I don’t blame them for not wanting to put the (much more difficult) technical effort into achieving (much lower quality) “authentic” sound.

            I used 68k Macs long ago, but it’s not really my scene. I didn’t even know there was a wifi card for the SE/30.

            1. 3

              There wasn’t, it’s also a trickery. There’s a dongle with ESP8266 which plugs into serial port and provides extended AT commands set so it can act more or less like dialup modem.

              1. 12

                Trickery feels like the wrong word there. That sounds like a damn good hack to me.

                1. 1

                  The „fake” is more appropriate, because it strips down the running computer to the form of dumb terminal and deprecates all its unique features so it doesn’t matter which machine you have at the end of the day.

                  You can surely set up a TCP stack on C64 or Atari. Well, you can even get a working 802.11 stack on Amiga and it doesn’t require using such lame solutions.

                2. 2

                  I’m not sure about that. In the picture, it sure looks like there’s a wifi antenna coming out the back, and nothing plugged in to the serial ports. Author linked to https://github.com/antscode/MacWifi which mentions some devices. I recall having a 68040 PowerBook with onboard ethernet (via a ridiculous dongle) and could use wifi PCMCIA cards, so it doesn’t seem all that far-fetched. I’m not going to dig any further, though. I waste enough time on even older machines!

                  1. 1

                    I need more information about this! Do you have a link?

                    1. 1

                      Just duck the “esp8266 serial WiFi”

                  2. 1

                    I wonder if any of the 68k Macs even have enough power to decode AAC…

                    1. 2

                      Spotify uses AAC only on macOS/iOS from what I remember, other platforms get Vorbis or MP3, depending on chosen quality.

                      1. 2

                        I imagine that even 128kbps MP3 is a big struggle for a 68030 on it’s own, but I wasn’t aware they still served some music as MP3.