Responsive design techniques were introduced to solve a problem: How can a cross-platform application be viewed (& used) successfully on a variety of (differently limited) devices?
Monitor dimensions, aspect ratios and pixel densities are probably less likely to vary on a laptop or desktop computer.
I would suggest thinking about the specific context your application is likely to be used in.
Eg. Is the resolution of your target users likely to be restricted? Are many users likely to use widescreen monitors? Which other programs are likely to be open / used at the same time as your application?
If you have a scenario where automatic reconfiguration of your interface layout makes sense, then use responsive techniques.
Thinking generally; if your application is provided with a greater area of screen real-estate, I think it's sensible to make use of it - but I'd choose to avoid re-positioning of a UI layout as a window is resized, as this could lead to confusion.
One major difference between a web and native application, it the fact that a native application can make use of the host operating system's windowing system.
There's less restriction in a desktop environment (Windows / OS X / Linux), so the original problem tackled by responsive design might be less relevant.