This is a great start. Some lightweight features that would make this even more ideal (for me) would be:
- retina/3x support
- support for styled components extend feature (if can be made a lightweight implementation)
- maybe default max width of 100% on mobile?
- optional ability to overlay an empty full size block so the image cant easily be right clicked and saved
We started using Prettier as a pre-commit git hook and the results have been amazing. There are developers in PRs who will not be comfortable with the eslint settings, have linting turned off or will otherwise ignore linting. Prettier just streamlines so much and you can disable the warnings in eslint that prettier handles automatically. It's insanely useful.
Yes but why represent data this way when HTTP can already handle binary? Does base64 actually compress binary data enough to make these optimized requests? I'm genuinely asking because I have not googled it yet.
Toyota owns Lexus, Ford had Jaguar and Land Rover, Hyundai owns Genesis, Volkswagon has Bentley, Fiat owns Ferrari. Just like other car manufacturers, Tesla does it all.
This is awful for things like screencasts, I agree with jhasse that it should be implemented by the browser if implemented at all. We shouldn't fix what really isn't broken.
My only complaint is it is written in Haxe instead of ES6. It would make sense to code it in Haxe if it were to be ported to PHP, C++ and the likes but it appears to be strictly for web audio
- retina/3x support - support for styled components extend feature (if can be made a lightweight implementation) - maybe default max width of 100% on mobile? - optional ability to overlay an empty full size block so the image cant easily be right clicked and saved