What I do is just take out the card a plug it into a little USB dongle thing which I can plug into either my phone or laptop.
What's wild to me is that anyone would do it any other way. I'm astounded that this is somehow a "tip".
Not even 10 years ago it was simply the way to do it.
It's actually just one atom away!
I've had someone tell me with a straight face that I'm "basically taking meth".
This is the same kind of person that says "American cheese slices are one molecule away from being plastic!"
It's not gamification that's the issue. That aspect really held my attention and gave me consistency.
It's the push to a pay-to-win model that made me quit. They made the challenges harder and harder to complete without using boosts, and to use the boosts you had to use gems. And gems were really hard to get unless you bought them with real money. It doesn't matter if you have a super subscription (or whatever it's called), you still had to pay to get the gems.
And the prices for the gems were just as predatory and the disgusting mobile gaming industry. Never should there be an option to spend over $20 for in-game consumables, nevermind over $100. It's sick.
It's actually astonishing how fast Tesla went from the most sought-after brand to becoming the most hated brand.
There are going to be case studies on this for centuries in all kinds of sciences.
Thank goodness they cleared out all that snow and ice so that we can finally see the pretty mountains.
Long time "old-school" kernel maintainers don't know Rust and don't want to learn Rust (completely fair and reasonable). But some of them don't want to work with the Rust guys for lots'o'technical reasons.
It's by far not an easy situation technically. Like this is a huge challenge.
But some of those old-school C guys are being vocal about their dislike of Rust in the kernel and gatekeeping the process. This came to a head at a recent conference (Linux Plumbers Conference?) and now one of the Rust maintainers has quit.
The big technical challenge is being confounded by professional opinions.
What the user was doing is that they don't trust that the system truly deleted the account, and they worry it was just deactivated (while claiming it was "deleted"). So they tried to do a password recovery which often reactivates a falsely "deleted" account.
I've done this before and had to message the company and have them confirm the account is entirely deleted.
Why should Amazon be liable for stuff sold by third parties?
Even when proven dangerous products are reported to Amazon they continue to sell it.
Louis Rossman talks about it a lot.
JSON data within a database is perfectly fine and has completely justified use cases. JSON is just a way to structure data. If it's bespoke data or something that doesn't need to be structured in a table, a JSON string can keep all that organized.
We use it for intake questionnaire data. It's something that needs to be on file for record purposes, but it doesn't need to be queried aside from simply being loaded with the rest of the record.
Edit: and just to add, even MS SQL/Azure SQL has the ability to both query and even index within a JSON object. Of course Postgres' JSONB data type is far better suited for that.
No, he meant what he wrote: hyprland
Edit: https://github.com/hyprwm/Hyprland