Yeah, I find it especially annoying when apps do use the XDG directories but use them incorrectly (dumping a bunch of state/data in .config is unfortunately too common). If apps want to do that I wish they would just grab $HOME/.appname rather than mess up my .config dir.
Besides cleanliness which is more a preference I agree, separating config, data, and cache makes it easy to know what can/should be backed up, what can be synced across machines, etc.
As I said in a different comment here, I have 94 files and folders in my home, 84 of which are hidden, approximately zero of which actually needed to be hidden.
If anything, it's the reason this is such a common issue, the dot lets everyone shit files out all over the place but oh it's hidden so no big deal.
My heart sank when they said 13 pro and then to see that so much is backwards compatible was amazing. It's quite refreshing to see a company live up to their mission so well.
Yeah, really impressive to see that you can take a 13 and turn it into a 13 pro with just a few new parts.
I've just ordered my own 13 pro. I've been waiting for a laptop and this ticks all the boxes. I'd previously ordered a new dell xps laptop and ultimately returned it because the keyboard was busted. I would have kept it if I could have swapped the keyboard for a new one. The use of LPCAMM is also really nice. I've hoped to see this standard start taking flight and I'm happy to grab a product with it included.
I'm not in the market for a Windows or Linux machine myself, but the way this company operates I feel like supporting them with a purchase at some point regardless.. maybe their Desktop tower
I was screaming at my screen when I heard 13 Pro but I am now ever so happy when they mentioned being able to just replace, part-by-part, a regular Framework 13 into a Framework 13 Pro.
Same, though the battery upgrade alone will be around $260 because of the new bottom cover, at that might just throw in the speaker upgrade as well for $19.
Not sure if I even want a haptic touchpad at all.
It's a matter of preferences. Actually I like trackpads that don't mind and have physical buttons. The separation between the surface that moves the pointer on screen and the surfaces that generate the clicks means that there are no misclicks and no involuntary pointer movements while clicking.
Haptic schmaptic, I just want my Framework's enormous trackpad to respect deadzones and stop detecting my palms. I had to entirely disable tap-to-click, because nothing else would work.
I might have to try their preinstalled Ubuntu images or something and see if there's some secret sauce in the input configs.
> For Linux libinput “Disable While Typing” (DWT) problems, this page claims libinput will only use the DWT setting if the keyboard and touchpad are either both identified as internal devices, or are both identified as the same device.
There is no accounting for taste.
For instance, I still prefer discrete buttons over tap-clicks or multi-finger-taps, but I would accept the mild annoyance of tap clicks over the pressing down the pad itself.
Not a huge fan of the "force touch" trackpads on newer macs, the old man yells at the clouds.
In all seriousness though I have used a pre force touch MacBook not too long ago and I prefer that experience a lot over the new one I have from work.
Though the larger size of these trackpads is something I really like and where neither the older MacBook nor the the current non-pro Framework 13 come close.
I did last year after deciding that Apple's software just isn't for me anymore. I've always had a Linux desktop around (and used to daily drive Linux on a laptop years ago) so I was happy to consolidate on my preferred platform.
Biggest gripes I had are:
A) battery life (both during use and standby just kinda sucking on Linux in general compared to os x, not exactly framework specific but I did get used to how amazing my m1 pro for longevity)
B) the case looking nice but feeling a little flimsy
C) the speakers are pretty bad (though I did get turned on to easyeffects and there is a profile for the 13 which helped a bit)
D) macs completely spoiled me trackpad wise
It seems like they are taking a stab at all of these in some way and I'm excited to see how it goes, especially with so much being backwards compatible.
All the same gripes from me. None enough to be a deal breaker, but every once in a while I'll do something on my GFs macbook pro and be blown away by how solid it feels.
I was pleased to see that The Verge's coverage of the event [1] was very positive on the feel of the laptop (even saying they got the hinge feel right like on the macbook which was the first thing I noticed being "not quite right" with the framework when I got it). I'm optimistic that this will be a big step in the right direction.
I don't know who you think the "real family" is but a) narrowing what a real family is does an awful disservice to a whole host of unique families, not just families that involve surrogacy and b) nearly all surrogacies in the US are gestational surrogacies where at least one parent is genetically related to the child and the surrogate is not at all related to the child (not that genetic relations is what makes something a real family or not, but I'm pretty sure thats what is implied here).
I think he's just trying to remind people that someone can both be a CEO of a powerful company you might disagree with/hate as well as a real human with a husband and child and that trying to set fire to his house could kill those people.
I personally wouldn't go as far as to say the Farrow article caused this but it seems fair game to respond to an article that had an over the top cover image of an animated Sam Altan picking and choosing faces with a photo reminding people he's human like everyone else.
Robinhood gets double shame points for naming the app "Banking" (previously "Credit Card"), no Robinhood or RH in the name. I love the card but hate everything about that app.
The site that irks me the most here is New York Times. Opening an article in the mobile browser often has a toast over the bottom third of the article to open it in their app for "a better experience". I struggle to think how nytimes isn't a perfect fit for a site over an app. The only frustrating experience I have with the web version that would be better in the app is not seeing that that pop-up.
I recently signed up for a membership (you can now supposedly cancel without making a phone call; WaPo has officially died in darkness) and this has been driving me mad, too.
If I'm paying for your service, you should not be degrading my experience using UX anti-patterns in any way, for any reason.
For games I agree that an app makes sense (though I think at least the games I used to play were in a separate nyt games app). For interactive articles, I've not seen anything I couldn't use fine in my browser, but in theory I wouldn't mind covering up the interactive part with a "Open in the app for a better experience" button (similar to what YouTube does on the video portion of the page). Where I encounter this though is in standard, text-heavy articles that maybe include a photo or two.
I assume the reason they are pushing me to the app is that it benefits them not me (longer dwell times, maybe easier tracking for behavior/ads), and that is precisely why I want to stay in the browser. Covering up a good portion of the article and preventing me from scrolling until I click the tiny link to decline is hostile and is the only thing degrading the experience on the website for most articles I read.
For arbitrary contracts I would agree, but I think increasing the limitations in severance agreements specifically makes sense. There are already certain requirements (at least in California) for severance agreements and I think limiting the duration of non-disparagement clauses to 1-2 years would be a positive change.
I don't have much skin in the game but as a passerby, I agree that the report obviously was made with a lot of time/effort but wouldn't dramatically change someone's view of Ruby Central or assure anyone this won't happen again. This is like writing an outage postmortem without really getting to the root cause and identifying what can be done to prevent in the future.
reply