4 ms·
It does look crappy, IMHO. It feels like a 2000's trend that was cute (pun intended) but nowadays it's been 20 years and now looks out of date. Probably it's j
by j1elo 5y ago
It does look crappy, IMHO. It feels like a 2000's trend that was cute (pun intended) but nowadays it's been 20 years and now looks out of date.
Probably it's just me, though: at that time I was working at a company with a name starting by V. The product name itself also started by V. We used the C++ Qt framework, where every class starts with Q. So the lead devs picked up the trend and all our classes' names also started with V. Basically everything was named as something following the same letter.
- simion314 5y ago>So the lead devs picked up the trend and all our classes' names also started with V. Basically everything was named as something following the same letter. That can be usefull, you know by looking at a class name , if it starts with Q is a native Qt stuff, and if it starts with V is your own custom stuff. As an example if you would see a VDropDown you will know that some of the developer in the company was asked to "improve" the native dropdown , you should check if there are bugs there.
- j1elo 5y agoYes, I liked at the moment, and still today see the appeal of using a common prefix for the internals of a software project. However I don't think it's a good idea, nor pretty or attractive, that such a technical decision transpires to the public facing side of the project: first and foremost, its name.
- e3bc54b2 5y agoLike how Apple continued the NS* trend for decades?
- j1elo 5y agoYes, something like that. But I never developed specifically for Apple platforms... what is (or was) the meaning behind "NS"?
- bschwindHN 5y agoNeXTSTEP, I believe. https://en.m.wikipedia.org/wiki/NeXTSTEP https://en.m.wikipedia.org/wiki/NeXTSTEP