11–20 of 107 posts
Almost broken on mobile, and my iphone gets really hot...
Which iphone do you use? Also is it safari? It's currently absolutely not optimized for mobile, as most content creation happens on the desktop. We might though at some point.
Almost broken on mobile, and my iphone gets really hot...
My Macbook gets really hot as well. It seems to be quite cpu intensive, and the editing is not very smooth. Otherwise, the product looks interesting
I'll resize that, and let you know - could you test again then?
> Promising libraries potentially solving the above where abandoned by their maintainers, because it started as a special use case, or a free-time project. > It is built by a company, reducing the likelihood of abandonment. Even projects "built by a company" suffer the same fate. The only way to reduce the likelihood of abandonment is to tie a revenue stream directly to it, like customers paying for support or a pro…
"A problem has ocurred, so the page has been reloaded"
I hope they fix it because it looks perfect for fast mockups
Edit: it seems to sadly happen with all ORY pages including the documentation
> Promising libraries potentially solving the above where abandoned by their maintainers, because it started as a special use case, or a free-time project. > It is built by a company, reducing the likelihood of abandonment. Even projects "built by a company" suffer the same fate. The only way to reduce the likelihood of abandonment is to tie a revenue stream directly to it, like customers paying for support or a pro…
I've come to the conclusion that "All software is ultimately abandoned". Ours is a fast-changing industry. If software isn't abandoned, it probably should be. Its the oldest frameworks and languages that get the most criticism.
Optimizations will go a long way to swaying adoption. Clients like easy-to-use editing capabilities, and it doesn't get much easier than this.
Earlier quoted context omitted.
I've come to the conclusion that "All software is ultimately abandoned". Ours is a fast-changing industry. If software isn't abandoned, it probably should be. Its the oldest frameworks and languages that get the most criticism.
Big parts of the toolset I use every day are several decades old; if done correctly, software can be iterated and refined until it's of a very high quality. In my experience, it tends to stand a much greater chance the smaller it is (the best examples I'm thinking of are small unix command-line tools like find, grep).
> Promising libraries potentially solving the above where abandoned by their maintainers, because it started as a special use case, or a free-time project. > It is built by a company, reducing the likelihood of abandonment. Even projects "built by a company" suffer the same fate. The only way to reduce the likelihood of abandonment is to tie a revenue stream directly to it, like customers paying for support or a pro…
I've come to the conclusion that "All software is ultimately abandoned". Ours is a fast-changing industry. If software isn't abandoned, it probably should be. Its the oldest frameworks and languages that get the most criticism.
> Promising libraries potentially solving the above where abandoned by their maintainers, because it started as a special use case, or a free-time project. > It is built by a company, reducing the likelihood of abandonment. Even projects "built by a company" suffer the same fate. The only way to reduce the likelihood of abandonment is to tie a revenue stream directly to it, like customers paying for support or a pro…
Yeah, I've gotten this response for my framework vs. a competing one from Mozilla. I usually reply "Mine came out a year before theirs and I still work on it all the time, and how 'bout that Shumway?"
Anyways, the gif is now removed. I hope the performance gets much better now. The CPU fans on macbooks going up where probably due to a lack of a dedicated graphics card. This happened to me with my macbook and large gifs too.
If the problems don't go away, please create an issue in the repo so we can work on improving this! It would be important to include your steps so we are able to reproduce these issues.
edit://
Since this comment is on the top, I'll address a few more questions here too. If you missed the demo, it's here: http://editor.ory.am/
First, this is a layout editor first- and foremost. Behind the scenes, React, Redux and slate.js ( http://slatejs.org/ ) is being used. Each cell is a React component that you can implement yourself. In fact, the text component itself is a plugin that wraps slate.js.
Second, we're integrating this editor in Germany's largest e-learning platform (wiki-esque) with ~1 million MAUs: https://de.serlo.org
And lastly we're working on a business model behind it, with our ory sites product (early access): http://ory.am/sites/
If you want to check out our other open source products, feel free to do so: https://github.com/ory
