smartmic

Off topic: nice, retro website look!

Buzzword bullshit bingo is a must for anyone who wants to ride the hype.

The most absurde thing is that nobody will ever read those notes, transcripts anyhow.

The most important information is this:

participants will contribute engineering resources

If it works out as planned, we will see. Apart from this, I am not overwhelmed by the claim of this project. It favors centralization and corporate circles, exactly the opposite of what the hacker ethics promotes for good reasons.

Btw this was initially coded without AI, but I've used it for the recent clean up and features

Then it makes sense to update the submission title. To me it reads as if the project was written completely without the help of AI (which might be a quality badge to some), but it is not 100% true then.

Anyhow, cool project ;)

The path is not closed; it must be earned through trust. It has always been this way. Also, note that "pull requests" are a GitHub invention; the concept is not native to Git or most other SCM systems. Before, you would have to submit your patch by email. It would be reviewed by the "maintainer" (or BDFL), who would then accept or reject it. If your contributions are accepted several times, you may be able to earn the rank of "maintainer."

Returning to the topic at hand, the challenge for new developers is to earn trust. I bet there are ways to do so aside from the muddy swamp of GitHub's (AI) bazaar.

There are great Open Source projects doing fine with the cathedral style, just look at Sqlite and its siblings (Fossil, …).

So I do not see a problem with Ladybirds decision, in contrary, IMHO it strengthens the human aspect of software development and puts the brakes on AI free riders

I am happy with https://github.com/pyrmont/churlish

Not by me, but by the mods. They also changed from "full of hallucinations" to "and most citations were hallucinated". Maybe a rep from "EY Global" filed a complain ;)

This is a refreshing attitude!

Well, I think the attitude is that costs are allowed to escalate faster and more steeply than the features delivered. From that perspective, semantic versioning is a handy tool for adjusting pricing strategies. IMHO, it (versioning) only makes sense for open-source projects, where you can clearly see the actual changes made with each version upgrade. Anything else is more than a little suspicious…

I am a happy user of dateutils [0], but I will try out Biff and see which one is more ergonomic.

[0] https://www.fresse.org/dateutils/

As is often the case in the GenAI space, this also appears to be a solution to a non-existent problem.

Can't comment on Mercurial, but "for all my personal project where I don't need to care what anyone else thinks" I am using Fossil. Ever since that decision, I've felt a bit, well, held back, or rather, I don't feel quite as comfortable as I do at home when I have to use Git.

A culture rooted in φιλοσοφία (greek, philosophia in Latin). So yes, I meant that literally. There were times, already 2500 years ago, where people wanted to study to become wiser.

It is worth to have a detailed look into the original essay and its arguments. My interpretation is https://smartmic.bearblog.dev/no-ai-silver-bullet/

I only work with LLMs in domains I'm expert in

This. Should become a general rule for any non-trivial use of LLM in a professionel setting.

Advertising prominently with "AI native" seems necessary today, at least for some folks. To me, that's kind of off-putting, since it doesn't really say anything.

Can anyone of the AI enthusiasts here explain, why, or, what is meant by

As a compiled, statically-typed language, it's also ideal for agentic programming.

Many comments here to your creation, PeakSlab, but not yet a dedicated praise. I didn't know it but I have to say it is really cool and innovative! The performance of the dictionary is indeed superb and I will definitely bookmark this for future reuse. So, in a nutshell: thanks for sharing!

I'm sure it was very difficult to program in machine code, but if now (or soon) anyone can just write software using a LLM without any sort of learning it changes everything. LLMs can plan and create something usable from simple instructions or ideas, and they will only get better.

Did you read the section "Power to the People?" ? In it, the author dismantles your thesis with powerful, highly plausible arguments.

If you're interested in Fred Brooks's "No Silver Bullet," I also explored it in the context of LLMs: https://smartmic.bearblog.dev/no-ai-silver-bullet/

I wonder, isn‘t any Lisp, be it Clojure, Scheme, etc. not exactly suited for such tasks?

Many CLI tools, SDKs, and frameworks collect telemetry data by default.

Any of those are using a dark pattern and before exploring new ways to opt out you should look for and spend your energy on an alternative which respects your freedoms upfront.

I am currently enjoying WYSIWYG with GNU TeXmacs for long-form or scientific text editing. Both, the concept and the tool, are amazingly capable and a breath of fresh air after all the LaTex, Markdown, Org s …

Gone are the days of deterministic programming, when computers simply carried out the operator’s commands because there was no other option but to close or open the relays exactly as the circuitry dictated. Welcome to the future of AI; the future we’ve been longing for and that will truly propel us forward, because AI knows and can do things better than we do.

Have a look at Janet. It is not as powerful as Clojure but for smaller projects, prototyping, scripting etc., it is really enjoyable.

https://janet-lang.org/

A System „Card“ spanning 244 pages. Quite a stretch of the original word meaning.

Correct[0]. This was also my first thought after reading

Unfortunately, unlike many other languages, SQLite has no formal specification describing how it should be parsed. It doesn’t expose a stable API for its parser either. In fact, quite uniquely, in its implementation it doesn’t even build a parse tree at all9! The only reasonable approach left in my opinion is to carefully extract the relevant parts of SQLite’s source code and adapt it to build the parser I wanted

Did they made a proper problem research in the first place?

[0] https://sqlite.org/lemon.html

AIpocalypse. Eaten too much Copilot dog food.

AI has become a commodity- for the better or worse. And yes, we should treat it as such, especially no more big ideas from (C-level) managers, please.

It’s only too late when we stop fighting back and accept it as a given. Don’t underestimate civil disobedience and the hacker spirit.