AFAIK everything was dropped in the end, and people went back to using audacity

I dislike that it takes way too long to boot

1. Use the Daemon, it starts a new client in a fraction of a second
2. Improve your config and it’ll start in under a second anyways

Emacs had some “premade IDE” project I recall that I tried and wasn’t that enthusiastic about.

Doom Emacs, spacemacs, etc.

And there are plenty of nvim “distros” like that (lazyvim for example).

They make getting started pretty easy. I’ve been using Doom for years and never bothered to make a full config of my own.

AI is quite fit for the task of understanding

Sure, and parrots are amazing at spotting fallacies like cherry picking…

Icy peepee

Or

I see peepeee

???

Inb4 it becomes/is a subsidiary of the NSO group…

Zerowriter Ink should get up to a week of battery life

ESP strikes again…

Hell no, Emacs and nvim UX is far superior. I won’t ever go back to clicking.

https://rosettacode.org/

And I think they rewrote a bunch of C libraries in order to have a better cross-platform compiler for C and zig. Or something along those lines

You can’t replace it.

Zig?

https://www.gnu.org/licenses/license-list.en.html

GPL is hard or tough to monetize

What do you mean?

stuff will get even spicier when we have conservations whether code is asset itself (especially scripts).

That’s true. What about LGPL?

Sure, but if you do that, and then follow it up with often outage and security issues, I’m going to seriously rethink using your services.

Oh, yes we have. Gitlab, Codeberg, Notabug, etc. You can even host your own Gitea or Forgejo instance if you want.

Self-hosting is right out for most people. It’s pretty expensive to even get started without compromising your home network (router with VLAN, switch, multiple servers (at least thinclients)), and then on top of that you need to maintain it, and can’t really ever max out your download/upload speeds because people are depending on your internet to interact with the repo.

Gitlab is also for-profit, but also has blackouts and devs going rm -rf on the production DB. It’s often in the news for bad things, so I’ve generally avoided it.

Codeberg is great for personal repos, but most smaller git hosting services have horrible SEO. Like I’ve had issues finding repos when searching for their exact name, if I had to use general search terms I’d only see github repos.

Gitlab: For profit (wouldn’t say it’s much better than github)

It’s got that added excitement that comes with a risk of someone doing a rm -rf on the production DB

e.g. don’t touch AGPL code unless you also use AGPL

Just to clear this up: copyleft licenses, GPL variants for example, require the license of your code to equally preserve the freedoms provided to your users, or in other words also be a copyleft license. There are some loopholes like GPL on a server, but be very careful when using copyleft code unless you want to use a copyleft license as well.

It gets somewhat murkier when you use someone’s code and base yours on that. IANAL, and that’s very much the legal territory. If at all possible, just reuse the original copyright and license and then derive your work (given the license allows that).

That all depends on the license AFAIK, but IANAL. Most FOSS licenses allow you to do whatever you want while preserving copyright claims, and that includes rewriting or changing the license. GPL forces copyleft, so even if you rewrote it from scratch, you could still be liable if you saw the original code.

For example I’ve heard that corpos bootleg copyleft code by having completely separate teams doing design and implementation. The implementation team can’t ever see any part of the original code, and they have limited communication with the design team. I think that would also go around the copyright claims as well.

If at all possible, just reuse the original copyright and license and then derive your work (given the license allows that).

Or just slap a GPL and subsume everything within a vortex of FREEDOM, and thusly become a true FOSS dude

there are very few “starter” Clojure jobs; they mostly expect you to have years of experience.

That’s because the language is made for people who wrote java for the last 10 years. It’s cool and all, but it’s horrible for learning programming when you compare it to cl or scheme. Neither of them break language uniformity and simplicity in order to accommodate java interop, while also having decades worth of excellent teaching material.

It’s a Lisp language which is the oldest kind.

Fortran, COBOL, ALGOL are older

Instead of “object oriented”, I think if it as verb oriented. Each statement is a verb (function) possibly followed by all the nouns you want to apply it to. Easy peasy, right?

I think you’re over complicating the explanation, it’s just a different notation:

(1 + 2 + 3) == (+ 1 2 3)

(1 + (2 * 3)) == (+ 1 (* 2 3))

People complain that there’s “too many parentheses”. People like to complain about dumb stuff.

I think it’s got more to do with everything seemingly being completely different. Most languages have C-style syntax, and python is like the only popular exception. It’s like knowing only latin and having to learn cyrilic or alphabet.

It’s not pretty, but it’s uniform, obvious, and easy to understand.

go is good grug friend who chase away complexity demon by limit damage of big brain developer

Julia, Clojure and Go. Are any of these good for a beginner or should I start with something else?

That totally depends on what you want to do.

Go should be easiest since it’s purposefully simplified in order to make learning it easier. There are some more difficult concepts, but the start should be easy enough. I know about go with tests, but it’s not really programming beginner friendly.

I’d avoid clojure as a beginner. It’s more for people who know java, but don’t want to write java. Common lisp and schemes are good for learning programming, but they’re not a popular group of languages and that can be a problem.