I can’t really see another market where it’d make sense.
649 karma · joined August 28, 2020
I can’t really see another market where it’d make sense.
Especially since I don't work on a fixed project for very long and am constantly installing new dependencies, using different data, etc.
Not to mention I've found adding a layer of virtualization can break some already fragile libraries (e.g., I'd be concerned about multi-GPU training over NVLink).
The worst part is, after spending a couple hours building 5 separate libraries from scratch and making sure all the versions match, there’s no easy way to reproduce your environment on another machine.
It’s natural to say plan a longer term trajectory at 1Hz, a short-term trajectory at 10Hz, and perform control at the 100Hz, obviously with those rates varying based on the system.
And since (generally speaking) higher levels of planning require more compute resources, it might make sense to partition the compute and take the latency penalty.
In terms of traditional automakers and systems that anyone can buy, Tesla is the leader (although I believe hyundai has a very good highway system, not city though). But in terms of self-driving, it's hard to rank precisely but they're certainly nowhere near, say, Waymo.
Plenty of people enjoy FSD and understand that they still have to correct it every so often but to a lot of people "self-driving" means just that.
I've been coding for the past 2 years almost exclusively through VSCode remote on Linux servers with few complaints.
Get a seperate SFTP/network file client as the built-in VSCode one is slow and unstable but otherwise everything works great. If you're considering using any Jetbrains IDE over a network connection however, I'd encourage you to think again.
And GPU-GPU interconnects are important for this type of training so putting as many GPUs as possible close together is necessary.
I thought the same thing about Python's indenting originally (and still do). But the ecosystem was enough to overcome it for me eventually.
Also don’t allow the pin for some operations (or let you disable this). E.g. for viewing passwords or other sensitive operations besides login, it’d be safer for me to not allow pin access and only Face ID.
I’ve found most of the alternatives have a high (for my use case) learning curve. For real debugging I use VSCode but it’s nice to be able to quickly throw breakpoints around.
macOS games are dead and iPad games are better but still adding a complex feature for a small group of iPad users might not make financial sense.
On the other hand, deep-learning based compression with autoencoders or something similar is pretty promising, since it can learn the constituent elements in a more general way, independent of what program was used to create it.
The barrier of writing both a front and backend for a simple demo/viz tool is pretty high (relative to the time it takes).
Also the line can be blurry with celebrities since they will engage in business deals.
Some people do all their work in browsers.