I 💔 the modern web

~ $ uname -srm OpenBSD 7.8 amd64 ~ $ sysctl -n hw.physmem |awk '{print $1/1024**3, " GiB"}' 3.72584 GiB ~ $ sysctl -n hw.physmem |awk '{print $1/1000**3, " GB"}' 4.00059 GB ~ $ ps wwaux |head -1 USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND ~ $ ps wwaux |awk '$0~/firefox/ {t+=$6}; END {print t/1024, "MiB"}' 972.234 MiB ~ $

P.S., I forgot to mention that this is with a fresh run of firefox with only a single blank tab. XD

@rl_dane Every browser is a rather complex piece of software, because they need to be due to the sheer amount of web standards they have to support. High memory usage is expected, especially since all of them are now multi-process IPC pipeline behemoths.

@dusnm

I know. I hate how the web standards have grown by sheer accretion.

I miss proper Web 2.0.

@rl_dane @dusnm

I have an upcoming blog post about this…

@amin @dusnm

YAAAAAS DEW IT

@rl_dane @dusnm

First though I need to write my upcoming post titled "you will never need the new iphone"

@amin @rl_dane @dusnm never had one, nobody needed one, they just want one because it's a fancy brand thing that conveys status.

@sotolf @rl_dane @dusnm

I'll be discussing smartphones in general, I just wanted to reference a specific type for title purposes. ;)

@amin @rl_dane @dusnm That title would be a surefire way to make people like me not read the post ;)

@sotolf @rl_dane @dusnm

hmmmmmmmmmmm

@sotolf @rl_dane @dusnm

"the new pixel" is ambiguous though, and "the new smartphone" just sounds odd to me

@amin @rl_dane @dusnm I'm not quite sure why the new smartphone sounds odd? it's more inclusive at least :) I would even say you don't need the newest phone, as I don't think there are that many people with a wired phone anymore :)

@sotolf @rl_dane @dusnm

I was kinda leaning toward iPhone because Apple fans seem to be the biggest offenders in terms of always wanting the newest model

@amin @rl_dane @dusnm It's because they aren't in it for the functionality, neither are they in it for the value, they are in it especially to have something that you don't have, the whole point for them is to have the newest fanciest thing that "you don't have" :)

@sotolf @amin @dusnm

I don't think most people are that shallow.

They're caught up in the "oooo, shiny!" and vendor lock-in.

And they have no clue why their evil cousin with the green bubbles "ruins" group chats. 🙄

@rl_dane @sotolf @dusnm

And the lack of OS and app support after a couple hardware versions have gone by is a big factor too…

@amin @sotolf @dusnm

I mean, iPhones have support for what, seven years?

Most android phones now have at least five.

@rl_dane @sotolf @dusnm

They're still perfectly functional from a hardware perspective for a long time after that mark though. :P

@amin @sotolf @dusnm

Yes, enshittification creates ewaste by not allowing you to put your own OS on them.

Of course, even if iPhone had unlocked bootloaders, ARM is such a horrid platform, it would take a team of dedicated devs weeks to reverse-engineer everything to make it totally functional with 100% FOSS stuff, if it were even possible.

@rl_dane @amin @sotolf @dusnm

I saw someone talking recently about how arm never gets any credit for what they've done for modern technology, and I was just like "GOOD, _fuck_ them"

@OpenComputeDesign @amin @sotolf @dusnm

I mean, it's a superior, RISC-ish architecture in many ways.

It's just that there's no openness or standardization, and kind of a nightmare for FOSS. :/

@rl_dane @OpenComputeDesign @amin @sotolf @dusnm
Isn't arm more open than x86? As in, everyone (with enough money) can buy the design and manufacture chips. And if you have the money to manufacture chips you should be able to afford an arm license.
And the nightmare for FOSS is more all the parts that the chip manufacturer adds that are not form ARM?
I'm not trying to defend ARM, i prefer RISC-V for developing their spec in the open.
<edit> which has the same problems </edit>

@kabel42 @OpenComputeDesign @amin @sotolf @dusnm

I think the ISA itself may be, but the hardware is less so. There are no VESA video modes or standard hardware interfaces for anything. Every single phone and bit of ARM cruft out there is a bespoke engineering job, and it's all a nightmare to reverse-engineer. (AFAIK)

