burrito VS UnnaturalScrollWheels

Most of the BEAM isn't well-suited for trends in today's immutable architecture world (Docker deploys on something like Kubernetes or ECS). Bootup time on the VM can be long compared to running a Go or OCaml binary, or some Python applications (I find larger Python apps tend to spend a ton of time loading modules). Compile times aren't as fast as Go, so if a fresh deploy requires downloading modules and compile-from-scratch, that'll be longer than other stacks. Now, if you use stateful deploys and hot-code reloading, it's not so bad, but incorporating that involves a bit more risk and specific expertise that most companies don't want to roll into. Basically, the opposite of this article https://ferd.ca/a-pipeline-made-of-airbags.html

Macros are neat but they can really mess up your compile times, and they don't compose well (e.g. ExConstructor and typed_struct and Ecto Schemas all operate on Elixir Structs, but you can't use all three)

If your problem is CPU-bound, there are much better choices: C++, Rust, C. Python has a million libraries that use great FFI so you'll be fine using that too. Ditto memory-bound: there are better languages for this.

This is also not borne from direct experience, but: my understanding is the JVM has a lot more knobs to tune GC. The BEAM GC is IMO amazing, and did the right thing from the beginning to prevent stop-the-world pauses, but if you care about other metrics (good list in this article https://blog.plan99.net/modern-garbage-collection-911ef4f8bd...) you're probably better off with a JVM language.

While the BEAM is great at distribution, "distributed Erlang" (using the VM's features instead of what most companies do, and ad-hoc it with containers and infra) makes assumptions that you can't break, like default k-clustering (one node must be connected to all other nodes). This means you can distribute to some number of nodes, but it's hard to use Distributed Erlang for hundreds or thousands of nodes.

Deployment can be mixed, depending on what you want. BEAM Releases are nice but the lack some of the niceness of direct binaries. Libraries can work around this (like Burrito https://github.com/burrito-elixir/burrito).

If you like static types, Dialyzer is the worst of the "bolted-on" type checkers. mypy/pyright/pyre, Sorbet, Typescript are all way better, since Dialyzer only does "success typing," and gives way worse messages.

   [1]: https://morepablo.com/2023/05/where-have-all-the-hackers-gone.html

The answer was given by the Elixir community with burrito which enables users to pack up everything an Elixir application needs within a binary namely Zig Archiver to package the binary and Zig Wrapper that wraps the Erlang Virtual Machine to be used in multiple platforms (Zig + Rust in the same project 🤯).

Might be worth looking into burrito for that use case?

Elixir is extremely practical for building systems, I know some sysadmin/devops that write their tools in it - which is maybe a bit of a leap for most. It has better support for cli stuff these days but it's not it's strong suit - you can create single-bin packages with stuff like https://github.com/burrito-elixir/burrito or regular "mix releases". (LiveView is very sexy.) It's not statically typed. There is some experimental skunkworks project to add typing to it but probably wont see any public preview until mid/late next year as I understand it.

I would consider 1 to be the major blocker but Burrito has addressed many of the concerns here, including cross-compilation. The only downside of Burrito is that the first boot has to unpack the runtime (which is sub-second in my experience).

Sure! Elixir's been great. Phoenix is a joy to work with, and many of the concurrency primitives built into OTP make it the perfect foundation for a product like this. And rustler makes it super easy to add low-level / native code.

I will say the big downside to using Elixir is that distributing releases is a bit cumbersome. `mix release` expects that you're building on the same OS / version as you'll be running on, though we're looking into using something like burrito [1] aim to alleviate this.

[1] https://github.com/burrito-elixir/burrito

I was intrigued so I went to hunt for the Burrito repo [1].

I thought it was some sort of Erlang native compiler written in Zig (which sounds like an incredible pain in the ass), but it's really "just" a cross-platform installer. Still useful !

[1]: https://github.com/burrito-elixir/burrito/issues?q=is%3Aissu...

For gaming, you want to use Crossover or the FOSS Whisky app. Parallels only runs Arm Windows which then emulates x86. This is much much slower than using Wine to translate system calls and Apple's Game Porting Toolkit to handle the Vulkan or DirectX graphics. Crossover and Whisky take care of the internals of those for you. Give those a shot, I think you'll find it much better than a full VM. In my experience some games do run better this way than the MacOS versions, though that's usually because the Mac client wasn't compiled for Apple Silicon and so Rosetta is emulating. Unfortunately, I'm pretty sure WOW is already Apple Silicon native, so you probably won't get better performance this way.

For the mouse stuff, try a USB mouse if you're not already using one, combined with https://github.com/ther0n/UnnaturalScrollWheels

That works really well for me to get a Windows-like mouse curve.

TLDR skip the emulation and go for translation layers via Crossover, Whisky, and GPT. It'll be much faster. The mouse thing is separate and has nothing to do with the graphics layer.

------

Personally though, I'd just pay $20 a month for Geforce Now. It is much much faster than even the highest end Mac.

Was the utility UnnaturalScrollWheels?

I use this tool to keep natural scrolling on trackpad and normal scrolling on my wheely mouse: https://github.com/ther0n/UnnaturalScrollWheels

A Free Tool UnnaturalScrollWheels is a MacOS app that allows you to invert the scroll direction for physical scroll wheels while maintaining the normal function for trackpads. aew3 recommends it "for those like me who go between dock and laptop and prefer my mouse to have a different scroll direction to the trackpad." Another Free Tool Locust is an open-source load testing tool that allows you to define whatever user behavior you like, and then swarm your system with millions of those users simultaneously. certTaker suggests, "If you want to test an actual application and how it handles network latency, potential buffering, QoS etc, then you could use Locust to stress-test REST-based applications and their APIs." A Tip Synssins shares a method for replacing an older Windows File Server with new, while keeping all shares and DNS intact:

UnnaturalScrollWheels is a MacOS app that allows you to invert the scroll direction for physical scroll wheels while maintaining the normal function for trackpads. aew3 recommends it "for those like me who go between dock and laptop and prefer my mouse to have a different scroll direction to the trackpad."

“For some reason in macOS, toggling the "Scroll direction: Natural" option in Mouse settings also changes it in Trackpad settings despite being in separate places.” Check out this app too which also takes care of acceleration. https://github.com/ther0n/UnnaturalScrollWheels