The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
I'm just guessing, but my guesses tend to be far more accurate than any politician's facts. It takes about 12.5 days for me to drink my own body weight of coffee, but I'm still gaining weight, so that number will eventually drop a bit.
That's cheap! It's good value at the £30 I paid - very, very nice piece of kit. Rare to find something that does what it says it does, right out of the box and with the lack of hassle and trouble it gives you.
The only thing I changed was to get a 20cm cable Ebay £1.52[^] as the original was too long and untidy.
Get LocalCast[^] - Android, but I understand there is an iOS version - and you are sorted.
You looking for sympathy? You'll find it in the dictionary, between sympathomimetic and sympatric (Page 1788, if it helps)
It should begin with an introduction to beginners and should also cover from basics to advanced level. Sure, I would be interested in learning the inner workings, it's architecture etc.
I always expect an article should present in a most simple, fluid manner and should be specific in explaining the topics and cover from how to use to how it's being implemented. Rather than being a single huge article, I prefer reading it in parts.
Here are few things you have to consider before you publish one.
1. Please remove the section above the download code at the beginning. That's optional and I hardly see those in articles. 2. Article requires code formatting. 3. I hope this is a beginners level article. Could be done better with Introduction etc. in terms of quality content. 4. You can name the Scenario within the "Using Code" section. That's the general CodeProject Guideline. 5. Could you explain the real world scenario were exactly SBWQL would be helpful. I see several hardcoded bit wise things but I'm getting little confused how to use these things without hardcoding. 6. How about the performance compared to the existing LINQ Query. 7. Don't mistake me, I feel this approach makes the code hard to read though it might simplify things.
With this you come to confirm the low acceptance of the new idea, as occurred in a previous post 'Short LINQ syntax', where I found professionals with much less ethics which you presented.
This fact makes me believe that I am still a simple developer who found an interesting way to solve everyday problems with little writing, and it is still not to be disclosed to any developer community.
Please believe, Your feedback has been positive in some way.
I live in Brazil where things are not as easy as in the first world countries, work intensively with technology 15 years.
But since my start on this journey, I was never very adept at discussions in Forums, Communities, etc.
Being a person with little patience to read responses that have nothing to do with the proposed content, disputes ego, etc.
By setting this idea, in the excitement of finding that this would be well, i'm encouraged me to publish it.
As I do not have much time to improve content for this idea is better understood, to be involved in my day job plus freelances and failing to give proper attention to my family, I end up not insist more on this idea.
I'm pulling me to meet a freelancer working this weekend.
I appreciate your patience. You have enough ideas and coded some innovative things for which the opensource communities always feel proud about it. I suggest you could have directly published an article and would anyways received proper feedbacks. Based upon that you can decide whether to improve and extend further.