![]() Adobe also makes getting in touch with support really hard unless you want to make a phone call. There's no way to remove them on the website if you're outside of your renewal period. I have 8 more Acrobat Pro licenses and one more CC license than what I have allocated. This post made me decide to try to clean up my Adobe licenses. Those three features might be where they spend a majority of their development dollars. They’re also probably maintaining their own OCR mechanism. You can see how that might make compare bizonkers as well. You have to scan through every glyph that appears under the redaction area and delete that text and hope to hell there’s no context metadata that can be used to figure out which character used to be rendered in that spot. You cannot simply draw a black box over the text and call it redacted because those boxes are vector graphics that can be removed (though you could for a raster document, but then you would have to tell users that there is a difference and you have to pay more for one). Letters that seem adjacent (even in the same word) on the page are not typically adjacent in data. If you’ve ever looked at the ass that is a “secured” PDF, you realize that secure redaction is freakin’ hard to do right programmatically. Took like a whole week just to get the logs across (after factoring in the communication delays and timezone differences). ![]() ![]() and this was after several back-and-forth emails where they claimed they couldn't see any logs - to the point that I had to take screenshots with timestamps as evidence that I had indeed uploaded the logs. cab format (which was spat out by their diagnostics tool, a tool they asked me to run) and their excuse was they had no way to extract a cab file - a file format invented by them - so they wanted me to extract the files and then compress to a. It can be incredibly frustrating dealing with their support, like this one time where they refused to accept logs in. Granted, Adobe/Oracle are probably worse, but at least you don't have to call Adobe every month, unlike Microsoft where shit breaks every month. To deal with professionally? Microsoft aren't even high on the list.Ĭlearly, you haven't dealt with Microsoft's customer support. Even back when Microsoft was a giant monopoly their licensing costs didn't get too silly or evil (as opposed to some of their anti-competitive business practices, which I won't defend). But purely from a professional standpoint, they're pretty reasonable and reliable in their approach. If that doesn't get you then their lawyers and auditors will search your network for a random employee installing the Java runtime or Adobe Reader then send you a bill for absurd amounts.ĭo I think Microsoft are the "good guys?" Na. OracleDB), start you at reasonable prices, then suddenly jam in a 5,000% increase that you'll negotiate back down to a "discount" of only 100%. Microsoft wants to be viewed like your electric or water bill: Just the non-optional utility cost of doing business.Īdobe/Oracle buy products with high lock in potential then add a bunch of their other products as dependencies (e.g. They keep price increases just at the level that they're mostly ignored. They just want to be unnoticed, unless you're looking to expand services. ![]() Microsoft's whole game is to keep you happy enough to become invisible, and to keep paying them until the earth falls into a blackhole. To deal with professionally? Microsoft aren't even high on the list. If you have some scale, you can usually consolidate services, as well. With SOA or its cousin Microservices, it's a tractable to rewrite a service from scratch in a new programming language if it seems warranted. Since you can switch out the front/middle/back independently. (Great code already has tests.) When there are problems, 95% of the time, the issues started when the original code was written, and the library swap ends up being an opportunity to refactor something that nobody knew needed to be refactored. In good code, there aren't really any surprises, and most of the work is in writing some tests. Out of a two dozen libraries, one of them gets deprecated after ten or twenty years. Some of the maintenance work I pick for myself is swapping libraries in underlying code. If the front-end is HTML5, it should be maintainable indefinitely. Anything built around HTML/JS/CSS, even if the backend technology is discontinued, you can likely keep re-using the front-end and as well as any database queries. ![]()
0 Comments
Leave a Reply. |