SpeakEZ.tech

Coeffects and Codata in Firefly A Fresh Take on Efficiency and Observability from Storied Mathematical Principles

#fsharp #haskell #scala #rust #ocaml #mlir speakez.tech/blog/coeffec...

Alloy.Rx: Native Reactivity in Fidelity Porting A Push Model with Principled Performance

#fsharp #cpp #mlir #llvm #AI #iot #webassembly #systemsprogramming #softwaredevelopment speakez.tech/blog/alloyrx...

Thanks! I too hope the Fidelity framework takes on a life of its own similar to the Fable Compiler/ecosystem - independent but with lots of sympathetic "shared edges" with dotnet. There's still work to do for MLIR to really express broad high-level languages but it's a very active ecosystem. 👍

The Continuation Preservation Paradox How Deep Can Delimited Continuations Survive in a Systems Compiler?

🔬 #fsharp #mlir #llvm #wasm #embeddedsystems #webassembly #wasm
speakez.tech/blog/the-con...

Why F# is a Natural Fit for MLIR How functional design can express low-level efficiency with safety

#fsharp #mlir #AI #machinelearning #systemsprogramming speakez.tech/blog/why-fsh...

Hardware Lessons from LISP Boom, Bust and Broadsides from the first era of AI

#FSharp #OCaml #StandardML #LISP speakez.tech/blog/hardwar...

Hundreds of victims, thousands of lives affected. Even if you don’t believe Epstein’s associates partook in the abuse (which would mean you don’t believe the testimony of his victims), at the very least the story of how the world’s wealthy and powerful enabled the abuse is real and underreported

Speed & Safety with Inet & Graph Coloring Keeping Parallel Computation on the Beam with a Rational Approach to Formal Methods

💸 #AI acceleration should be a commodity, not a monopoly. 💰Our design for the Fidelity framework uses interaction nets to target GPU & CPU/SIMD via #MLIR. No opaque vendor APIs that sacrifice accuracy, efficiency or safety. Just functional code → silicon. #FSharp #LLVM speakez.tech/blog/speed-a...

😆 to each their own 👌 enjoy life!

#fsharp ☝️
try.fsharp.org

And the runtime diaspora! That's going to take some time to sort out. 🫢

OCaml had already figured out a significant portion of this 17 years ago. They were preserving type information in the wire format when everyone else was bedazzled by shiny versions of corporate surveillance courtesy of Google and Facebook. github.com/mfp/extprot

On the "Fidelity" name, it was chosen for the metaphor of preserving type information to *not* fall back on heuristics too soon - and - to provide memory layout optimization *to* MLIR rather than waste passes for it to determine its own (and risk getting it wrong).

I just learned this week that...

It's great you shouted out the F# native markdown processing that's around. The bias here to to break the interop habit wherever possible to keep doors open to port to Fidelity where a component is useful. 👍

Our site is still on Hugo - for now. But of course I want to have some options for middleware, semantic search and other bits and bobs to show a few more of our wares along the way. Baby steps!

For markdown, we started with the notion of forking Fornax and extending it Hugo-style to deploy to Cloudflare Pages. That has done a full pivot to Oxpecker and leaning heavily into Markdig (for now) with a side quest into presentation formatting using the Fable wrapper for Reveal.js.

I'm saying the same thing about my own project as I have a talk to give in a little under a month. 😲☺️

Would love to see your work with markdown handling - looks super slick. 🌟

We're building Elmish into the Fidelity - borrowing heavily from @jordanmarr.bsky.social ReactiveElmish and Avalonia/Skia.

This is great - just catching up on your project. Have you considered doing an @amplifyingfsharp.io session to showcase bits and pieces you're willing to present? That would be really cool! 🚀

Exclusive: Meta fixes bug that could leak users’ AI prompts and generated content The tech giant fixed the security flaw, netting a security researcher $10,000 for privately disclosing the bug.

Move fast and leak things 🙄

Meta fixes bug that could leak users' AI prompts and generated content | TechCrunch share.google/WA3goFCVjBy1...

Today, this thought crossed my mind:

Claude Code appears to be the current pinnacle of AI-supported software development. In the videos I've seen, considerable emphasis is placed on the importance of a detailed and precise specification. The better the spec, the better the outcome.

#fsharp

It's nice to see models that reward structure in a well designed language. But the issue of more recent API updates needing special prompting yields shorter discourse with the model. I wanted to squeeze F# Compiler Services 43.9.300 for insight and answered my own question in prepping the prompt. ☺️

The fact that 'bad' F# code is less prevalent in the commons (and therefore not as much mid-code to be inferred due to dilution in training) is part of why things tend to line up well once the prompt orients the model. Another reason is the relatively consistent API.

🤔 "Why are you so focused on low-level memory operations in a functional language?" Here's the thing: We're not abandoning high-level abstractions. We're making them work everywhere 🎯

The path is more direct than you might think 👇
speakez.tech/blog/beyond-...

#FunctionalProgramming #FSharp

Microsoft management is a circle jerk of MBAs so why bother learning anything beyond Excel to work there?

Coupling & Cohesion: Structure is Speed Using Functional Programming as a Super-Power for Efficient Compilation

Fun with #fsharp and a hat tip to @rtfeldman.bsky.social for inspo from www.youtube.com/watch?v=vzfy... speakez.tech/blog/couplin...

We appreciate the clarity (to our view) of the API. We're standardizing on it. 👍

Building Firefly with Alloy How the Fidelity framework achieves zero-allocation performance with F#

speakez.tech/blog/buildin...

Having some #fsharp fun building Alloy's shadow API! 🎭 These look like System/Core calls but they're statically resolved to our dependency-free implementations. Same familiar F# idioms, zero BCL dependencies. It's like BCL cosplay for native compilation! 🚀 #dotnet

"Copilots! Copilots! Copilots!" #dotnet 🫣