Great news to hear Lexical replacing Draft. Also great that you're handling `beforeinput` (like Slate). I work on a text expander browser extension and supporting Draft is a pain[1].

Are there any plans to make inserting text from the "outside" easier on Lexical? Maybe exposing the Lexical instance on the dom node (like CKEditor does)? Right now we're using `execCommand` to support Lexical.

[1] https://github.com/Briskine/briskine/blob/master/src/content...

Great work! Have you found a way to compress/shorten the urls?

I built something similar[1] a while ago, but the urls are still too long for sharing without a shortener. I'm using lz-string[2].

[1] https://www.siloz.io

[2] https://github.com/pieroxy/lz-string

CouchApps had a better vision for the web. You would run a local CouchDB and replicate the app next to your data, rather then giving the app access to your data while hosted somewhere else. It has the added benefit of working offline.

Some sort of cross-domain request blocking could then prevent the app from stealing your data.

Thanks for mentioning CouchApps (based on CouchDB, or the scalable BigCouch). I haven’t thought about CouchDB as a platform for a long time, but it does hit a sweet spot for local data, distributed replication. Seems like a good basis for a Decentralized Web on a small scale where you share with a small number of people.

A bit of a shameless plug, but if you want predictable, I've built a browser extension for the "nudge" part: https://www.nudgeti.com/

It shows a browser notification when you spend more than two minutes on certain websites.

You have most of these, or at least very similar versions, in Plasma/KDE today:

> Document Database

This is what Akonadi was when when it came out for 4.x. Nepomuk was the semantic search framework so you could rate/tag/comments on files and search by them. They had some performance problems and were not very well received.

Nepomuk has been superseded by Baloo, so you can still tag/rate/comment files now.

Most KDE apps also use KIO slaves: https://www.maketecheasier.com/quick-easy-guide-to-kde-kio-s...

> System Side Semantic Keybindings

> Windows

Plasma 4 used to have compositor-powered tabs for any apps. Can't say if it will be coming back to Plasma 5. Automatic app-specific colors (and other rules) are possible now.

> Smart copy and paste

The clipboard plasmoid in the system tray has multiple items, automatic actions for what to do with different types of content and can be pinned, to remain visible.

> Working Sets

These are very similar to how Activities work. Don't seem to be very popular.

Those KIO slaves are really interesting. I've never seen those before. Thanks!

I built something very similar a while ago: https://github.com/ghinda/jotted

I'd say it's more lightweight by default (it's not mandatory to use an editor like CodeMirror) and more flexible because of the plugin system (there are plugins for using Ace or CodeMirror as editors, or for compiling ES6, CoffeeScript, Less, Stylus, Markdown).

It also has a Console plugin, like the one in devtools, that makes it work like klipse. https://twitter.com/ghindas/status/697790917302996993

There are a bunch of demos on the site: https://ghinda.net/jotted/#demos

Shout-out to @ghinda for creating Jotted. We've been using it for our startup [Educative](https://www.educative.io) and are pretty happy with it.

Sure, because of the plugin support it shouldn't get too complicated.

You can use strings instead of urls, for files. So you could do something like:

  loadFromS3(function (fileContent) {
    j = new Jotted($container, {
      files: [ type: 'css', content: fileContent ]
    })
  })

then create a plugin for it that saves the changes back to s3:

  j.done('change', function (err, params) {
    saveToS3(params.content)
  })

Here's some details about the plugin api: https://github.com/ghinda/jotted#plugin-api

Ironically IE9+ support for display:table is worse then IE8-, especially regarding inherited dimensions on child elements.

I wrote a small grid library[1] using display:table, as a flexbox alternative for older browsers, and had no choice but to use js to fix IE support.

Firefox also has some issues, don't know if because of the spec or the implementation, but those can be worked around with css.

[1] https://github.com/ghinda/gridlayout

GridLayout, a flexbox-alternative CSS grid with support for older browsers. Needs a small script for IE support.

https://github.com/ghinda/gridlayout

I don’t want to sound like a broken record, but Webkit was originally a fork of KHTML, which is LGPL, so they were required/forced to release it under the same license.

And based on the their upstream contributions[1] it doesn’t look like it was a gesture of goodwill.

[1] https://en.wikipedia.org/wiki/WebKit#Split_development

> I don’t want to sound like a broken record, but Webkit was originally a fork of KHTML, which is LGPL, so they were required/forced to release it under the same license

No, they were forced to release parts of it under the same license. There was a lot of original Apple code that could be separated out easily and released under any license they wanted (or kept proprietary) as long as they released them as object files so could modify and relink in the modified LGPL parts.

The parts that Apple was not required to release under LGPL they released under BSD.

The well-known fact that WebKit has an origin story in KHTML is completely irrelevant to the point being made. Apple was the one who put substantial engineering effort into making the mobile web work well, and released their work with the most open licenses they could.