Correct, JSON can handle any precision, because it’s just dumped as a string anyway, just not enclosed in the "". However, as you mentioned, as soon as it comes through the parser it’ll put it into an underlying float value. In C# I create a save high precision attribute that will take the value and put it directly into a decimal. In JS I’m sure there’s some way to do that, but that parser is way less extensible compared to C#. However, this also all assumes you know the client will parse it correctly, overriding the default behavior. Safest is to just send it as a string, and then create your parsers to automatically send to and from strings

Until you get to multi currency, which is why I don’t support using ints or longs, and strings are still the only way. There are currencies that have no precision, and others that have 3 or more digits of precision - and then you’re looking at doing calculations each time. Strings are the safest way to make sure you’re representing exactly what you want to when sending data over the wire or persisting

The fun differences between the perfect world of theoretical and the realistic. Everyone thinks of computers as perfect - but it’s not until you’re asked to solve “How do you store decimals using only 0s and 1s?” does it start to click. Not as easy. It’s why I’m hesitant to hire bootcampers into my roles. Bootcamps are great, and they get more people coding, but you don’t learn that theory behind the scenes - you don’t really know what the computer and operating systems are doing. For 90% of the time it doesn’t matter, it’s abstracted away - but that last 10% man, that can really fuck up an entire system.

All of us fintech devs however, know the true horrors. Make everything a string, lest ye end up in precision hell

bingo. Timezones became easier when I learned that all apps and databases should have all times be in UTC. Let the UI do it’s thing and accept local time and convert it, and vis versa.

This is all over a GitHub stars badge? Developers probably want to encourage people to star it. It’s a huge stretch to say they’re trying to track people

Yeah it’s pricey, very pricey, but the risks are just too high for a home not to be properly grounded anymore. Homeowners have had 50 years to do it, it’s time to get it done.

I know that the answer is yes

I mean, there you go, and all of the above. I’d add in a pretty large fire risk too. I hear my battery backups kick in regularly, and we’re talking about enough power to equal a large appliance (at least in my case). It’s 100% worth it to move them to a grounded outlet.

They are, but I’m still disheartened. Googlers tried to take a stand last year and they immediately paid them all off

That’s great! Unfortunately for every one of them there’s 4x more who gladly would

Nothing proves a backup like forcing yourself to simulate a recovery! I like to make one setting change, then make a backup, and then delete everything and try to rebuild it from scratch to see if I can do it and prove the setting change is still there

Exactly right there with the not worrying. Getting started can be brutal. I always recommend people start without worrying about it, be okay with the idea that you’re going to lose everything.

When you start really understanding how the tech works, then start playing with backups and how to recover. By that time you’ve probably set up enough that you are ready for a solution that doesn’t require setting everything up again. When you’re starting though? Getting it up and running is enough

I love that you reversed it, when it should be “how terrible do Americans have it where we have to commute so far just to get to work”

Red 8TB+ are CMR, OP said they’re using 14TB drives, they’re fine

WD Red has always been my go-to, and in the last 8 years of homelabbing I haven’t had a single one fail. Blues and Greens are not build for NAS operations, and you’ll see them fail. Toshibas I haven’t had a single one make it past a year, except for their gaming drives.

If you want the shortcut, the WD Elements usually go on sale at Best Buy regularly, and they’re always a WD Red or White, which will also work. All of my drives have been one of those. You just shuck the internal drive out of the enclosure

Unfortunately both 0.19.4 and 0.19.5 are hanging for me when spinning up my containers, getting some weird issue with inbox timeouts. Opened a bug here

Big companies will constantly work against open standards.

ah your instance has debugging enabled. Message your instance admins to remove it.

I’m sure they will be slightly inconvenienced for the duration of a single meeting

I do something similar to op, however, running llms is what finally convinced me to switch over to kubernetes for these exact reasons, I needed the ability to have gpus running on separate nodes that then I could toggle on or off. Power concerns here are real, the only real solution is to separate your storage and your compute nodes.

What OP is suggesting is not only not going to work, and cause damage probably to the motherboard and gpus, but I would assume is also a pretty large fire hazard. One GPU takes in an insane amount of power, two gpus is not something to sneeze at. It’s worth the investment of getting a very good power supply and not cheaping out on any components.