Or, just don't use JSON for config files. There are plenty of human-friendly config file options, so there is no reason to frankenstein JSON in this way.
DX7s don't go for a high price. The market is flooded with them. If you pay more than $600, you paid too much. You can easily find one in the $400 range.
It's a 40 years old digital synth (so trivial to replicate one to one), with no special hands on controls as a keyboard, and one with 150,000+ units sold, with about a dozen modern replications.
$400 would already be an impressive sum for such constraints.
But it regularly goes for 800+ in Reverb.com for example.
Good luck finding a 60-key MIDI controller with velocity-sensitivity and aftertouch for less than $200, and it's without getting into replication (of either the controller or the synth).
This is strangely written. NL is not a character. It is an operation. Every time he writes "NL character" he means an LF, i.e. 0x0A.
The NL operation is defined differently for different OSs. Yes, CRLF is a relic of the teletype, but in practice, it's really the Windows convention inherited from DOS. L/unix has always been LF. On old Mac operating systems it was CR alone.
I use Z-Wave for everything. I looked into Home Assistant, but went with a Hubitat C8 Pro hub bridged to HomeKit on my Apple TV. A Z-wave multi-relay and tilt sensor kit is under $100, and just works.
Home Assistant is more flexible, and has nicer dashboards, but it's also way more of a PITA to get everything working consistently. Hubitat, OTOH, has just worked, with very little tinkering. I had some issues early on with it running slow, but later firmwares resolved all such issues.
Why are enterprise SANs so good at dedupe, but filesystems so bad? We use HPE Nimble (yeah, they changed the name recently but I can't be bothered to remember it), and the space savings are insane for the large filesystems we work with. And there is no performance hit.
Some of this is straight up VM storage volumes for ESX virtual disks, some direct LUNs for our file servers. Our gains are upwards of 70%.
No. This is just wrong and fails to understand not just how transformers work but the conceptual mapping that results from their training.
All these arguments about whether or not LLMs think are missing the point. They do not “think” as humans think due to their intrinsically transactional nature. But calling them “fancy statistical autocomplete algorithms” is also wrong.
LLMs contain within their matrix a massively high dimensional concept map. In this coordinate space, high order vectors map the distance between abstract concepts. This is a natural result of consuming language, which by its very nature is a symbolic concept map.
The uncomfortable question becomes: Is the human brain similarly using a massively high-dimensional concept map? Can a significant part of human thought be described as a fancy autocomplete algorithm? Can a significant amount of human reasoning be mapped as a nested series of transactions?
Actual article title: Benchmarking Qualcomm's NPU on the Microsoft Surface Tablet
Because this isn't about NPUs. It's about a specific NPU, on a specific benchmark, with a specific set of libraries and frameworks. So basically, this proves nothing.
But you can’t get more clicks. You have to attack enough people to get clicks.I feel like this place is becoming more and more filled with posts and titles like this.
"To run more complex requests that require more processing power, Private Cloud Compute extends the privacy and security of Apple devices into the cloud to unlock even more intelligence.
With Private Cloud Compute, Apple Intelligence can flex and scale its computational capacity and draw on larger, server-based models for more complex requests."
