forgefed
AECforWebAssembly
forgefed | AECforWebAssembly | |
---|---|---|
20 | 51 | |
982 | 31 | |
0.1% | - | |
5.5 | 8.0 | |
23 days ago | 8 days ago | |
Bikeshed | C++ | |
Creative Commons Zero v1.0 Universal | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
forgefed
- Gitlab's ActivityPub architecture blueprint
- PyPy has moved to Git, GitHub
-
Harness launches Gitness, an open-source GitHub competitor
If you don't mind me asking since you're here: will you be implementing ForgeFed in Gitness [0]? My sense is that federation is our best hope for breaking GitHub's network effects, and I'd love to see more projects like yours join the protocol.
[0] https://forgefed.org/
- ForgeFed
-
Gitlab's plan to support ActivityPub for merge requests
From the comments, Forgejo is also already working on implementing ForgeFed, an ActivityPub extension specifically designed for software forges [0]. Judging from the issue, it looks like they're well on their way [1].
I have to say, I'm not super into the idea of social media, but this is a use for federation I approve of wholeheartedly. The friction of having to create accounts on X forges (where X is the number of projects that self-host GitLab) is a huge moat for GitHub, and federation could solve that very handily and create an environment where FOSS projects can feasibly host their own code away from Microsoft's control without horribly inconveniencing everyone who wants to participate.
[0] https://forgefed.org/
[1] https://codeberg.org/forgejo/forgejo/issues/59
-
git-appraise – Distributed Code Review for Git
> I agree that e-mail is not perfect, but... how is GitHub better?
Please look at my comment again. I prefer email to locked in forges.
> Devs like new shiny toys, and e-mails are old technology
There is one aspect where such forges have an advantage over email - a better user experience. Aerc and the likes all good - but Github and others provide a good user experience over a tool that everyone uses - the web browser.
> we should have something better than e-mail in 2023
We really should have something better than email. I'm saying this as someone who operates a personal mail server and a bunch of desktop services for it. It's really hard to get the setup correct.
In that context, it's worth looking at forgefed (https://forgefed.org/). It's a protocol for federating forges like Gitea and Gitlab. It's built on top of ActivityPub - which behaves a bit like email (it has inboxes and outboxes for every user). From the spec, it seems like pull requests happen by sending patches to the destination forge.
> Nobody takes the time to try the e-mail workflow (even though it's really two git commands)
Email workflow seems simple. But there are two things that make it complicated:
1. The patches don't specify the commits they apply to. It's simply assumed that they apply to the head of the main branch. The commits have to be carefully rebased on the main branch before sending the patches. It could otherwise lead to conflicts and a lot of wasted time.
2. Each commit/patch is send as a single email. Developers usually make frequent commits when they develop. Such patches can be confusing and hellish to review. A sane patchset requires the developers to edit the commit history, usually using interactive rebases. Each commit should contain a single feature and shouldn't break the build.
I consider both the above to be good development practices and follow them even on my personal projects. However, this is an additional barrier to entry. In fact, this may be a bigger problem for many than setting up git for email.
-
Leveling Up Your Git Server: Sharing Repos with a Friend
Another interesting topic to look into is forge federation. Forgejo [0], the code forge on which Codeberg is based is one forge software that intends to federate their repositories between server instances over the network using ActivityPub protocol extensions such as ForgeFed [1] and F3 [2] specifications.
[0] https://forgejo.org
[1] https://forgefed.org
[2] https://lab.forgefriends.org/friendlyforgeformat
- Sono Moreno di Morrolinux. AMA!
-
Let's Make Sure Github Doesn't Become the only Option
> If you want to look into people who disagree with you: https://forgefed.org/
AECforWebAssembly
-
Gren 0.3: Source maps
Great! I have not yet made source maps for my programming language that compiles to WebAssembly, and I probably never will.
- Mislite li da okolina ima potpuno pogrešno mišljenje o ljudima koji rade u IT-u?
- Koja je najapsurdnija poruka o pogrešci koju je neki vaš program ispisivao?
-
What is the most absurd error message your compiler/interpreter was once outputting?
Up until today, my AEC-to-WebAssembly was, if somebody tried to use two structures of different types as the second and the third operand to the ?: (ternary conditional) operator, as in this example: ``` Structure First Consists Of Nothing; EndStructure
- Poteškoće s pronalaskom posla
-
Good languages for writing compilers in?
Well, I have written the first compiler for my programming language, targetting x86, in IE6-compatible JavaScript, and the second compiler, targetting WebAssembly, has been written in C++11. I think that, to choose a language to write a compiler in, you need to look at at least two things:
-
Why does GCC run in Docker produce around 30% smaller statically linked C++ executables than GCC run on Linux? AECforWebAssembly is 1.08 MB large if compiled using GCC 13.1 in Docker, but it is 1.59 MB if compiled using GCC 13.1 on Debian.
You can see the releases v2.5.3 and v2.5.2 of AECforWebAssembly on GitHub. They are produced with the same version of GCC, the only difference (as far as I know) is that v2.5.2 was produced directly on Debian, whereas v2.5.3 was cross-compiled from Windows to Linux using Docker.
-
Let's Make Sure Github Doesn't Become the only Option
That could be true. I host my AEC-to-WebAssembly compiler on GitHub, GitLab and SourceForge, and it's only on GitHub that it has 21 stars and 2 forks. On GitLab and SourceForge, it has zero of both.
- koliko vam je bilo tesko nac posao u programiranju?
-
Does the JVM / CLR even make sense nowadays?
Well, the main compiler for my programming language is targetting the JavaScript Virtual Machine by outputting WebAssembly. I think it's even better than targetting Java Virtual Machine, because, for one thing, your executables can run in any modern browser if you output WebAssembly. If you target Java Virtual Machine, the users need to actually download your app. Furthermore, there is an official assembler for WebAssembly called WebAssembly Binary Toolkit (WABT), so your compiler can output assembly and not have to deal with binary files. There is nothing equivalent to that for Java Virtual Machine.
What are some alternatives?
kyoto - Golang SSR-first Frontend Library
Lark - Lark is a parsing toolkit for Python, built with a focus on ergonomics, performance and modularity.
gitness - Gitness is an Open Source developer platform with Source Control management, Continuous Integration and Continuous Delivery.
wasm-fizzbuzz - WebAssembly from Scratch: From FizzBuzz to DooM.
cicada - A FOSS, cross-platform version of GitHub Actions and Gitlab CI
mal - mal - Make a Lisp
killed-by-microsoft - Part guillotine, part graveyard for Microsoft's doomed apps, services, and hardware.
Drogon-torch-serve - Serve pytorch / torch models using Drogon
git-appraise - Distributed code review system for Git repos
libCat - 🐈⬛ A runtime for C++26 w/out libC or POSIX. Smaller binaries, only arena allocators, SIMD, stronger type safety than STL, and value-based errors!
gitlab
gdal-js - This is an Emscripten port of GDAL, an open source X/MIT licensed translator library for raster and vector geospatial data formats.