8,351 karma · joined June 7, 2016
Twitter: @tomduncalf
Maybe their philosophy is that the Top 100 should be an open thing and they shouldn't restrict who can enter based on music style... to me, it makes DJ Mag way less credible, but I guess they probably make money out of the Top 100 being so big.
Presumably because it’s free, but I’m with you on the clunkiness. The UI looks very dated.
I can recommend OcenAudio, which is free though not open source, and for me offers just the right level of functionality in a clean user interface. It’s very similar to how I remember the old versions of Cool Edit pre-Pro, which I thought were amazing bits of software.
I always default to AU just because I’m on a Mac and I arbitrarily decided to do so long ago. The Rosetta thing has been a nice bonus. Not sure what the other (dis)advantages are, these days I try to focus on using native Ableton and M4L stuff anyway!
The only downsides are:
- I've had keycaps fall off after a couple of years and they're almost impossible to get back on (for me at least). The second time this happened I realised it had a 3 year warranty though, so got a replacement.
- It requires a dongle rather than Bluetooth, and if you lose the dongle, you're screwed, as they're paired in the factory and can't be reconfigured.
Are there any other similar keyboards worth considering? Must be wireless, low profile keys and split layout. The Logitech K860 looks alright but I don't need or want the numpad really (I like having my Magic Trackpad closer).
File management on iOS is a mess too. It’s a shame as there’s so much good stuff in the Apple ecosystem but their cloud file storage is not something I want to get involved with any more than I need to!
- Working with unfamiliar APIs which don’t have great documentation. It can be quite helpful for asking questions here, essentially taking the role of Google/StackOverflow, as long as the API was created before the knowledge cutoff and I guess as long as there’s enough content out there. It felt to me like it was able to do quite a good job of linking together the (rather terse) official docs with code from GitHub to show real world examples of how to do stuff. This was definitely net useful for me, but it does like to hallucinate APIs that should exist but don’t.
- Working with unfamiliar languages. I used it to help me write Rust recently (“how can I express this code more succinctly?”, “why won’t this compile?”) and it was quite useful, though I feel like you hit the limits of it if you get deeper into e.g. trying to find a workaround for a borrow checker situation and it’ll just make up code that doesn’t work.
Outside of that, I find it can be quite useful as a supplement to Google, and is good for writing things like regexes, but when I’ve tried doing more advanced coding tasks with GPT-4, I felt like I ended up spending more time trying to make the output compile and work (sometimes without success) than if I had just written it myself. It can be good for working out the broad outline of a solution though.
Overall, I find it a useful tool but I am sceptical of people claiming a 5x increase in productivity thanks to GPT.
I created an issue, if you have an example prompt to add that would be helpful! https://github.com/jmorganca/ollama/issues/422
For me being able to do this kind of stuff without needing a tripod or external features was a big selling point of the camera.
There’s an iPhone app called Spectre (from the makers of Halide) which can do long exposures like this too, but I’ve not had the best luck with the results in comparison