Param and Traitlets solve similar problems but were developed independently, with Param starting in 2003 and Traitlets appearing in 2009. By now both are well established enough in their different ecosystems (Jupyter and PyViz) that it would be very difficult to move away from either one. However, there are certain cases where one might want to supply a HasTraits object where a Parameterized object is expected, and vice versa. For instance, a dashboard or app may want to include allow configuring either type of object, but it is unlikely to be written explicitly to provide that flexibility. Instead, maybe it would be possible for us to write a wrapper for a HasTraits object so that it can appear as a Parameterized object, at least for certain use cases such as for ParamBokeh? Not sure how feasible that is, but it seems worth considering when it comes up.
Param and Traitlets solve similar problems but were developed independently, with Param starting in 2003 and Traitlets appearing in 2009. By now both are well established enough in their different ecosystems (Jupyter and PyViz) that it would be very difficult to move away from either one. However, there are certain cases where one might want to supply a HasTraits object where a Parameterized object is expected, and vice versa. For instance, a dashboard or app may want to include allow configuring either type of object, but it is unlikely to be written explicitly to provide that flexibility. Instead, maybe it would be possible for us to write a wrapper for a HasTraits object so that it can appear as a Parameterized object, at least for certain use cases such as for ParamBokeh? Not sure how feasible that is, but it seems worth considering when it comes up.