|
Any preferences?
Keep it running?
Stop for a couple of days and restart next Tuesday?
Stop for a several days and restart next Month?
I leave it entirely in your hands: the option with the most votes (that isn't physically impossible or against any laws, natural or legal) will probably get it, but I'm easy any way.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
I would say a good Christmas/New Year break.
A week off. [No CCC from 25th Dec 20 to 3rd Jan 21]
|
|
|
|
|
I haven't been putting much effort into solving them for the past few weeks, so my opinion probably shouldn't factor in to it too much, but I will cast my vote onto the "After tomorrow, put a break on them until the new year" pile.
|
|
|
|
|
Now that the days are short, it's usually all over before I even get up!
|
|
|
|
|
I recently posted an article on efficient JSON processing and I have over 600 views and no downloads.
Writing this article took more effort than most of the articles I've posted here. I think it's too long though. 
I guess maybe if it takes that much to explain something it's too difficult to use. 
I may write a code generator to generate the C++ code from JSONPath queries that will use it for you.
Real programmers use butterflies
|
|
|
|
|
A given article is as long as it's gotta be. Don't shorten it, but maybe create a section at the top that gives an abbreviate explanation of what the code does, and then a (much) more detailed explanation for people that don't have ADD and want to know the innermost workings. That will appease both camps.
As far as downloads, i wouldn't worry about it. You did your job and put the code out there. When people need it, they'll download it. At just 600 views, i think it's a little early to be concerned. I posted an article last week and didn't get a download until it got over 900 views.
I've found that highly technical or extremely detailed articles are not appreciated for their content, and this is reflected by the dearth of articles that are submitted that are only a couple hundred words over the last have dozen years. I've actually had artcles down-voted because someone thinks they're too long.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Hi you've written a couple on JSON which one do you mean ?
"I didn't mention the bats - he'd see them soon enough" - Hunter S Thompson - RIP
|
|
|
|
|
|
Thanks for that
"I didn't mention the bats - he'd see them soon enough" - Hunter S Thompson - RIP
|
|
|
|
|
Let me know what you think if/when you get a chance to read it. It's an entirely different way of processing JSON and I'm not sure how understandable it is so I'd love feedback!
If it's effective enough I may port it back to C# (my original came from a port of a C# one I wrote and then evolved it several times in C++) but you'll lose the RAM efficiency. It's still good for selectively bulk uploading in that case though. The thing chews through JSON like nobody's business.
The main downside is at the moment it's ASCII only but I'm working on utf8 encoded unicode support right now.
Real programmers use butterflies
|
|
|
|
|
I look forward to reading it - it will give something to focus on as I'm in the UK south of London and we're locked down big time - thanks for replying
"I didn't mention the bats - he'd see them soon enough" - Hunter S Thompson - RIP
|
|
|
|
|
We're locked down here too. That's part of why I wrote it. Be well. 
Real programmers use butterflies
|
|
|
|
|
honey the codewitch wrote: I have over 600 views and no downloads.
I am going to guess that the majority of us in the industry do not have a pressing need for a new json processor/parser.
give it time and you may have a few downloads from people who need an efficient json processor.
|
|
|
|
|
I thought people wouldn't have a pressing need for my IoT stuff either but they snapped it up.
This is actually a library targeting IoT devices like Arduinos (even 8 bit) but it scales to at least 32 bit on PC and server where it can be used to do bulk uploading, which it does very well - better than most engines.
So it's niche, but it's quite useful, even if there are existing ones out there. Particularly for IoT where mostly there's just ArduinoJson and other in-memory models - which aren't so great when you have 8kB of RAM like on a lil ATmega2560
Real programmers use butterflies
|
|
|
|
|
Arduino? popular. I do Arduino as a hobby. a lot of people do.
json processor - not popular. doesn't mean that it is not important, just not popular as IoT at the moment.
Edit: since you said it is "niche", then I double down on "give it time".
|
|
|
|
|
Fair enough, although my previous offering was similar but less efficient, forcing me to rethink how queries worked, redesign, and rewrite to make something better. That's the main difference between now and a few days ago with my last article. Oh well, maybe I've just approached article saturation point WRT to JSON, but what I've been doing lately is heavy research into better ways to do it which leads me to produce a lot of CP content.
Real programmers use butterflies
|
|
|
|
|
honey the codewitch wrote: maybe I've just approached article saturation point
Take a break. Relax. Enjoy the Holidays!!
Your work has merit, purpose, and place. Just give it time, and don't fret about it so much.
Just my opinion.
Cheers.
|
|
|
|
|
I especially like to occupy myself during the holidays because at least to me it mainly feels like mass retail therapy and I find that depressing. I'm visiting my sister after the holidays (due to the 'rona) so I can dump toys on the nephew - I'm guilty of falling into the retail trap too but i do it for the kids. Anyway I'll enjoy it then.
Real programmers use butterflies
|
|
|
|
|
If you want accurate download numbers then you might want to remove the github link. I pulled your source code off github six hours ago when I commented on your last thread.
Best Wishes,
-David Delaune
|
|
|
|
|
That's true. I like linking to my github if I release something while I'm still working on it.
What did you think of the article? Was it digestible, understandable?
I'd love your thoughts on it because it's so different than how traditional JSON processors work.
Real programmers use butterflies
|
|
|
|
|
honey the codewitch wrote: What did you think of the article? Was it digestible, understandable?
It reads like a manual in the beginning... which is what I would be looking for if I were using your code. Beginning with 'Coding this Mess' is where I was able to immerse into your development story.
honey the codewitch wrote: I'd love your thoughts on it because it's so different than how traditional JSON processors work.
I don't have an opinion on the code. I would need to do a full review.
I would like to add that the fastest known JSON parser in the world right now is simdjson[^]. But it requires the Intel AVX512[^] instructions.
Best Wishes,
-David Delaune
|
|
|
|
|
Yeah I don't use specialized instructions because this isn't about bit twiddling, but coming up with an algorithmic improvement over traditional JSON processing.
The other thing about my library is its priority is efficient RAM use. It's second priority is raw speed.
Although, I'd still stack it up against most if not any JSON processor in terms of speed because it does partial parsing. Also in terms of when it does parse, my library's primary speed advantage is it only reads a string once, not twice like most libraries do - once to get it off the "disk" (input source), and then again to compare it. It does all string comparisons in a streaming fashion right off the "disk" (input source) like that.
I'd be curious about simdjson because it's the only one I've found that might be competitive, but my problem with it is RAM use. It's demand/lazy parsed, but it still parses into memory. I don't. The only time my values get into memory is if they're specifically requested from a query. Everything else is streamed.
It's a fully validating parser. Mine isn't, typically, although you *can* use it that way - it's just slower. simdjson probably tans its hide when it comes to validated parsing because I did nothing really to optimize it.
Real programmers use butterflies
modified 23-Dec-20 9:56am.
|
|
|
|
|
I haven't read your article, but this is what I aim for:
- what the code does
- the rationale behind its design
- overview of the classes involved
I avoid details of how the code works unless there are key points. Code pasted into the article may have details in its comments, but that's more accidental. I leave the details to the comments in the download, figuring that anyone who's really interested will look at the code itself. This limits the articles to a reasonable size even though many of them cover somewhat broad topics.
|
|
|
|
|
I try to cover the first two by the Introduction and then I flesh it out while adding the 3rd in "Conceptualizing this Mess" (my typical Background section)
In this case I went with a slightly different format than my usual and I also detailed major methods under different sections like "Navigation" and "In-Memory Trees"
I think that may put people off though as it's a lot to scroll through before the "Coding this Mess" section where I take the abstract stuff and make it concrete.
For me I like to put comments in the code in my articles because it's easier to "fisk" my own code line by line with comments, rather than directing the reader to the comments in the paragraph below. There I like to summarize what I did in the code. I find people seem to receive that well. But YMMV.
Real programmers use butterflies
|
|
|
|
|
To be honest... I haven't read all of your items, but the ones I read I liked it.
I don't really care about the length of an article, as long as the text is not unnecessarily repeating things and is not telling bullsh1t.
In the written communication we miss every every other non-verbal aspect that is so important when talking face to face (or video conference these days). So if the text is telling a story, explaining things in a proper way and making it a light read... I will never complain about the length.
About the usability and usefulness... I don't think I will use many of the things you post about, but it doesn't mean I don't appretiate your work.
Just an advice... although I know it is important for you, try to be a bit more careless about the stats of your posts. You life will be more relaxed and you won't stress yourself or get disappointed before needed so fast.
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
