Readit Newsjasonthorsness commented on UK government advises deleting emails to save water gov.uk/government/news/na... · Posted by u/bifftastic
As an unashamed digital hoarder I never expected the UK to declare war.
jasonthorsness commented on Claude Sonnet 4 now supports 1M tokens of context anthropic.com/news/1m-con... · Posted by u/adocomplete
This is definitely good to have this as an option but at the same time having more context reduces the quality of the output because it's easier for the LLM to get "distracted". So, I wonder what will happen to the quality of code produced by tools like Claude Code if users don't properly understand the trade off being made (if they leave it in auto mode of coding right up to the auto compact).
What do you recommend doing instead? I've been using Claude Code a lot but am still pretty novice at the best practices around this.
jasonthorsness commented on Jetbrains announces price increase. jetbrains.com/store/... · Posted by u/seatac76
I couldn't readily tell which number you typoed but from the linked page it's the former; it's a $6/year increase. However, I didn't comment just for the correction, I wanted to draw attention to the "for a long time" part so others wouldn't get sticker shock at the $299/year initial price, going down to $239/year for the 2nd contiguous year, and then to the aforementioned $179 from that point forward
And also to say that I firmly agree that $180 for a year of all access to the best development tools money can buy is a deal that I happily pay. I also get to use them for work, which for bigger orgs can save some red tape
I've had the all-products-pack for a long time, definitely enjoy the "loyalty pricing". And using the same tools for home, work, anything is a big plus.
Haven’t done much in C# since Claude Code has been available but I’ve found strict linting and style rules are very helpful for such agents when writing Go. I used to run a fairly strict and customized config with StyleCop etc; I wonder if something maybe more standardized like this will be more effective.
jasonthorsness commented on The Windows 10 emoji picker has been broken for a month rozab.dev/blog/emoji-sear... · Posted by u/rozab
I refuse to provide any help or even sympathy to people who insert emoji into documents.
What did the Unicode Consortium ever do to you?
jasonthorsness commented on Consider using Zstandard and/or LZ4 instead of Deflate github.com/w3c/png/issues... · Posted by u/marklit
One of the interesting features of ZStandard is the support for external dictionaries. It supports "training" a dictionary on a set of samples, of whatever size (16KiB, 64 KiB, etc.), then applying that dictionary as a separate input file for compression and decompression. This lets you compress short content much more effectively.
I doubt it would apply to PNG because of the length and content doesn't seem to be dictionary-friendly, but it would be interesting to try from some giant collection of scraped PNGs. This approach was important enough for Brotli to include a "built-in" dictionary covering HTML.
jasonthorsness commented on Ask HN: Have you ever regretted open-sourcing something? · Posted by u/paulwilsonn
Here is one such story of regret for paint.net (not my project but I'm a fan). I think the author's take was quite reasonable for this project.
https://blog.getpaint.net/2009/11/06/a-new-license-for-paint...
jasonthorsness commented on Go Assembly Mutation Testing words.filippo.io/assembly... · Posted by u/Metalnem
Code coverage not being meaningful because all instructions are always executed in order to make the crypto function constant-time is certainly a niche issue! It’s great to see such rigor going into Go.
Not assembly, but one of the side benefits of Go’s infamously verbose error handling is that code coverage generally tells you when you’ve never tested error cases. It gives a more fine-grained picture than languages using exception handling (unless you try/catch at a similarly fine-grained level).
https://go.dev/blog/fips140
Nonce management with AES GCM is a huge pain, and I think this provides a way to just throw more randomness at the problem and stop worrying about it.