We recently conducted a survey among Brackets users. It was open for a limited time and we had 2500+ participants. As promised, we are sharing what we learned.
We had participants from 130 countries.
64% of the participants are less than 30 years of age.
Most Brackets users are Freelancers or Self-Employed.
Most of the participants identified themselves with the title “Full Stack Web Developer”.
jQuery continues to be the most popular framework.
42% of the participants use build tools.
56% of the participants use a CSS processing tool.
60% of the participants use design tool.
We thank all Brackets users who participated in this survey.
As web technology continues to rapidly evolve, tools and web developers are challenged to stay ahead of the curve – a goal seemingly insurmountable. Understanding the evolution becomes a key factor to achieve this goal, and we are constantly trying to better understand you. To that end, we’re launching the 2017 Brackets Web Tools survey to profile and understand you, and all of the apps & services that you use. Please take part in this survey to help us understand you and your world of web development better! The results of the survey would be published on the Brackets blog.
With the launch of Project Parfait in preview, as well as Lee’s open sourcing of his Response tool, I wanted to provide an update on the “Design Comp to Code” tool that we showed last year at Adobe MAX. After a bit of a delay in getting started, we’ve been hard at work turning that vision into a reality as an extension for Brackets. We’ve been able to leverage a lot of work from the Parfait team to bring a comp to code workflow directly into your code editor.
We’re excited about where we’re at now and we’ve recorded a video to share some of the progress we’ve been making. If you’ve seen the MAX video, you’ll see the core features that were in that original vision, as well as some new concepts like code hints for text and generating an asset from multiple layers.
We’ll be doing a private beta of the extension soon and we would love you to be a part of it! If you’re interested in participating, you can fill out the survey here. We’ll be starting small but hope to expand the group fairly quickly after the initial invites.
Over the next couple of months we’ll be sharing more about what features we have planned, so keep an eye on the Brackets blog for updates. We’re looking forward to sharing more of the roadmap and information on the
public preview. Let us know what you think!
=Ryan and the Comp to Code Team
One of the best aspects of hacking on Brackets is that there are no limits. If there isn’t an explicit API, you can just hack the DOM directly. Of course, hacking the DOM isn’t always ideal. For this reason we keep an eye on what extension developers are doing and iterate over the extension API. Here’s our recent proposal.
Ever since I first used TextMate several years ago, I’ve been hooked on “Quick Open” (the feature that lets you jump to any file in your project with just a few keystrokes). I have worked on Brackets’ version of this feature and I thought I’d take advantage of Brackets being open source to talk about how it works.
You may not have noticed, but Brackets has a lot of extensions. These extensions add all kinds of useful capabilities to Brackets (take a look! I bet you’ll find at least one that you’d want). But, I’m sure that many Brackets users aren’t aware of this list of extensions. Even for those who know about the list, it’s inconvenient to install an extension and hard to find out what’s new or keep your extensions up to date.
I personally couldn’t be happier with the open process the team is using to develop Brackets. Following their lead I will be doing my best to keep the design process as open as is useful by posting design drafts for new or planned features here on the blog. If you have any feedback on these design proposals feel free to respond in the comments, ping me on twitter, or find me in the Brackets IRC channel (garthdb).
Currently the Brackets team is implementing an initial version of code hinting. This post outlines user experience design in connection with this feature.