Jump to content

SlithyMatt

Members
  • Posts

    790
  • Joined

  • Last visited

  • Days Won

    59

Everything posted by SlithyMatt

  1. I use Gimp, and that works just fine on any desktop platform.
  2. I don't doubt you could pack a very simple C++ program into that much memory. But you are also dealing with a MUCH faster processor than an 8MHz 6502, and a much simpler system that doesn't have to do things like manage VERA graphics and play PSG sound effects. As for C++ on mid-80s DOS PCs, it was not really a common thing, and I don't know of any commercial software that was developed using C++ for that platform in that era. C++ didn't really take off on Wintel PCs until the advent of Visual C++, and that was really for 486 machines and better. Look, I don't want to discourage people from trying anything, but just to manage expectations. We have the gift of the X16: a machine so beautifully simple and yet so capable it becomes a joy to program in assembly language or in very simplified C and create really wonderful software. Adding all this complexity and abstraction is just going to give you something watered down, a less capable PC. Again, JUST MY OPINION, but this goes into the territory of just getting a Raspberry Pi and doing C++ development there. Or python or whatever.
  3. Even if it's a freestanding application with no iostream or other standard library calls, this is still not a bare-metal Raspberry Pi were talking about here. The X16 is much, much smaller. You will still need a separate frame stack and probably a heap to make C++ worthwhile. You could allocate everything statically, and then you just have classes standing in for structs and not doing any of the actual OO things. The question really becomes, "what is the value added by developing with C++ over C for the X16?" Sure, you COULD do it, but is it really going to make development any more efficient or enjoyable? Or is it just a parlor trick of "hey, look: 8-bit C++" and then you go back to assembly or just plain old C to develop a real application?
  4. It's about what kind of 6502/X16 code would be generated from an LLVM iostream implementation. Using C++ is nice, but using the language as intended on a 6502-based system is a bit dicey. What's lean and efficient on an x86-64 or ARM64 with GB of RAM could still be bloated and sluggish on a 6502 with kB of RAM.
  5. cout << "Hello, World!"; Hello, World!
  6. It would help to better define what you mean. Are you looking for something like a 486 motherboard?
  7. This is the best one I've found: http://map.grauw.nl/resources/sound/yamaha_ym2151_synthesis.pdf
  8. This reminds me of a stash of faxes from the 70s that were from my grandfather's desk at AT&T. They were totally memes, and early fax adopters did share them with their social network. Like, political memes from the 1972 election, but then they would have just called them cartoons. Anyway, to get back on topic, if Commodore did the right thing and hired me (a grade school kid) to replace Jack, I would have made much better decisions. I mean, it would be hard to make worse decisions. First off, when the C128 failed to expand the 8-bit market, that would have been the end of it. Keep selling C64s and software and peripherals until the market dried up, just like Apple did with the ][ line, meanwhile concentrating R&D and marketing efforts on the Amiga. If they hadn't tried coming up with 50 different 8-bit platforms that nobody wanted, they could have made the investment that would have prevented PCs and Macs from overtaking the Amiga in capability in the early 90s. As I recall, the Amiga barely existed in the US -- I only knew it was still around because of magazine articles mentioning that certain games were also on Amiga (to only a slightly greater extent that Atari ST support). They should have been matching Apple's marketing budget dollar for dollar, and making sure the tech stayed just ahead of PCs as Apple did and managed to survive long enough for Jobs to refocus and reinvigorate the company. Who knows who the savior of Commodore could have been in the mid 90s (besides a now-adult me, of course), but I bet they could have pulled through if they didn't make half of the staggeringly bad choices they made in the late 80s and early 90s.
  9. It's really hard to beat a Chromebook for value: https://www.amazon.com/Samsung-Chromebook-Celeron-Processor-Gigabit/dp/B07XL4JHXR?ref_=Oct_DLandingS_D_d11b2207_65&smid=ATVPDKIKX0DER&th=1 You can run python and all sorts of games on them now. Not really for learning about low-level stuff, but it's a great option for a kid's first PC and meets all their needs, including learning how to code. If you are marketing something less capable at the same price point, you might as well just make a bonfire with your money.
  10. You could try contacting the developer. There is an email on the Google Play page. Chances are they are not active in this community anymore, but may be willing to share their code.
  11. Actually, there is: https://play.google.com/store/apps/details?id=dk.applimate.x16emu&hl=en_US&gl=US Funny thing, that Google. You can actually search for apps on the Google Play store for the Google-controlled Android OS. Just note that this is not an official build of the emulator, and it is using a very old version of the emulator code and ROM. Also, without a bluetooth or USB keyboard, it's pretty useless. But the work has been done, and it shouldn't be too difficult to update the build.
  12. And to be clear, it's really a VIC-20 with only IEC and no VIC chip.
  13. The years line up with III, which is why I guessed that.
  14. There is pretty much only one compiler used for WebAssembly, which is clang, which compiled to LLVM and then Emcripten can take LLVM and make it either WebAssembly (which is not actually JavaScript, but a virtual machine code implemented by all modern browsers) or asm.js (which is a virtual machine implemented in actual JavaScript).
  15. It's just one source "flavor": C. It can be compiled to different platforms, including WebAssembly, which is how the web version works.
  16. A lot of folk have proposed things, mostly related to networking or some other comms, like an ethernet or RS-232 serial port. Pretty much anything you can think of, especially if you have extra processing capability on the board.
  17. The X16 won't be compatible with ISA, but it will have expansion slots with edge connection sockets, much like 8-bit ISA in form factor, but with a different pin out. So, there won't be any off-the-shelf cards at first, but pretty much all of those things are possible, but some may require "cheating" by sticking a PiZero or something on the card.
  18. The Mega 65 is not compatible with MS-DOS, which I assume you mean. CBM/Commodore DOS is not a game platform, just a means of dealing with floppy-based file systems. But there are all sorts of demos out there for the Mega 65.
  19. I use Audacity, and it works great for any bitrate you want. That's what I used to generate all the tracks for this demo:
  20. It's also worth noting that C/C++ jobs are generally better paying, as well.
×
×
  • Create New...

Important Information

Please review our Terms of Use