e3bc54b2

Thanks, I wondered why my router kernel went from 4.xx to 6.1 after flashing OpenWRT, especially when MediaTek is notorious for poor kernel support. This actually makes me respect OpenWRT even more.

Boy am I glad I replaced stock firmware with OpenWRT the moment my router came out of box last week. It was also extremely painless experience, and I'd really recommend people to buy routers with OpenWRT support, even if they cost a little more. A router is something you buy for a decade or more, and it's worth the investment. Our livelihood depends on network availability, and depending on whims of terrible router firmware is not something to rely on.

It doesn't has to match rustc on nightly, only the 3-yearly releases. That seems doable, considering Rust has slowed down a bit, compared to super fast pace of change in early years. Regardless, it is always good to have alternate implementations, C++ has only benefited from it.

There is a tree-sitter parser in the works and neovim plugin is already using it.

I think that makes more sense than full blown LSP.

Usually this is done by means of Enumerated types. As someone who didn't get conventional CS education, Enums were bit of me-too for me, but the moment I realised they can be used to make invalid states unrepresentable, I was hooked.

Sure, they can be better in java, but they cover a large enough ground, and as always, most people find that sufficient.

KeepassXC for password management and Syncthing for syncing across devices. Everything I'd available offline and syncs on network availability. Working well for years now.

Rust (what I consider to be gold standard at this point), Java, C#, Clojure (piggy-backs on Java/Maven).. Hell, even Emacs-lisp has better dependency management because lack of dependency version control has established strong backwards compatibility culture within community.

Python has neither standard tooling (de facto nor de jure), has no consensus within community where everyone seems to invent their own yet-another-dependency-management-tool and no culture of preserving strong backwards compatibility (never mind the core 2->3 transition).

direnv has integration with old nix shell as well as new nix develop. It also happens to have lot more editor integration that can utilize nix indirectly instead of not having access to nix at all.

Yeah, Python's dependency management is already abysmal, but when lower level language modules get involved its suddenly whole different level of hell. This actually put me off Python entirely. Sadly no real alternative in ML.

AOT is coming in 29.1.

> about 10% maintains an elisp package

IMO that is probably better than most other ecosystems where this percentage is often 1-3%.

> about 90% can program in elisp

Emacs doesn't really make a distinction between user and developer, and its a major driving principle behind the whole endeavor.

> makes me suspect the outcomes are skewed

Very much possible. But the survey was advertised over HN, matrix, IRC and Reddit. The last being a lot more 'general' audience than other 3, which I expect skews other ways. Anyway, knowing what Emacs is itself is a selection bias, so this is hardly unexpected.

> or emacs is doomed

If current breakneck speed of development of core Emacs as well as ecosystem at large is any indicator, I'm not preparing the doomsday shelter any time soon :)

Thanks for BOFH. Whole series is genius!

Not to mention the humongous pile of Elisp written over 40 years of its existence is hard to be backwards compatible with for any new implementation.

Emacs' core isn't known to be the best codebase in existence, but it is battle hardened and hard to replicate.

Here you go: https://github.com/a-schaefers/systemE

It is not stalled, but as it currently stands, Henrik is bottleneck. He used to work like a fiend, but obviously its not sustainable for one guy to keep carrying on for something with as large scope as an Emacs distribution.

There are plans to split doom-emacs' core and contrib modules in separate modules, but no idea what the progress is on that.

They had multiple issues with opsec in the past. Something that when repeats, makes people skittish. Fool me once and al..

For what its worth, Scrubs did put a real number in one of their episodes. They had a real phone that went around being answered by cast & crew and everyone had a blast. They remember it quite fondly.

2000s were a different time.

> Was there any reason for that?

Perfect is the enemy of good, and good enough is the perfect enemy of better.

Unix/Linux were/are good enough for vast majority of world's needs. So anything better is not worth the hassle.

I tried to look around, but is there a blog or something detailing before/after/why etc.? Should be very interesting read..

Tangential, but what's the best way to get Elixir dev environment with database on Windows?

A friend and I have been trying it for a project and for a NixOS dweller like me it was less than 2 minutes of work. But for her it has been never ending troubles.

Otherwise, Elixir and Phoenix are fantastic! No explicit JavaScript is necessary and that alone sells it for me, but the concurrency story is so easy to grok that I'm amazed nobody else managed to recreate it in so many years..

It doesn't matter how many people are on twitter, because all the journalists are already there. They pick the official's tweets and turn it to news.

There seems to be okay-ish activity on the repo: https://github.com/triplea-game/triplea/commits/master

Pretty sure Target use{sd} it, because they're the ones who sponsored original flakes implementation.

You are right of course. NixOS ain't for the faint of heart.

OTOH it finally got me over my fear of being a n00b and just use the source.

Neither does Apple. Beyond providing initial download the apps run on phones paid for by users and any back end runs on servers paid for by developer.

> Only projects that sign in are receiving funds.

Are you also only receiving funds for projects that sign in?

Otherwise it seems awful lot like impersonating someone else and withholding money until they finally sign into your platform.

CI can definitely done on mailing lists. The interface is bit worse than PRs, but I'm sure with enough imagination that can be overcome.

Pulling local trees has been absolutely better IMO with mailing list. I can literally with single keybinding apply patch to relevant repo, something that takes much longer route with Github. (convert URL to raw.github/whatever, copy and paste to apply, or do clicky-clicky in the Github app or whathaveyou)

My personal experience has been very opposite.

All the relevant mailing lists for my interest projects have web interface/archive, I can selectively reply/participate in any or no ongoing threads, and stop at any time.

As someone who formerly used to be in no-ML camp, I am proudly converted. Mailing Lists are decidedly democratic, and have least barrier to entry. It is also technically superior in providing unified interface to patches, communication, bug reports and everything adjacent.

Compared to that any fancy service provides lock-in under thin veil of "friendly interface".

I agree. I can't even remember why I was so scared of trying out email + path workflow, but after trying it for just 1 time I was convinced. It is so obviously good way to manage patches, you get a unified interface to bugs, patches, communication and everything in-between.

I can understand some folks not wanting to do initial setup and sourcehut already provides a nice web interface for it. But for actually contributing stuff emails are pretty unbeatable IMO.