Partly, but Signal etc. could just as well have a fast and polished client, and Telegram a clunky electron sloth. Even if you restrict yourself to one device (so no syncing) the difference in quality is undeniable.
This argument works against all payment systems that are conceivably bannable (likely all of them). If a payment system doesn't collaborate, the government can ban it.
> The only thing stopping them is the sheer unpopularity of such an action.
This is the intended functioning of democracies I guess.
I personally searched for and couldn't find an app that gathered various random generation tools, like the ones on random.org (integer sequences and sets, dice, list shuffle...)
Other than that banking, transport, government apps are (almost) never on fdroid, but that's not something a weekend project can fix :)
If you want to set e-bikes folks' hair on fire, show how many shoes the government could buy for the cost of an e-bike distribution program. Then, apply that number to the population that would be served by those e-bikes.
I've recently installed (a maintained fork of) Krohnkite[0], a tiling WM for Plasma 6, and I'm happy with it so far after tweaking the key bindings.
Things I miss:
- a scratchpad;
- toggling back and forth between desktops/workspaces with super+number (e.g. super+3 goes to desktop 3, but if I'm already on 3 I want to go back to the previous desktop);
- I also miss a bit the "manual" tiling from i3/sway (where you can choose where the next split will be). Krohnkite is DWM-style with predefined layouts (two columns, spiral, monocle...).
Maybe some of this can be done on Plasma/Krohnkite too (for the third I doubt but it's low priority), I haven't really looked into that.
I've started using TW in the past days with the goal of setting up a cookbook + meal planner with nutritional values computes from the ingredients.
It feels very malleable/hackable, I'm happy with my progress so far, the biggest annoyance is that as far as I can tell the JavaScript API is not documented anywhere.
Initially I looked at Decker and LÖVE, but the former is not suitable for a phone screen and the latter isn't meant for UIs. I would have preferres a non-web solution but TW is a solid choice nonetheless.
Changes to Zig can still be very significant. I found myself stuck between a rock and an hard place when I found out that:
- Zig v0.11 doesn't have async/await, which I needed, because they haven't implemented it yet on the self-hosted compiler;
- I couldn't use v0.10 due to some bugs with comptime in the old compiler, which are solved in v0.11.
Still, while bold, I don't think it's totally unwarranted to tag Bun 1.0. They may have to put some extra effort here and there to work around the language's instability.
This is not a critique of the Zig team, they make it very clear that the language is not ready for production use yet.
1. The chance of getting popular support for a protest like this diminishes with the number of people you piss off. You may be able to earn some sympathy by targeting SUVs only, but doing the same with all cars wouldn't be a good strategy.
2. There are good reasons to own a car, and in some places a significant number of people may be justified in using one. Blanket targeting everyone would be unfair to those who really need it. By contrast, SUVs don't have any (significant?) utility over a regular car (other than ego boosting maybe...).
There's also the new Body Weight Strength Foundations (BWSF) Routine [0]. BWSF is the routine they now recommend, not to be confused with the Recommended Routine ;)
Thank you, from the other replies it seems like they would be enough for my needs.
> Would be curious to hear your thoughts on how they compare given your (presumed) background in functional programming.
I'm just a student with an interest in programming languages and very little knowledge and experience, so I don't think I'll be able to provide any significant insight ;)