Tumgik
#json
kushblazer666 · 2 months
Text
Tumblr media
2K notes · View notes
radiation · 7 months
Text
Tumblr media
4K notes · View notes
gougerre · 8 months
Text
Tumblr media
456 notes · View notes
snarp · 9 months
Text
Test post: [ { "json": " json " } ]
53 notes · View notes
bryce-bucher · 1 year
Text
Tumblr media Tumblr media Tumblr media Tumblr media Tumblr media Tumblr media Tumblr media Tumblr media Tumblr media Tumblr media
Been dealing with some medical stuff, so I've been "taking a break" this week by learning how to model in the style of ps1-era FMVs. This is a WIP model of the protagonist of my game J(a)SON: The Dog Living Inside a Mistake. It has taken me a few days to chip away at the face, and the latest thing I've gotten done is the hair. Idk what I'm gonna do to get the whole ass body done, but I'm happy with how it's come out so far. I've never hard modeled a face like this, and I'm kinda surprised how fun and not a complete nightmare it is. This has also been a great way for me to nail down the design of the protagonist. Since it's a first person game and the only art of the character I've made before this is the little logo seen above, I hadn't really nailed down various aspects of the design. Mostly color stuff. In the middle of doing this, I realized it'd be best if the glasses were dark orange and the lips were black. Can't wait to get this model done and make some renders with it. This character currently doesn't have a name (they might never have one), but they are a goth, enby hacker. You can read more about that in my post(s) about the development of the game if u want idk I'm not ur dad.
92 notes · View notes
nerdymemes · 3 months
Text
Tumblr media
7 notes · View notes
iheartvelma · 2 months
Text
I applied to ten jobs and it's EXHAUSTING
Tumblr media
...mostly because of the 30 minutes I have to spend each time cleaning up what their "smart" CV parsers get wrong.
THEY grab random text from grouped paragraphs and insert them into the wrong fields CONSTANTLY!!!!
I've now reformatted my CV into a bare-bones plaintext document, but even so, it'll be interesting to see what the next ones get wrong.
If we're going to anoint LinkedIn as our State-Sanctioned Monopoly for Job Searches, can we just settle on a single JSON format for CV exchange between it and applicant tracking systems (ATSes?)
You know, make it part of the ADA or the Paperwork Reduction Act etc?
Like, if you want to add custom fields after that, fine, but don't make me retype my entire CV. I formatted it properly, if your machine can't read, that's your problem.
I can't understand why Microsoft (LinkedIn's parent company) can't fix this. Like, they're the lead investor in OpenAI, couldn't they at least set it to work parsing CVs so it can get some pattern recognition going?
4 notes · View notes
brightgreendandelions · 10 months
Text
You've heard of LGBT representation
now get ready for....... JSON representation!!
i've made a little change to my tumblr theme. for pride month :)
if you also want JSON to be represented on you blog, read the code after the break.
first you have to insert this
{block:PermalinkPage} <details> <summary>JSON representation✨</summary> <code class="brightgreendandelions-npf">{NPF}</code> </details> {/block:PermalinkPage}
after the "{/block:Answer}" on line 757 in the default theme
and then add this custom css (there's a spatial little box for custom css)
.date-notes .post-date.post-date { display: inline-block !important; }
details { padding: 0 20px; }
summary { display: list-item; }
15 notes · View notes
xpc-web-dev · 1 year
Text
100 days of code: Day 2 and Day 3
(23/02/2023)
Day 2
Tumblr media
Yesterday I continued my studies through MDN and tested this example.
Of course I didn't understand almost anything, but I found it interesting. But after that I went to see the Odin one and I found it more accepted to first do its fundamentals (and it references mdn articles) and then see where I follow.
Day 3
Tumblr media
Today I finished odin fundamentals 1 and these were the assignments
Today was a tiring day and I really didn't want to study.
BUT besides being obsessed with not breaking the sequence of green squares on my github , I also remembered that I need to do what has to be done even when I'm tired. So I studied this and other tasks.
And you, how are your studies?
I wish you a great night/day/Friday, take care of your mental health, don't be stupid with people on the internet just because there's a screen protecting you, and drink water.
27 notes · View notes
kawaoneechan · 1 month
Text
Yesterday I replaced the RapidJSON in Project Special K with the SimpleJSON I already had in another C++ toy project, after discovering a somewhat simpler variation on JSON patch formats (RFC 7396 JSON Merge Patch opposed to 6902 JSON Patch) but found that the way RapidJSON worked made it next to impossible for me to implement.
I got walled by adding/replacing into arrays and 7396 doesn't support such an operation to begin with so that would simplify the job as well as the patch files.
Now, RFC 8396 does not require 6901 JSON Pointer, unlike 6902, support for which came free with RapidJSON. But why did I use RapidJSON in the first place? Because glTF importing requires JSON and lazy-gltf2 uses RapidJSON specifically.
I could use assimp instead I guess but that seems way overkill?
So I spent last night adapting everything to use SimpleJSON, added RFC 7396 support (though "remove if value is null" is missing right now) and got back to the point where I left off before.
Now I have some choices to consider.
Rework lazy-gltf2 to use SimpleJSON instead of RapidJSON. May find out there's no pointer support and lazy-gltf2 requires it.
Use assimp, end up with an external dependency that carries its own JSON parser but is also way too much for what I need.
Stop using C++, go back to C#, and find out that all the glTF importers available out there are all meant for VS2019 or later and won't compile on 2015, and/or use Newtonsoft JSON while I have a perfectly good library of my implementation right here with passable pointer and patch support.
Stop using C++, go back to C#, write my own glTF importer bound to my own JSON library.
Give the fuck up.
Sometimes I hate my special interests.
4 notes · View notes
eurritz · 16 days
Text
Tumblr media
I love to see JSON ads
3 notes · View notes
kushblazer666 · 1 year
Text
Tumblr media
8K notes · View notes
radiation · 10 months
Text
Tumblr media
8K notes · View notes
gougerre · 8 months
Text
Tumblr media
9 notes · View notes
snarp · 9 months
Text
Tumblr media Tumblr media Tumblr media Tumblr media Tumblr media Tumblr media Tumblr media
WHY
13 notes · View notes
vidadelafuerza · 1 month
Text
JavaScript Node.js PowerShell JSON Repeat
Lately, I've taken a lot of time to reacquaint myself with JavaScript usage in Node.js. Specifically, I'm learning all the basic things I enjoy doing in PowerShell: File manipulation (list, read, write) and data manipulation (parse, extract, interpret, summarize).
Specifically, my favorite thing is to see something of interest on a website and/or analyze a website's requests in the Network tab of DevTools (CTRL+SHIFT+I). It has to be something useful. Such things can be scraped for data I might want. The way I do that is in the Network tab of DevTools (Chrome, MS Edge). Looking at a request, I can right click and get the PowerShell (or other code) that would give me that exact same information in Windows Terminal. Then, I typically do an ad-hoc script to get what I want.
Current Web Scrape++ Project
The project that has my interest at the moment is one where I'm taking all the text of a copyrighted version of the Bible, then using DOM queries and JavaScript to get just the verse numbers and verse text per chapter from the HTML. It sounds as complicated as it is, but it's the kind of thing I do for fun.
Node.js comes into play when I want to loop through all the HTML I've pulled and sanitized. The sanitization wasn't easy. I kept only the HTML with actual Bible text - which reduced the HTML payload to less than 2% its original size. That part was in PowerShell and Visual Studio Code. But I digress.
Using the Console of DevTools, I already have the JavaScript I'll need to pull what I want from the HTML file data into an array of "verse" objects, which I can then easily translate to JSON and write out.
Next, my goal is to take the data, store it as JSON files, and then manipulate it with PowerShell. For instance, I wonder what it looks like if I replace the word "Lord" with "Earl" or "Duke". As silly as that sounds, that's the entire modus operandi for my project, which has been maybe as much as 6 to 8 hours. The rest probably won't take that long, but each step has to be pursued with the smallest steps I can think to make. (There's no use looping 1189 chapters / files of HTML text to get erroneous stuff, so I go small and then large.)
2 notes · View notes