chaxor

The comparison is to pandas, so single node performance is understood in the scope. This is for people running small tasks that may only take a couple days on a single node with a 32 core CPU or something, not tasks that take 3 months using thousands of cores. My understanding for the latter is that pyspark is a decent option, while ballista is the better option for which to look forward. Perhaps using bastion-rs as a backend can be useful for an upcoming system as well. Databricks et al are cloud trash IMO, as is anything that isn't meant to be run on a local single node system and a local HPC cluster with zero code change and a single line of config change.

While for most of my jobs I ended up being able to evade the use of HPC by simply being smarter and discovering better algorithms to process information, I recall like pyspark decently, but preferring the simplicity of ballista over pyspark due to the simpler installation of Rust over managing Java and JVM junk. The constant problems caused by anything using JVM backend and the environment config with it was terrible to add to a new system every time I ran a new program.

In this regard, ballista is a enormous improvement. Anything that is a one-line install via pip on any new system, runs local-first without any cloud or telemetry, and requires no change in code to run on a laptop vs HPC is the only option worth even beginning to look into and use.

Aw man, are they selling only 4GB ones now?

More seriously, even 16GB was essentially the 'norm' in consumer PCs about 15 years ago.

As indicated by the explanation, better for people who believe in FOSS rather than closed corporate software.

Most developers work with a Unix mindset (do one thing well, with focus on simple and easily managed code), which tyically means telemetry is _wildly_ out of line (offers no real benefit for the basics while adding huge complexity), so privacy and security are naturally far better. Lynx like TUI browsers are a nice idea, but unfortunately sometimes an image is desired to be manually viewed, or javascript is required. It would be wonderful if javascript were simply dropped from most websites, but we don't live in that world, so we're stuck with the next best thing (disabling all js until explicitly allowed by the user).

These are the types of things people in software devs typically care about, which there are many in HN.

Mooers law in the consumer space seems to be pretty much asymptoting now, as indicated by Apple's amazing Macbooks with an astounding 8GB of RAM. Data center compute is arguable, as it tends to be catered to some niche, making it confusing (cerebras as an example vs GPU datacenters vs more standard HPC). Also Clusters and even GPUs don't really fit in to Mooers law as originally framed.

What do you mean by Mastadon is a bloated sloppy mess?

It was my understanding that Mastadon has _far less_ javascript than Twitter, not more.

The UI for mastadon always seemed far cleaner, more performant, and importantly - capable of actually loading, compared to twitter

Essentially, anytime something is shared from twitter I simply ignore it, because it may take a good 40 minutes to figure out the workaround to view it, compared to Mastadon which 'just works'.

The biggest thing I want to see from framework is ARM (or better, Risc-V that achieves great low power performance) with an enormous battery and linux or BSD with all the optimizations to improve battery life.

I bought a macbook a while ago specifically because I can get it to last about 45-50 hours non-stop usage on one charge, so getting a system tailored for even better performance and a longer battery life (macbooks could probably double or triple battery life if they bulked up and stopped trying to be so petite) would be incredible.

>100 hour battery lifes should be very achiebable for developers, as limiting screen brightness and using only terminal with a black background can increase battery life _enormously_.

Thanks, this is good information. I'm still curious about size, as it removes attack surface for security. The glibc to musl conversion is obviously not the direct change to occur in BSD, since BSD has its own libc, but an even smaller alternative would be interesting. My understanding is that OpenBSD is about 100x the size of Alpine right now. In modern times, a Rust-based option is also intriguing if the goal is security as well, though things like Redox are _extremely_ heavy for these considerations.

What BSD is the closest to alpine in the Linux space? Which BSD is the smallest in size and very security focused by selecting for minimalism while also being well maintained and used like alpine? That seems like it would be a great starting place for a good desktop os

Of anyone is making a browser in todays age, I would imagine starting with something like Servo would be best. There are far too many chromium based browsers.

A very minimal Rust-only browser with security and privacy in mind at every single step is completely missing from browsers today. Things like waterfox et al are enormous projects that take far too long for one person to audit the entire code base to ensure correctness. Something like the 'wireguard of browsers' in this regard is needed (single repo that one person can read over in a day and can be built with a single cargo build command). Even servo unfortunately falls just barely shy of this goal, but one can dream.

Is that just openssh with an obscured name? It would be nice to simply use the correct basic tool instead of some strange rebranding by a company of a much more well understood and trusted standard