I've tended to use nginx with a separate letsencrypt setup for projects before, and it's much more awkward.
I've tended to use nginx with a separate letsencrypt setup for projects before, and it's much more awkward.
So if you've given permission to run e.g. 'cargo test' or even 'cargo run', you need to be sure that all future invocations are safe too.
So if you've given permission to run e.g. 'cargo test' or even 'cargo run', you need to be sure that all future invocations are safe too.
It's a been a lot of work to lock down appropriately. It still needs some UI polish but it's so nice to be able to try snippets immediately.
www.garden-lang.org
It's a been a lot of work to lock down appropriately. It still needs some UI polish but it's so nice to be able to try snippets immediately.
www.garden-lang.org
Hello World is too simple to show much syntax. Fibonacci is OK but the reader may not know what print(fib(10)) should show.
Maybe print(greet("World")) is better? It gives you a function definition at least.
Hello World is too simple to show much syntax. Fibonacci is OK but the reader may not know what print(fib(10)) should show.
Maybe print(greet("World")) is better? It gives you a function definition at least.
I'm really impressed, it's rare to see LLMs ask follow-up questions.
(I wanted Emacs in this case.)
I'm really impressed, it's rare to see LLMs ask follow-up questions.
(I wanted Emacs in this case.)
devblogs.microsoft.com/typescript/p...
devblogs.microsoft.com/typescript/p...
"Expected Int here, but this value has type String" or "This expression requires Int, but the value is String".
Do you have a favourite?
"Expected Int here, but this value has type String" or "This expression requires Int, but the value is String".
Do you have a favourite?
* Added support for protobuf, improved bash and YAML.
* Updated 16 parsers to the latest upstream version (thanks Antonin Delpeuch!)
* A ton of display polish for word highlighting, alignment, and binary files.
github.com/Wilfred/diff...
* Added support for protobuf, improved bash and YAML.
* Updated 16 parsers to the latest upstream version (thanks Antonin Delpeuch!)
* A ton of display polish for word highlighting, alignment, and binary files.
github.com/Wilfred/diff...
I see tradeoffs on both sides, although it's not a decision I've needed to make myself.
I see tradeoffs on both sides, although it's not a decision I've needed to make myself.
lwn.net/Articles/714...
lwn.net/Articles/714...
The primary user is a 3 year old who can only count to 20 😊
The primary user is a 3 year old who can only count to 20 😊
It feels weird deliberately ignoring helpers though.
It feels weird deliberately ignoring helpers though.
www.scannedinavian.com/tools-built-...
www.scannedinavian.com/tools-built-...
E.g. your last release was 5.2025-09-13 and you've just changed a type, so today's release is 6.2025-11-05.
E.g. your last release was 5.2025-09-13 and you've just changed a type, so today's release is 6.2025-11-05.
The text search is constrained to the languages I care about enough to download the docset, substantially increasing the relevance. In Google I'd need to specify the language.
The text search is constrained to the languages I care about enough to download the docset, substantially increasing the relevance. In Google I'd need to specify the language.
(I've been coding on public transport recently, without a reliable data connection.)
Anyone have tips for making the most of this setup? AFAICT docsets are basically HTML underneath.
(I've been coding on public transport recently, without a reliable data connection.)
Anyone have tips for making the most of this setup? AFAICT docsets are basically HTML underneath.
I used it this week to convert images from obscure formats to common ones. It's a great swiss army knife and runs everywhere.
I used it this week to convert images from obscure formats to common ones. It's a great swiss army knife and runs everywhere.
This is the best I've come up with so far. I'm showing the terminal GUI to show where you'd use the tool.
I'm also trying several standalone screenshots to make it more comprehensible.
This is the best I've come up with so far. I'm showing the terminal GUI to show where you'd use the tool.
I'm also trying several standalone screenshots to make it more comprehensible.
It's not strictly necessary, but it's nice to have. It caught a bug with lexing incomplete string literals too.
It's not strictly necessary, but it's nice to have. It caught a bug with lexing incomplete string literals too.
You can see if you've been somewhere before based on whether there are coins present.
You can see if you've been somewhere before based on whether there are coins present.
For example, I'm very confident (say 90%) that the coin in my pocket is 50% likely to land on heads.
For example, I'm very confident (say 90%) that the coin in my pocket is 50% likely to land on heads.