If you must add a rich text editor to an interface, this open source offering from Basecamp looks good.
Monday, October 1st, 2018
Thursday, August 2nd, 2018
Chris has written about switching code editors. I’m a real stick-in-the-mud when it comes to switching editors. Partly that’s because I’m generally pretty happy with whatever I’m using (right now it’s Atom) but it’s also because I just don’t get that excited about software like this. I probably should care more; I spend plenty of time inside a code editor. And I should really take the time to get to grips with features like keyboard shortcuts—I’m sure I’m working very inefficiently. But, like I said, I find it hard to care enough, and on the whole, I’m content.
I was struck by this observation from Chris:
When moving, I have to take time to make sure it works pretty much like the old one.
That reminded me of a recent switch I made, not with code editors, but with browsers.
I’ve been using Chrome for years. One day it started crashing a lot. So I decided to make the switch to Firefox. Looking back, I’m glad to have had this prompt—I think it’s good to shake things up every now and then, so I don’t get too complacent (says the hypocrite who can’t be bothered to try a new code editor).
Just as Chris noticed with code editors, it was really important that I could move bookmarks (and bookmarklets!) over to my new browser. On the whole, it went pretty smoothly. I had to seek out a few browser extensions but that was pretty much it. And because I use a password manager, logging into all my usual services wasn’t a hassle.
Of all the pieces of software on my computer, the web browser is the one where I definitely spend the most time: reading, linking, publishing. At this point, I’m very used to life with Firefox as my main browser. It’s speedy and stable, and the dev tools are very similar to Chrome’s.
Maybe I’ll switch to Safari at some point. Like I said, I think it’s good to shake things up and get out of my comfort zone.
Now, if I really wanted to get out of my comfort zone, I’d switch operating systems like Dave did with his move to Windows. And I should really try using a different phone OS. Again, this is something that Dave tried with his switch to Android (although that turned out to be unacceptably creepy), and Paul did it ages ago using a Windows phone for a week.
There’s probably a balance to be struck here. I think it’s good to change code editors, browsers, even operating systems and phones every now and then, but I don’t want to feel like I’m constantly in learning mode. There’s something to be said for using tools that are comfortable and familiar, even if they’re outdated.
Monday, July 9th, 2018
Is it a graphic design tool? Is it a text editor? Is it just good fun?
Wednesday, May 16th, 2018
This is the dumbest publishing platform on the web.
Write something, hit publish, and it’s live.
Wednesday, March 7th, 2018
This is impressive—a fully featured graphics app for creating SVGS right in your browser.
Tuesday, August 29th, 2017
Tuukka Ojala is a programmer working on the web. He’s also blind. Here are the tools of his trade.
Thursday, May 18th, 2017
Lea has also written an introductory article on Smashing Mag.
Wednesday, March 22nd, 2017
Incredibly impressive work from the CodePen team—you can now edit entire projects in your web browser …and then deploy them to a live site!
Monday, January 9th, 2017
This looks like an interesting little Markdown editor. I think I’ll take it for a spin.
Wednesday, October 12th, 2016
It’s a bit like CodePen but it shows the whole HTML document, which makes it particularly useful for teaching front-end development to beginners (ideal for Codebar!).
CodePen for snippets; Thimble for pages.
Sunday, June 26th, 2016
At An Event Apart in Boston, I had the pleasure of meeting Hannah Birch from Pro Publica. It turns out that she was a copy editor in a previous life. I began gushing about the pleasure of working with a great editor.
When I think back on happy memories of working with world-class editors, I always a remember a Skype call about an article I was writing for The Manual. I talked with my editor for hours about the finer points of wordsmithery, completely losing track of time. It was a real joy. That editor was Carolyn Wood.
Carolyn is going through a bad time right now. A really bad time. A combination of awful medical problems combined with a Kafkaesque labyrinth of health insurance have combined to create a perfect shitstorm. I feel angry, sad, and helpless. At least I can do something about that last part. And you can too.
Thursday, April 14th, 2016
This looks like it could be a very nifty tool to have at your disposal while coding. I like that it’s editor-agnostic.
Saturday, March 26th, 2016
This could pair up nicely with the most dangerous writing app.
Monday, December 28th, 2015
I really, really want to like this article—it’s chock full of confirmation bias for me. But it’s so badly-written …I mean like, just the worst.
Here’s an actual sentence:
So with a capable, HTML-based platform and a well-designed program that makes good use of CSS, one site could support phones, tablets, PCs, and just about anything else with one site.
So, yeah, I’m still linking to it, but instead of it being for the content, it’s because I want to lament the dreadful state of technology writing.
Sunday, March 30th, 2014
A useful text editor that analyses your writing for excess verbiage and sloppy construction. It helps you process your words, as it were.
Tuesday, October 29th, 2013
From the lovely people behind Editorially comes STET:
A Writers’ Journal on Culture & Technology
Monday, February 11th, 2013
A collaborative writing tool built by a dream team. I’ve been using it for a while now and it’s very nice indeed.
Friday, October 22nd, 2010
Tuesday, March 9th, 2010
Edit some CSS rules and this in-browser code editor will automatically update related browser-specific declarations.
Friday, February 13th, 2009
An in-browser code editor from Mozilla Labs.