Why Haptic

We built Haptic to make markdown writing simpler and more accessible. We believe that many existing editors are too complex for simple use cases and day-to-day note writing, so we decided to fix that.

What Makes Haptic Special

1. Ready to Use: Open Haptic and start writing. No setup needed.

2. Simple Design: Clean interface so you can focus on your writing.

3. Write Anywhere: Use Haptic on any computer with internet. Great for public or work computers where you can’t download software.

4. Made for Everyone: If other editors feel overwhelming, you’ll like Haptic.

5. Open Source: Self-host your own instance, giving you full control over your setup.

Haptic is all about making writing easier. We’ve left out extra features to keep things simple and help you get your ideas down without fuss.

Note: If you’re looking for a markdown editor with plugin systems, complex setups, or feature-packed interfaces, Haptic might not be for you. But if you want something straightforward that just works, give Haptic a try!

Silly question: what’s the difference between the otf and ttf fonts?

Edit: thanks for the explainers!

I know a bunch of people that own Steam Decks, know nothing about Linux, and have no idea that their games are running on it. I’d say it’s pretty easy now

“Karen compiler” is almost perfect, except unlike Karens, the compiler is delightfully helpful with the error messages it gives you (usually). It usually gives a straightforward error, an error code, and sometimes, an easy fix.

As someone that started with Rust, but just yesterday had to fix some C++ code, working with any other compiled language makes me shudder. I have nothing but respect for devs that have to wade through stuff like that.

Just don’t ls /dev/loop* 🫣

I just pre-ordered five of these. lol. Thanks for the rec. Wendell from Level1Techs always has his eye on the coolest stuff.

I’d love some suggestions. I have a 1440p 32:9 monitor that can act as separate displays, but since Synergy, input-leap, and the other software KVMs don’t work on Wayland, I’m having a bad time :(

I agree with your sentiment. Just one small thing: .c files are usually C source code, and are meant to be compiled into binaries.

It doesn’t change OP’s situation at all though.

Using containers on Linux has basically no performance loss compared to running on the host. They share a kernel and nothing needs to be virtualized (unlike containers on macOS and Windows), so anything you run in a container is basically the same performance as running it on the host.

I still agree though: using Nix is better than using Distrobox for many other reasons.

Nix has more packages , by far. Nix also automatically handles the dependent libraries for each package, which is something you can’t do with brew on immutable systems. This means that Nix can install software like espanso, which wouldn’t work on uBlue derivatives otherwise.

I really wish the uBlue maintainers would have opted for Nix over brew for that reason. It’s not much more difficult to do nix profile install nixpkgs#package-name over brew install package-name. They could have even aliased it to make it easier.

While I generally agree with your skeptical attitude toward this, I think the fact that they were targeting Apple’s Metal graphics API to built the most performant possible IDE makes sense. You can’t just snap your fingers and have a Linux graphical stack start working with your software.

I think the reason they targeted macOS first is probably because many of the dev team uses Macs.

As a Linux user, I’ll happily wait for software like this to get ported to native Linux APIs so we get performant text editors instead of more Electron crap.