Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "light-vs-dark"
-
Friend: Atom
Me: Vs Code
Friend: Light theme
Me: Dark theme
Friend: I believe there's some kind of energy that rules our destiny.
Me: Haha, seriously, no
Friend: (Starts telling me about some proposal of how he's going to build something).
Me: Yeah that's not going to work.
Friend: (Gets angry and proceeds to explain his idea on a whiteboard)
Me: Ahhhh yeah, sure it looks great
Friend: Dammit!!
Me: (I start telling him about some proposal of how I'm going to build something).
Friend: Yeah that's not going to work.
Me: (I get angry and proceed to explain my idea on a whiteboard)
Friend: Ahhhh yeah, sure it looks great.
Me: Dammit!!
If we didn't have such a solid friendship, I think we'd hate each other by now hahaha15 -
Light vs dark IDE themes
I personally prefer dark and all my coworkers use light. When they ask me to look at something, it hurts my eyes just scrolling for 5 minutes on their computer.19 -
People fighting about spaces vs tabs and I'm here fighting about coding in light theme or dark theme.11
-
Use light IDE when there's a lot of light around and dark in the dark.
Your eyes will thank you too in the future.4 -
So I agree with some arguments against using dark themes but only because they all seem to be about white text on black, but I would never use that as a dark theme... (who would?) Dark shades are where it's at! Take devRant itself as an example.
I had a hockey accident where the hockey stick hook caught me in the eye and among many other things, tore my iris to the point that the doctors couldn't stitch it (something about cutting being reparable but tearing not :/ )
Luckily with some exercises, it healed a lot in its own but still let's in about double the light it should. Since then, black on white for more than a few hours will, without fail, give me a migraine. But then so would white on black, too much light allowed in means that white on black give an almost blurry effect on the characters. Hence, colour shades for the win :D
Just my 2 cents ¯\_(ツ)_/¯ -
We need a thread dedicated to just debating tabs vs spaces and light vs dark themes, every third post is about one of them!1
-
There should be image-whiteness-check when posting images. It hurts so much when mostly white images throws white spears to my eyes while I scroll in dark theme unprepared for war with the white side.7
-
Finally convince my colleague to try sublime text. His coming from notepad++ and netbeans.
First thing he do, figure out how to change the theme to white background. -.- not so cool anymore.2 -
!rant
Another day, another weird trend that's come up on devRant. Today it's Light Theme vs Dark Theme. Take your pick and place your bets! 'cause after setting Windows to dark theme, I ain't leavin' it! What about you guys?2 -
Debate with fellow student:
Should the square within a PowerPoint slide (dedicated for a second projector video stream) be black or white?
"Of course it has to be white, otherwise we won't see the video stream!" -
Hi, in my latest project I'm stuck on the CSS part.
I've already an Grunt + Sass Asset Generator for bootstrap.
The project has several (> 70) subpages aka modules.
The theming is client based, currently 4 clients with different colors.
At first I thought it was easy...
Splitting bootstrap to variables per client + bootstrap, so:
client1_variables.scss
client1_bootstrap.scss (including client1_variables).
client2_variables.scss
client2_bootstrap.scss
. . .
But now I'm stuck.
Reaason: The css classes are the same between the clients, eg client-bg-primary is the class.
I wanted to prevent generating for each client a folder - as every folder would contain the same content:
module/news/client1.scss
module/news/client2.scss
module/news/client3.scss
module/dashboard/client1.scss
module/dashboard/client2.scss
module/dashboard/client3.scss
...
Each SCSS file would only differ in the variable import...
Is there a way to prevent a Global Module CSS file for each client (as there are @##* fucking classes duplicated and I really don't want to untangle that mess) but not ending up with writing the same Code over and over?
The IRC sass channel is moderated, not possible to ask there... And when I google I find mostly themes based on an class approach (border-light vs border-dark)… :(2