FordGT90Concept
"I go fast!1!11!1!"
- Joined
- Oct 13, 2008
- Messages
- 26,259 (4.63/day)
- Location
- IA, USA
| System Name | BY-2021 |
|---|---|
| Processor | AMD Ryzen 7 5800X (65w eco profile) |
| Motherboard | MSI B550 Gaming Plus |
| Cooling | Scythe Mugen (rev 5) |
| Memory | 2 x Kingston HyperX DDR4-3200 32 GiB |
| Video Card(s) | AMD Radeon RX 7900 XT |
| Storage | Samsung 980 Pro, Seagate Exos X20 TB 7200 RPM |
| Display(s) | Nixeus NX-EDG274K (3840x2160@144 DP) + Samsung SyncMaster 906BW (1440x900@60 HDMI-DVI) |
| Case | Coolermaster HAF 932 w/ USB 3.0 5.25" bay + USB 3.2 (A+C) 3.5" bay |
| Audio Device(s) | Realtek ALC1150, Micca OriGen+ |
| Power Supply | Enermax Platimax 850w |
| Mouse | Nixeus REVEL-X |
| Keyboard | Tesoro Excalibur |
| Software | Windows 10 Home 64-bit |
| Benchmark Scores | Faster than the tortoise; slower than the hare. |
For those who haven't heard about it, here's the official site for it:
http://www.yaml.org/
Sure, it is a readable format but it is the worst format I've ever worked with in terms of coding for. I tried using other people's libraries (three of them I think) and was so confused, I trashed them. I tried coding my own, also resulted in confusion and trashing it. Finally, I decided the only way I can navigate the all important "spaces" (because they refuse to use tabs) was to use a tree so I could easily tell it to move between children and parents as it was parsing each line. That finally got the hierarchy mess sorted but then, to output the file back in YAML format, I had to write a wall of text because Trees aren't navigator friendly (have to open child after child after child and/or assign new objects to new objects to new objects). Not only that but in order to do the "name: value" at the end, I had to put in some shameful, unflexible wizardry to make it ignore outputting tabs (which breaks the format), not output colons, and ignore linebreaks. It's amazing it works at all.
For the love of the computing gods, use XML, INI, or some other decent scripting format than YAML. They may not be as human ledgible as YAML but editors are relatively easy to make which end up being infinitely better than text editing a YAML anyway.
JSON is better than YAML because it has brackets to tell when something starts and stops. YAML omits almost all of them.
http://www.yaml.org/
Sure, it is a readable format but it is the worst format I've ever worked with in terms of coding for. I tried using other people's libraries (three of them I think) and was so confused, I trashed them. I tried coding my own, also resulted in confusion and trashing it. Finally, I decided the only way I can navigate the all important "spaces" (because they refuse to use tabs) was to use a tree so I could easily tell it to move between children and parents as it was parsing each line. That finally got the hierarchy mess sorted but then, to output the file back in YAML format, I had to write a wall of text because Trees aren't navigator friendly (have to open child after child after child and/or assign new objects to new objects to new objects). Not only that but in order to do the "name: value" at the end, I had to put in some shameful, unflexible wizardry to make it ignore outputting tabs (which breaks the format), not output colons, and ignore linebreaks. It's amazing it works at all.
For the love of the computing gods, use XML, INI, or some other decent scripting format than YAML. They may not be as human ledgible as YAML but editors are relatively easy to make which end up being infinitely better than text editing a YAML anyway.
JSON is better than YAML because it has brackets to tell when something starts and stops. YAML omits almost all of them.
