verdagon

9 ms·

1. 31.▲
   by verdagon 3y ago

   Perhaps. The problem space's difficulty can bring some inherent complexity, yes... but I often hear that fact used to justify adding complexity that isn't actually necessary. Biggest example I've seen: wanting to use Java for
2. 32.▲
   by verdagon 3y ago

   This PumpkinOS project is pretty incredible. I can't imagine how much effort it would take to be compatible with all the system calls that the average Palm app would expect. I remember Palm did some truly weird things with memory: anyt
3. 33.▲
   by verdagon 3y ago

   It makes me wonder if there are any language constructs that can make this a reasonable feature. One idea I've been tossing around is having the ability to roll back any changes to mutex-guarded data if an exception drops a mutex guard
4. 34.▲
   by verdagon 3y ago

   Why's that?
5. 35.▲
   by verdagon 3y ago

   I made no assumption like that, though do let me know if I've said something that could be interpreted that way. Rather, I think that the static analysis we see in today's languages just isn't powerful/flexible enough to
6. 36.▲
   by verdagon 3y ago

   I don't think the article made that conclusion? I see this in there: > As seen in the benchmarks, the current Rust standard library unstable sort implementation outperforms the C++ standard library counterparts And I can't find
7. 37.▲
   by verdagon 3y ago

   > Often safety and performance are characterized as a set of zero sum tradeoffs, yet often it's possible to find better tradeoffs who's holistic properties improve upon a previously seen "either or". There is truth in
8. 38.▲
   by verdagon 3y ago

   > Often safety and performance are characterized as a set of zero sum tradeoffs, yet often it's possible to find better tradeoffs who's holistic properties improve upon a previously seen "either or". There is truth in
9. 39.▲
   by verdagon 3y ago

   Sometimes, having a quick, inaccurate, but easily-verifiable answer is better. For example, when you're trying to remember the name of that one function to call, or ideas on where to travel next month. Also, not super relevant, but in
10. 40.▲
    Rhovas: A programming language for API design and enforcement(rhovas.dev)

    2 points by verdagon 3y ago|0 comments
11. 41.▲
    by verdagon 3y ago

    I believe coroutines are mostly unrelated to RAII. One can still have coroutines in a single ownership world and guarantee destructors are called. (If not, I have a lot of redesigning to do for Vale!) Also, doesn't your mentioned probl
12. 42.▲
    by verdagon 3y ago

    I'd love to hear more on this, what are some problems we don't see? And what do you mean by effective?
13. 43.▲
    by verdagon 3y ago

    ELI5 layers? Could someone like me see when I've used one layer as opposed to another, when using ChatGPT?
14. 44.▲
    You Need More Constraints(borretti.me)

    3 points by verdagon 3y ago|0 comments
15. 45.▲
    by verdagon 3y ago

    Austral is still alpha, so this kind of thing is expected. It's heading in a good direction, give it some time.
16. 46.▲
    by verdagon 3y ago

    Amazing article! I especially like the distinction between resource safety and memory safety. I think a lot of folks don't realize that a memory safety approach can help or hurt one's resource safety. The only mainstream language
17. 47.▲
    by verdagon 3y ago

    Yep, then today's Vlang got to that name first, so we had to call it Vale instead!
18. 48.▲
    by verdagon 3y ago

    As another compiler developer, there are few mistakes more damaging than self-hosting too soon. A language will be a net benefit for small and medium programs long, long before it's a net benefit for (and has the tooling for) a project
19. 49.▲
    by verdagon 3y ago

    We all just have similarly good taste in naming =) party on this end of the alphabet!
20. 50.▲
    by verdagon 3y ago

    Or the other Vale! https://vale.sh/
21. 51.▲
    by verdagon 3y ago

    Not much! It's still very young, still in the prototype phases. When it's more mature and polished I hope it will be useful for those writing servers and games mostly.
22. 52.▲
    by verdagon 3y ago

    Yeah, this article was rather sparse on background, more intended for friends and sponsors and people who have been following along with Vale. A strategy that backfires with general audiences like HN! TL;DR: Vale is like a cleaner C++, and
23. 53.▲
    Five Years of Rhovas(blog.willbanders.dev)

    1 points by verdagon 3y ago|0 comments
24. 54.▲
    by verdagon 3y ago

    Funny story, that wasn't my original intent! I have a programming blog, but every day I'm finding weird facts that I want to write about, so I tend to sneak them in: * I like mythical birds, so I wrote an article about memory safe
25. 55.▲
    by verdagon 3y ago

    Double-frees are prevented by Vale's single ownership (in the C++ sense), generational references make it so use-after-frees are safely detected. If we try to access released memory via a reference, we should predictably+safely get eit
26. 56.▲
    by verdagon 3y ago

    Thanks for your support, I really appreciate it =) I would love to do this full time!
27. 57.▲
    by verdagon 3y ago

    I would keep it! But alas, I have to remove it at some point today. I plan on keeping a record of all of them at https://verdagon.dev/blog/easter-egg-notes though.
28. 58.▲
    by verdagon 3y ago

    Honor to Brigadier Sir Nils Olav III!
29. 59.▲
    by verdagon 3y ago

    Yep, this was my bad. I thought Vala was dead because of a certain post (I think it was this one [0]), and because I rarely ever heard anyone mention it. I suspect I was wrong. I've been tossing around the idea of switching Vale's
30. 60.▲
    by verdagon 3y ago

    Thanks! Glad you enjoy them =)