HN user

continuational

1,200 karma

Hi there!

I'm a husband and a father of two. I've been working in Scala for over a decade, and I'm part of the founding team at Paqle.

I work on a full stack programming language called Firefly and I organize a functional programming meetup in Copenhagen:

https://www.meetup.com/moedegruppefunktionellekoebenhavnere/

It's once a month - swing by if you'd like to meet up!

meet.hn/city/55.6867243,12.5700724/Copenhagen

Posts5
Comments475
View on HN

I do, and frankly I enjoy my day more when I don't feel like I'm being a jerk, even towards a robot. But mostly as part of a follow up message.

I also think it signals that I was happy with that solution in the ongoing conversation.

On the other hand, I'm much more sloppy with my writing.

The token cost is irrelevant, tool calls and reasoning probably dominates.

Do you really prefer this:

  fn Maybe(comptime T: type) type {
    return union(enum) {
        value: T,
        nothing,

        const Self = @This();

        pub fn just(the_val: T) Self   { return .{ .value = the_val }; }
        pub fn nothing() Self          { return .nothing; }

      }
    }
Over this?
    data Maybe a = Just a | Nothing

Not long ago I was looking through programming language sites to figure out how to best introduce the language I'm working on.

ruby-lang.com stood out with a text in a big font:

Ruby is...

Followed by a paragraph about what makes Ruby special. I think that was an exceptionally simple and natural way of introducing something as complex as a programming language.

Comic Code Reviews 8 months ago

I think this kind of slop has negative value. It's unclear how much of the information in the comic is hallucinated, and the malformed code "for i = i1+|>" and nonsense text "(starts write hooks!" doesn't bode well.

Thank you! Yeah, I think some of the newer frameworks really complicate dataflow. We're trying to keep dataflow clear, though it's a big design space given the distributed nature of webapps.

In any case, if you take it for a spin, I'd love some feedback.

Working on a programming language for webapps!

https://www.firefly-lang.org/

Speed is not an optional feature on the web. The site above is written in Firefly, uses hydration, and scores 100% on PageSpeed Insights.

The language is largely complete, and we're now working on DX: Got a language server, a devserver, and some essential libraries.

Basic greenhouse effect: Visible light (and ultraviolet light) comes in relatively unhindered. Gets absorbed by the earth and heats it up. The heat is emitted as infrared radiation. This gets absorbed by CO2 (and equivalents) and reemitted in a random direction. Takes a long time to reach space by chance, so the energy stays in the atmosphere for a while.

The reason working with the DOM directly is hard is that you have to implement arbitrary patching to go from one state to another.

The entire point of frameworks like React is to avoid the problem, by automatically creating and applying the patch for you.

It's not irrational; quite the contrary.