squoosh VS Mono

Image optimizer: Squoosh your images for better performance

I'm increasingly building entire functional prototypes from start to finish using Claude 3.5 Sonnet. It's an amazing productivity boost. Here are a few recent examples:

https://tools.simonwillison.net/image-resize-quality is a tool for dropping in an image and instantly seeing resized versions of that image at different JPEG qualities, each of which can be downloaded. I used to use the (much better) https://squoosh.app/ for this, but my cut-down version is optimized for my workflow (pick the smallest JPEG version that remains legible). Notes and prompts on how I built that here: https://simonwillison.net/2024/Jul/26/image-resize-and-quali...

django-http-debug - https://github.com/simonw/django-http-debug - is an actual open source Python package I released that was mostly written for me by Claude. It's a webhooks debugger - you can set up a URL and it will log all incoming requests to a database table for you. Notes on how I built that here: https://simonwillison.net/2024/Aug/8/django-http-debug/

datasette-checkbox is a Datasette plugin adding toggle checkboxes to any table with is_ or has_ columns. Animated demo and prompts showing how I built the initial prototype here: https://simonwillison.net/2024/Aug/16/datasette-checkbox/

https://tools.simonwillison.net/gemini-bbox is a tool for trying out Gemini 1.5 Pro's ability to return bounding boxes for items it identifies. You'll need a Gemini API key for this one, or take a look at the demo and notes here: https://simonwillison.net/2024/Aug/26/gemini-bounding-box-vi...

https://tools.simonwillison.net/gemini-chat is a similar tool for trying out different Gemini models (Google released three more yesterday) with a streaming chat interface. Notes on how I built that here: https://tools.simonwillison.net/gemini-chat

I still see some people arguing that LLM-assisted development like this is a waste of time, and they spend more effort correcting mistakes in the code than if they had written it from scratch themselves.

I couldn't disagree more. My development process has always started with prototypes, and the speed at which I can get a proof-of-concept prototype up and running with these tools is quite frankly absurd.

Online Converters: Websites like Squoosh or Convertio allow you to easily convert images to WebP.

Use an image conversion tool or software like Photoshop, GIMP, or an online converter (e.g., Squoosh) to convert your PNG or JPEG images to WebP format.

Squoosh

This ensures security for sensitive content. (https://squoosh.app/)

Image optimizer: Squoosh your images for better performance

Here's another handy tool that I use: https://squoosh.app/

For everyone who is confused by what is going on, here's the explanation:

Today, there are 2.5 Mono's:

Mono that lives in https://github.com/mono/mono. This is the original Mono codebase that was written back then and was the .NET Framework for Linux, with corresponding compat. and such, pioneered by Miguel De Icana, who now seems to be happier in Swift land. At the present day, it was receiving very little maintenance and I don't believe was actively used. Please correct me if I'm wrong.

Mono that lives in https://github.com/dotnet/runtime/tree/main/src/mono. This is the mono that got "merged" into .NET, giving the basis for multiple components and becoming one of the official runtime flavours. It is actively maintained and is at relative feature parity with CoreCLR, predominantly serving mobile targets (iOS, Android) and WASM as well as exotic or legacy targets like ARMv6, LA64, s390x(?), ppc64. Note that you are not expected to use it for targets that support CoreCLR due to absolutely massive rift in performance between the two. When you are using it, you do so as a part of standard .NET toolchain - it is picked automatically for appropriate targets, or can be opted into with some configuration.

Mono that lives in https://gitlab.winehq.org/wine-mono/mono which is a Mono fork actively maintained by Wine for its own usage. Going forward, any possible ambiguities regarding ownership and stewardship are considered resolved and the ownership of mono/mono and everything related to it is transferred to WineHQ.

Honorable mention also goes to private Mono fork used by Unity which they are (painfully) trying to migrate from.

I'm not using the dotnet framework, just the clr, and for the use cases covered by Oberon+ security is of little concern. The project is still regularly updated, see https://github.com/mono/mono/commits/main/.

In the video you basically install .NET 7.0 SDK with the deb packages from Microsoft repos AND mono deb packages from repos laid out in https://www.mono-project.com/ apart from Unity and VS Code. And then you configure VS Code so that it always uses Mono installed in the system (not Unity Editor's own instance???)

4- Any user-side telemetry would be in the MS .Net framework, which is not used when you selfhost as .net based stuff like Jellyfin use Mono, which is fully open-source and independent (https://www.mono-project.com/)

Did they intentionally name it after a widely used, well known programming framework[1], or did they want to guarantee, I dunno, that they will fly way, way under the radar? I thought it was bad form to name a new programming language 'Cedar', but at least the other Cedar isn't actively developed, unlike the other Mono.

[1] https://www.mono-project.com/ for the few of you who didn't know.

.NET 4.8.1 and earlier do not install on Linux. Unless you want to play around with Mono (your mileage may vary): https://www.mono-project.com/

They have deceived you. https://www.mono-project.com/ I seriously don't know how well wine can deal with newer .NET winforms

It also gained a lot of more popularity and success after the release of the open source implementation of it called Mono.

Hey, I'm working on a C++ game engine in VS Code and wanted to add C# scripting, so I'm trying to install Mono. I already got SDL2 working with CMake, but I'm having trouble setting up Mono because it doesn't seem to have any out of the box CMake support.