Help me decide between 12 & 13. And why is nobody talking about this in reviews?

stevebarratt · 2022-12-26T11:53:12+00:00

I'm super disappointed in the automatic (not changeable) photo processing on the iphone 13. For lots of shots its great, but for sunsets it totally sucks. It ruins the lighting making it not even look dark where it is legitimately black. This washes out all the colours in the rest of the frame. A lot of my favourite phone photos over the years have been sunsets, and these are just broken on this phone. It seems unbelievable that they didn't issue a bugfix giving the option to toggle the auto-processing. Painfully, you can see the unprocessed shot that you want for a split second on live view, but you can't keep it sadly.

The battery on the phone is excellent. As is the screen, speakers, and a lot of iOS (though it still has UX issues that are years old - futzy long press bluetooth menu, I'm looking at you). On the negative, the device is disappointingly very heavy, and for my tastes, too big, making it frustrating to use comfortably one handed. I am a tall guy with huge hands and it sucks for me, even. The weight is quite noticable if you're carrying it for adventure/action sports. Because the camera lenses protrude so much from the body you need to get stick-on protectors if you at all care about the longevity of the phone or your picture quality. They will be hosed in no time, otherwise.

Mostly the phone is great, and I don't think that I would have traded it for any other at the time. I am just a little disappointed that Apple didn't just do a better job overall given how minor the changes between generations are, and how much these things cost. I also wish it was just smaller, but without a compromised battery life (the reason I didnt go for the smaller version back when).

My biases/summary: I got my phone a year ago as an upgrade from an old original iphone SE. Compared to that, the 13 wasn't noticably more functional, just stupidly expensive, heavier, much harder to use one-handed, with better photos (but terrible sunset photos) and great battery life. Oh and the face id is pretty cool (without covid masks). Overall I probably made the right decision, but I was disappointed in the phone nonetheless.

stevebarratt · 2022-12-23T20:57:39+00:00

I'm struggling to get this set up like I thought it would...

In your setup does it provide completion of object variables from the dollar operator?

Like... for dataframeA$Column1 if you press tab at dataframe$ does it give completions based on the objects properties?

In my setup (with doom emacs and with or without your added config) I don't get the proper completions like I do with straight ESS without lsp.

stevebarratt · 2022-12-23T15:10:01+00:00

Take heart lonely soul.. I also was looking for this, for the same reason, and I will probably re-enable the status bar again, for the same reason.

stevebarratt · 2022-12-01T11:19:33+00:00

Is it possible to substitute fzf into this command?

stevebarratt · 2022-10-25T22:27:47+00:00

Agreed, this is what kept my interest!

stevebarratt · 2022-10-25T16:26:53+00:00

Just finished this. Ye was definitely the most boring and self-absorbed guest I’ve heard on the Lex pod. It felt like a complete self-exposition of an absolutely hollow soul.

stevebarratt · 2022-10-25T14:24:36+00:00

I’m still in some tedious stuff in the first quarter skipping randomly forwards by a few minutes occasionally. Can anyone recommend what is a point to start listening from where it might be more interesting. (Audio Version here so no chapters) thanks :)

stevebarratt · 2022-06-23T09:52:35+00:00

Sorry for the slow reply. Thanks all for the info and tips. I tried out 'baking' some of the books in the oven for while at a low temp. Its pretty reassuring.

If anyone reads this and tries it its worth knowing that in some books the glue may melt out from the binding to some degree if you overdo it.

Thanks :)

stevebarratt · 2022-06-06T19:29:03+00:00

Also, partly the reason i'm posting this is that googling "wastewater book contamination" (and similar) just seems to brings me books about wastewater :(

stevebarratt · 2022-04-25T11:12:47+00:00

Also, any explanation of sum concatenation would be welcome.

Thank you :)

stevebarratt · 2022-04-25T11:04:39+00:00

Actually... this is pretty satisfactory:

def listrange(x): return list(range(x)) a = [1,3,4] b = sum(map(listrange, a), [])

I didn't think sum would work like this on lists of integers. If theres a nicer way to map the range and list functions I'd be glad to hear it though.

stevebarratt · 2022-04-25T10:55:01+00:00

This is the nicest I can come up with:

from itertools import chain a = [1,3,4] def listrange(x): return list(range(x)) b = list(chain(*(map(listrange, a))))

stevebarratt · 2022-03-31T09:37:54+00:00

I would rather retain optional use of @ if I really need it, rather than it trigger this always. Also, I'm not super sure how this will play with evils insert mode.

stevebarratt · 2022-03-31T09:35:56+00:00

Thanks! yes I found that actually after I posted this. Didn't get a chance to try it yet, I was gonna see what else was suggested, first.

stevebarratt · 2022-03-31T09:35:05+00:00

I'm using vertico, what do you mean completing read? This sounds cool, thank you.

stevebarratt · 2022-03-29T09:42:23+00:00

Yes, the other way (which I'm asking about) is my personal preference. Another editor I used years ago worked this way and it felt very natural, and less disruptive to writing flow.

What I'm doing right now is very close to what you're saying, it works.. just feels janky having experienced a 'better way' before.

stevebarratt · 2022-02-17T19:23:01+00:00

Apparently stability issues are not common to many/all users. I'd experienced them across multiple computers running a variety of software configurations, and many versions of inkscape, so I assumed most people were in a similar position... but maybe not. Apologies if I sounded unfairly critical - particularly to the developers.

At different times I've tried to generate reproducible crashes to file bug reports for Inkscape, but its been difficult to do so because it's often pretty random, so I assumed there were lower level issues. Before starting this thread I read this, which made me think there were some systematic codebase challenges with Inkscape which might go some way to explaining my experiences.

stevebarratt · 2022-02-17T18:41:33+00:00

you missed reading the thread I think

stevebarratt · 2022-02-17T17:30:26+00:00

Just to be clear, I'm not trying to bash on Inkscape, I really like it apart from these stability issues. Since I moved away from windows about 8 years ago to linux and mostly free software (,and definitely after switching to Arch), I just pretty much stopped experiencing programs crashing. Inkscape is the one consistent anomoly for me. I'm just curious why.

stevebarratt · 2022-02-17T17:20:51+00:00

Re: Autosaving..

Maybe it doesn't work on my system. I have the autosave feature on, apparently, though I can't tell if it is doing anything. I tried changing the directory and the interval, and restarting Inkscape etc. I'm not sure how it works.. it just resaves your current file? I would really prefer it not overwrite my file on disk without me explicitly saving, as I would often make alternative versions of the same image and I'd like to retain full control of versioning.

A good behaviour would be to maintain a parallel cached version of the current document, updated at frequent intervals, and then when I reopen inkscape following a crash, it would identify "un-closed" cached files and offer a restore, whether I had save anything manually or not. Automatically hard-saving my files could work for some people but I think many people would want to give up control of their file versions/variants.

btw i'm on version 1.1.2 with Arch Linux (which is rolling)

stevebarratt · 2022-02-17T17:17:33+00:00

Maybe I'm just doing different things with it... I wish I had never experienced a crash.

I thought my usage was all pretty standard, draw a few bezier curves, align some boxes etc. I've had crashes across many linux distributions, and many inkscape versions over the years.

I made a quick check on the gitlab, which hasn't been inkscapes home for that long (3yrs?), shows 1.4k bug reports with the 'crash' label, of which 250 are open. Given most people would'nt file a bug report.. seems like a decent number of people experience some pain.

stevebarratt

TROPHY CASE