Comment

Comment by calpaterson

It's funny, this architecture he mentions of one-page-app clients on the frontend and microframework servers on the backend with Python is precisely the model I choose for a recent side project.

What I learned: - Javascript requires a lot of architecture to be sustainable over even medium size apps (I stole N. Zaka's architecture)

- Writing functional tests for Javascript is difficult. (Writing unit tests is easy)

- Most web browsers are nearly there with everything you need for one-page-apps. IE8 is the only real problem, and I think my problems are soluble.

- Python's single threaded nature requires that you make explicit effort to add offline jobs (I added a priority queue using redis)

- Elasticsearch is actually quite complicated once your needs move out of the completely trivial

- Most of the documentation for Elasticsearch assumes a working knowledge of Lucene (which I don't have).

- Mongodb is really really easy to develop against

- Getting a single page app to be sensibly indexed by Google is not easy.

Here's the backend source:

- https://github.com/calpaterson/recall

And the frontend source:

https://github.com/calpaterson/web-recall

And the current deployed version is here:

https://recall.calpaterson.com/about/

I'd love to answer any questions, I'm not as keen on one-page-apps now as I was when I started.

parent calpaterson 13 years ago

Discussion

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton