Hi, I once tried that, but I ran into problems with lazyness. In particular my data structure was rather simple (famous gap data structure), but editing "large" files (>1000LOC) became rather unpleasant (too big input-feedback latency).
However I managed to build a _very_ basic proof-of-concept editor (no dependencies) in just a few hundreds lines of code which I could explain, but until now I was too shy to share it as it did not involve magic abstract Haskell-foo ... ;)
This is not a critique to the author, but for me, who just did classic webdev (server side templated html), this was very surprising.
I am not that into webdev, but shouldn't a page like HN be fast TODAY, as it has very basic functionality (CRUD)? I mean if this is slow, how can I expect acceptable performance from involved applications?
The problem is the site is not sending any (useful) HTML during the first HTTP request. Therefore the browser has to wait for the JS to render the page before it can even think about displaying anything.
The fact the site then loads content from firebase is obviously a problem, but it's not so much firebase's problem as it is of the codebase itself - in an ideal world it should be rendering the initial HTML to send to the client on the server.
I have seen React based websites with server side rendering work with firebase with much better performance.
I rode a bike that I rescued from the dump for over a year. Besides a new chain, tubes and loving maintenance it was a nice solid 70s era bike. I swear it was made out of iron pipe. Oddly, it came with track drop bars.
I agree with that. We live in a marketing bubble and the power of advertising will decrease a lot in the next years as new generations will just get more and more immune to it. Which is actually a good thing.
However I managed to build a _very_ basic proof-of-concept editor (no dependencies) in just a few hundreds lines of code which I could explain, but until now I was too shy to share it as it did not involve magic abstract Haskell-foo ... ;)