stefcoetzee

Enjoyed this demonstration as well: https://max.computer/blog/solving-the-expression-problem-in-...

Of course :)

"There was (still is) a massive cyberattack against .

We get attacked every day, but this was done with a lot of resources. Either a large, coordinated group and/or a country is involved."

https://x.com/elonmusk/status/1899149509407473825

X/Twitter appears to be down right now

Some contributions to this discussion here: https://youtu.be/vUe3slLHk20?si=57O9CdyPakxrD4Rx&t=1469

From [0]: “We’ve historically used venture capital to fund Electric’s development costs—4 team years, do the math!—but the seed market has tightened, and we realized that it’s in everyone’s interest to maintain a strong and ongoing investment in Electric that is decoupled from VC. That’s why with v3 we’re changing the licensing model to a source available business license:

1. Free “community” license for non-commercial use (e.g. FOSS toolmaker, enthusiast, researcher). You’ll need to login to activate, i.e. it will “phone home” and we will receive light usage analytics, e.g. to count active Electric users and projects. We will of course comply with privacy regulations such as GDPR. We will also use your email to send project updates and community surveys, which you want to participate in, right?

2. Commercial use costs $480/month/developer (33% startup discount). No login or analytics (obviously unacceptable for security and privacy), instead you’ll validate a license key (like Datomic). We also offer support and project implementations and are flexible with fee structure (i.e. services vs licenses). For free trials at work, use the community version with your work email. Talk to us, we will arm you to make the case to management.

Special deal for bootstrappers: FREE until you reach $200k revenue or $500k funding. Just use the community license, and come tell us what you’re doing.”

[0] https://tana.pub/lQwRvGRaQ7hM/electric-v3-license-change

Think Datomic is unitemporal a.o.t. bitemporal.

SIMATIC AX seems to be a step in the direction of VSCode integration.

Where's my flying car?! ;)

The universe is an interesting place. Certainly won't complain if there's more time in the day to get lost in its details.

There's still so much to do, however. Fully open to the upside of artificial intelligence, but cautiously so. I fear it is invoked as a kind of deus ex machina. In my view, it is a multiplier and not a substitute.

Replace in Python with 4-space / tab indentation.

With Specter [0] to lend a hand for more uncommon operations. ;)

[0] https://github.com/redplanetlabs/specter

Fonts included in the repo. [0]

Tooling is a combo of Shadow CLJS and Clojure CLI.

[0] See `resources/public/fonts` here: https://github.com/eliascotto/tryclojure/tree/main/resources...

[1] https://github.com/thheller/shadow-cljs

[2] https://clojure.org/reference/clojure_cli

The CLJS + RN route is doable. [0] Not familiar with the other approach.

[0] https://github.com/PEZ/rn-rf-shadow

Yup, Calva's pretty great.

Agreed. Perhaps using VSCode with the Calva plugin if the reader has no previous experience with Emacs.

Long live the king!

I've only kicked the tires, not used it in anger.

The tutorials are fairly accessible: https://cljdoc.org/d/missionary/missionary/b.33/doc/readme/t...

In a recent London Clojurians talk, the author Leo Noel explained Electric can be thought of as a frontend for Missionary. Rama is by a different team (RPL), but agreed, their philosophies are similar.

next.jdbc is the go-to library to interact with SQL databases. https://cljdoc.org/d/com.github.seancorfield/next.jdbc/1.3.8...

Consider the tutorial on the Kit website: https://kit-clj.github.io/docs/guestbook.html#guestbook_appl...

Seems like `core.async`: https://github.com/search?q=repo%3Ajepsen-io%2Fjepsen+core.a...

(As an aside: Missionary is a higher-level, more recent option in this area.)

How so?

What do you prefer?

(I quite like ClojureScript.)

Hakan and Steven used to be associated with Juxt, the makers of XTDB, but I don't see them listed on the Juxt About page anymore.

Elixir creator just entered the chat ;)

See https://news.ycombinator.com/item?id=38314074 for explanation

What is a good starting point to follow all the implications down the rabbit hole?

Sane defaults for most (all?) aspects of the run-of-the-mill CRUD app, a.k.a. "convention over configuration". Helps focus development energy on solving the problem at hand as opposed to on bike shedding or being slowed down due to decision fatigue.

AFAICT, one has to go with the conventions as far as possible. Straying off the beaten path can lead one to lose time fighting the framework.