anttiharju

8 ms·

1. 61.▲
   by anttiharju 1y ago

   All pure functions have complexity?
2. 62.▲
   by anttiharju 1y ago

   Checking the first one > Intel staging area for llvm.org contribution. Home for Intel LLVM-based projects. Seems like they use it to contribute to upstream which is business as usual?
3. 63.▲
   by anttiharju 1y ago

   Zsa voyager is low profile, you aware of that? Happy user for 1+ year here
4. 64.▲
   by anttiharju 1y ago

   Responding to an anecdote with another is fair I suppose
5. 65.▲
   by anttiharju 1y ago

   > This already the case today, you can't run your bank's app or government eID apps on anything but Google or Apple devices. Fairphone 6 with e/OS begs to differ. Dutch phone with a French OS. No issues.
6. 66.▲
   by anttiharju 1y ago

   Love the writing style
7. 67.▲
   by anttiharju 1y ago

   I think most of the pain with GitHub Actions goes away if you use actionlint, action-validator, prettier/yamlfmt in a single ci job to validate your setup. Can even add them as git hooks that automatically stage changes and give quick
8. 68.▲
   by anttiharju 1y ago

   Or just use composite actions, it's not 2020 anymore. Templating GitHub Actions is very powerful (I've worked with such a setup) but it has its own headaches and if you don't _need_ custom tooling better to not have it. I can
9. 69.▲
   by anttiharju 1y ago

   I think YAML anchors in GitHub Actions are very welcome, for example for DRYing the push/pull_request 'paths:' filters [1]. Now only if they supported paths filter for `workflow_call` [2] event in addition to push/pull_r
10. 70.▲
    by anttiharju 1y ago

    I wish it'd be easy to plug it to a s3 backend and thumbnails etc. ephemeral things could just be on disk.
11. 71.▲
    by anttiharju 1y ago

    I think people should do/go where they have a peace of mind, whatever that place may be.
12. 72.▲
    by anttiharju 1y ago

    Nokia (mostly networking-related things nowadays) touts - or at least used to, haven't kept up to date - itself as one of the most ethical companies around. > But isn't that true for every big corp, or even every public company
13. 73.▲
    by anttiharju 1y ago

    Unity Ads have been a thing long before (2014) ironSource merger (2022) https://unity.com/news/unity-technologies-acquire-applifier-... https://unity.com/blog/news/welcome-ironsource
14. 74.▲
    by anttiharju 1y ago

    I've also been eyeing Rust, but coming from Go where you can build more or less complete cli tools with just the standard library I'm not overtly exited by occurrences like this. From what I've seen Rust projects seem more or
15. 75.▲
    by anttiharju 1y ago

    Linters that catch any silly mistakes. Shellcheck, actionlint, action-validator, prettier, ... coupled with automated release process. I find that when merges break due to trivial issues I lose motivation. Also Lefthook with stage fixed is
16. 76.▲
    by anttiharju 1y ago

    I don't doubt any of that but why stick to such old conventions when there are explicit and immediately clear options? I don't think me writing an if condition if boolean != true instead of if boolean == false should pass code rev
17. 77.▲
    by anttiharju 1y ago

    I've no issues with boolean logic (&&, ||) but unfortunately all my schooling has done those with the notion of true/false instead of bits iirc.
18. 78.▲
    by anttiharju 1y ago

    At least in the case of cgo_enabled it does define the default behaviour
19. 79.▲
    by anttiharju 1y ago

    pydantic?
20. 80.▲
    by anttiharju 1y ago

    My pet peeve is CGO_ENABLED compiler option in Go. It's set to 0 or 1 to enable/disable (can never remember which mapa to which) If it was just CGO=true or CGO=false I think so much confusion could have been avoided. I think simil
21. 81.▲
    by anttiharju 1y ago

    https://flox.dev is pretty great
22. 82.▲
    by anttiharju 1y ago

    Curious about whether you're aware of https://www.aitofit.io/en and how your app compares to it
23. 83.▲
    by anttiharju 1y ago

    I suppose I phrased this poorly. Stack traces are useful indeed. I guess what I like that usually wrapped errors are bit more thoughtful, stack traces can look a bit like "vomit".
24. 84.▲
    by anttiharju 1y ago

    Posted this because of the other Go error handling post today https://news.ycombinator.com/item?id=44171677 I like error wrapping. I've worked in codebases where systems had to be debugged by piecing together individua
25. 85.▲
    Don't just check errors, handle them gracefully (2016)(dave.cheney.net)

    44 points by anttiharju 1y ago|45 comments
26. 86.▲
    by anttiharju 1y ago

    I was actually bit scared, so read through the whole post and am happy with the conclusion. Go is very readable in my experience. I'd like to keep it that way.
27. 87.▲
    by anttiharju 1y ago

    With `brew install go` and module github.com/anttiharju/vmatch go 1.21.0 toolchain go1.21.1 I still get a binary that claims to be built with the latest version of Go instead of 1.21.1 or .0 vmatch has version 0.1.6+dirty built wi
28. 88.▲
    by anttiharju 1y ago

    It's a helpful link, thank you. I think I need to play with toolchain more. Last time I checked I think there was some corner case that was not covered but I could be wrong.
29. 89.▲
    by anttiharju 1y ago

    On https://github.com/anttiharju/vmatch as a hobby. It's starting to get to a workable state, I'm using it to manage Go and golangci-lint for the project itself. It even works with the Go vs code plugin. I th
30. 90.▲
    by anttiharju 1y ago

    Everyone needs hobbies