Summary of the KX Community Edition License Agreement:
Key Points:
What you get:
- Free license to use KX software for personal or internal business purposes only
- No support or maintenance services included
- Software provided "as is" without warranties
Major restrictions:
- NO commercial use
- Cannot sell, distribute, or monetize any product that uses or depends on this software
- Cannot bundle it with commercial products
- Cannot reverse engineer, modify, or create derivative works
- Cannot remove copyright notices or trademarks
- Software may phone home to verify valid license
Important limitations:
- KX's liability capped at $100
- They disclaim all warranties including fitness for purpose
- You must delete software if agreement terminates
- Subject to export control laws
- KX can audit your compliance
Legal terms:
- Governed by New York law
- You retain no IP rights in the software
- Confidentiality obligations for 5 years
- KX can terminate at any time
Bottom line:
This is a restrictive free license meant for evaluation/personal use only. Any commercial use or distribution is strictly prohibited. If you need commercial rights, you'll need a different license.
Neither Claude Sonet 3.5 or 3.7 could solve this correctly unless you add to the prompt “ Prove it with the js analysis tool, please use an efficient combinatorial algorithm to find the solution”… and I had to correct 3.7 because it was not following the instructions as 3.5 did
I don't know what in my comment made you assume I use an EQ.
As a first-time Hi-Fi headphone buyer, the reviews on Amazon and Youtube didn't surface the nuances of the different headphone models using quantitative information as DIY-Audio-Heaven does.
After purchasing the Beyerdynamic DT 770 PRO, I discovered the Superlux HD 662 EVO on this website and decided to buy them for $38 to see how they would compare. I was pleasantly surprised by the significant difference in quality, considering the Superlux headphones were almost five times cheaper. This experience led me to return the Beyerdynamic headphones and approach overpriced headphone reviews with more skepticism.
Given the recent discussions about hi-fi headphone misleading marketing https://news.ycombinator.com/item?id=36377875, and how hard it is to quantify quality, I found this resource a while ago and loved how they tear them apart and fixed the shortcomings of $40 headphones with simple hacks like adding a coffee filter on the cup to make them sound better than $500 models
Shameless plug. I open-sourced https://snapdir.org/ to explore how to solve these exact issues.
It's an early prototype to gather feedback around the ergonomics of the interface and the manifest format, and I would love to learn if people might find it useful enough for the use cases where LFS falls short.
The performance is directly related to the number of files you track. The first time it runs, it will be slow for large datasets, but incremental changes can use the local cache to speed up things.
That said, I built the bash version as a proof-of-concept with the idea of implementing it using Zig once I'm happy with the tool's usability.
This 2015 post and the code on the 20k challenge to find correctness and liveness bugs on TiggerBettle's implementation are helping my understand better what VSR is all about.
I wonder what other projects are using it in the wild.
I recommend reading the book “ Panic: The Story of Modern Financial Insanity” by
Michael Lewis. It’s a series of articles and expert opinions before and after modern market crashes that helps gaining perspective of expert opinions during the ups and downs of the market.
It makes sense, DuckDB's documentation has significantly improved, but it is still lacking when it comes to the limitations of using parquet. We have also hit some roadblocks when updating schemas backed by parquet files, so we now only use DuckDB for querying parquet via SQL.
Here’s Tamir’s call for action https://www.linkedin.com/feed/update/urn:li:activity:7419994...