What finally worked well for me was an "ear loop" tool, a small, cheap plastic tool with a safety guard, that makes extracting the wax quite easy. They cost less than $10 USD, do not rely on uncomfortable squeezing of water or liquid, nor do they just push the wax farther in (unlike a cotton swab).
It was a big deal for me to discover these existed, and when I did, I was surprised I hadn't heard of them.
I had a 'rattling' issue, but mine correlated with moving my head. If I held very still, the sound was fine. This didn't happen at first, it developed over time. I wondered if the issue was either loose/dirty silcone tips, even though I was wearing the best fitting size (and they passed the ios ear tip test). Cleaning the tips didn't make a difference.
So I bought some new foam tips from www.complyfoam.com , and to my pleasant surprise, the rattling stopped.
Not sure if this is different from the vast number of other reports, but fyi.
We currently use this to store security log data, but think it's an interesting midpoint between having no schema at all vs requiring schema registries to do useful work.
Perhaps Ithaca, New York? It's a smallish college town (Cornell, Ithaca College), but with lots of great scenery nearby, including forest, lakes, and gorges.
An advantage of dynamic libraries is that the memory used to hold the library's executable pages can be shared across processes. So using static only binaries will lead to less free memory on the OS.
That's the party line. It's often wrong. If two copies of the same program are running, they share memory for code. For a shared library to reduce memory consumption, there must be multiple different programs using the same version of the same library. That's not all that common, beyond very basic libraries such as "libc".
Linking to a shared library brings in and initializes the whole library, even if you only need one function from it. So you tend to get stuff paged in during load that never gets used.
Isn't it? Usually distros target their packages to a single library version, and often people run suites (Gnome, KDE, etc) that use a similar set of libraries in their different processes.
I'd argue that libraries like GTK were only allowed to become so bloated because dynamic linking masked their true impact on the system. If static linking were the norm, we'd be using much simpler, cleaner libraries because people would think twice about adding 100+ megabytes to their binaries for basic GUIs.
You can't just say you worked at Be and not tell more stories! When were you there and what did you do? Why do you think you didn't take over the world? Have you tried Haiku?
indeed. Be belongs to a list of companies that would be great to hear insider stories about. also NeXT, Thinking Machines, Symbolics (sp?), Infocom, Cray, etc
Yes, as I understand it, is_computer_on and is_computer_on_fire were basically no-ops to benchmark kernel calls. One returns an integer and the other a double. But I could be very wrong, I have absolutely zero authoritative knowledge and this is simply an explanation I once heard that made sense to me.
It was a big deal for me to discover these existed, and when I did, I was surprised I hadn't heard of them.