One of the biggest reason I migrated to Codex. I'd like to see each agentic CLI process as a simple building block, and having 100 claude session means I sometimes run out of memory (and I have 256GB of them). Codex never have this problem.
The communication is more direct too with GPT5.6 family of LLM. No more belt and suspenders.
When my Intel Mac ran out of disk space once, it became impossible to clear the space without rebooting (due to APFS's annoying journaling crap or whatever -- it would literally say "rm: can not remove [whatever]: no space left on device" or something), which caused Google Chrome to wipe all my local storage and cookies because it loves to do that when you run out of disk space, and there's no way to get that data back even if you do somehow clear space with the browser still running. I've been bitten by this many times on at least four different platforms. I wish it could just keep everything on disk instead of deleting it all? Like anything that deletes my data automatically can just go die in my opinion. This is one of the reasons I don't use Google Chrome anymore, another is how it deletes "old" history too (after 3 months) even if you have terabytes free, which is just so offensive I can't even explain it. Ungoogled Chromium lets you turn some of this stuff off, but when I moved to Mac I just started using Safari.
The only way to save my file system was to boot into recovery mode and run a verification with Disk Utility, then I was able to remove some files and get my space back.
I've also found that the fastest way to totally lock up a Mac kernel is to have some external hard drive fail while connected. You will be unable to open, quit, force quit, or reboot, and it won't boot up again unless that drive is disconnected.
Both MacOS and Windows start having issues if you have less than 10% of the disk free. The problem with the Mac is your ~/Library/Application support/ folder can get huge and take up a ton of space. Mine is currently at 55GB
Around my location (southern brazil) there are hundreds of species of stingless bees, living in colonies. Many (most?) produce honey too. I don't dispute that there are also lots of solitary bees. Bees are wonderful and way more diverse than people usually think.
"Vocal fry", aka "creaky voice". It's stereotypically associated with irritating young women.
I like me a good rabbit hole that's interesting and also digs into stereotypes.
Turns out, like many memes, it's not just that. It's (also?) a normal speech pattern, used by different genders, ages, and social groups, in many languages.
This doesn't mean that vocal fry isn't used as social signaling. But complaining about it, well, isn't that social signalling too?
It's both; the one I mentioned is for system drivers, the one you're talking about is for running applications (which you can also do on a regular non-Halium GNU/Linux using e.g. Waydroid).
I'm sure that if you tell Jolla about a relatively modern mobile SOC with mainline linux support, they'll look into it instead of relying on libhybris.
They can rely on libhybris if they want, why should I care - I just object to calling that "a full-stack alternative", especially when alternatives do exist.
That wasn't modern when they released it in 2020. Jolla chose a little more pragmatism for their hardware in the hope that they actually sell phones to other people than 100% open-source purists. I find it funny when dudes like you go all "well awkshwally" on them...
I use my Librem 5 as a daily driver, and I’m certainly not an open source purist.
What I do care about is that my phone isn’t going to run into obsolescence a few years down the road (due to hard kernel forks and YOLO’ed device drivers that are not going to be updated for newer kernels).
Battery: I unplugged it from the charger 10 hours ago, it's currently at 55%. Typically it's up to 22 hours when suspended, up to 12 hours when idling without suspend and about 3-5 hours of active use depending on what you're doing. Could be better, but can be worked with.
What I was trying to tell you with my original reply to you is that Jolla chose a different point on the free/pramatic curve of available SoCs. They selected a phone that's more likely to be used by average people rather than a fully open one. (You can still see in this very thread, complains about the high price for what it offers, showing they haven't fully succeeded, at that.)
Pointing out that they still rely on Android drivers for booting the thing is a little tone-deaf from my perspective when they're basically choosing a different path towards a similar goal to Purism and other alternative mobile vendors: higher availability of non Google, non Apple mobile devices. Perfect is the enemy of good and all that. And like I explained the reason for their choice is not nefarious but a pragmatic one.
And what I was trying to tell you is that they're free to choose whatever point on the curve they want and pursue that as long as they don't misrepresent what they're doing. What is "full-stack alternative" supposed to mean when it relies on the very thing it's supposed to be an alternative to? What is Purism's effort then, "even fuller-stack alternative"? Words have meanings.
The tv remote sensor stopped working (and broke again after servicing), so now the only way to use the TV is by the LG app on my phone.. which asks for permissions to Nearby Devices, Location, Camera, Microphone, Notifications, Phone, Music&Audio...
This remembers me of the Modbook, back in... check notes... 2008? I'm old. They would take a Macbook, re-case it and transform it into a tablet. Super cool. Looks like they kept doing this for a few iterations.
Not sure if it adds anything, but a factoid I know is that CD timing is expressed in minutes, seconds, and frames, where each frame is 1/75th of a second.
I'm not sure but I think this is also the smallest time resolution.
Then each frame is composed of samples, but they seem to be counted in groups of 1/75th os a second anyway.
I was also wondering about the inherent resolution for the BPM precision claims.
Besides the sample period, the total number of samples matter for frequency resolution (aka BPM precision).
44100 Hz sampling frequency (22.675737 us period) for 216.276 s is 9537772 samples (rounding to nearest integer). This gives frequency samples with a bandsize of 0.0046237213 Hz which is 0.27742328 BPM.
Any claim of a BPM more precise than about 0.3 BPM is "creative interpretation".
And this is a minimum precision. Peaks in real-world spectra have width which further reduces the precision of their location.
This takes my flac rip of the CD and simply uses the full song waveform. This artificially increases frequency precision by a little compared to taking only the time span where beats are occurring.
This is plainly false though. You're saying beats can't be localized to less than one second of precision (regardless of track length, which already smells suspect). Humans can localize a beat to within 50ms.
Yes, I got lost in the numbers and made a blunder by misinterpreting what we mean by frequency resolution expressed in "BPM" instead of Hz.
It is correct to say "0.0046237213 Hz which is 0.27742328 BPM". My mistake was to interpret 0.27742328 BPM as the limit of frequency resolution in units of BPM. Rather, any BPM measured must be an exact multiple of 0.27742328 BPM.
Thanks for pointing out my mistake!
> (regardless of track length, which already smells suspect)
Frequency resolution being dependent on the number of samples is a very well known property of basic sampling theory and signal analysis.
In fact, one can interpolate the frequency spectrum by zero-padding the time samples. This increases the resolution in an artificial way because it is after all an interpolation. However, a longer song has more natural frequency resolution than a shorter song.
Note, this frequency resolution is not related to fidelity which is some messy human related thing that is over a sliding window of shorter duration that I don't pretend to understand.
BTW, the opposite is also possible. You can zero-pad the spectrum as a means of resampling (interpolating) the time domain. This is slower but more spectrally correct than say time-domain linear or cubic interpolation.
These techniques require an FFT and so are somewhat expensive to apply to long signals like an entire song, as I did for the plot. Daft Punk's HBFS takes about 8 seconds on one CPU core with Numpy's FFT.
I'm on a 36gb M3 and I have to reboot it every three to five days to have it behave again.
I have normal dev apps open: a browser with jira, another with testing, another with documentation, an ide, teams, calendar, zoom.. it adds up very, very quickly. 16gigs are gone in the blink of an eye
If you have to reboot to get it useable again instead of just killing and re-launching the applications there's something wrong with the OS, not with the applications. Have you tried killing and re-launching the browsers and pseudo-browsers (Teams etc.)?
adults passengers can adapt the conversation to your needs, keeping quiet and even helping with decisions.
screens, kids, dogs, people on the phone, etc can't do that
all these electron apps and invisible virtual machines (looking at you Claude) really don't help.