@rl_dane @OpenComputeDesign @amin @sotolf @dusnm
but that's the, there is no default video interface, there isn't even a standard GPIO interface, every manufacturer adds their own. But AFAIK that's a problem every architecture has, unless it specifies the whole computer.
@rl_dane @OpenComputeDesign @amin @sotolf @dusnm
newer ARM has at least a default float interface, ARMv6 had AFAIK 3 incompatible official ones

@kabel42 @rl_dane @amin @sotolf @dusnm

Hottest of takes:
It doesn't matter a single fucknegle how open something is if it facilitates making other things closed

@OpenComputeDesign @rl_dane @amin @sotolf @dusnm sure, but i still don't see how that is an ARM thing? If the CPU ate x86 or RISC or MIPS or whatever Instructions, it would be just as bad.
It's a problem of missing system spec and standard peripheral interface.

@kabel42 @rl_dane @amin @sotolf @dusnm

Maybe its just an expectation I've gotten from x86, where the name of the architecture, to me, implies there is at least _some_ level of intercompatibility. Arm does not, to any practical degree, have this. But maybe that's just an x86 thing

@OpenComputeDesign @rl_dane @amin @sotolf @dusnm you can execute code, but i think that's all that's in the arm spec. An architecture would at least need a table with all the peripherals and some standardised interface, but arm chips are so different, I don't even know what a relevant minimal interface would be. There is probably a serial interface in every arm chip :)

It would be great to have something similar to IBM AT compatible for general *NIX compatible stuff. That could even be the same between ARM and RISC-V and ...

@kabel42 @rl_dane @amin @sotolf @dusnm

It's my understanding that various arm CPUs absolutely cannot all run the same code. Even the at a software level, each chip requires tons of fussing and fiddling to port code between arm chips.

also, a further hot take, in this era of SoCs, if common peripherals _aren't_ standardized in your architecture, it's not a real architecture.

@OpenComputeDesign @rl_dane @amin @sotolf @dusnm but ARM is just an instruction set, and even then there have been different versions over the decades.

@kabel42 @rl_dane @amin @sotolf @dusnm

Fullest level of hot take:
if all arm means is "a chip with these sets of operations, maybe" then it's completely meaningless

@kabel42 @rl_dane @amin @sotolf @dusnm

before SoCs, pretty much no chip maker ever released just a CPU. They always released a full suite of PIOs and timers and stuff. Sure, not every computer used the standard chips, and they were usually at different hardware addresses on different computers. But since processors these days are expected to have all those features baked in, now more than ever, any architecture that doesn't include those just emphatically not a full architecture

@OpenComputeDesign @rl_dane @amin @sotolf @dusnm
Is ARM selling Chips?
AFAIK every manufacturer has their own timer/... they put in their chips. And those can be the same between ARM and RISC-V (the only two i've used).

@kabel42 @rl_dane @amin @sotolf @dusnm

my point is really, if timers and peripheral controllers and such aren't part of the architecture, it's not actually an architecture, or indeed, anything of real value.

@OpenComputeDesign @rl_dane @amin @sotolf @dusnm yeah, more a compiler target
@OpenComputeDesign @rl_dane @amin @sotolf @dusnm
At least for embedded MCUs and C code, switching manufacturers is a bigger difference than switching between ARM and RISC-V

@kabel42 @rl_dane @amin @sotolf @dusnm

yeah, that really speaks to "this is an NXP cpu, that just happens to have a bit of ARM patent bs inside it".

Arm, I continue to insist, deserves no credit.
And I guess that goes for a lot of so called "architectures"

At least z80s and 6502s had better code compatibility, and were nearly functional fully standalone.

@OpenComputeDesign @rl_dane @amin @sotolf @dusnm thats why mbed exists, so you can have the same high level source code on different ARM MCUs
Free open source IoT OS and development tools from Arm | Mbed

Mbed OS is the fastest way to build IoT products with Arm processors

@OpenComputeDesign @rl_dane @amin @sotolf @dusnm and thats a dumpster fire with two incompatible versions and a thing that tries to be npm and make at the same time