> I feel like Github actions should just be a call to some bash or python file. Bash has its issues so I prefer python
...and that's how it is supposed to be used. The YAML file is mainly there for defining the runtime environment (e.g. the operating system or docker image to run in), and to describe the job dependency tree. The actual actions to execute should be delegated to scripts outside the GH YAML.
GH Actions isn't great compared to other CI systems, but it's also not particularly worse until you get into the nitty gritty details.
The most important advice is probably to put as much code as possible into locally runnable scripts written in a cross-platform scripting language (e.g. Python or Node.js) to avoid 'commit-push-ci-failure' roundtrips.
Only use the GH Actions YAML for defining the runtime environment and job dependency tree.
Maybe you don't use the mouse because it just doesn't work as expected? ;)
> So I am wondering, are people fighting using a Mac in the most effective way simply because of old patterns and habit
"Most effective" doesn't mean "most intuitive". I don't want to learn keyboard shortcuts just to move or resize a window. That's the entire premise of graphical user interfaces.
Windows Vista may have been plagued by programs assuming administrator access for everything but at least it isolated the security prompt.
You can verify that you're interacting with a real UAC prompt (by pressing ctrl+alt+delete for instance, which can be configured to he required before approving a prompt).
Any program can replicate the macOS security dialogs. You just have to hope that you can safely enter the password to your account into one, or activate TouchID when prompted.
I don't know if any of the links below will count as crying; but here are some, from the British media reporting on Russia:
- BBC, 2018: Russia: Google removes Putin critic's ads from YouTube https://www.bbc.co.uk/news/technology-45471519
- BBC, 2021: How Russia tries to censor Western social media https://www.bbc.co.uk/news/blogs-trending-59687496
- BBC, 2021: Russia slows down Twitter over 'banned content' https://www.bbc.co.uk/news/world-europe-56344304
- BBC, 2021: Russia threatens YouTube ban for deleting RT channels https://www.bbc.co.uk/news/technology-58737433
- BBC, 2021: Russia threatens to slow down Google over banned content https://www.bbc.co.uk/news/technology-57241779
- Reuters, 2022: Russia blocks access to BBC and Voice of America websites https://www.reuters.com/business/media-telecom/russia-restricts-access-bbc-russian-service-radio-liberty-ria-2022-03-04/
- The Guardian, 2022: Russia blocks access to Facebook and Twitter https://www.theguardian.com/world/2022/mar/04/russia-completely-blocks-access-to-facebook-and-twitter
- BBC, 2022: Russia restricts social media access https://www.bbc.co.uk/news/technology-60533083
- BBC, 2022: Russia confirms Meta's designation as extremist https://www.bbc.co.uk/news/technology-63218095
- BBC, 2024: Data shows YouTube 'practically blocked' in Russia - https://monitoring.bbc.co.uk/product/b0003111
- BBC, 2024: Russia's 2024 digital crackdown reshapes social media landscape - https://monitoring.bbc.co.uk/product/b0003arza
"The EU condemns the totally unfounded decision by the Russian authorities to block access to over eighty European media in Russia.
This decision further restricts access to free and independent information and expands the already severe media censorship in Russia. The banned European media work according to journalistic principles and standards. They give factual information, also to Russian audiences, including on Russia’s illegal war of aggression against Ukraine.
In contrast, the Russian disinformation and propaganda outlets, against which the EU has introduced restrictive measures, do not represent a free and independent media. Their broadcasting activities in the EU have been suspended because these outlets are under the control of the Russian authorities and they are instrumental in supporting the war of aggression against Ukraine.
Respect for the freedom of expression and media is a core value for the EU. It will continue supporting availability of factual information also to audiences in Russia."[0]
FWIW the native and WASM versions of my home computer emulators are within about 5% of each other (on an ARM Mac), e.g. more or less 'measuring noise':
Maybe the emulator code is particularly WASM friendly ... it's mostly bit twiddling on 64-bit integers with very little regular integer math (except incrementing counters) and relatively few memory load/stores.
Yet still the 'raw' pixel data of old games rendered on modern displays without any filtering also doesn't look anything like they looked on CRT monitors (and even on CRT monitors there's a huge range between "game console connected to a dirt cheap tv via coax cable" and "desktop publishing workstation connected to professional monitor via VGA cable").
All the CRT shaders are just compromises on the 'correctness' vs 'aesthetics' vs 'performance' triangle (and everybody has a different sweet spot in this triangle, that's why there are so many CRT shaders to choose from).
This CRT shader actually has a flicker slider. But 'brain melting flicker' sounds more like you were gaming with a 50Hz PAL console (or home computer) on a professional computer monitor which was intended for higher frequencies (like 72Hz). Regular TVs normally had plenty of 'afterglow' to reduce flicker.
...and that's how it is supposed to be used. The YAML file is mainly there for defining the runtime environment (e.g. the operating system or docker image to run in), and to describe the job dependency tree. The actual actions to execute should be delegated to scripts outside the GH YAML.
reply