Brackets, a code editor
brackets.io
Brackets, a code editor
1–10 of 128 posts
Re: Brackets, a code editor
#2Re: Brackets, a code editor
#3IMHO The title should be a little bit more humble.
Re: Brackets, a code editor
#4IMHO The title should be a little bit more humble.
If the person who posted this link believes that it is Beautiful, then it is. You may agree or disagree but humility has nothing to do with it.
Re: Brackets, a code editor
#5IMHO The title should be a little bit more humble.
What's with all of this nonsense about 'humility' lately? It's almost as obnoxious as 'entitled'. If the person who posted this link believes that it is Beautiful, then it is. You may agree or disagree but humility has nothing to do with it.
> Please don't do things to make titles stand out, like using uppercase or exclamation points, or adding a parenthetical remark saying how great an article is. It's implicit in submitting something that you think it's important.
> Otherwise please use the original title, unless it is misleading or linkbait.
Re: Brackets, a code editor
#6IMHO The title should be a little bit more humble.
Re: Brackets, a code editor
#7That's what drew me to the editor in the first place, but it seems to be very buggy. It stops updating the preview sporadically — and predictably, each time I open the JS Console.
As a front-end dev, I can't really count on a preview that doesn't function with developer tools open.
Having said all that, I understand that Brackets is relatively new, and it takes time to iron things out. I will keep up-to-date with their progress and consider using the service in the future.
Re: Brackets, a code editor
#8Re: Brackets, a code editor
#9Re: Brackets, a code editor
#10IMHO The title should be a little bit more humble.
It even includes the domain, which I think is redundant.
> If the original title includes the name of the site,
> please take it out, because the site name will be
> displayed after the link anyway.