Search
71 results for “ryguw”
-
Suddenly Bun has become much, much more interesting as a longterm Node.js competitor. Dropping Zig for Rust is a bold but ultimately wise move, in their specific case.
-
It's official. I'm starting an AI company: @HiddenAI. All our models will be fully open source: source available but hidden.
Accepting your investment term sheets starting today.
#ai #artificial #apr1 #startup #company #golang #rust #python #easteregg
-
It's official. I'm starting an AI company: @HiddenAI. All our models will be fully open source: source available but hidden.
Accepting your investment term sheets starting today.
#ai #artificial #apr1 #startup #company #golang #rust #python #easteregg
-
It's official. I'm starting an AI company: @HiddenAI. All our models will be fully open source: source available but hidden.
Accepting your investment term sheets starting today.
#ai #artificial #apr1 #startup #company #golang #rust #python #easteregg
-
It's official. I'm starting an AI company: @HiddenAI. All our models will be fully open source: source available but hidden.
Accepting your investment term sheets starting today.
#ai #artificial #apr1 #startup #company #golang #rust #python #easteregg
-
It's official. I'm starting an AI company: @HiddenAI. All our models will be fully open source: source available but hidden.
Accepting your investment term sheets starting today.
#ai #artificial #apr1 #startup #company #golang #rust #python #easteregg
-
Simplicity means sacrifice.
More: https://lukeplant.me.uk/blog/posts/no-one-actually-wants-simplicity/
-
While I don't think code reviews are all bad and waste of time, I do think some are bad or partial waste of time. There are effective alternatives to those weeks-long PR reviews, worth exploring imo.
-
On Feb 1st, 2024, #Apple released Pkl. Pronounced "pickle", it is a complete configuration scripting language, including a JSON/YAML/XML/more compiler, a language server, bunch of IDE plugins, and of course direct bindings for your favorite programming language, for quick adoption. A #Python binding seems missing.
I like how a Pkl config's specs and values are colocated. Always hated maintaining separate schemas for very simple configs.
-
@lorddimwit any struct that only consists of comparables (ints, strings, arrays) can be used as map key. And it’s faster than any bytes-converting hash function that I tried in userland (gob, jsoniter). For example, to speed up one of my #aoc2023 solutions I converted an []int slice field to a fixed size [32]int field and was able to use the parent struct as map key for a 5x speedboost.
-
@lorddimwit any struct that only consists of comparables (ints, strings, arrays) can be used as map key. And it’s faster than any bytes-converting hash function that I tried in userland (gob, jsoniter). For example, to speed up one of my #aoc2023 solutions I converted an []int slice field to a fixed size [32]int field and was able to use the parent struct as map key for a 5x speedboost.
-
@lorddimwit any struct that only consists of comparables (ints, strings, arrays) can be used as map key. And it’s faster than any bytes-converting hash function that I tried in userland (gob, jsoniter). For example, to speed up one of my #aoc2023 solutions I converted an []int slice field to a fixed size [32]int field and was able to use the parent struct as map key for a 5x speedboost.
-
@lorddimwit any struct that only consists of comparables (ints, strings, arrays) can be used as map key. And it’s faster than any bytes-converting hash function that I tried in userland (gob, jsoniter). For example, to speed up one of my #aoc2023 solutions I converted an []int slice field to a fixed size [32]int field and was able to use the parent struct as map key for a 5x speedboost.
-
@lorddimwit any struct that only consists of comparables (ints, strings, arrays) can be used as map key. And it’s faster than any bytes-converting hash function that I tried in userland (gob, jsoniter). For example, to speed up one of my #aoc2023 solutions I converted an []int slice field to a fixed size [32]int field and was able to use the parent struct as map key for a 5x speedboost.
-
Managed to reduce the exec time for 2023 day 23 part 2 from 513 seconds (~8.5 mins) to a stellar 0.310 seconds. Looking back at my commits these were the biggest leaps:
- By far the biggest leap: Shrink unique nodes to <= 64, then instead of a map simply use a `uint64` bitmask for boolean lookups (visited or not). Saves a lot of map accesses & assignments
- Prefer `int` when doing most calculations and comparisons, seems super optimized in the Go runtime -
Managed to reduce the exec time for 2023 day 23 part 2 from 513 seconds (~8.5 mins) to a stellar 0.310 seconds. Looking back at my commits these were the biggest leaps:
- By far the biggest leap: Shrink unique nodes to <= 64, then instead of a map simply use a `uint64` bitmask for boolean lookups (visited or not). Saves a lot of map accesses & assignments
- Prefer `int` when doing most calculations and comparisons, seems super optimized in the Go runtime -
Managed to reduce the exec time for 2023 day 23 part 2 from 513 seconds (~8.5 mins) to a stellar 0.310 seconds. Looking back at my commits these were the biggest leaps:
- By far the biggest leap: Shrink unique nodes to <= 64, then instead of a map simply use a `uint64` bitmask for boolean lookups (visited or not). Saves a lot of map accesses & assignments
- Prefer `int` when doing most calculations and comparisons, seems super optimized in the Go runtime -
Managed to reduce the exec time for 2023 day 23 part 2 from 513 seconds (~8.5 mins) to a stellar 0.310 seconds. Looking back at my commits these were the biggest leaps:
- By far the biggest leap: Shrink unique nodes to <= 64, then instead of a map simply use a `uint64` bitmask for boolean lookups (visited or not). Saves a lot of map accesses & assignments
- Prefer `int` when doing most calculations and comparisons, seems super optimized in the Go runtime -
Managed to reduce the exec time for 2023 day 23 part 2 from 513 seconds (~8.5 mins) to a stellar 0.310 seconds. Looking back at my commits these were the biggest leaps:
- By far the biggest leap: Shrink unique nodes to <= 64, then instead of a map simply use a `uint64` bitmask for boolean lookups (visited or not). Saves a lot of map accesses & assignments
- Prefer `int` when doing most calculations and comparisons, seems super optimized in the Go runtime -
To me this HN thread is pure gold. When I first discovered Dynamic Programming (DP) in Python with the @cache decorator quite late actually, it looked like magic to me. I could not find as much wisdom on it (top search results are all leetcode tutorials) but once again @hn_discussions fill that gap. Will dive deeper into the topic of generative recursion.
#hackernews #dynamicprogramming #dynamic #recursion #python
🧵 HN thread: https://news.ycombinator.com/item?id=38988948
-
That said, running the exact squeezed single-core-optimized algorithm, but for multiple inputs on multiple cores simultaneously with 5 lines of code, feels absolutely awesome! 😎
-
That said, running the exact squeezed single-core-optimized algorithm, but for multiple inputs on multiple cores simultaneously with 5 lines of code, feels absolutely awesome! 😎
-
That said, running the exact squeezed single-core-optimized algorithm, but for multiple inputs on multiple cores simultaneously with 5 lines of code, feels absolutely awesome! 😎
-
That said, running the exact squeezed single-core-optimized algorithm, but for multiple inputs on multiple cores simultaneously with 5 lines of code, feels absolutely awesome! 😎
-
That said, running the exact squeezed single-core-optimized algorithm, but for multiple inputs on multiple cores simultaneously with 5 lines of code, feels absolutely awesome! 😎
-
Being able to use all cores with ease in #Go, has taught me that not all problems can be parallelized. In fact, only few algorithms are concurrent, and CPU-bound. CPU caches, instruction sets, and single-core #performance is still very relevant.
-
After doing #AoC2023 I like to think I know #Golang quite well now… I miss ternaries. Although famous, nobody actually uses the go keyword. Pointers are fun, I missed them. Tools for testing and profiling are keys to mastering our craft. I deeply want a sound type system like that of #Rust and #TypeScript.
