Was helping somebody with a little C++ issue (disclaimer: I know jackshit about C++).
After a while off reading his code and opening a file called "pi.cpp", I noticed something odd...

This guy literally thought is was a good idea to put 81663 fucking decimals of pi in a #define statement :^)

On the screenshot, that weird "noise" on the right is actually a scrollbar of the code itself...

You know you're in for a difficult time when the answer on stack overflow has a code area with a scrollbar.

Just who the fuck from apple thought its a good idea to make the FUCKING SCROLL BAR overlap, the FUCKING PROPERTY ARROWS, everytime i accidentaly hover over it? I cant change shit! I have to wait few seconds every time i accidentaly hover over the scrollbar so i can be able to FUCKING CHANGE the value!

Dear Apple Inc,

Fix your shit! We're paying 100$ a year for what? More bugs and toruture? I didnt sign up for this bullshit! Give us back some real quality products, or just buy the company Jetbrains and let them build the IDE for you instead.

"We want to change the scrollbar colour." -Client

Oh no, no no no; we sorted this years ago. Nobody should have that power.

Designer: Can you hide scrollbar and still make web scrollable?
I: Sure.
Designer: Ok fine, i'll do that in next design.
I: Wait, how users will know the web has more content?
Designer: I'll put the mouse icon on the bottom.
I: It is not good idea. People can overlook it.
Designer: It will be fine.
I: I strongly recommend to you not to do it.
Designer: Why?
I: Confusion besides other reasons.
Designer: If you can do it, do it.
I: Ok than.

$request->getIP() == 'his_ip' ? 'hide-scrollbar';

What's with the 4 pixel wide scrollbars on some desktop software these days? Does nobody care about accessibility anymore?

No seriously.

Fuck you.

And why the fuck does open source software seem to be the main culprit - as usual.

And tutorials telling us to add an extra blank line to our source code because fucking Linux distros decide to put an overlay horizontal scrollbar just over the top of where the last visible line in an editor appears.

YOU KNOW WHAT I FUCKING HATE.

THE IPHONE'S DEFAULT WEB BROWSER, SAFARI

"OH YOU WANTED THIS TO BE EXACTLY HEIGHT:100VH? HERE'S A FUCKING SCROLLBAR."

I finaly managed to make a dark mode on slack desktop app! Still has some bugs (like scrollbar being white) but works well enough for me. If anyone is interested tell me in the comments 🙂

How i did it (Linux paths but should be the same process for Windows):

You can execute scripts in /usr/lib/slack/resources/app.asar.unpacked/src/static/index.js

Using that i figgured out that slack desktop is basically an actual webview to their website and some os hooks.

To edit the contents of the webview you can call `document.getElementsByClassName('WebViewContext')[0].executeJavaScript("alert(1)")`

Then i just simply packaged up some custom css to be loaded with JS.

Quite simple actually.

Using this method you can create all kinds of plugins for slack, so go wild!

css quick maffs

so you did this:

.foo:hover {
transform: scale(1.1);
}

and now ugly scrollbar is there when the element is scaled.

No, don't do overflow: hidden. There's a better way. Instead, do this:

.container {
padding: 1rem;
box-sizing: border-box;
}

the element total width is calculated based on the width of its content. That's true unless you specified width and height explicitly (if you did so, you're a doofus, I'm sorry).

Scaling makes content somewhat larger. With border-box, paddings work differently with the total width.

By default, if you set width to say 100px, and paddings are 20px, total width will be 140px — it's your 100px of content plus two paddings of 20px. width property set the width of the content, not the total width.

With border-box, width property sets the total width. So if you set width to 100px and paddings to 20px, total width would be 100px, just like you set it, and content will be 60px wide — it's 100px minus 20px times two.

The key part is it doesn't end with explicit width. The algorithm remains. When some node is rendered, its total width is calculated. When you use border-box, the total width will stay the same even if your content grows by some value that is less than your paddings. So, your content was 100px, you scaled it, and it became 110px. Well, then that extra 10px will be subtracted from your paddings, and they will be 15px each instead of 20px.

No more ugly scroll bar. Yaaay!

aight bye

I think, after a few weeks, I'm actually quite enjoying that the Android SDK is genuinely awful.

