It's a struggle even finding the manual these days if you don't already know where it is / what it's called. I was searching about an issue with my car recently and like 90% of the results are generic AI-generated "How to fix ______" with no actual information specific to the car I'm searching for.
"High Quality Audio" in terms of the sample rate and bit depth, but considering the quality of most of these DAC/ADCs you get integrated in cables like this, I somehow doubt the data rate is actually the limiting factor on quality.
Personally I can't tell the difference between 192kHz and 96kHz samples rates, or 16bit and 24 bit either (maybe a young kid with perfect ears could, but they'll probably also notice background noise due to most of these using unfiltered USB power). The dongle manufacturers seem to care more about the marketing value of bigger numbers than actual usability.
Well considering almost every time I reboot it seems to do a windows update, those optimizations are probably running every time anyway. It's almost fair.
That's Article 51, not 5. If you read the very first thing from the link:
Article 5 of the North Atlantic Treaty states that an armed attack against one NATO member shall be considered an attack against all members, and triggers an obligation for each member to come to its assistance.
Are we looking at the same image? I can't even tell the brand of the drives, let alone the model or specs. One of them might be an HGST drive? It's too pixelated/JPEGd to tell.
I've already been discussing this. Maybe read the rest of the thread.
Also the case in the standard library
I think you're missing the point of why. I built this to be a nearly drop in replacement for the standard string. If this wasn't the case it would need to do even more processing and work to pass the strings to anything.
discontinued because it was against the standard.
Standards don't matter for an internal type that's not exposed to public APIs. I'm not trying to be exactly compatible with everything under the sun. There's no undefined behavior here so it's fine
I had blanked this from my memory, but my very first programming job was to reimplement some FoxPro code in... Visual Basic.
FoxPro is so strange to work in. It's like programming in SQL, and the codebase I was in had global variables everywhere.
I don't use 256 bytes everywhere. I use a mix of 64, 128, and 256 byte strings depending on the specific use case.In a hot path, having the data inline is much more important than saving a few hundred bytes. Cache efficiency plus eliminating heap allocations has huge performance benefits in a game engine that's running frames as fast as possible.
22 characters is significantly less useful than 255 characters. I use this for resource name keys, asset file paths, and a few other scenarios. The max size is configurable, so I know that nothing I am going to store is ever going to require heap allocations (really bad to be doing every frame in a game engine).
I developed this specifically after benchmarking a simpler version and noticed a significant amount of time being spent in strlen(), and it had real benefits in my case.Admittedly just storing a struct with a static buffer and separate size would have worked pretty much the same and eliminated the 255 char limitation, but it was fun to build.
One cool trick that can be used with circular buffers is to use memory mapping to map the same block of memory to 2 consecutive virtual address blocks. That way you can read the entire contents of the buffer as if it was just a regular linear buffer with an offset.
I came up with a kind of clever data type for storing short strings in a fixed size struct so they can be stored on the stack or inline without any allocations.It's always null-terminated so it can be passed directly as a C-style string, but it also stores the string length without using any additional data (Getting the length would normally have to iterate to find the end).The trick is to store the number of unused bytes in the last character of the buffer. When the string is full, there are 0 unused bytes and the size byte overlaps the null terminator.(Only works for strings < 256 chars excluding null byte)
Edit: Since a couple people don't seem to understand the performance impact of this vs regular std::string, here's a demo:
https://godbolt.org/z/34j7obnbs
This generates 10000 strings like "Hello, World! 00001" via concatenation. The effect is huge in debug mode, but still has performance benefits with optimizations turned on:
With -O3 optimization
std::string: 0.949216ms
char[256] with strlen: 0.88104ms
char[256] without strlen: 0.684734ms
With no optimization:
std::string: 3.5501ms
char[256] with strlen: 0.885888ms
char[256] without strlen: 0.687733ms
(You may need to run it a few times to get sample numbers due to random server load on godbolt)
Changing the buffer size to 32 bytes has a negligible performance improvement over 256 bytes in this case, but might be slightly faster due to the whole string fitting in a cache line.
It's not actually the transistors that break down in flash memory. Flash memory works by storing charges in what is effectively a grid of capacitors, and in order for the data to remain stored, the insulating oxide layers in the cells need to be preserved. Every time a cell gets written, a charge is forced through the insulation with high voltage, and this degrades the insulation. A single flash cell might only have a few 1000 writes before this insulation goes bad and it no longer holds data. Modern SSDs have wear levelling techniques to make the drive as a whole last longer.
Transistors on the other hand don't have any inherent degradation that I'm aware of other than external factors like corrosion. The first thing that's likely to die on a GPU is the electrolytic capacitors in the power filtering electronics, which have fluid in them that dries out over many years.
This guy should be smart enough to realize he's complaining about not getting free storage from Google. You can't just run a business off other people's infrastructure and expect it to work out without any business agreement or contract. Google Workplace is a thing, and it sounds like this guy is just cheap if he won't pay for either it or his own harddrives.
I still have gmail polling my old hotmail//live addresses, and it's been that way since the day I signed up. Back when the slogan was still "Don't be evil"
It's a struggle even finding the manual these days if you don't already know where it is / what it's called. I was searching about an issue with my car recently and like 90% of the results are generic AI-generated "How to fix ______" with no actual information specific to the car I'm searching for.