A place to share screenshots of Microblog posts, whether from Mastodon, tumblr, ~~Twitter~~ X, KBin, Threads or elsewhere.
Created as an evolution of White People Twitter and other tweet-capture subreddits.
RULES:
RELATED COMMUNITIES:
Anyone using Electron to build any greenfield app is a fucking moron, full stop.
When you have to consume 300+Mb of memory just to display 15Kb of text, when the exact same thing can be done in native code for less than 2Mb of memory, “moron” is the kind and gentle word to use.
Excuse me, but did you not see my fancy graphic and animation? And my cool autoplaying adverts? And the dickbar asking you to subscribe to my annoying newsletter?
I don't know what web you're looking for, but it's not the one I (and my many clients) design for. /s
/s I'm not a web designer or coder. I only host plain html. Shut up. It's sarcasm / satire done poorly.
Just use Qt and you're already cross-platform.
Or if it has to be web, you can get crazy far with a 15 kB HTML document and possibly some native JS.
I mean, even before everything went to hell and prices shot up, this is sane.
around 75% of the project lifecycle, All developers should be moved to the min spec hardware they plan to support at launch.
I...I kinda like that.
The problem is crunch happens toward the end and no sane company would do it.
It is kinda what needs to be done though. QA complaining the experience is poor doesn't have the same driving factor. Fuck polish, make it feel good first
Especially Atlassian.
I had a Jira Tab (one single Tab) once use 1.2GB.
Whenever I have to open a jira link, I click it and go for a coffee break
CSS files shouldn't be heavier than HTML, that's literally form over substance.
All JS code should require pressing a button to run.
Ouu, that's actually a really smart rule of thumb, why should js be running if nothing has even been clicked?
Ad auctions, tracking pixels. You know all the fun parts of a web page.
As a mobile developer, I got an email from google saying they're going to be adding new memory restrictions in apps and it'll crash if you exceed them.
Thanks google, for buying all the ram, and then punishing us for it.
i can see how this might evolve... someone, the app developer or the user, will end up having to pay google to let an app use more ram than google allows it to for 'free'.
They need this to compete with Apple, apple runs on a lot less Ram because it imposes such limits already, simply by not having as much RAM to begin with
gotta get rid of their fast internet, too. 128kbps max (like 2 channel bonded isdn).
...and they should not have a GPU either, so they can feel the cost of full-motion parallax-scrolling fade-in backgrounds.
Hot take: node.js was a mistake
Electron was a colossal mistake.
js was a mistake
JavaScript was a mistake.
And it's my fault, and I'm really sorry.
~ Ryan Dahl onnode_modules.
As somebody whose most familiar language is JavaScript, I agree.
Hotter(?) take: JavaScript is a mistake
2GB? Barely enough for the VM of the Docker of the flatpack for the cloud mouse driver's DRM!
Dicker is the new container virtualization technology.
it uses middle-out compression
👉👈
✊
They misspelt 640K
Instructions unclear, the site is now best viewed with at 640K Transcendent HD.
Your 100 MB webäpp is still shit, in every metric.
No monitors above 1920x1200 and they must code in bright sunlight at least 8 hours a day. I'm convinced some websites look like ass because the developers haven't look at anything below 4k. Maybe ever. Some may not have seen sunlight in years. Not everything needs to be made for dark viewing with white text everywhere.
I've found most websites that look like ass on a 24" 1920x1200 screen (or really any desktop monitor) is because they are designed for a 5-6" cell phone screen.
Oh god, yes, I wish they had to work in a bright environment. Every other website (and even some desktop applications) feel like it was coded by someone who hasn't left their basement since Obama was still in office.
I mean, seriously, how can people unironically say stuff like 'black text on a white background hurts my eyes'? Turn on the fricking lights damn it. Staying in badly lit environments is bad for your eyesight anyway.
Also, while we're at it, I am also not a fan of grey text on a grey background. Okay, rant over.
LOL, just turning on Windows will blow that up. Then, opening Chrome... LMAO. Can you even run on 4GB of RAM anymore? Like, Raspberry Pis have over 4GB now.
OS developers should be banned from having more than 2GiB of RAM too.
You absolutely can. I have Linux with Hyprland and it is less than 2gb doing nothing. You can probably run ARM boards and do the same. I think with browser it is still less than 4Gb. Your system just needs to be free of corporate garbage.
I guess if you're running 32-bit, but in 64-bit land the word size is double so it'll barebones run on double the 32-bit system (at minimum). Once you open a modern browser, it opens like 6 tabs (with a blank tab); there are background tabs. Pictures and active media consume a large amount of bandwidth and memory, which is a con against the modern web. I guess we should go back to BBSs.
I also don't run "corporate garbage." I use FOSS exclusively. But Windows, and its svchost'd jobs, eats over 2GiB ram idling.
I have a console window open on my debian desktop that is eating 5.1gb.
That's almost all just text in the tabs.
Stuff also just takes a lot of memory.
The one thing that the Fediverse wanted to destroy: not being able to cross post across social media software.
What people do: 📸
I fucking LOVE things breaking when the other node inevitably goes down, or the person deletes there post.
The URL to the originating instance is right there.
Edit: the microblogging quote post standard is just a URL as well.
4k fullscreen uncompressed picture is a bit under 24MB. (3840*2160/1024/1024*3 = 23.73)
Which is why you show a lower-res preview as default. Don't want to wait a fucking minute to decide if i like your picture or not.
Which reminds me, Chrome/ium/Firefox's dev tools have a bandwith limiting feature. A lot of so-called web developers don't know that.
Another idea: ban all public-userspace devs from have more than 2GB ram on their dev systems.
If it's going on the market for joe-schmoe, ya gotta make it work on a complete shitbox before shipping.
