In my experience, I've seen this get messy having to have some apps on the windows filesystem and reading and writing back and forth to the WSL layer for various files. It works, it's just a degraded experience compared to what I have seen going all in on either side.
This reminds me of an small app I wrote and didn't do anything with-- You would choose an API / endpoint to grab data from, then choose how to display that text on a prebuilt or custom uploaded picture. On the ping it would rebuild the image and put the updated text from the api on it so you could have images with more current information (every 5/10/30 mins, etc.) Updating readmes with new screenshots on push is probably a much less cpu and better way to do dynamic image generation, for this use case.
I never ended up using the idea the way I wanted, but this makes me think there's potential in this dynamic image domain yet!
Interesting, I'm using chrome on windows. One thing I also dislike, if I may keep ranting to the internet, is how much windows has fucked with their windowing system in W10. For example: I'd be playing a game and something would cause the game to hang. It happens. But in windows 10 I couldn't even alt-tab because the focus would never leave the hanging 3d area. Couldn't control + alt + delete. Couldn't Windows key + tab, or alt + tab. Couldn't ctrl + shift + esc. Just had to hold the power button down. May I ask you: when was the last time you had to hold the power button down on your mac?
I know this is completely beyond the topic, and only relevant in regards to the website, but, as someone who has been convulsively clicking text while reading articles his whole life, this site design is absolute garbage. When i double click text I do not expect the site to interact. Double click in my world is known for highlighting. Not increasing font size. Sorry, end rant.
I don't think it will be hard for them to introduce voice commands to it with the google home. I understand not wanting to spend more money on another device but this is their whiteboard, then google home is their voice command module.
If I had unlimited funds, I would probably just build a desktop, since they have a really good monthly recap of what hardware works with the current software.
https://www.tonymacx86.com/buyersguide/april/2017
I guess that's sort of where the line is drawn is you can't really "build" a laptop. Seems like there are a few good Dell models that chose hardware that works with mac, though. I'm sure in the near future we'll start seeing more 4k capable hackintosh laptops.
I bought an m.2 solid state and a wifi adapter that is known to work well with hackintosh's (the stock wifi card wasn't compatible), and another 8gb of ram for another ~$150.
So for ~$850, after 'hackintoshing' this computer, I get:
A laptop that gives me the choice to boot into an SSD imaged with latest OSX Sierra, or the regular 5,400 rpm Windows 10 drive. The last thing I want to do with this laptop is exchange the 1tb 5,400 windows drive for a 1tb SSD.
When booted into Sierra:
The software runs exactly the same as using a real mac. I've done some video editing in Final Cut, some audio work in Ableton, streamed 1080p youtube / netflix videos no problem. There's decent battery life, as the guide above shows you how to disable the nvidia graphics card entirely when running OSX (doesn't work anyways) to save battery. The specs are comparable to a modern macbook pro, and in one case even better.
Pros
- Actually get 4k resolution/screen
Cons
- SD card reader does not work
- Mobile graphics Nvidia 960m does not work, but intel 530 HD graphics card does just fine
- Backlight adjustment doesn't not work (could probably spend time to get it to work, but I'm fine without it for now)
- Trackpad is a little too sensitive
Sames
- Hardware: Core i7, 16gb ram
- Full airdrop support
Where am I going with this? In my opinion the general public is becoming more tech savvy. If Apple does not embrace the culture of people wanting to experiment with code (theirs or not) on different devices, then they are putting themselves at a disadvantage. The guides to make hackintoshes are more than likely getting easier and easier as time goes on and support grows. (this was my second attempt and first success)
What a disappointment this macbook pro reveal was. So instead of spending $2,399.00 on a new 15" macbook pro, I decided to hack together a very comparable one for ~$850.
I'll take the $1,550 savings for a little software and screwdriver work, even with a couple of minor issues, any day.
As long as those dedicated apple fans eat it up, I don't expect anything to change anytime soon. But for everyone else who can't afford those business practices, there are ways like what I did above to get what you want without breaking the bank.