cocalc

Coincidentally, I'm in the middle [1] of building something for https://CoCalc.com that is exactly what you're describing. For collaborative document editing (e.g., google drive and overleaf) it's a common feature, but for code editors it isn't. CoCalc is both. Anyway, nothing to see yet, but you might want to check with us in a month. After thinking about this problem a lot recently, I think it’s critical to store the comment locations with all versions of the file, so you don’t lose comment locations, or at least maximize the information you have available to locate comments when they get lost. [1] https://github.com/sagemathinc/cocalc/pull/8071

- CoCalc (which I wrote) can be self-hosted but is NOT FOSS, though you can browse the code here: https://github.com/sagemathinc/cocalc -- do a quick "self hosted" test if you want by typing "docker run --name=cocalc-trial -d -p 4043:443 sagemathinc/cocalc-trial" - Google Colab is fully closed source and I think there is no self hosted option. - Deepnote is fully closed source and I think has no self hosted option. - Saturn Cloud enterprise is a self hosted option for Saturn Cloud. Saturn Cloud is I think a nice management layer around open source JupyterLab. - I think Apache Zeppelin is self-hostable FOSS.

I have some unit tests for billing and subscription code for my company that started breaking in CI today due to the leap day: https://github.com/sagemathinc/cocalc/commit/8575029c2b76787...

