Rump kernels can also help by simplifying the OS level interface to where effective sandboxing is possible. Microsoft seems much better at this than the others you mentioned (or Linux).Ĭompatability seems like something that the Qubes model could help with quite a bit. Once we do I think we'll be in much better shape to undertake dramatic rewrites, and to reuse code between projects/rewrites. No large projects today meet this standard. ![]() The goal: to be able to certify a release to production just by running its automated tests. I've been working on ways to express more tests than our current (c 1970) unix stack can support. The bottleneck isn't the rewrite itself, it's all the risk due to the regressions that rewrites tend to cause, and all the stress from trying to catch these regressions before a release. The challenge is to make codebases rewrite friendly. Open source is a prerequisite, but this isn't a solved technical problem. Rolling back a set of packages to some older state isn't a trivial operation, and rewrites are incredibly expensive no matter who's doing them. Notice that grandparent said "the situation is even wilder in the closed gardens". I'm not sure I've ever received personal support from Google prior to that, but in my experience, the GCS support team was/is absolutely top notch. It took a couple weeks or so to fix the problem, but they contacted me after each upgrade (rather than waiting for me to contact them) to follow-up and see if my issue had been resolved. I got another reasonably-timed response, and this was an issue on their end (something to do with an occasionally missed automated notification when files were uploaded). The last time I was in contact with them was a few months ago. ![]() That first problem was due to my own misunderstanding of the API, which the person in question patiently helped me better understand. I didn't have high hopes when I first contacted them with an issue, but I got a response in less than 24 hours, and a similarly quick response to my following response. There was only an email address listed in the API docs. I received some excellent support from the GCS (Google Cloud Storage) team while I was working on my last project. (d) Just arriving in person at their nearest Google office, getting entrance somehow, and then directly providing my complaints to the next manager (at risk of getting sued for entering their office illegally) Support methods I have not tried yet, but plan to, in case the previous ones don’t work anymore: (c) Buying Google Apps for Business (the 30 day free month), then calling their support, after the support call was successful, cancelling it again (doesn’t work, Google doesn’t answer Google Apps for Business calls, someone takes your call, you say hi, in the same second they hang up on you) Start an angry thread, get it to the front page – or post a comment on a frontpage thread about a dev topic – and suddenly some Google dev ends up fixing it, and in the same moment, your comment on here disappears. (a) (support for youtube partners, monetized, back in the days, German), The best support (the only real support) I’ve ever gotten for Google products were A desktop application has none of these limitations, whereas they're inherent flaws in the webapp ecosystem. ![]() ![]() You are limited in how you can post your content, where you can post your content, and even what content you're allowed to post. Webapps mean you're even more beholden to someone else for functionality than a desktop app. Not everyone wants to be hyperconnected all the time. So, needing a webapp in such a situation means that I can't edit and arrange my photos at all until I get to a location that has internet access. I'm also not always in a place where I have internet access which is particularly fast and reliable. So again, the webapp usage story falls apart. A lot of the images I make, I tend to want to share in 2 or more other places, not just a random web album. By saving everything locally, I can have the full-resolution image for my own usage, and just pay the occasional cost to upgrade/replace hard drives.įurthermore, I'm almost certainly going to have to have a copy of many of the images on my computer anyways. Webapps right now are amazingly primitive and crude for even the most basic of workflows, especially when you're working with raw images.Īdditionally, in order to save the images I want how I created them, I'd have to pay a non-insubstantial amount of money to store them. Images which I can and do want to work on, crop, tune brightness, contrast, etc, before publishing them. I've got a rather large collection of large photo images.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |