4 ms·

You missed out: modifying source code, deducing and adding optimal screen resolutions, editing and compiling keyboard layout, and more. But thanks for reading!

smoldesu 6y ago
To be fair, modifying source code and deducing optimal screen resolutions is all in a days work for most of the people on this site. I'm glad you had fun learning about virtual machines, but GP is right; this article isn't terribly interesting or thought provoking.
- macintux 6y ago
  > Be kind. Don't be snarky. Have curious conversation; don't cross-examine. Please don't fulminate. Please don't sneer, including at the rest of the community. https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html
- msephton 6y ago
  I'm on this site. I'm on your team. The point is that this—however easy you might consider it to be—is a first. Nobody else has done this specific setup. Also, it's an emulator not a virtual machine. 68K vs ARM.
- deleted 6y ago
  [deleted]
stolen_biscuit 6y ago
You should show those changes in your post or elaborate a little bit IMO. I'm being blunt but your blog post is really not engaging because you skip over the most interesting content. Even diagrams showing how you deduced the screen sizes, the changes you made to the code, any problems you encountered etc. I clicked because it was an interesting heading, I skimmed through and gave the TL;DR because it's a 2 minute read that could have been engaging but missed the mark. At the moment the read is essentially compiled an emulator and made some macro keys, you have 1 sentence in the whole post about modifying the source code.
- msephton 6y ago
  Appreciated. If I'm honest I didn't expect this blog post to be read by this many people or get this level of feedback. It was meant as an overview, with a plan to write about the gory details in other posts. For example I've already written a whole section on automation and how the custom keys trigger things (by sending Apple Events). And I've detailed code changes on the GitHub repo wiki. I just didn't think people would be this interested!

smoldesu 6y ago

To be fair, modifying source code and deducing optimal screen resolutions is all in a days work for most of the people on this site. I'm glad you had fun learning about virtual machines, but GP is right; this article isn't terribly interesting or thought provoking.

macintux 6y ago
> Be kind. Don't be snarky. Have curious conversation; don't cross-examine. Please don't fulminate. Please don't sneer, including at the rest of the community. https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html
msephton 6y ago
I'm on this site. I'm on your team. The point is that this—however easy you might consider it to be—is a first. Nobody else has done this specific setup. Also, it's an emulator not a virtual machine. 68K vs ARM.
deleted 6y ago
[deleted]

stolen_biscuit 6y ago

You should show those changes in your post or elaborate a little bit IMO. I'm being blunt but your blog post is really not engaging because you skip over the most interesting content. Even diagrams showing how you deduced the screen sizes, the changes you made to the code, any problems you encountered etc. I clicked because it was an interesting heading, I skimmed through and gave the TL;DR because it's a 2 minute read that could have been engaging but missed the mark. At the moment the read is essentially compiled an emulator and made some macro keys, you have 1 sentence in the whole post about modifying the source code.

msephton 6y ago
Appreciated. If I'm honest I didn't expect this blog post to be read by this many people or get this level of feedback. It was meant as an overview, with a plan to write about the gory details in other posts. For example I've already written a whole section on automation and how the custom keys trigger things (by sending Apple Events). And I've detailed code changes on the GitHub repo wiki. I just didn't think people would be this interested!