I've been rocking the pinebook pro since it arrived, and have to tell ya folks... double the ram, give it a backlight keyboard and it would be a perfect travel laptop.
Uptime is at 7:30 hours, 25% battery left and most of the day I was watching videos and reading pdfs and did some light scripting. My only complaint is KDE being unstable, I'll see if putting together a WM setup for this one makes things even more fun.
Pine64 guys and gals, arm64 linux devs thank you for all the hard work!
It's interesting how there are notable events buried in the source control history of a lot of software we use every day. Huge refactors, large merges and splits of codebases, filter-branches, places where lines have been drawn and a before & after exist. Large, coordinated events with tens or hundreds of participants. No one is documenting this history, aside from our tools dutifully keeping the record keeping. No one is interpreting these records or telling stories about these events.
* comes up with a nice project name
* checks if it's available on crates.io
* tries to be considerate and not take the name away with a dummy publish and instead works on the code first
* reaches a point where the functionality is not there but at least something that worth the name
* the project name was taken 3 days ago
* cries inside
LLVM's newest target: Minecraft
Now... if someone would compile Minecraft for Minecraft, the simulation would go full circle and our universe implodes, right?!
Openness and transparency. Something I don't see enough of, but really appreciate when I do.
So I've often said that Google doesn't deserve credit for Go, and that Go is the product of a small number of language designers and derives from a history of system design which is external to Google. What Google has done with it since becoming its steward is, on the whole, more negative than positive.
I can now hold up pkg.go.dev as more evidence of this fact. It's obviously a product of the dysfunctional Google corporate engineering culture rather than a product of the principles that underlie Go's design. The care and deliberacy which went into Go's engineering design choices is entirely absent from pkg.go.dev.
1. Was big old monolith born from Google's giant monorepo with no intentions of open sourcing until the community pressed the issue
2. Drops support for generating docs locally or hosting them off-site
3. Discussion hosted on a Slack channel
4. Hard-codes a list of centralized git hosts, despite being told that this is now how git works
5. Refuses to consider language-agnostic approaches to Go package hosting, instead forcing downstream git hosts to add Go-specific support
Basically, good engineering has been abandoned in favor of promoting Google's interests and a corporate, centralized view of the software ecosystem
Sourcehut Q2 2020 Financial report
> Linux and BSD user
> Network engineer student
> Embedded C developer
Fosstodon is an English speaking Mastodon instance that is open to anyone who is interested in technology; particularly free & open source software.