bbkane

Yup I switched to WezTerm from iTerm2 and being able to version control the settings is one of the biggest benefits (especially because WezTerm allows more complicated Lua scripts)

One reason is portability if you use (or plan to use) desktop Linux

Don't let the Emacs folks read this :)

I read the comments before the link and thought this was a bit harsh, but reading that response I now feel the same way you do.

The reporter ALREADY provided a minimal example and Apple is like "yup we're going to keep changing things and you need to keep rerunning the code you sent us and reporting here because we won't bother to run your minimal example ourselves".

Just wow.

A friend encouraged me to write the paper, even if I didn't submit it, as a means of self-reflecting.

I wish that article showed what the display looks like instead of just the keyboard. Others here have mentioned the lovely information density; I'll have to search elsewhere to see it

Go doesn't monomorphize, so benchmark your generics- they might not be zero cost

Are you referring to writing a wrapper cli? Or adding a GUI?

Oh you mean algebraic types (Elm terminology)? Or the newtype pattern? Or something else?

That sounds like it'll be easier to maintain. Will it also be faster?

Good for him! That's the dream!

Nushell does have types: https://www.nushell.sh/book/types_of_data.html

I'm sorry, what are the same problems you're referring to? I ended up leaving because:

- it was unstable and kept changing (less of an issue now)

- I still need to know bash due to its ubiquity

- it was worse than python for data crunching scripts (ide tooling + my familiarity)

This was several years ago so I'm curious about a more recent perspective

They should adopt Nushell! It would be seen as very "Apple"- a brave great somewhat non interoperable user experience upgrade

I'm assuming this was a while back, mind sharing how far he went or what he was able to produce with this focus?

CRDTs are eventually consistent data structures

Interesting, but I'm not sure how it's different from Observable Framework ( https://observablehq.github.io/framework/ ) for dashboards as code. I like that one because it's Markdown and JS instead of a language defined in YAML + templates

Maybe it's because I'm not an RBAC expert, but I had a hard time understanding the data model for folders. Are they a subject? And then there's a layered CASL where layers overwrite each other? And the user is an actor?

Pop a screenshot in your README please!

I just started diagramming with d2- I'll have to try this one out!

Interesting, it's not mentioned anywhere in the https://github.com/dbos-inc/dbos-transact-golang README. By contrast, Postgres is mentioned right at the top.

I recommend updating the README to mention SQLite somewhere, with maybe a link to https://docs.dbos.dev/golang/reference/configuration#using-s... ?

Even for a personal project such as the one in the blog post, I'd still rather use a package manager to install SQLite.

It's POSSIBLE to build it from source, and manually re-download the source and C compiler (and any dependencies, though I'm not sure SQLite has any) when I want to update and instruct any collaborators to do the same thing... But I'd still rather automate it all with a package manager.

Especially because I'm probably also handling other dependencies in the project and I value the uniform simplicity of using a package manager for all of them

The great thing about using a package manager is that it also handles updating and uninstalling software, not just the initial install

How are you using dbos with SQLite? The docs say its a Postgres library

I love XFCE, but I switched to KDE as it supports Wayland (and I want to use WayDroid). KDE has a similar window + shortcut philosophy.

Safer? From a mental health perspective? Tbh I like human names

Entropy finds a way :)

You can use a trigger with INSTEAD OF to update a view:

CREATE TRIGGER update_customer_emails_trigger INSTEAD OF UPDATE ON customer_emails BEGIN UPDATE customers SET email = new.email, name = new.name WHERE id = old.id; END;

Maybe that's not as flexible as you need.

SQLites process for table updates can be pretty onerous if their ALTER TABLE lacks support. Its a 12 step process the docs have the temerity to call "simple" instead of "tedious and risky" - https://www.sqlite.org/lang_altertable.html#otheralter

What don't you like about SQLite views or foreign keys?