For your other questions I found these in the linked text

    - https://sr.ht/~jprotopopov/kefir/#goals-and-priorities
    - https://sr.ht/~jprotopopov/kefir/#history-and-future-plans

    const item = for (let sample .. items) {
        if (item.key == key) {
            break item;
        };
    } else { ... };

"In v1, a nil Go slice or Go map is marshaled as a JSON null. In contrast, v2 marshals a nil Go slice or Go map as an empty JSON array or JSON object, respectively. The jsonv2.FormatNilSliceAsNull and jsonv2.FormatNilMapAsNull options control this behavior difference. To explicitly specify a Go struct field to use a particular representation for nil, either the `format:emitempty` or `format:emitnull` field option can be specified. Field-specified options take precedence over caller-specified options."

    if err == nil { // inverted
        return err
    }

Comments URL: https://news.ycombinator.com/item?id=43720070

Points: 3

# Comments: 0

They do monthly newsletter and accompanying youtube video: https://www.youtube.com/@LadybirdBrowser

That's a great summary. I wrote a few significant flask apps many years ago as well and I'm a huge fan of SQLAlchemy. My flask apps were greenfield so I ended up building crappier versions of alot that Django provides. I still enjoyed it but I wasn't as productive. But with a legacy integration, it would be hard to beat SQLAlchemy (I think its great for greenfield too). I've basically landed on your comment above as well.

But I built 3 large successful applications in it in that time. I loved it. I don't use it regularly anymore since I mostly moved away from webdev, but I recently came back into contact with my largest project I build in 2018/2019 and its been running perfect this whole time and was a pleasure to dive back into.

Django just felt logically organized, documentation was on point, core was very readable (at least then).

I always just felt so productive in it. I know everyone has different opinions, experiences and products they are building, but I'm always surprised with the negative comments. I definitely prefer SSR with its reasonable though, so maybe thats part of it.

I use many features of git that I probably wouldn’t otherwise due to having to remember flags and copying around hashes. It also makes discovering git functionality very easy.

Have you used OpenBSD? You're telling them they should be doing something, that is already basically their mission statement.

They are know for doing exactly what you are suggesting.

Go ask @tedunangst. It was literally called "tedu'd" for ripping out old crusty code.

Here is a list of OSes[0]. Where do you draw the line on supporting these? Should every new project try to support all of these? Do you, doublerabbit, get to decide which OSes are important enough for support?

Or do you think the person who created the project and does all the work should be able to decide where to spend their free time?

[0] https://en.wikipedia.org/wiki/List_of_operating_systems

Plus nostalgia.

Comments URL: https://news.ycombinator.com/item?id=37391934

Points: 133

# Comments: 148