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 - "it's free real estate"
-
How many here know surge.sh? it seems each time I mention it somewhere, nobody knows it, checks it out and thanks me. It basically allows you to host a static webpage on their servers - for free and with custom domain if you wish. They are also the creators of Cordova/Phonegap.3
-
Android studio gradle nightmares, cli not picking active jdk, intellij maven horrorshow, vscode being the nexus of perdition itself. When I'm dead and gone, scatter my ashes over sublime text. NEVER encountered a headache, ever. The setting for autosave is one forum visit away. 1000s of utilities at my fingertips, with shortcuts, not silly plugins. Neither hangs nor fusses irrespective of how many windows, projects, tabs I've got open. Gargantuan code real estate despite having a file panel and file preview. The only guys who got monokai right. Can open random editors and fill them with notes without first saving. A more intuitive vcs gui than even github desktop. More lightweight to download than an beep.ogg. Never lags cuz it wants to be powered by a wind turbine. It's free. Literally all the sorrows that terrorise my dev in its peers, all gone
Yes, it's not "integrated" to my de, in the sense that its intellisense is a glorified autocomplete for existing tokens. I guess, tradeoffs must be made. If you know the language well enough not to grope handheld by the ide, or in dynamic typed languages where red, squiggly lines will not bring your software down to its knees, it should be head and shoulders above those conartistes
Enterprise edition una -
So yeah, my IDE is open and I'm just doing my daily rounds on SO when my rig suddenly feels like it's melting from playing Battlefield in 4K everything max. Chrome! Chrome! Chrome! It thinks were married, taking liberties with all my free real estate. You are out! Hey Firefox DE.1
-
It's CSS quick maffs time! Consider the following code:
<div class='container flex'>
<nav class='menu flex'>
<a href='#'>Menu item 1</a>
(arbitrary amount of links)
</nav>
<button type='button'>Sign in</button>
</div>
You want the layout to look like a horizontally scrolling, single line menu with a Sign in button to the right. Both container and menu are flex containers. So, here's the code for the menu:
.menu {
overflow: auto;
}
The problem is, as there is no flex-wrap, menu will not be wrapped, and it will occupy all the space it's needed to accommodate all the elements, breaking its container. Pesky horizontal scroll appears on the whole body.
Boubas will set menu's width to some fixed value like 800px, and this is a bouba approach because bye-bye responsiveness.
Here's what you should do:
.menu {
overflow: auto;
min-width: 0;
}
.menu * {
flex-shrink: 0;
}
This way, menu will occupy exactly the width of an empty div. In flexbox, its width will be equal to all free space that is not occupied by the Sign in button. Setting flex-shrink is needed for items to preserve their original width. We don't care about making those items narrower on narrower screens, because we now have infinite amount of horizontal real estate. Pure, inherent responsiveness achieved without filthy media queries, yay!
The menu will scroll horizontally just like you wanted.
aight bye14