2 ms·
No, I end up with classes like that because when I wrap APIs the point is to simplify, so I simplify. Though that is a last effort if ditching the broken API en
by vidarh 5y ago
No, I end up with classes like that because when I wrap APIs the point is to simplify, so I simplify. Though that is a last effort if ditching the broken API entirely isn't an option - e.g. if it's a third party API we can't avoid. That is rare to begin with.
You're free to find Intellisense etc. useful. I just don't. I go to great lengths to have an uncluttered view of the code when I work, because I find it far more preferable to focus on just the code. I'm not against it in principle - I've just not seen any solutions like that which works for me. I don't tend to need to look up methods much; when I work on a piece of code I tend to hold the APIs in memory pretty effortlessly, so that's just not much of a consideration.
I spent years actually looking at implementing visual languages because I liked the idea of providing more contextual information and views of information flows etc. to aid development, but I've yet to find something that works better for me than an uncluttered view of the text.