1. I'm integrating ChatGPT extensively into https://CoCalc.com. This integration makes a lot of sense, because cocalc is a platform in which relatively inexperienced students use Jupyter notebooks, linux terminals and Latex. So far, the most popular feature by far is a "Help me fix this" button that appears above stacktraces in Jupyter notebooks. 2. One software engineering challenges is that ChatGPT often outputs code in markdown blocks. I've had to emphasize in prompts that it should explicitly mark the language. I then got inspired to make it possible to evaluate in place the code that appears in these blocks using a Jupyter kernel, and spent a week making that work (so, e.g., if you type a question into the chatgpt box on the landing page at https://cocalc.com, and code appears in the output, often you can just evaluate it right th

There are many approaches to this problem. E.g., Jupyter notebooks implement one that has matured in the wild over a decade. There's this very flexible markdown-it plugin that implements anther https://github.com/goessner/markdown-it-texmath, and my version of it here https://github.com/sagemathinc/cocalc/blob/master/src/packag... which I rewrote in typescript with a focus on the same semantics as Jupyter has, but for CoCalc. I've also been working on using unifiedjs to provide more general latex for Markdown (not just formulas) here https://github.com/sagemathinc/cocalc/pull/5982 Parsing math in markdown is easier if you use a plugin to an existing markdown parser, rather than trying to do some hack outside of that (which is what Github probably does, and also what Jupyter does).

RETHINKDB: - There is a recent discussion about whether or not RethinkDB is dead here: https://github.com/rethinkdb/rethinkdb/issues/6747 - Judging by new PR's and commits, Rethinkdb development slowed down substantially in Jan 2016. SAGEMATH: - SageMath development is still very active; maybe more so, due probably to strong Europe grant support (OpenDreamKit): https://github.com/sagemath/sage/graphs/contributors SAGEMATHCLOUD: What this blog post is "really" about. - We renamed it "CoCalc" -- https://cocalc.com - I rewrote everything that depended on RethinkDB using PostgreSQL. Though it was months of work, this was obviously a VERY good decision in retrospect! - I rewrote all the realtime sync functionality to not depend on the database at all (just use a custom protocol over websockets), which is obviously a much more scalable approac

"seems to be pretty dormant in terms of development" -- that's because Overleaf purchased ShareLaTeX. https://www.overleaf.com/blog/518-exciting-news-sharelatex-i... Also, you might be unaware of CoCalc, which is open source https://github.com/sagemathinc/cocalc. CoCalc supports collaborative editing of many structured documents, including Jupyter notebooks, but not rich text at present.

We use KaTeX for https://cocalc.com (source here https://github.com/sagemathinc/cocalc) because it is dramatically faster than MathJax. When KaTeX fails due to an error (e.g., something missing) our code falls back to MathJax, so we still get full MathJax support when needed, but with all the benefits of KaTeX. The code that John Jeng and I wrote to do this is tangled up with the rest of cocalc's code; I hope somebody else writes a standalone library that accomplishes that same thing. It wasn't too difficult to write this, though a couple of subtle issues arose in production, which we had to sort out.

This bug [1] in recent versions of Firefox broke websockets for some sites (I don't know how many, but it included [2]). It was a major bug in their implementation of TLS 1.3 in Firefox, but its symptoms were subtle. You could connect the first time, but reconnecting would then be completely broken until you restarted Firefox (due to some sort of caching). For years, the Firefox flex css layout implementation was unbelievably slow [3], which basically broke usability of some sites. For the web application I work on, we've had to contend with over 10 Firefox-specific bugs [4]. I think everything works fine today though. [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1453204 [2] https://cocalc.com [3] https://bugzilla.mozilla.org/show_bug.cgi?id=1209697 [4] https://github.com/sagemathinc/cocalc/issues?utf8=%E2%9C%93&...

Probably LISTEN/NOTIFY. I explain in detail how I migrated from RethinkDB to PostgreSQL using LISTEN/NOTIFY + tons of additional work here http://blog.sagemath.com/2017/02/09/rethinkdb-vs-postgres.ht... I've continued working on this codebase, even pushing commits this week like this one: https://github.com/sagemathinc/cocalc/commit/c20a62446b6e43c...

I recently built a complete node.js Jupyter server on top off https://github.com/nteract/spawnteract (also used by nteract). There is no Python involved at all unless you connect to a Python kernel. Some of the code of what I wrote: https://github.com/sagemathinc/cocalc/tree/master/src/smc-pr... I'm not suggesting you use what I wrote. I'm just pointing out that there exist alternatives to the Python-based Jupyter server that accomplish the same goal. And I strongly agree with you -- it would be great to have even more implementations of the server part of the Jupyter stack!

I’m also a software dev who has been painfully dogfooding an iPad Pro 10.5 fulltime for development of CoCalc/SageMath for the last few weeks. I even opened (and fixed) a bunch of bugs in our site as a result: https://github.com/sagemathinc/cocalc/issues?utf8=&q=label%3... I’ve been using iOS 11 beta3. Surprisingly, there actually exist some clear advantages over most laptops: Physical Hardware Advantages over laptops (not over surface pro): - More cameras (e.g., an extra 12MP camera on back); you can easily snap a picture or shoot video. - The iPad 10.5 weighs 1 pound, which is way less than most notebooks; it is EXTREMELY portable. - Portrait mode (i.e., rotate screen) with no keyboard, which is useful, e.g., for reading pages of technical documentation. - No trackpad, so the keyboard/bottom takes up much less space, meaning you can

The price for g1-small also increased from $0.021/hour to $0.0257/hour. Here's the diff for where I track this: https://github.com/sagemathinc/smc/commit/13edcd3772daf07d0d...

This is a very valuable article about what it would take to do such a migration. I also work on a large CoffeeScript + React codebase (https://github.com/sagemathinc/smc), write a lot of new CoffeeScript every day, and I have no plans to do a rewrite. I just don't see the value of doing a rewrite, given how hard it would be. I like CoffeeScript, find it expressive, and I think it would be easier to fix or maintain the relevant CoffeeScript tooling than to do a rewrite (just because a rewrite would be so damned difficult). Also, CoffeeScript really is sufficiently close to Javascript, and it interoperates effectively enough for now. CoffeeScript is not totally dead. There's pretty regular activity this month (see https://github.com/jashkenas/coffeescript/commits/master). That said, personally, I find the stability of CoffeeScript to b