@retoor if course it would. First, they make Chromium closed-source. Then, they replace HTTP with something proprietary. Then, their telemetry will be mandatory and won't show in devtools/be blocked by extensions.

@azuredivay I don't care about CSS libs. I do everything myself. All CSS libs suck and they're fucking ugly, except for one obscure React UI kit made by HP (of all people) that was deprecated around 7 years ago. It's a bummer that I can't use it because I quit doing react

@12bitfloat ouch

@devJs I consider iOS Safari to be the ultimate litmus test for hacky code. Chrome is good at absorbing hacks, while Safari is more strict and exact. For example, it shouldn't be possible to synchronize positions of two elements while they're being transitioned, if one of them is moved with translate() and the other one with margin. Chrome will sync them up for you, Safari won't, because that's lowkey a hack, and you shouldn't write hacks. If you need animations to sync, animate the same exact property. Use translate() everywhere.

If my site works in Safari, I know it works everywhere. From my 10 years of experience, every "bug" that people attributed to Safari was actually their code's fault, sans some quirks that I can name. For example, Safari's 100vh, as well as position: fixed's data is not necessarily equal to the viewport data you can get with JS during and after the on-screen keyboard is being collapsed, so your fixed elements can get stuck mid-air. But thats about it really

@devJs for attribute not working? Never happened to me ever.

@hjk101 are those "past issues" really past?

it's a bummer devrant pics are broken. I would've shown you some of my js that is the opposite of what you're describing

@Tounai it doesn't happen in _my_ browser though.

@IHateFrameworks you’re mixing up surveillance capitalism and targeted cyberattacks by the govt.

@IHateFrameworks people pay for linux knowledge. so yeah, it's potentially useful. also, the time you spent on things you enjoy wasn't wasted, eh

@IHateFrameworks if you want to escape surveillance capitalism, you have several options: linux, bsd, haiku os. bsd is harder than linux. haiku is not ready yet. so yeah, linux it is. I prefer to know that 100% of tools I use are fully open source. if I had more spare cash, I would've bought a computer with open source firmware too, but right now that's not an option. So yeah, my setup is like 99.8% open source

@Tounai turns out it isn't!

@iiii I would argue the opposite: a smaller tool is always better, unless you have a rare specific case that requires a larger tool. This goes for doas, glibc and systemd.

Why use sudo when smaller doas works for me? Why use glibc when smaller musl works for me? Why use systemd over openrc when openrc works just fine?

So far, I don't have any justification for a bigger, more bloated distro. I can code/browse web/listen to music just fine on Alpine with Gnome. That's about all I need.

I have dualboot with windows 11 for games. Running modern games on desktop linux is an exercise in frustration.

I like fast linux. Alpine is fast linux.

@iiii about musl vs glibc argument. I believe you just googled that and repeated the first thing you read there. I’ve heard that point too, that glibc is faster than musl. Have you tried a musl-based desktop distro yourself? Because I did, and on my machine, alpine is faster than ubuntu.
I have 16 threads, 16 gigs of ram and an RTX 3070. Ubuntu had tiny little freezes sometimes. Alpine though? None.

@iiii systemd is a disaster
http://suckless.org/sucks/systemd/
https://nosystemd.org

https://github.com/miloxeon/...

@tosensei congrats! You’re the only one who got it.

@SidTheITGuy wait till you learn about Logitech Forever Mouse subscription

they were like "fine, environment, amiright? just buy our mouse, and instead of buying a new mouse every year because the old one breaks, just pay us every year to use your existing mouse"

@retoor why?

merzbow

@iiii big icons does not equal touchscreen. Gnome has tiling, workspace switching, all on hotkeys. If you think Gnome is touchscreen-oriented, then macOS should be too, because of their Launchpad panel with all the apps (the thing that Gnome copied). Yet, no device that natively ran OSX and above had a touchscreen, despite apple holding the fingerworks patent and being famous for their touchscreen application to handsets that shaped what our phones look like

@retoor what do you mean what problem
Bloat, ram consumption, systemd

@iiii huh?

@iiii when you have a big screen, you want big heavy software fluidly rendered, especially if you use a trackpad. Every swipe a deliberate decision. Every two-finger swipe a statement. Every three-finger swipe a painting, a monument to your GPU’s power.
Small efficient wm with no animations feels just right when you’re rocking your 900 gram, 13” thinkpad x1 nano at 7am at local maccas, listening to music, coding and chilling before the city wakes up.
Big screen though? Yeah, give me that fat ass bitch, bring it on motherfucker, my GPU can take it

@lorentz how is pipewire paid if I just installed it on alpine linux for free?

use pipewire

@Liebranca please file the form 21B.3a with the Bureaucratic Union, and if the majority votes for it, it will be legal in about three years

@12bitfloat yes, they do need a lot of users for their anonymity. Yes, they’re okay with CP. With PRISM, with the ability to use WiFi 6 to scan the room and find the number of people in it, with 5G triangulation being precise to the centimeter, with Intel ME, do you really think they can’t stop the CP production? The thing is, f you’re a regular CIA operative, you can’t really do anything about CP because main CP consumers and the people that pay you your salary are the same people.

It’s bad because app interfaces are naturally modular and they reuse design patterns a lot. UI kits are a good example.
First, if I want to change border radius of all standard buttons, I shouldn’t go and manually update inline styles of every such button. I just change it in CSS under that button’s class, and that’s it. Also, if you use inline css and want to copy the element, you have to copy inline styles as well, and files can get way bigger than they should be. I don’t need 20 instances of the exact same CSS string to style 20 similar-looking buttons.
The only case where the difference is negligible is when you’re styling just one element that is unique and won’t occur anywhere else ever. But in apps that are alive, every element will eventually be reused.

Your example touches tailwind. Tailwind is retarded, don’t use it. Your exact problem is Tailwind’s problem, not a CSS one

landsat. helped to farm better, track and fight floods & wildfires, and still helps