Notices by Wolf480pl (wolf480pl@niu.moe), page 13

@sir @alcinnz
But to me, it seems like we need a new low-level language, one that is a better match for our modern hardware.
One where all dependencies are explicit, instead of being hidden behind "statement A is textually above statement B".

@sir @alcinnz
From what I've heard, the CPU burns 90% of power on turning your linear assembly back into a graph of operations and dependencies between them (sth like LLVM IR I guess?), reordering the shit out of them, doing some of them in parallel, keeping track of which hardware register holds the value of EAX from particular instruction's POV, etc.

And, as we've seen with Meltdown and Spectre, it sometimes does it wrong.

@sir @alcinnz
Tbh, even assembly is far from how hardware works.
In assembly you're shown an illusion of linear program execution and uniform memory.
Unless you write assembly for some VLIW architecture, what happens in the hardware has little to do with your assembly code.

@duponin @lis

git commit --fixup HEAD^^^^^
git rebase --autosquash HEAD^^^^^^^^^^^^^^^^^
git push -f

@phryk don't forget about the Sillicon Valley

@Shamar imitation[1]. Let invite someone to observe your lessons, and then go to their place and give a similar lesson.

[1]: https://en.wikipedia.org/wiki/Imitation

@Michcioperz but it's not The Algorithm, a.k.a. the evil entity onto which all companies push the blame for their software's user-hostile decisions.

@Michcioperz @sir @Liberapay
but they still use medium...

@Shamar Heck, I wish I were like that.

I can often notice that there's something wrong with a simplistic and emotionally-charged statement, but I have trouble explaining why it's not that simple.

@Shamar You're pretty good at explaining how "it's not that simple", when confronted with a simplistic and emotionally-charged statement.

At least in this case.

I wish more people were like that.

@Shamar so you hacked C# against MS? cool!

Wouldn't it be cool to have a client-side option in mastodon/pleroma/etc to display the timestamp of a post in red or sth if it's from earler than $X time ago, but you're seeing it because of a recent boost?

@Shamar aren't you legitimizing Microsoft by coding in C#?

@Argus
>5.7"
Too big. Can't reach the top left corner with my thumb.

>600 USD

That's 4x the price of the laptop I'm typing this on.

Tbh, I have more hopes about the phone Pine64 is considering developing, than about Librem5.

Don't get me wrong, Librem5 is an amazing project and something very much needed in the ecosystem, it's just not for me.

@Argus
But as for practical requirements of mine:

1. A 4" phone or smaller.
2. If possible, with a physical keyboard.
3. If possible, with apps optimized for low resource usage.

It's hard to find anything that satisfies 1, let alone 2 and 3.

And 4" is as much as I can comfortably reach with my thumb.

@Argus
Another interesting front to investigate would be adding more input devices to a smartphone. A lot of inspiration could be drawn from game controllers. Buttons on sides? Buttons on the back? Maybe a 1- or 2-dimensional touchpad on the back?

@Argus Ideally, I'd like to split what currently constitutes a smartphone into multiple devices:
- cpu module in backpack, with storage, wifi, bluetooth, etc.
- electrically spearate GSM module, connected over wifi to the cpu module
- a bunch of thin clients connected over wifi:
* a handset with numpad for calls
* a qwerty keyboard with display for chat
* a big standalone touchscreen for maps, reading, etc.

@Argus the apps on F-Droid are more than enough for my needs. OTOH, the F-Droid client became shit after the UI redesign.
Actually, that's a problem not just with F-Droid, but also OSMAnd, and may other apps. With time, they became more resource hungry, and made their UI less ergonomic.

Other than that, the concept of using touchscreen for everything is IMO fundamentally flawed. Typing is the worst. You can't sense where the keys are!

A phone with physical keyboard would be a good first step.