nexus VS homebrew-core

Nexus: https://github.com/jfilby/nexus

This is a web framework + ORM for Nim. It's in desperate need of more work to support DBs other than PostgreSQL and make the ORM more flexible. The web side also needs more work.

I use it mainly for high-performance backend engines. E.g. I'm writing an automated trading system and the trading engine is written in Nim.

I wrote a Nim web framework that has an ORM: https://github.com/jfilby/nexus. However I mainly use the ORM with the back-end engines. You could write a Django-style web app with Nexus + Nimja, but it's difficult to compete with the huge ecosystems of React and Flutter.

It's not good for Nim, unfortunately. The language is great, but the community isn't that big.

If you're looking for a web framework with an ORM for Nim, check out Nexus: https://github.com/jfilby/nexus

There's no Discord yet, just GitHub issues. Here's an issue to track this request: https://github.com/jfilby/nexus/issues/14

I'll email you regarding what/how to help.

Django is a great MVC framework. It might be overkill for a blog as another poster wrote, but it's still a good way to learn Django.

If you ever want to learn Nim, please consider Nexus (https://github.com/jfilby/nexus) as I'm building it to be something like Django for Nim.

Nexus is a Nim development framework.

https://github.com/jfilby/nexus

The aim to create a web framework similar to Django, with a built-in ORM. The view layer needs work, and is mostly built out of available libraries with Jester for routing and Nimja for templating.

Nexus Development Framework, for Nim, is now available: https://github.com/jfilby/nexus

Nim. It's just so quick and easy to write high performance code. That's why I'm writing a web framework for it, soon to be released: https://github.com/jfilby/nexus

$ brew info eza ==> eza: stable 0.18.13 (bottled) Modern, maintained replacement for ls https://github.com/eza-community/eza Not installed From: https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/e/eza.rb License: MIT ==> Dependencies Build: pandoc ✘, pkg-config ✔, rust ✘ Required: libgit2 ✘ ==> Analytics install: 12,792 (30 days), 38,295 (90 days), 68,375 (365 days) install-on-request: 12,790 (30 days), 38,293 (90 days), 68,375 (365 days) build-error: 0 (30 days)

Is disabling the compromised repo the typical GitHub policy? My concern is there are monorepos used by package managers, like brew, that are a collection of thousands of projects [1]. These monorepos seem like a prime target for attack and if GitHub disables one because a malicious commit was merged then you've taken down an entire ecosystem.

[1] https://github.com/Homebrew/homebrew-core

> Correct. Though we do not appear to be affected, this revert was done out of an abundance of caution.

[1] https://github.com/Homebrew/homebrew-core/pull/167512

> right, but now you know even less about your setup when you some roadblock

This is the same with a binary though. And with homebrew, you can't follow patches or flags used or if they change.

- https://github.com/Homebrew/homebrew-core/blob/c964ad7fa53ad...

definitely be careful about using fortune in a corporate environment or public space if you don't know what dat files you are using or you might just get an extremely unwelcome surprise.

I was practicing a presentation and used to use "fortune" all the time. I forget exactly what it output but I remember being absolutely mortified about what could have happened if that had popped up during an internal company tech talk.

Kudos to brew for keeping unsuspecting people safe

https://github.com/Homebrew/homebrew-core/commit/3fb3c4c3e55...

I'm sorry to be asking this as I find it a bit silly, but it's blocking my PR [3], so could a few of you star the project on Github [1] to get my PR to run?

[1] https://github.com/laktak/chkbit-py

[2] https://brew.sh

[3] https://github.com/Homebrew/homebrew-core/pull/160018