Jarkko Sakkinen
Posts
4463Following
315Followers
474OpenPGP: 3AB05486C7752FE1
The main budget hit comes obviously from CI.
Also, #Woodpecker #CI usability for local builds could be perhaps improved, in order lower the barrier to do them (and to get that done, it would require money for sponsorship/bounty/grant).
Also, #Woodpecker #CI usability for local builds could be perhaps improved, in order lower the barrier to do them (and to get that done, it would require money for sponsorship/bounty/grant).
0
0
0
Jarkko Sakkinen
jarkko
Edited 1 year ago
#Wikipedia has a great coverage on what #Codeberg is all about:
https://en.wikipedia.org/wiki/Codeberg
I'd like to see actors like EU and Linux Foundation give some donations/funding/hosting for the sake of providing non-profit but still easy to use and competitive Git hosting for the open source ecosystem (but that is not up to me).
https://en.wikipedia.org/wiki/Codeberg
I'd like to see actors like EU and Linux Foundation give some donations/funding/hosting for the sake of providing non-profit but still easy to use and competitive Git hosting for the open source ecosystem (but that is not up to me).
1
0
0
Stimulus to try out Codeberg came from looking for a plugin for enabling matrix in irssi: https://codeberg.org/ticho/irssi-matrix
Codeberg is clean and snappy, and so much less noisy than Gitlab and Github. I move my own projects and hacks here, and only use aforementioned for upstream contributions from now on.
Codeberg is clean and snappy, and so much less noisy than Gitlab and Github. I move my own projects and hacks here, and only use aforementioned for upstream contributions from now on.
0
0
1
It took me hours to figure out that I need a branch called pages for deploying the generated content in .woodpecker.yml.
Even after figuring out that I could not find any information on how to first initialize it, so here’s how I did it:
git checkout --orphan pages
git rm -rf .
git commit -a --allow-empty --allow-empty-message
This results nice empty commit, i.e. a commit which has neither payload nor commit message:
❯ git show
commit a6e593d5e8f3d75c3bb682762ac2940dc237080b (HEAD -> pages)
Author: Jarkko Sakkinen <jarkko.sakkinen@iki.fi>
Date: Tue Jun 18 06:02:33 2024 +0300
After a single CI run:
❯ git n log
commit 05e254e5d6b2dc8c29ac2d36ddfa68b9b1d56d2f (HEAD -> pages, origin/pages)
Author: Codeberg CI <jarkko.sakkinen@iki.fi>
Date: Tue Jun 18 03:08:27 2024 +0000
CI a7dc6158185fa87bc6d31431e417a10a00c6a6f8
commit a6e593d5e8f3d75c3bb682762ac2940dc237080b
Author: Jarkko Sakkinen <jarkko.sakkinen@iki.fi>
Date: Tue Jun 18 06:02:33 2024 +0300
Gives expected results so I guess this works :-)
1
0
1
Jarkko Sakkinen
jarkko
Migrating my stuff from #Github and #Gitlab to #Codeberg. The first successful CI run done. And seems to generate legit results: https://jarkko.codeberg.page/ #Woodpecker #CI
1
0
2
@codrusofathens wasm had no previous "dominator", Rust came out with right timing and as a language it fits quite well to the wasm architecture. In all other domains there's something already existing, which people find useful and productive.
0
0
0
@codrusofathens
Rust is pretty much owning WebAssembly at least. For wasm it is almost like what C is for bare metal.
So one probably quite widely used web stack in future has along the lines these layers:
1. JavaScript/TypeScript as orchestrator
3. Rust compiled into wasm as "client-side" latency backend.
3. Java in the "server-side" backend.
Makes sense because more stuff can offloaded to the client. For large batch computations Java is pretty solid, but for more latency sensitive stuff you'd want to use Rust.
And obviously it makes sense in any possible business to scale down the amount of investment to the "new", or like find a sweet spot for that investment...
Rust is pretty much owning WebAssembly at least. For wasm it is almost like what C is for bare metal.
So one probably quite widely used web stack in future has along the lines these layers:
1. JavaScript/TypeScript as orchestrator
3. Rust compiled into wasm as "client-side" latency backend.
3. Java in the "server-side" backend.
Makes sense because more stuff can offloaded to the client. For large batch computations Java is pretty solid, but for more latency sensitive stuff you'd want to use Rust.
And obviously it makes sense in any possible business to scale down the amount of investment to the "new", or like find a sweet spot for that investment...
1
1
0
@codrusofathens
Rust is pretty much owning WebAssembly at least. For wasm it is almost like what C is for bare metal.
So one probably quite widely used web stack in future has along the lines these layers:
1. JavaScript/TypeScript as orchestrator
3. Rust compiled into wasm as "client-side" latency backend.
3. Java in the "server-side" backend.
Makes sense because more stuff can offloaded to the client. For large batch computations Java is pretty solid, but for more latency sensitive stuff you'd want to use Rust.
And obviously it makes sense in any possible business to scale down the amount of investment to the "new", or like find a sweet spot for that investment...
Rust is pretty much owning WebAssembly at least. For wasm it is almost like what C is for bare metal.
So one probably quite widely used web stack in future has along the lines these layers:
1. JavaScript/TypeScript as orchestrator
3. Rust compiled into wasm as "client-side" latency backend.
3. Java in the "server-side" backend.
Makes sense because more stuff can offloaded to the client. For large batch computations Java is pretty solid, but for more latency sensitive stuff you'd want to use Rust.
And obviously it makes sense in any possible business to scale down the amount of investment to the "new", or like find a sweet spot for that investment...
1
1
0
Jarkko Sakkinen
jarkko
Edited 1 year ago
Installed gh (cli.github.com) for the sake of convenience of being able to do this:
gh release download v2.6.0 -R woodpecker-ci/woodpecker
Jarkko Sakkinen
jarkko
@oranki This is a valid point!
And simple batched sync's with rclone have been much nicer 99% of the time nice behavior as far as I'm concerned.
Sometimes tho would be nice to have quick real-time sync'd access. So what I do instead is that I simply run it at localhost 🤷 Then I know at least when I spending my quota, right? :-)
Thanks for the comment! Was a money saver...
And simple batched sync's with rclone have been much nicer 99% of the time nice behavior as far as I'm concerned.
Sometimes tho would be nice to have quick real-time sync'd access. So what I do instead is that I simply run it at localhost 🤷 Then I know at least when I spending my quota, right? :-)
Thanks for the comment! Was a money saver...
0
0
1
@codrusofathens ... and counter arguments are 90% of time qualitative arguments, e.g. "we have this contract/abstraction/invariant so you're wrong".
I only believe in quantitative arguments for the most part. E.g. spec growth is one of such, e.g. you can compare that to a spec that does not grow. Would be foolish to think that spec growth does not have a negative impact to static analysis.
But for any quantitative arguments it is hard to say anything conclusive. Can't beat Gödel's theory of incompleteness, right? ;-)
I only believe in quantitative arguments for the most part. E.g. spec growth is one of such, e.g. you can compare that to a spec that does not grow. Would be foolish to think that spec growth does not have a negative impact to static analysis.
But for any quantitative arguments it is hard to say anything conclusive. Can't beat Gödel's theory of incompleteness, right? ;-)
0
0
1
@codrusofathens and the whole narrative that Rust almost invented memory safety is like totally untrue.
E.g. in the backend Java has delivered the whole gist of memory safety literally decades and JVM's JIT is a monster dealing with server payloads... It is optimized by the best breed of Intel, ARM etc. companies for each micro-architecture.
When looking at beyond the hype I feel that there's exactly one area where I find Rust best tool so far: cli-interfaces. For tpm2-cli I chose Rust because input validation was easier with it than in my previous python experiments (I've done a small Python based stack for kselftest previously).
Not a revolution really ;-)
E.g. in the backend Java has delivered the whole gist of memory safety literally decades and JVM's JIT is a monster dealing with server payloads... It is optimized by the best breed of Intel, ARM etc. companies for each micro-architecture.
When looking at beyond the hype I feel that there's exactly one area where I find Rust best tool so far: cli-interfaces. For tpm2-cli I chose Rust because input validation was easier with it than in my previous python experiments (I've done a small Python based stack for kselftest previously).
Not a revolution really ;-)
2
0
1
Jarkko Sakkinen
jarkko
@codrusofathens yeah, it is f*****g horror story how this plays :-) absolutely hate rusty forking culture.
1
0
0
@hunger I do like Rust, I'm using it too, and have contributed to some upstream projects features and also have some things of my own going on too (still unreleased ASN.1 to bytecode compiler, and alternative super light-weight TPM2 stack).
I just generally learn best by applying "learn by hate"-methodology ;-)
Like when doing kernel dev, I look Linux more like how bad it is, and from that angle I find ways to improve it. And even look into how great NT kernel or Darwin are doing some things, whereas Linux is under-performing.
I just generally learn best by applying "learn by hate"-methodology ;-)
Like when doing kernel dev, I look Linux more like how bad it is, and from that angle I find ways to improve it. And even look into how great NT kernel or Darwin are doing some things, whereas Linux is under-performing.
1
0
0