I've only recently switched to Cursor so am not clued up about everything, but they mention that the embedded indexing they do on your code is shared with others (others who have access to that repository? Unsure).
It did seem to take a while to index, even though my colleagues had been using Cursor for a while, so I'm likely misunderstanding something.
If you use the terminal for any appreciable amount of time I heavily suggest getting fzf (even if just for the search).
Tmux is great if you need any more than 1 terminal window open at once - just remap some of its hotkeys to stuff that make more sense for you (e.g. I use "Alt + |" to split vertically and "Alt + -" (minus) to split horizontally).
Man pages are generally about 500 times longer than I need them to be (just help me do a basic curl/SSH copy/... please) - so I have cheat.sh aliased which helps a lot with simple "how do I use X".
Aliases in general are insanely useful. If you're a fzf search whiz they may not help you as much but seeing people type common commands out multiple times a day... makes me happy knowing I have my alias bank.
> Tmux is great if you need any more than 1 terminal window open at once - just remap some of its hotkeys to stuff that make more sense for you (e.g. I use "Alt + |" to split vertically and "Alt + -" (minus) to split horizontally).
Nice tip! While I don't mind the default Tmux keybindings (<prefix> " and prefix % for horizontal and vertical splits), one thing that used to annoy me early on was how new panes would default to the directory where Tmux was originally launched, rather than inheriting the current working directory. Fortunately it was easy to fix with a few lines of code in ~/.tmux.conf:
This ensures that while splitting a pane with <prefix> " or <prefix> %, or while creating a new window with <prefix> c, the new shell inherits the working directory of the previous pane. This small tweak saved me countless unnecessary "cd" commands.
`fzf` is so universally useful I just recommend it by default to everyone I work with now who touches a terminal. The new fuzzy finding shortcuts it creates for shell history and switching directories alone makes it worth it, even if you never call `fzf` itself, as I recorded back in my tutorial eons ago. [1]
It seems nobody has asked/suggested this so I'll do it - I would love to specify time of day/traffic conditions during which to determine time taken to travel.
In the next year or two we'll be looking to move and since we work on the southern side of the city, living out to the north wouldn't work due to traffic through the city.
In the same vein as this I've wondered for a couple years now what the impact of flash storage longevity is on mobile phone performance over time. Felt like my Samsung S8 was very snappy when I got it, yet a couple years later things that used to be fast - like finding specific music, scrolling through the photos in my gallery, etc. - had slowed down considerably.
Could also just be software updates or other things causing this but there should be some component of decreasing performance caused by wear on flash storage.
You're right, flash degradation and deterioration of write speeds is pretty much primary reason why older phones feel slow and laggy.
A lot of - especially older or mid/low range - phones have cheap eMMC storage which is signifcantly worse at wear leveling than the higher end UFS storage.
> phones have cheap eMMC storage which is signifcantly worse at wear leveling than the higher end UFS storage.
Which is shocking really - the phones should switch the eMMC to RAW flash mode (ie. no wear levelling), and then write an actually-smart wear levelling algorithm that runs in the OS.
The OS has far better info for wear levelling anyway - it has more visibility into read-write patterns, it has more RAM to store more state, it can cron background scrubs and reorganisation to idle periods, it can be patched if a bug is found which only manifests after years, etc.
Unfortunately, as far as I'm aware, most eMMC's can't be put into any kind of RAW mode anyway.
The only part of a far future sci-fi that stayed with me is the use of memory chips as universal (ha) currency :ie capacity was face value and then total value was determined by the data contained on the chip and how much someone(thing) wanted that.
Sometimes it looks like that is an inevitable outcome.
That's possible, but it doesn't sound like an analogy to me, and I've known enough selfish assholes in my life to absolutely be able to picture this as a real thing that's currently happening.
Glean.com? We had an intro meeting with them, pricing only makes sense if you're in a first world country and have 100+ or maybe 150+ employees.
I recall pricing started at 50k USD per year but may be remembering incorrectly. Please take this with a grain of salt as they may have changed their pricing models or whatever - I just get really annoyed at the "contact us" stuff so thought I'd try to help out here.
Have you not had any of the classic Gnome/Linux/Wayland issues? Electron apps running slow/freezing, weird scaling issues, screen recording issues, display output/detection issues, sound and Bluetooth issues, ...
Some of these may be due to my laptop's shoddy support for Linux but I also had issues on my Lenovo ThinkPad X1 a couple years ago.
I don't know that I actually have any Electron apps installed on my computer, unless VSCode is Electron, in which case that one hasn't given me any issues.
I haven't had any scaling issues, I haven't tried screen recording. Sound mostly works fine, though it occasionally gets pretty confused by HDMI sound output (though that's usually resolved by re-plugging the cable). Bluetooth worked fine for me without any headaches, I even got Airpods to work without much trouble.
The only issue I've really had with Gnome, and I have no idea what this is and it's probably a bug in Firefox, is that for some reason the web interface for Transmission Server will crash the entire desktop. I need to muck about with dmesg or journalctl to figure out why and then file a bug report, but it's definitely that page (I've recreated it with just Firefox open on the Transmission Web page).
Otherwise, it's been great, I really like Gnome right now.
Scaling issues and screen recording are application side problems.
Fractional scaling works only for native wayland applications. For X11 applications running under Xwayland, they run at classic 96 dpi and are upscaled to the given fractional scale. Obviously, upscaling and bilinear filtering means blurry applications. (Even vscode has to be forced to use wayland - it is capable of doing so, but it still uses x11 even on wayland system by default).
Screen recoding problems are also legacy issues. All these application that have problem (Webex, looking especially at you) are trying to screengrab using XGetImage at x11 window, root window for entire desktop; which obviously doesn't work (and it ever worked under X11 only due PCs using global framebuffer without any overlay planes in the past). The proper way is to use Pipewire, which Chrome or Firefox has been doing for ages already. Just some apps think, that what they were doing 15 years ago is fine today too, why bother updating.
reply