Live data from Hacker News

Viewing profile — aapoalas

aapoalas

HN member
Joined
Sat, Aug 12, 2023, 11:05 AM UTC
HN karma
463
Public activity
169 items

About aapoalas

SW engineer in automation business

TypeScript by day, Rust and big dreams by night

Recent public activity

  1. comment
    Comment #49201147

    It is not.

  2. comment
    Comment #48988931

    I believe Zig will always do bounds checks, except maybe in ReleaseFast mode?

  3. comment
    Comment #48959850

    I had an HP Mini 5102 and I absolutely loved it! I actually revived it a few years ago and used it for some modern programming tasks. I think I tried to compile rustc on it once an…

  4. comment
    Comment #48634716

    Really cool to see Zig have strong support and a stable financial status <3

  5. comment
    Comment #48545719

    Ooh, cooll to hear you got some uptake on the call for formal methods help! Or did you end up figuring it out on your own? Either way, looking forward to the followup!

  6. comment
    Comment #48389287

    Oh, I was just watching this yesterday and got a little re-energised about getting back to more active development of my DoD JS engine! Thanks!

  7. comment
    Comment #48255796

    Beyond just quite possibly being slop, this is also sloppy and confused: complaining that C++ cannot remove features because they live in the stdlib forever while listing out a bev…

  8. comment
    Comment #48139673

    This bug was already reported very soon after the merge.

  9. comment
    Comment #48134210

    They have a PR (~~closed by GitHub bot as AI slop, ironically~~ this was wrong info, it was apparently closed by Jarred himself as it missed a conversion or some 20 Zig files to Ru…

  10. comment
    Comment #48082589

    Regarding the architecture documentation you have up on tsz.dev, one thing that jumped out to me was the use of the per node typed side pools. A semi-recent talk[0] had benchmarked…

  11. comment
    Comment #47939879

    "They're your feelings and no one else has the right to how you should feel about them."

  12. comment
    Comment #47815932

    Remember to be careful with looping lest you create an ikikieriö.

  13. comment
    Comment #47733412

    Would kernel huge pages possibly have an effect here also?

  14. comment
  15. comment
    Comment #47139639

    I may have not properly read the paper that said "This is not a visa, you should apply for a visa using this paper"...

  16. comment
    Comment #47139489

    I have very fond memories of Kansai airport. First time I went to Japan I ... Uhh, I didn't have a visa despite going there for exchange. The Kansai airport immigration office utte…

  17. comment
    Comment #47129333

    You and me both; never change you beautiful bastard of a language <3

  18. comment
    Comment #47129303

    If you want to take a look at some of the "big drivers", the Project Goals[1] is the right place. These are goals proposed by the community and the language developers put together…

  19. comment
    Comment #47129195

    He is the Rust project lead, and the Rust project has been doing quite a bit of user, adopter, and non-adopter interviews over the past few years.

  20. comment
    Comment #47063888

    It's also been ridiculously slow for a month or two now :/ not a good time to be working on some relatively intricate performance optimisation with DevTools taking 1-4 seconds to e…

  21. comment
    Comment #46856393

    I was sitting behind you as you wrote this comment. I just wanted to tell you that.

  22. comment
    Comment #46856349

    F.ex. they didn't do postgresql and other DBs separately but instead just had a databases room.

  23. comment
    Comment #46589285

    Monkey's paw: you get your wish, but so does someone who wants RAII and single-use-malloc to be left behind as a leaky and bad abstractions. We all happily march into a future wher…

  24. comment
    Comment #46586913

    I aim to displease!

  25. comment
    Comment #46586699

    Author here: to get the compiler to help me as the programmer to produce correct code (not accidentally using handles after GC) without being massively manual, but (at least curren…