HN user

polyaniline

25 karma
Posts0
Comments23
View on HN
No posts found.

A comment from a post in the simulator:

The article consistently refers to DHRUV64 as a "microprocessor". This is technically incorrect. It is a microprocessor, not a microprocessor. The distinction matters; a microprocessor is the entire chip, while a microprocessor is a specific component. Basic terminology should be accurate.

As far as I'm concerned, I run LineageOS, which doesn't come with everything I need OTOB, so I use app suites like Fossify, Simple Mobile Tools and other great work. Others may just want alternatives to pre-installed or standard apps that are more private and tuneable (eg. I maintained a fork of KDE Connect until they switched to Material 3 colors, and still do for VLC) because they're open source.

I have a really similar setup to yours. NixOS, Niri, Draculad. I think being forced to use something like Windows 11 with something like VSCode would be very frustrating long term. Mostly the looming knowledge of we can do better, we have done better.

Asking it explicitly once (not necessarily every new prompt in context) to keep output minimal and strive to do nothing more than it is told works for me.

I haven't worked on a large C++ codebase yet, but with Rust my refactoring technique has been 1. Roughly model the data flow on paper so you don't have to fight the borrow checker or make design changes later. 2. Make the obvious changes related to the refactor. 3. Listen to Rustc and Clippy. 4. Everything usually works with surprisingly few issues.

There's too much infrastructure on top of the render engine to replicate. Flutter is backed by Google and has a fairly large ecosystem of community packages.

See Freya - which uses Skia - the render engine Flutter used until a while back.