One of my CS professors told the story about when MCSFT demonstrated their implementation of the Korn shell at a USENIX conference. Gasbag on stage tells the guy in the question line that he (questioner) has misinterpreted something in the software's original intention. Gasbag figures out something is up when half the room cracked up. The guy at the mic was David Korn, author of the Korn shell.
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).
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.
So is the 6k±1 rule: 6k and 6k±2 are all even, 6k±3 is divisible by 3. You can extend this further: all primes greater than 5 must take one of the forms 30k±1, 30k±7, 30k±11, 30k±13. This is much less exciting, but ... suggestive. (No, not that suggestion, that one isn't actually true.)
For a certain point of view, most of math is trivial corollaries.
Well I'm sure it looks trivial to you. But the joys of math often aren't in the difficulty but the discovery. Would your prefer it not have been stated at all, or did you just want to let us know you understood it.
As well, i think the 2k+1 thing is drastically more trivial and not at all equivalent being that all you need to know for 2k+1 is that 2k+1=odd. 4k and especially 6k take a larger generalization and different analytical method and often aren't included in the definition of the primes we learn like 2k+1 (odd) is.
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).
I would die a little inside (ok, maybe that's dramatic :D ) if I was presented a trackpoint-like device but didn't work properly. I had that once - an X1 Carbon 5th gen actually I was using temporarily, struggling to make that useful, because it was too tight (I feel like post-*30 models, you need to break them in, a lesson that I eventually learned) and it would float a lot.
One nice thing about many used ThinkPads at least: trackpoints are usually the one component that are brand new on the device :D
It's great but it's very expensive so be aware that if you are down to the level of caring about things in the single-digit percentages of your budget, something like atop once per second could easily consume that amount of resources. A lot of these stats are really not cheap at all. E.g. you may find a substantial difference in the amount of CPU time needed to produce /proc/pid/stat as opposed to /proc/pid/statm. And some of the system-wide stats are even worse.
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.
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).
I don’t understand. How is the app working in offline mode when the Phoenix server is not reachable, since the interactions are managed server-side with LiveView?
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.
