This looks very promising. In addition to using KOReader I will be able to customize the lock screen and remove Amazon's upsells. I guess the only downside is that I won't be able to use WiFi or buy e-books from Amazon.
Do you know if that affects movies bought through Apple’s TV app (US)? I have quite a few movies in my collection and would be really annoyed if they didn’t work in Europe.
Is there a non-DRM format + an e-reader combo that allows for bookmarks, text selection, dictionary search? Ideally I would prefer to keep my Kindle but would really love to buy and own non-DRM books.
This is really sad. Artificial constraints on a medium that was supposed to democratize access to information.
I am right now in line to borrow the new DeGrasse Tyson’s book and will have to wait for almost 6 weeks for my turn. They have only 3 digital copies available and almost a hundred people waiting ahead of me.
This is one of those cases when Jira is suffering from its UI/IA mess. It has lots of good feature but the discoverability is horrendous, which leads to so much user (my) confusion.
This positioning is confusing as most of the features are an overkill for a solo engineer/entrepreneur/etc.
The free tier is not a perfect fit a solo person for the same reason.
Wonder if it could be worth trying offering tiers based on your vision for different size teams. Eg a solo person gets a single user (no user management features), no chat, no any multi-user features.
My experience is different regarding Electron apps. Many of the Electron apps I use (Spotify, Slack, Notion) have a web UI option. I never use it and now just a handful of people who sometimes open Notion or Slack on web.
I think we need to define better (or re-define) what offline support actually means. Even an ideal fantasy implementation of a PM app with offline support will have limitations unless you sync the entire company’s space with all clients (users, files, docs, comments, tasks, roadmaps, etc).
So IMO selling offline support as a feature has to come with a clear description of what it means.
Linear looks great! I love how focused it is on this specific problem area. I don’t find all-in-one apps like OPs very useful. Can’t replace all my tools like chat, docs, project management, etc at once.
"Easier" is a difficult word to describe and agree on. Building rich UI is incomparably faster and more enjoyable in React than it is in Django or RoR (hence why most rich web UIs are built using JS frameworks).
Deploying API and FE separately can also be more efficient, as these services likely require a different tech stack, a different scaling/load balancing setup, and have a different release cycle.
API can be a very thin layer that a well constructed client can utilize right from the "view" (a React component). A template file in a backend framework is a one-way feature in the majority of cases. You have to construct and pass _all_ its context (or create helpers, global context, etc) every time. So the controller needs to request data, prepare it (template data manipulation is mostly minimal), pass it. Basically a controller starts doing too many things over time, too much business logic is added to accommodate pretty low featured templates.
> Don't you pass already massive JSON payloads from your API endpoints down to your client to update the views?
Not really. You send many parallel API requests from the client, each response is a smaller JSON. And when you navigate to the next page, most of its data is already in your state, so you have to request just the missing part (e.g. a different post). When you are constructing context for a page on the backend you have to provide all its context every time. The template doesn't make requests based on some logic.
Having heard of Django-Ninja before. Looks really good! If I understand correctly it would allow me to keep the best parts of Django (ORM, Admin UI) and build a FastAPI-inspired API? That’s an awesome combo! Curious to see benchmarks how it compares to ExpressJS.