[depricated]

been using .NET Core 3.1 for 6 months.
Stuck with the NewtonsoftJson library because .NET has never had JSON support.
Discovered the brand shiny new System.Text.Json namespace.

siiigh

Oh well

[NeoTifa]

Been grinding my teeth in my sleep for the last few weeks, and I guess my cheeks have finally become unfortunate collateral damage, as I just discovered a few blood blisters on the insides on my cheeks. Gross. Also broken record, feel like crap again, so much so I was up all night getting sick, and now nausea is kicking in again a lil bit? I blame Panera bread. My appointment to figure out why keeps getting cancelled and rescheduled by the doctor. >=[ Got a new doc.

[jon.kiparsky]

I'm at a virtual demo day for the bootcamp I mentor at. Always a good day, seeing folks show off the stuff they've been working on.

[h4nnib4l]

depricated, on 15 October 2020 - 12:21 PM, said:

been using .NET Core 3.1 for 6 months.
Stuck with the NewtonsoftJson library because .NET has never had JSON support.
Discovered the brand shiny new System.Text.Json namespace.

siiigh

Oh well

Watch out for System.Text.Json - there's some collection serialization functionality that they haven't implemented yet. It's MS's path forward as far as removing the Newtonsoft dependency from .NET Core as whole - among other things, to alleviate dependency version clashes when using other .NET libraries (like Functions) that do still take a dependency on Json.NET - but it's not quite there. From what we found, it sounds like the intent is to have those issues resolved by the release of .NET 5, but for now if you start getting some weird serialization issues using System.Text.Json, that's potentially the cause and the easiest solution is to just switch back for now.

If I can manage to dig the docs/articles we found out of my history or my colleague's, I'll add them to the post.

EDIT: release of .NET 5. I hear .NET has been out for a while...

This post has been edited by h4nnib4l: 16 October 2020 - 05:57 AM

[depricated]

Ah, that's still pretty cool. I decided that I've got Newtonsoft too deeply embedded to cut it out at this stage of the project. It would take a not insignificant amount of time to refactor. I actually found a great use for it though: Newtonsoft can't serialize/deserialize byte arrays - what comes out on the other end isn't a valid or correct byte array. I was having to encode/decode them to/from strings previously. But System.Text.Json handles it pretty smoothly - possibly doing exactly that under the hood.

[TechnoBear]

I had an interview once where they wanted me to pull data from a JSON object and manipulate it, they gave me 10 minutes.

So, I pull JSON.NET from NuGet (this was before core was even a thing), build my object, deserialize the JSON in to the object, do what they want me to do, and slide the computer over to them with time to spare.

After looking at my code the conversation goes like so:

Them: Why did you use Json.Net?
Me: Because it is a quick way to pull data from Json in to an object
Them: Why didn't you just map the Json yourself?
Me: Because you gave me 10 minutes
Them: We wanted you to do it yourself
Me: Why when tools exist to speed it up?
Them: Because how would you handle it if you had to do this with limited time in the real world?
Me: Exactly how I just did it now
Them: We'll be in touch.

I don't know if it is obvious, but that made me a little salty and I have stayed mad lol

[h4nnib4l]

You can at least feel a bit vindicated that MS engineering made the exact same decision from .NET Core 1.0 until 3.0, and that plenty of their internal teams are still doing the same.

[TechnoBear]

h4nnib4l, on 16 October 2020 - 07:46 AM, said:

You can at least feel a bit vindicated that MS engineering made the exact same decision from .NET Core 1.0 until 3.0, and that plenty of their internal teams are still doing the same.

That is why I am still mad about it, because I did exactly what somebody in my position should do - especially with a particularly tight deadline- and apparently that was the wrong course of action.

[depricated]

So consider that they're the ones who failed the interview. You don't want to work for chudsmackers like that. They prefer inefficiency - consider how that mentality cascades through the rest of their business. If one was to be your boss, consider how that mentality affects their team and would have affected your job daily if you did accept an offer.

[modi123_1]

Yesterday I took a realization that it's been over seven years since I've upgraded my cpu and motherboard.. and 11 years since I've upgraded my case.. so what I thought was a quick pop in to price something out, turned into two-plus hour zone out comparing things.

At best found 850 for an intel 10th gen. Now I hear the ol' AMDs has been doing something, and I haven't had an AMD chip in at least three or four rebuild cycles.. I guess I'll spend tonight looking into those comparisons.

[jon.kiparsky]

TechnoBear, on 16 October 2020 - 07:56 AM, said:

Them: Because how would you handle it if you had to do this with limited time in the real world?
Me: Exactly how I just did it now

Sounds like someone who's not altogether brilliant when it comes to communication, and also someone who is weirdly interested in fantastically uninteresting things, like your ability to parse JSON at high speed.

Quote

Them: We'll be in touch.

Correct answer: I won't.

[Skydiver]

As I recall, early iterations of the JsonSerializer could only deserialize things correctly if the names of the objects were in sorted order. The issue wasn't uncovered because the test would first serialize some object, be and the details would write out the fields in sorted order, so the deserialize would always succeed. I vaguely recall a question here in DIC where someone asked why they could not deserialize something that was coming from some web API using the JsonSerializer.

[NeoTifa]

Lead and other developer are trying to argue with me about what the domain objects refer to in an api model and I already have a headache. They're from a heavy database background.

[Skydiver]

Makes me think of baklava code.

[NeoTifa]

Nah it's just a simple Spring Boot app. Pretty standard, but these people don't understand Java and its paradigms.