GitTrends VS FFmpeg

Thanks for the kind words!

I’ve also published an open-source iOS + Android app to the App Stores, called GitTrends that leverages my AsyncAwaitBestPractices library if anyone wants to see how to use it in a real/live production app!

The source code for GitTrends is available here: https://gittrends.com

On the bright side, I was able to push a new App Store release for my Xamarin.Forms app, GitTrends, which I couldn't do previously in VS for Mac 2022 Preview.

Here’s a couple open-source apps I’ve made that you can check out if you’re interested in how to use C# instead of XAML: - GitTrends - An open-source iOS and Android app built in Xamarin.Forms to monitor the Views, Clones and Star history of your GitHub repos - All UI is written in C# using the Xamarin.CommunityToolkit.Markup NuGet package - Also free to download from the iOS App Store and Google Play Store - HackerNews - An open-source .NET MAUI app for displaying the top posts on Hacker News that demonstrates text sentiment analysis of each headline gathered using artificial intelligence - All UI is written in C# using the CommunityToolkit.Maui.Markup NuGet Package

For example, here’s an open-source app I’ve published to the App Store, GitTrends, that doesn’t use any XAML.

Was GitTrends causing the trouble? I’d love to fix the bug if you found one!

I created an open-source app, GitTrends, that’s available for free on the iOS and Android app stores that could help.

GPL2

Since FFmpeg is GPL2, doesn’t that require CompressX to disclose its source code?

IANAL, apologies if I miss understand license requirements.

https://github.com/FFmpeg/FFmpeg?tab=License-1-ov-file

This turns out to be a lot of assembly macros to help write one x86 assembly. https://github.com/FFmpeg/FFmpeg/blob/master/libavutil/x86/x...

The sibling comment recommending compiler intrinsics is probably the best way to go for writing SIMD code. A mixture of `` style types and intrinsics to specify instructions is a solid 90% solution compared to assembly.

If you want that last 10%, I think macros are putting the emphasis in the wrong place. They're a somewhat easy way to build up a language abstraction which will work if held carefully, but I'm confident the dev experience using this abstraction when you write invalid code will be deeply confusing.

I would suggest to write a parser instead of the macros. That'll tell you clearly when the syntax is invalid (though possibly not with much precision) and it'll give you a place to put semantic analysis for where valid syntax encodes nonsense. Do the equivalent of the macro expansions on the parsed tree instead of on the text. Emit asm as the "back end".

You might have heard of FFMPEG or ImageMagick for image and video edition in a programmatic way. MoviePy is a Python module for video editing (Python wrapper for FFMPEG and ImageMagick). It provides functions for cutting, concatenations, title insertions, video compositing, video processing, and the creation of custom effects. It can read and write common video and audio formats and be run on any platform with Python 2.7 or 3+.

There are many cloud-based tools and websites that can convert your images, but the problem with these tools is that you usually have to upload the files for them to be processed, and some of their services are not free. In this article, I'd like to introduce a piece of software called FFmpeg, which allows you convert the images locally with one simple command.

To run the demo locally, be sure to have Python 3.11 and FFmpeg installed.