tie_

Ain't it cute 'splaining what redis is designed for to the person who designed it

Very cool project and would be super useful with something like GraphQL, which tends to produce big nested JSON objects. Thanks for sharing it!

One improvement in my eyes would be to remove the "connector" boxes, like `members (2): "Array"` and `powers (3): "Array"` and have the arrow go straight to the array property. Those connector boxes take up a lot of real estate without conveying new information.

The "two big mobile platforms" were not established by an irreversible act of God. Before the current time of two platforms, there was a time of (mostly-)one platform i.e. the Web, and that platform had quite a few nice features.

One of the small conveniences is indeed that you didn't need to develop the same thing twice, which made the barrier to entry much lower. The functionality that you were exposing to users did not need to pass a review at one of two US tech giant companies, which could reject publishing it for any or no sensible reason at all. You were not forced to pay 30% of your revenue to the gatekeepers of the platform. You were not banned to invite users to buy your product in any way that works for them, even if it meant sending you checks over carrier pigeons. There was no _chokepoints_ that a single company could squeeze to further its own interests (after the collapse of IE).

Isn't 4k+1/4k-1 rule trivial though?

If we take any number K=N*4 divisible by 4 and >2, that'd be an even number by definition. The two closest odd numbers on either side would be (K-3), (K-1), (K+1), (K+3). As it happens (K+3) is the same as K(-1) for the next N, and (K-3) is the same as (K+1) for the previous N. So _all_ odd numbers follow this rule.

What "4k+1 or 4k-1" says in a roundabout way is that all prime numbers (>2) are odd, which isn't much of a surprise.

Ever tried playing something like (multiplayer) Quake with an Apple trackpad? I used to win online matches with the trackpoint. Once you get use to it, the difference in speed and precision is quite significant.

Totally understandable. I'm a trackpoint junkie, but I also could not get to using it on an HP laptop from work. It felt completely gimped (and yes, having just 2 buttons was probably a part of it).

Word! PWAs are awesome (for a lot of usecases), and I don't quite get how they are not becoming a center pillar of mobile development.

Install atop and configure it to sample every second.

I can't count the number of times this has helped solve a mysterious behavior. Atop is king.

I'm using Firefox fulltime, both on my work and my personal machine. The two things I'd love to see are: - Fix the ever-growing memory usage on Linux - Make it the best platform for using Progressive Web Apps (PWAs)

Despite PWAs not being a mainstream thing now, there are still a lot of them. Particularly on Linux, a PWA can be the best option for software that doesn't have a native client - e.g. Outlook 365. PWAs have a lot of untapped potential, mainly due to mobile software authors not being familiar with the approach.

With Firefox standing for the open, net-neutral web, it makes sense to me that they would also stand for web-based, cross-platfrom, appstore-neutral apps.

Sorry, my statement indeed got confusing. I'm using LiveView for online interactions. I'm using PouchDB + JS for data synchronization and enabling offline work. You are right that LiveView itself does need to be online, since it's whole point is to move (back) the UI logic to the server side.

I'm happily using Phoenix+LiveView for a website that works as a PWA. This also includes offline mode with sync-when-internet-is-available functionality (thanks PouchDB!). This covers online/offline/mobile usecases, with no explicit RPC, and no requirements for the end device that the app would run on, other than a _capable_ browser.

(Admittedly, browsers on iOS are gimped, but that's part of the Apple tax).

Same here. The first time I hear that containers are hard-linked with Kubernetes in anyone's mind. Docker standalone was used for a long time before Kuberbetes was a thing. AWS, Azure and Google have had options to run containers long before they had managed K8s. There have always been excellent ways to use containers without involving Kubernetes.

Same here. Fixed by deleting the traefik pods. The underlying Deployment regenerated them and a new cert was obtained.