4 ms·

This doesn't do a terribly good job at the moment of explaining why I might want to investigate it further or consider using it. What are the advantages it offe

This doesn't do a terribly good job at the moment of explaining why I might want to investigate it further or consider using it. What are the advantages it offers?

corysama 8y ago
Agreed. A huge amount of text goes into explaining how much work it was to make and tons about what it's not. But, I'm having a hard time finding explanation of what it is.
- CyberDildonics 8y ago
  He has done the same thing on the cpp subreddit with regards to his 'object request broker'. Lots and lots of text talking about how many lines it is and what it isn't, while never giving an example of a problem that it solves that couldn't be done easier with other simpler and more established libraries.
  - corysama 8y ago
    It's a pretty common problem when explaining tech. You (non-specific "you") have spent so much time thinking about a topic that all knowledge about it is assumed. You feel the need to defend your position from misunderstanding and misrepresentation. Contrasting it against other tech is of great interest to you. Meanwhile, I have no idea what you are talking about because you haven't actually explained what it is. But, explaining this big, complicated thing you've been working on forever is hard and could potentially expose you to criticism. Much more fun to continue bragging about how it's different/better than other people's stuff.
    - DeanRoddey 8y ago
      This is the kind of positive response that makes me glad I did this. There's LOTS of descriptions out there of what ORBs are. I have a good video about how it works and what it does. I can't put ten books worth of explanation in a read me.
      - corysama 8y ago
        I don't need a book. I just need something. The word "ORB" is not even present in the GitHub readme. You don't link your blog or your videos. You know that the explanations are sitting there waiting for me. I don't and you didn't tell me. Here's a positive suggestion: In the GitHub readme, lead with the second paragraph. The first paragraph is not important to anyone but you. Having it as the project's intro makes you come off as a self-important wank. Cut the first paragraph and the first sentence of the second out completely. Cut the third and forth paragraphs as well. Keep the fifth "Because it doesn't use the STL" paragraph, then skip straight to the Goals section. Rewrite it to explain itself in concrete, positive assertions instead of what it's not and what it's anti. Portability should come next. Then Gotchas. But, Modern vs. Classical is mostly a rant that doesn't help me understand your project. You've already heard more than enough about the license :p You've made something really cool. You have every right to be proud of it. But, other people don't know how cool it is and they never will if you don't improve how you communicate with them. It's not just a matter of stating the facts. It's understanding their point of view and tailoring your communication around that. You are a busy person. You know that there's more stuff being published every day than you could possibly even glance over. And, you know that most of that stuff is useless crap created by self-important wanks. So, what would it take to get you to invest the time to understand some random wank's project? If you are like most people, you aren't going to sit down with a cup of tea and read the backstory of some random project like it's a New Yorker article. You are going to read the first paragraph, then briefly skip around the rest of the doc before deciding to move on or not. It's the only efficient way to filter through the fire hose of crap. When writing your description, you need to respect the reader's time and ignorance. They don't know the huge amount that you know. They especially don't know why this project is worth their attention. Your job is to sell them on your project by being as clear, concrete, brief and genuine as possible.
        DeanCIDLib 8y ago
        I'll take another shot at it. But on the ORB thing, wires got crossed there. There's no way I'd mention the ORB in the read me. That's very important but small piece of the overall thing. He was referring to some of the videos on my personal Youtube channel where I talk about some of the technologies I've created as part of this project. Some of them are related to the ORB. Obviously, if you have never heard of an ORB before it might take a bit of effort to understand. But I can't really explain in-depth the foundations of technology concepts in a video. I can only give the basics and demonstrate how I've implemented that technology. Beyond that, it would require a bit of study on the reader's part, as it does for pretty much all libraries of this type. Qt's 3D graphics docs probably don't include a fundamental tutorial on modern graphics architectures, right?

This doesn't do a terribly good job at the moment of explaining why I might want to investigate it further or consider using it. What are the advantages it offers?

corysama 8y ago

Agreed. A huge amount of text goes into explaining how much work it was to make and tons about what it's not. But, I'm having a hard time finding explanation of what it is.

CyberDildonics 8y ago
He has done the same thing on the cpp subreddit with regards to his 'object request broker'. Lots and lots of text talking about how many lines it is and what it isn't, while never giving an example of a problem that it solves that couldn't be done easier with other simpler and more established libraries.
- corysama 8y ago
  It's a pretty common problem when explaining tech. You (non-specific "you") have spent so much time thinking about a topic that all knowledge about it is assumed. You feel the need to defend your position from misunderstanding and misrepresentation. Contrasting it against other tech is of great interest to you. Meanwhile, I have no idea what you are talking about because you haven't actually explained what it is. But, explaining this big, complicated thing you've been working on forever is hard and could potentially expose you to criticism. Much more fun to continue bragging about how it's different/better than other people's stuff.
  - DeanRoddey 8y ago
    This is the kind of positive response that makes me glad I did this. There's LOTS of descriptions out there of what ORBs are. I have a good video about how it works and what it does. I can't put ten books worth of explanation in a read me.
    - corysama 8y ago
      I don't need a book. I just need something. The word "ORB" is not even present in the GitHub readme. You don't link your blog or your videos. You know that the explanations are sitting there waiting for me. I don't and you didn't tell me. Here's a positive suggestion: In the GitHub readme, lead with the second paragraph. The first paragraph is not important to anyone but you. Having it as the project's intro makes you come off as a self-important wank. Cut the first paragraph and the first sentence of the second out completely. Cut the third and forth paragraphs as well. Keep the fifth "Because it doesn't use the STL" paragraph, then skip straight to the Goals section. Rewrite it to explain itself in concrete, positive assertions instead of what it's not and what it's anti. Portability should come next. Then Gotchas. But, Modern vs. Classical is mostly a rant that doesn't help me understand your project. You've already heard more than enough about the license :p You've made something really cool. You have every right to be proud of it. But, other people don't know how cool it is and they never will if you don't improve how you communicate with them. It's not just a matter of stating the facts. It's understanding their point of view and tailoring your communication around that. You are a busy person. You know that there's more stuff being published every day than you could possibly even glance over. And, you know that most of that stuff is useless crap created by self-important wanks. So, what would it take to get you to invest the time to understand some random wank's project? If you are like most people, you aren't going to sit down with a cup of tea and read the backstory of some random project like it's a New Yorker article. You are going to read the first paragraph, then briefly skip around the rest of the doc before deciding to move on or not. It's the only efficient way to filter through the fire hose of crap. When writing your description, you need to respect the reader's time and ignorance. They don't know the huge amount that you know. They especially don't know why this project is worth their attention. Your job is to sell them on your project by being as clear, concrete, brief and genuine as possible.
      - DeanCIDLib 8y ago
        I'll take another shot at it. But on the ORB thing, wires got crossed there. There's no way I'd mention the ORB in the read me. That's very important but small piece of the overall thing. He was referring to some of the videos on my personal Youtube channel where I talk about some of the technologies I've created as part of this project. Some of them are related to the ORB. Obviously, if you have never heard of an ORB before it might take a bit of effort to understand. But I can't really explain in-depth the foundations of technology concepts in a video. I can only give the basics and demonstrate how I've implemented that technology. Beyond that, it would require a bit of study on the reader's part, as it does for pretty much all libraries of this type. Qt's 3D graphics docs probably don't include a fundamental tutorial on modern graphics architectures, right?