Sure, I read that in TFA too. My point is that if USB transfers of Kindle eBooks are being sunsetted, I would estimate that Send to Kindle's days are also numbered.
419 karma · joined July 29, 2019
I'm a huge user of the Send to Kindle feature via my Calibre library too, so this has me pretty bummed and pessimistic for the future. I guess if the worst comes to pass, I can just look into jailbreaking or getting any of the zillion other Android-based eReaders from AliExpress.
[1] http://sunnyday.mit.edu/papers/therac.pdf
One of the biggest pain points I had when setting up a self-hosted Matrix instance and getting all my devices signed in was the crypto stuff. At least in the client I use, Element, I was bombarded with tons of popups with vague "Upgrade your encryption!" prompts upon logging in the first time. The copywriting on the "Security & Privacy" page was less than helpful in illuminating what I was actually "upgrading" or setting up, since specific technical terms (e.g. recovery key/security phrase/security key) were all used more or less interchangeably. If that kind of confusion can be reduced or swept under the rug for end-users, it'd be a huge improvement on user experience.
- Lack of dependency injection/inversion of control. I find it interesting the author lists this as an advantage. With Rails, I was always a little anxious not knowing where things were defined or being implemented.
- Validation happens on models, not requests. With Laravel, I really appreciate being able to validate pretty much any data coming into the application regardless of whether or not it ends up in the database. With Rails, I tried to look for something similar to FormRequest and its validation rules, but I couldn't find many solutions. I think it might just be one of those things that's not the "Rails way".
- Perhaps more of a Ruby issue than a Rails issue, but the dynamism of the language - especially in its type system - was a bit of a drawback for me. I really appreciate PHP 8 and newer versions of Laravel for their support in type hinting and static analysis; being able to mouseover anything and know pretty confidently what I'm working with is a huge boon in my productivity.
I definitely agree with the author on a lot of the Laravel tooling stuff. I've learned to just kind of ignore most of the offerings outside of the core framework. I'm sure it's all great, but there's always a bit of churn in Laravel as the author mentioned so I'd rather save myself the future heartbreak.
Regarding sidenote #1, I actually very deliberately did not mention the language or company ;) Here's the full text of the sidenote, if you're still unable to get it rendering:
> I'm not going to name the language itself, because this post would just turn into a flame war over that language specifically, and I definitely don't want to cast shade on any language/community in particular. I'm also kind of hoping that the most annoying people read this and think, "Ah, of course he's talking about that language over there! This criticism obviously doesn't apply to my perfect and favorite language!" Regardless, I feel that the thesis and content of this post applies pretty evenly to most functional programming languages.
> As I said, the problem is a classic one; it was formulated during the war, and efforts to solve it so sapped the energies and minds of Allied analysts that the suggestion was made that the problem be dropped over Germany, as the ultimate instrument of intellectual sabotage.
[0]: https://academic.oup.com/jrsssb/article-pdf/41/2/164/4909740...
The only issue is remotely deploying Nix configs. The only first-party tool, nixops, is all but abandoned and unsupported. The community driven tools like morph and deploy-rs seem promising, but they vary in terms of Flakes support and how much activity/longevity they seem to have.
[0] https://blog.janissary.xyz/posts/nixos-install-custom-image
That being said, when I finally got around to rackmounting and upgrading some of the other hardware in my lab, this "beginner"'s guide was really helpful.
[0] https://blog.janissary.xyz/posts/docker-gripes , see `Conclusion` section
Mostly technical stuff, some non-technical stuff. I'm currently (indefinitely?) writing a series of posts documenting all the stuff I'm working on in my homelab, which has been fun.
My personal blog, most posts are programming-related but I have a couple on movies/books/history type stuff.
[0] https://www.strongtowns.org/journal/2018/3/1/whats-a-stroad-...
I get that SEO is kind of a race-to-the-bottom scenario, but I always wonder - how are these random sites in business? I understand that they get a good amount of traffic from said SEO and "advertising" pays good money for that traffic, but do advertisers really not grasp that people spend all of five seconds on these pages before going somewhere else?
Now it's gone, and who knows how much music has been lost to time as a result.
The PHP language obviously still has some sharp edges and annoying design choices, but it's seen some huge improvements in the past few years imo. Simply using a framework like Laravel will also save you from some of the more infamous footguns, since there's a lot of secure/sane defaults included.
If I take the liberty of assuming you'll give me $5 for whatever reason (or in the case of taxation, I threaten to take $5 and assume you'll comply), and you do not do so, is it fair to say that I've "lost" that $5?
I haven't used Common Lisp much, but I've seen a few really impressive demos of debugging in its available REPLs. This is a longer one, but a good tour of SLIME (also an Emacs package): https://youtu.be/_B_4vhsmRRI
A good example is a tool like `create-react-app` (especially if you add TypeScript support). It's super easy to use and creates the project scaffold and enormous JS build system for you, but good luck trying to fix it if something breaks!
- Short battery life, was pretty much drained after maybe 4 hours of light use
- The phone would get insanely hot during use, or while plugged into the charger
- Display bugs, every time the phone rotated from portrait to landscape there were black bars or other artifacts
- Poor performance in general, typing too fast caused latency issues and opening apps really made the phone chug
Overall, I think Linux on mobile just needs some more time in the oven along with access to the hardware market that Android/iOS has been able to use for a while. I could probably deal with not having access to the Google/Apple app ecosystem if the phone itself were a smooth user experience, but that's just not the reality of it yet.