We all know the feeling: "This is shit, whoever designed this is a fuc...oh, I get it. This is pretty cool actually."

So, it's nice to encounter a genuine dumpster fire of a platform.

I think the beautiful thing about its absolute obsession with providing a context to every single operation, is that you end up passing it around so much that the very concept of context becomes redundant.

Honestly, half of the stuff in here I've just attached to a global statics class, because it saves having to request a context, or a manager or some fucking kind of adapter, and it works just fine.

I've started to laugh when I look up a solution and see the browser scrollbar shrink into infinity, because the recommended answer is about two whole pages' worth of boilerplate to make the back button disappear or something.

I don't think there's been a single moment where I've just been in the flow of writing code. Pretty much all of the process is grafting boilerplate into it.

Not long til deadline, thank fuck.

WHAT THE FUCK!!

For a freelance job I searched for a JS function in the HTML document of a Wordpress site that was given to me.

Found it and wanted to get started on the project, but there was something odd about this website (besides it's a Wordpress site). The scrollbar was fucking small and when I scrolled down, all I saw was breaks. An almost endless number of breaks.

Then suddenly There was a line of HTML!! And then another 126 breaks.. :/
(Yeah that's right, I calculated the number of breaks between every line of HTML). This document has 75732 lines of shit.

The whole fucking website loaded in over 20 seconds!! What the fuck is that?!?! The document itself is 258 kB!!

But whatever, I get paid.

I'm new into Java and tried creating a simple GUI.

Took me about 3 hours until i've found out that I must put a JTextArea into a JScollPane and not the other way around to display the textarea with a working scrollbar.

I love this already.

(I'm also a new devRant user, so... Hey :] !)

Im getting annoyed by the new layout of google. Hovering the sidebar will make a scrollbar appear but the main part of the site's scrollbar will disapear. This results in most content moving from their original place. Let's make a Stlyish script to fix this problem I thought. Guess what now somethings stay where they should be, but the things that were first on the right place have moved. Also this will make the header shorter. I'm getting more and more amazed how shitty some frontend devs are at google.
To fix one bug they, instead of solving the bug, tried to counter the result of the bug.

I do like the z-index of the sidemenu though (it's 2005, the year youtube was created)

Changing the native browser scrollbar should warrant the death penalty.

Do not make it narrower. Do not make the colors blend with the background. Do not hijack it its functionality. Do not minimize it until I hover.

I am so fucking tired of websites that think they are in charge of my browsing "experience" and hide or otherwise marginalize the single most useful part of the page's UI.

Fuck Unity.
Every single time I try to use Unity to develop my well-along-in-development video game, it finds some way of fucking itself up.
Be it from somehow failing to compile a DLL - which is something completely out of my control, the inspector failing to update itself when I select a new object every five minutes, to the engine managing to fail to load its UI layout because it somehow managed to lose a file responsible for containing the layout, the Inspector forgetting to include a scrollbar and as such trying to cram a bunch of components into one area, crashing in a certain area because I tried using reflections, crashing because I tried running the game in a place that always works, all the way to the whole thing closing instantaneously when I try selecting a new layout.
My experience with using this god-forsaken configuration of code and imagery has been one of endless torment; I've spent hours lamenting about the pain this piece of utter horseshit has caused me to those who'd listen.
I don't know what I did to this thing to deserve to be shown the absolute worst of this engine for the year I've been working on my game for. I can't even take a look at its source code to see if I can piece together things I'll pick up from alien code to fix obnoxious bugs myself because you cunts have it under lock-and-key for some dumbass reason.
Even updating my install of this engine is a gamble; I remember clear-as-day updating my project from 2019.3.14 to whichever one was most recent at the time, and everything breaking. This time, I got lucky and managed to update to 2020.1.4 with no issue on the surface, except I inadvertently let in a host of other issues that somehow made the editor worse than the older one.
There's little point in even bothering to report a bug because this shit happens so randomly that I could be just working on auto-pilot and the next thing I know Unity's stupid "crash handler" rears its ugly head yet again, or you people are probably too busy adding support for platforms no sane person uses like fucking Chromebooks.
There've been times where it's crashed upwards of three times in the span of 40 minutes of light use.
How is one expected to cough up hundreds of dollars a year to use a "pro" version of this horrid editor when every session of use yields a 50/50 chance that it'll either work like it's supposed to, or break in one way or another?
It's a miracle I even managed to type all of this out in one go, I expected the website to just stop responding entirely once I got past four lines.
Do what you will with my post, I don't care.

i noticed just know that the scrollbar in Devrant kinda moves like a caterpillar. especially with long posts.

Notepad of all things just freezed on me and restarted, losing my notes progress three times before I realized what was happening.

Thanks Microsoft for giving me a reason to hate Win11

Turns out the moment the vertical scrollbar appears, it crashes. That's it, a fucking scrollbar.

!rant

Could anyone explain to me what the meaning of the size changing scrollbar is?
Does it show the ratio of window height over the height of the current rant or comment it the latter is longer than the window?

*adds border to the bottom of a fucking div*

Why, hello there Mr. FUCKTARD HORIZONTAL-FUCKING-SCROLLBAR. That totally makes God damn fucking shittard fuck'ala'fucking fuck-damn'le-shit-fucka-shittard sense.

Took an hour to fix color of scroll bar.
The issue I fixed from this "#injectLocation ::-webkit-scrollbar-thumb" to this "#injectLocation::-webkit-scrollbar-thumb"

What's up with the scrollbar?

So my company wanted a view in view look on their website. So it would look like a black background with a while box in the middle, right?

Well, the devs apparently thought that screens were capped height! On my monitor, the box is less than half the height, but since it stretches the width, the image got larger. So my screen has a scrollbar, and the actually useful part also has a scrollbar, with a shitton of space below!

If that didn't make sense, see crappy drawing of what I see...(painted on Phone). The dashes are the hidden parts that I can't see because of the window!

Did you notice that the scrollbar in the devrant (android) app changes size depending on the lenght/number of posts/comments you can see at the moment? Just scroll down in the posts list and see the scroll bar crawl like a caterpillar 😮

What the hell is this website's problem?

Why must the scrollbar look like its having a seizure whenever I scroll faster than a brisk scroll? Why does it even have to change length at all? Why can't it just be the same length all the time? It happens a bit in the devRant app, but it's even worse in other apps (like the reddit app).

Holy shit. I'm on the devrant app and I just noticed that the scrollbar on the right does this weird worm thingy.

As I scroll up and down, the scrollbar size keeps changing. It's a cool effect where it twitches like a worm.

Is that an android o feature or something or did @dfox or @trogus add that shet.

I really don’t get it, how can most people just so easily accept shortcomings and not even try for a second to improve the situation?

It drives me crazy ...

story:
I’m debugging an issue with a colleague over screen sharing, both of us have huge 4k screens. Colleague sets a breakpoint, popup opens „do you want to switch to debug perspective“, clicks on yes for the umpteenth time. Breakpoint halts, IDE is full of open and unrelated panels, he doesn’t even see the whole line if code but still grabs the scrollbar every friggin time and scrolls left, right, left, right, ...
changes some code, popup that hot code reload didn’t work, clicks ok for the umpth time here as well, although it has a don’t show again checkbox, like every frigging dialog in eclipse.

how can people work like this, it’s driving me nuts. Am I the only sane dev here??
Other colleague has weird message in the browser console (angular). I ask whats the problem and if he can’t just set a breakpoint to analyze the situation. No thats not possible, he says, instead he’s going to add a return statement to check how far the code execution goes ...

I wonder sometimes if I‘m already dead and have to suffer in dev hell for an unknown reason ... 🤔

When my Firefox window is too narrow devRant completely shits all over itself and glitches so hard that rants cannot be scrolled anymore unless I make the window larger and go apeshit on the scrollbar until it fixes itself again.

I thought my mouse broke.

Just Installed devRantron, and noticed I cannot navigate through rants/posts by arrowkey.

Am I missing somthing ?
I clicked on the scrollbar and arrowDown scrolls down but not able to navigate through post with arrowKeys.

2 hours of debugging a web page. We had a simple border: 1px; margin: 4px; on the container, but on the right side it the border was outside the screenspace.

Like, gooohhh I hate this, is it some element that's making the container grow or something? Doesn't happen on all screen sizes..? So confused. No scrollbar so where's the overflow: hidden? ARGH I'm no pro at this! And this is a spagetti css file; just work stupid css!

The reason why, which took toooo long to find 😓, was that the monitors physical border was overlapping the right side of the screen, oh at such a suddle amount. Enough to not be noticeable normally, it looks completely usual, but it hid that stupidly stupid border!

I so hate/love when there's so such a simple solution. But now I'm gonna be stuck checking the screen border when instead it's my css that is off...

Javafx is annoying as fuck.
I still don't know how to add a scrollbar to a vertical box. Why can't it be like visual studio? Just drag and drop.

So, my experience is all with relational DBs (mssql) mainly and this job is the first time I've had to deal with mongodb.

I'm using the default compass client and I'm struggling with just how shit it is.
- A default font size of 5px high which resets every time it starts.
- Total lack of keyboard shortcuts.
- Inconsistent expansion& folding behaviours
- No saving of aggregates/queries if you accidentally click on another collection.
- ittle bitty query window which is actually multi line but with no scrollbar...
The list goes on.

And mongodb, whoever thought JavaScript is an appropriate query language... It's not.
It's probably because I don't have enough experience with it but the mix of quotes and $ seems so random...

Does anybody have an idea how the height of the scrollbar of the devRant app is determined? It changes while scrolling, and I have not figured out yet why.

I just noticed something.... I think I read more rants if they're displayed in pages with a scrollbar instead of infinite scrolling in the app.

Guess the rewarding feeling of reaching the end of a page helps?

What kind of scrollbar design is that?

This is why those "smart" scrollbars that "save space by only showing when needed" are a foolish idea.

Fuck the trend in reducing scrollbar size. Has no one heard of Fitts' law?

How does anyone wrangle all these fucking JS packages!

Trying to fix issue where a table overflow problem...only in firefox. Found a quick fix then discovered it does not work when there is an event with a handle.

So come to find out perfect scrollbar does not like flex nor firefox (the only browser for the end user)

Jesus christ I miss laravel.

Why the fuck would Google promote Jetpack Compose as a stable toolset when it doesn't even support a basic feature such as a scrollbar.
A. Fucking. Scrollbar.
LazyColumn can't even come close to being as powerful as Recyclerview.

Here's an idea, before launching something and touting it as something usable, and encouraging people to drop the old, battle tested tool for the new shiny one, how about you make sure the new doesn't lack features present in the old one?
Seems logical, right?

Methinks somebody was just looking for a promotion because, clearly, Jetpack Compose is a half-baked product.
Now, developers will have to suffer because project managers will read about the new framework and ask devs to use it, then wonder why the app is suffering.

My computer after installing Solus has some pretty weird behavior.

It is with the keyboard and the mouse. The keyboard often writes the highlighted part, which is super annoying, because I have this habit of using the highlighted feature as a scrollbar, so if I am using this feature to scroll in the terminal, when I am editing, the keyboard will paste the content of the highlighted text when I am typing randomly, which is why I have to highlight a space, and also why I have to put my cursor to where I am typing to prevent it from randomly teleporting. And the mouse often left click / right click randomly, and sometimes the cursor has a seizure.

This is not something that happens to me recently. It has been happened to me when I was using Manjaro (which was way long ago), and at that time only the seizure cursor is happened. Now more stuff happened, and they are happening more frequently than ever.

The Internet on my computer is also terrible today, I cannot access to any website on the browser (Until now). I first thought that it's my browser (Brave)'s fault and I tried on Firefox, also not working. I tried to reconnect to the Wi-Fi, reboot the computer, nothing worked. Then I think of switching between Wi-Fis, because it's a strat that worked with my phone, and surprisingly, it worked!

(I really don't know what to end this rant, so I will just put this text here as a way to end the rant.)

I love how the devRant webapp is intercepting scroll events (I assume) such that attempting to scroll down results in one step down, two steps up.

Why? Is this an attempt to solve jellypotato for infiniscrolling?

Looking further I see the scrollbar itself is actually getting smaller, like some element on the page is extending beyond the end or something. 🤔

I don't know, man...

goddamnshitmotherfuckingshit wtf brain? why do all the examples just work, but my code looking similar just doesn´t. why the fuck is this basic thumbsucking baby topic of a scrollable canvas screwing me over since this morning?

So when will DevRant stop taking over my fucking scrollbar in Chrome?