Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Building a Text Editor for a Digital-First Newsroom

open.nytimes.com

Post reply on HN
Print view View original

151–160 of 176 posts

Re: Building a Text Editor for a Digital-First Newsroom

#151

Post by crcl »

noir_lord wrote: post #56
amelius wrote: post #39

Earlier quoted context omitted.

But at least they run everywhere.

Where everywhere is some subset of browsers in the wild and often not that consistently anywhere. I mean the web is awesome but it’s far from perfect from a programming point of view but that of course doesn’t matter for other reasons.

> Where everywhere is some subset of browsers in the wild and often not that consistently anywhere.

Yes, but it's easier to download a version of the browser that works. The alternative is for the developer to build native apps for each OS they want to support. In my experience, it's easier to build cross-browser than it is to build cross-platform.

Re: Building a Text Editor for a Digital-First Newsroom

#152

Post by coob »

vertex-four wrote: post #125
JasonSage wrote: post #55

Earlier quoted context omitted.

Impressions matter, no matter how outdated they are. I also don't think the concept of fairness applies since I'm accounting the details of my personal experience and the conclusions I personally drew from it. Some of those are subjective (code quality) while others are purely objective (I got a lot of errors). What I infer from that may be entirely different from what you do, but that does not make your characteriza…

Does a review of Windows 3.1 give you any idea at all of how applicable Windows 10 would be to solving a given problem? At best, you’ve stated a bunch of nonsense for people to filter out once they eventually realise you’re talking about a version which bears little similarity to the current state of things.

It's more important to appear smart and to spread your opinion than to contribute anything of value!

Re: Building a Text Editor for a Digital-First Newsroom

#153

Post by andrei_says_ »

youpassbutter wrote: post #149
mattberkowitz wrote: post #141

Earlier quoted context omitted.

I'm an engineer on our CMS team and as Albert mentioned we're currently seeking both back-end and front-end team members. We're not opposed to hiring skilled developers that don't have deep experience the specific language or frameworks we use. There's also always the option of joining the back-end and transitioning over time to a more front-end role. If you're interested, I'm happy to answer any questions or connect…

A CMS team? Christ, no wonder NYTimes is losing money.

As someone who has worked on the integration of off the shelf CMS and as well as built in house ones, I question this statement.

There’s a lot of value in building tools that fit the domain and workflow perfectly well. It’s expensive in the short term but in the long term saves a lot of time and money.

Re: Building a Text Editor for a Digital-First Newsroom

#155

Post by joemi »

Phrodo_00 wrote: post #19

This isn't even a test editor. It's closer to a web publishing tool. The article also didn't talk about the normal text editor challenges like the way the text is stored in memory and modified.

That seems a bit too pedantic of an argument for this article. The very first paragraph implicitly states its definition of text editor:

    If you’re like most people in America, you use a text editor nearly every day. Whether it’s your basic Apple Notes, or something more advanced like Google Docs, Microsoft Word or Medium, our text editors allow us to record and render our important thoughts and information, enabling us to tell stories in the most engaging ways.
Also, it could be argued that all word processors are also text editors but with added features. The fact that they allow the presentation to be edited does not mean that they stop allowing text to be edited.

Re: Building a Text Editor for a Digital-First Newsroom

#156

Post by nwmcsween »

TeMPOraL wrote: post #108
nwmcsween wrote: post #105

Earlier quoted context omitted.

Any sufficiently complicated editor contains an ad-hoc, informally-specified, bug-ridden, slow implementation of half of emacs? I prefer vim though..

Vim ain't sufficiently complicated (that can arguably be seen as a good thing). That's why it's been mostly reimplemented in Emacs.

Vim has vimscript (ugh) with a lua and python gaining popularity so emacs sort of got it right IMO anyways.

Re: Building a Text Editor for a Digital-First Newsroom

#157

Post by youpassbutter »

andrei_says_ wrote: post #153
youpassbutter wrote: post #149

Earlier quoted context omitted.

A CMS team? Christ, no wonder NYTimes is losing money.

As someone who has worked on the integration of off the shelf CMS and as well as built in house ones, I question this statement. There’s a lot of value in building tools that fit the domain and workflow perfectly well. It’s expensive in the short term but in the long term saves a lot of time and money.

Sure. But it doesn't take a "team" to build up a CMS. This is why media "tech teams" are viewed as a joke in the tech industry.

Re: Building a Text Editor for a Digital-First Newsroom

#158

Post by iamcasen »

vertex-four wrote: post #125
JasonSage wrote: post #55

Earlier quoted context omitted.

Impressions matter, no matter how outdated they are. I also don't think the concept of fairness applies since I'm accounting the details of my personal experience and the conclusions I personally drew from it. Some of those are subjective (code quality) while others are purely objective (I got a lot of errors). What I infer from that may be entirely different from what you do, but that does not make your characteriza…

Does a review of Windows 3.1 give you any idea at all of how applicable Windows 10 would be to solving a given problem? At best, you’ve stated a bunch of nonsense for people to filter out once they eventually realise you’re talking about a version which bears little similarity to the current state of things.

I have also used the newest version of prosemirror recently, and it caused me and my team so much pain we had to rip it out of our codebase.

The documentation is still no good. The underlying tech looks super promising, but the plugin system makes no sense.

If all they did was update their documentation so you can clearly see how to use it, perhaps it would be great.

Re: Building a Text Editor for a Digital-First Newsroom

#159

Post by iamcasen »

marijn wrote: post #47
JasonSage wrote: post #35

Earlier quoted context omitted.

Just my experience: I had a rough time with ProseMirror trying to use it before it was released. It didn't use modern JS modules for a long time, the source code was a mess as far as I could tell, and JavaScript variable errors would surface with every version. Maybe the author has overcome these issues, but I'd be inclined to go with a different editor. Also, ProseMirror's architecture is extremely close to DraftJS,…

Yeah thanks for dropping some deeply outdated impressions in here. (Also not even fair—the code was never a mess and at the time it wasn't clear how ES modules would be used so using CommonJS was a completely reasonable choice.)

Hey there,

Just wanted to offer some feedback. Prosemirror's docs are woefully incomplete. The way controls are added is extremely confusing. Why do we need some node module called "prose-mirror-example-setup" ?

I know I'd personally prefer being able to add all the markup and style for the editor, and then just use prosemirror underneath the hood for state management.

Another thing that I found quite difficult, was programmatically inserting images at the cursor.

Finally, storing state as markdown has turned out to be a nightmare. Not really your fault, but perhaps something you should be aware of.

Post reply on HN