Sure thing. I looked a few local (in my city, Brisbane, Australia, within ~1.5h of commute). I want to do a combination of dry and wet labs, so I need to be able to attend in person. I cannot relocate (have family).
I reached out to a few people in my network who did related study at the universities. In general, they all had good things to say. I ended up going with the one I thought had the best reputation both locally and nation-wide, which is UQ. Link: https://study.uq.edu.au/study-options/programs/master-bioinf...
Definitely targeted at the enterprise, but it's entirely possible to provision and operate a single instance without any kind of enterprise-level agreement.
Thanks for answering! Other providers for OS X solutions are super dodgy / shutdown / involve time sharing (no imaging, you store everything into a personal Dropbox).
I ask about OS X support as the requirement for OS X to run Xcode kills a lot of iOS development workshops as the cost is to high / device availability is low.
As a (primarily) iOS developer by trade, I feel your pain. There are colocation operations that seem to do well. They involve racks and racks of Mac minis hanging out in a datacenter somewhere -- since it's Apple hardware, it's totally acceptable within OS X licensing terms. It costs more, of course, but it might be a valuable investment to an operation that relies on a volume of machines to be available and shareable while staving off concerns about wear and tear.
I'm with MacStadium and we just acquired Macminicolo. Let me know if you have any questions. We've got large enterprise customers, developer shops, and popular SaaS tools like Travis CI using our dedicated rented Mac servers and Mac private cloud platform.
Apple's included screen sharing tool is a Mac-specific solution. At MacStadium, we provide iRAAP server on our dedicated Mac servers for customers connecting from Windows computers; it allows for RDP access to the remote Mac.
Worked on Workspaces at AWS for about a year, on the software clients in particular. I think their product has potential but for the moment is limited by some underlying technology decisions made in the interest of a quicker go-to-market.
I would not be surprised if at some point soon their underlying tech became all first-party and we saw some significant improvement. There are plenty of resources throughout AWS that with some work could be composed into a better stack than the 3P pieces and protocols they use currently.
I don't think I've disclosed anything here that isn't already public knowledge, past my own wild speculation based on zero knowledge of internal workings since my departure. If anyone has any questions that I can answer without endangering myself to NDA issues, I'd be glad to answer about Workspaces.
I think it's a great product for those who benefit from it; I ended up leaving the team because while the technological challenges were interesting, I couldn't put myself in any potential users' shoes, and therefore really couldn't drum up much organic passion of my own.
Is there any possibility of insuring that Workspaces will be accessible to users of assistive technology? I use a WIndows PC because that's what has the best screen reader support, a quick google search didn't turn anything up about running a screen reader in the workspace and having it's sound piped back to the thin client.
coincidentally, that's what I was doing in march, and... surprisingly, it sort of worked.
client had JAWS, and the JAWS installer read itself to me while it was installing - I was rather impressed. Had to reboot, and it never came up after that - assuming it was related, but never figured it out.
The NVDA screen reader did work, as well as the windows voice assistant thing itself. both would generate audio in the workspace, and I was hearing it over my el capitan local setup.
The Jaws problem may have been video card drivers. Jaws installs it's own video driver that I have found to not work under Virtualbox unless guest additions are installed. I could see there being something in the Amazon virtualization solution that could cause problems with the driver.
I wanted to dig in to a bit further, but the client just reset the whole thing and said "you don't get JAWS now". Project cancelled soon after that - unrelated to JAWS/workspace.
Don't have time now, but hopefully it will be resolved at some point. NVDA was 'good enough' for the testing I was doing, and it was pretty slick to know the audio was streaming and working without any extra configuration. Probably old hat for some folks, but I'd never experienced that before. :)
