... well, I guess that means I’m a lucky person when it comes to passports. When I reverse search, the best second passport for a German is “Application Error”, and I sure have plenty of those as well :)
... which also happens to match the style of the fossil readme where they are comparing it against git. Instead of presenting factual differences and their dis-/advatages in practical application, it reads like an ego piece and, at least for me, does not win fossil any sympathy.
In general I have sympathy for the free core + pay for enterprise features approach. Seems like a fair model. Where it starts to fall apart for me, is when basic quality of life features like a usable code review (do not trigger a notification for every line I comment) are tagged as “enterprise features”.
At 100% zoom level, the type is not rendered with crisp edges. It looks as if someone had applied a mild gaussian blur. Only once you zoom in, the outlines are sharp as they should be.
I have this issue on a 2012 and 2015 MBP as well as on a MP 5.1. With the built in screens, Eizos and a NEC SV. The only thing thats common across all builds is the OS.
If you think you dont have this issue, compare the rendering of Preview.app at 100% with that of Acrobat.
I’ll be happy if the only thing that ships with 10.14 is a bugfix for the Preview.app. It amazes me that they have not yet unfucked the PDF rendering with a minor release. It amazes me even more, that this issue is not present on the linked wishlist. Do people not view PDFs on their Macs?
“How to take a Photoshop design” should not be a task for the “Modern Frontend Developer in 2018”, because “How to create actionable, annotated design specs” should be a core skill of the “Modern UI Designer in 2018”.
Dropbox provides great value and I dearly miss it, but I can not support a company that willingly hosts a person so closely connected to illegitemate war and crimes against humanity. I doubt this has significance for Dropbox. It is more a matter of personal moral hygiene.
It seems a bit unfair to blame the language for the added complexity that is introduced when debugging a browser script. Pycharm (or any of the JetBrains IDEs with JS support) offer a very comparable debugging experience for server side Javascript.
I would say you are wrong. I have used both and the experience was always worse compared to that of competitors, despite their advantage of
a) deep hardware integration
b) deep platform integration (so much, that it feels like effort is required to not use the services).
I guess it depends on what your bar is for “better than terrible”, but when I look at the richest company in tech that also happens to own the entire stack in play, then “better than terrible” is not remotely good enough.