diff options
Diffstat (limited to 'blisk.txt')
| -rw-r--r-- | blisk.txt | 6 |
1 files changed, 3 insertions, 3 deletions
@@ -4,7 +4,7 @@ The Developer Edition is of course based on Firefox, which isn't to every develo To say Firefox is slower than Chromium is, in my experience, sometimes true, sometimes not. The two tend to be a bit like race horses that are neck and neck, one occasionally inching ahead of the other only to be overtaken again a month later. -The problem is, for those releases where Firefox is noticeably slower it can be painful to move back to Chromium, which lacks tools I use everyday, like Responsive Design Mode or the pixel-based measurement tools. +The problem is, for those releases where Firefox is noticeably slower, it can be painful to move back to Chromium, which lacks tools I use everyday, like Responsive Design Mode or the pixel-based measurement tools. Enter Blisk. Blisk is a customized build of Chromium that bolts on nearly everything you'll find in Firefox Developer Edition and half a dozen very useful tools you won't. In fact once you try Blisk there's a good chance you'll never use anything else for web development. @@ -20,12 +20,12 @@ The downside to emulation of course is that you're not going to get, for example Another fantastically useful tool in Blisk is the built-in code "analytics" view, which checks your code through various syntax checkers and also looks at performance and cross-browser compatibility. It means you find bugs sooner than if you have to remember to run those tools on your own. It also makes it easier to diagnose the problem -Blisk has a few features I haven't used extensively that might be handy in some workflows, including integration with a cloud-based back end that allows you to, among other things, quickly screenshot problem views and save the image to your Blisk account for sharing with team members. There's also a video recording tool if you need to demonstrate a bug in animation. +Blisk has a few features I haven't used extensively that might be handy in some workflows, including integration with a cloud-based back end that allows you to, among other things, quickly screenshot problem views and save the images to your Blisk account for sharing with team members. There's also a video recording tool if you need to demonstrate a bug in animation. Blisk is also planning to integrate with outside services that would make it possible, for instance, to screenshot a bug and file it to your team's Bugzilla tracker. The integration isn't baked in yet, but it makes Blisk worth keeping an eye on even if you don't jump on it right now. While Blisk has some very useful stuff, it's not yet available for my main development platform -- Linux. Thankfully, while Blisk does add some extras like the synced scrolling and code checking, I've found that most of its features can be replicated in Chrome proper with a few add-ons. If you're a fellow Linux user or you just don't want a dedicated development browser, there are Chromium add-ons that can do some of these things without needing to install Blisk. For instance <a href="http://re-view.emmet.io/">Emmet Re:view</a> offers a similar take on the built-in Chrome device emulator. -The auto-refresh feature is harder to get. It will require a tool like <a href="https://www.browsersync.io/docs"<>Browsersync</a>, which turn requires you first install Node.js. On the plus side Browsersync will work in any browser. +The auto-refresh feature is harder to get. It will require a tool like <a href="https://www.browsersync.io/docs"<>Browsersync</a>, which in turn requires you first install Node.js. On the plus side Browsersync will work in any browser. Still, while you can get close to Blisk, it's unquestionably easier to just download Blisk and get to work. |