theres an about:config setting thats something like replace.newtab and if you set it to false it brings back new tabs. you can also set the urlbar behavior to normal and it will stop floating

is that a thing?

how my phone looks at me every time google does anything

no, I mean a whole dumb terminal (basically a digital typewriter that was used for early computers) but using paper as its display. I’m pretty sure that was a thing before the digital ones but I want to see one that works with modern linux

same

i did know, but thanks for telling me

yeah basically

i want to see a paper based dumb terminal now

I’ve failed in my duties as a penguin and am not nerdy enough to get the joke. could a more pious user explain?

junji ito moment

hey I’m pretty new to stuff like this, can someone explain?

mines been staying awake and asking me to confirm when I open it back up.

my issue with snaps is honestly just that they are controlled too much by just one entity (canonical) and there is no reason for them to exist because flatpak already does everything they do.

yiff is furry sex

I think it’s meant to be about gnome’s refusal to show the user anything ever lest they be overwhelmed by 1 (one) ui element cluttering the screen.

no more issues since that one thing i mentioned in matrix

when the obvious troll is obvious

I may have issues I never had on windows but I have way fewer issues and if I mention them online roughly half the time a dude who develops the thing that caused it sees it and, completely unlike any microsoft employee, gives a fuck. I once mentioned that I experienced a bug in the only mbin mobile app in reply to a post that was related to mbin but not the app (directly, anyway) and jwr1, the guy who makes that app, responded asking what it was.

I have seen the reasoning they are actually presenting, and it is just various versions of “but I don’t want this to be here” even though they have the option of not interacting with it. nobody is forcing maintainers to support rust code in the thing they maintain, they just can’t prevent rust code from interfacing with it. their arguments are based purely on not wanting to interact with rust but they don’t have to, so they are wrong to block it.

being new does not mean you do not have the right to develop the same way everybody else is. they did not start these issues, there were C people causing issues for no reason other than not liking rust that started it.