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

Show HN: ORY Editor – A rich editor for the browser, built with React and Redux

github.com

Post reply on HN
Print view View original

101–107 of 107 posts

Re: Show HN: ORY Editor – A rich editor for the browser, built with React and Redux

#101

Post by ralmidani »

PythonicAlpha wrote: post #57
ralmidani wrote: post #41

Earlier quoted context omitted.

Actually, I would be more confident working with a GPL- or AGPL-licensed product, because enhancements are more likely to go back upstream.

That is right. I just know, that many companies flee from GPL licenses (and more so AGPL). They omit any product involving GPL just to be sure not to get any juristic hassles (if rational or not). Here is the culprit: When no other people invest in enhancements, there is also nothing that can go back upstream. I like free software very much, but I also don't want to be forced to give things free, that I make. Problem…

> many companies flee from GPL licenses

That's a feature, not a bug. If I release free software and you are unable or unwilling to play fair, I don't __want__ you to use my software.

Re: Show HN: ORY Editor – A rich editor for the browser, built with React and Redux

#102

Post by izacus »

underdown wrote: post #79
ctoth wrote: post #61

Earlier quoted context omitted.

This does not appear to work at all with my screen reader. Accessibility as afterthought, as always. I used to look forward to trying to help people fix their stuff to be accessible, but now I'm just tired of every single fucking thing somebody creates being broken for me because everything is a complete heaping pile of inaccessible garbage and nobody even thinks about accessibility. It's not like there aren't thousa…

So I take it you've never shipped an MVP?

A lot of us did and those worked perfectly with screen readers. It's not hard or even additional work, you just need to give a crap while doing basic design.

This is similar to the responsive/mobile design - if you care about it from the start, you'll structure the site/component in a way that it really won't take you much more time to support accessibility features. If you don't care at all, retrofitting accessibility will require severe refactoring and probably won't ever be done.

So not caring about it in "MVP" is about the worst thing you can do.

Re: Show HN: ORY Editor – A rich editor for the browser, built with React and Redux

#103

Post by aeorgnoieang »

izacus wrote: post #102
underdown wrote: post #79

Earlier quoted context omitted.

So I take it you've never shipped an MVP?

A lot of us did and those worked perfectly with screen readers. It's not hard or even additional work, you just need to give a crap while doing basic design. This is similar to the responsive/mobile design - if you care about it from the start, you'll structure the site/component in a way that it really won't take you much more time to support accessibility features. If you don't care at all, retrofitting accessibili…

Not having something in the 'forefront' of one's mind isn't equivalent to "not caring".

You should also keep in mind that you're (implicitly) asking people to do more work – which is fine, but there are real costs and people aren't bad because they haven't already borne them.

Re: Show HN: ORY Editor – A rich editor for the browser, built with React and Redux

#104

Post by izacus »

aeorgnoieang wrote: post #103
izacus wrote: post #102

Earlier quoted context omitted.

A lot of us did and those worked perfectly with screen readers. It's not hard or even additional work, you just need to give a crap while doing basic design. This is similar to the responsive/mobile design - if you care about it from the start, you'll structure the site/component in a way that it really won't take you much more time to support accessibility features. If you don't care at all, retrofitting accessibili…

Not having something in the 'forefront' of one's mind isn't equivalent to "not caring". You should also keep in mind that you're (implicitly) asking people to do more work – which is fine, but there are real costs and people aren't bad because they haven't already borne them.

No that is exactly my point - it's not "more work" if you think about it from the start. Just like it isn't more work to make a site responsive if you start correctly - but it's significantly more work when you have to rewrite a lot of components later because you didn't take accessibility (or responsiveness) in consideration at the start.

Re: Show HN: ORY Editor – A rich editor for the browser, built with React and Redux

#105

Post by Prefinem »

izacus wrote: post #104
aeorgnoieang wrote: post #103

Earlier quoted context omitted.

Not having something in the 'forefront' of one's mind isn't equivalent to "not caring". You should also keep in mind that you're (implicitly) asking people to do more work – which is fine, but there are real costs and people aren't bad because they haven't already borne them.

No that is exactly my point - it's not "more work" if you think about it from the start. Just like it isn't more work to make a site responsive if you start correctly - but it's significantly more work when you have to rewrite a lot of components later because you didn't take accessibility (or responsiveness) in consideration at the start.

>it's not "more work" if you think about it from the start

Most of my job as a developer is thinking. So yes, it is more work. Accessibility / Responsiveness isn't always done first because it takes more time (either thinking or "working").

Re: Show HN: ORY Editor – A rich editor for the browser, built with React and Redux

#106

Post by ergo14 »

t1amat wrote: post #82
ergo14 wrote: post #34

But this is built with React so its not really reusable outside of its ecosystem. Is there a version that would run on preact instead? Maybe QuillJS would be a better option for general purpose editor.

If you use preact without preact-compat then you seal yourself into the preact ecosystem. That's why preact-compat exists.

I was thinking more about using the editor with our polymer and vuejs applications.
Post reply on HN