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 - "footers"
-
Getting rrreeaaalll tired of the Treehouse ads in my YouTube videos. In my sidebars. In the footers. In my kitchen. Following me down the street. Join us, they say. You'll get a job in six weeks, they whisper. Life without Treehouse is empty and meaningless, joinnn usssss.
-
Didn't know about using php includes for headers and footers when I coded my first big site. Now having to go back through and add it in page by page so I can roll out updates more easily down the line. Bleeeuuggghhh1
-
Fucking jesus christ, for some reason in chromium-based browsers if you have a table that fills up to the full height of the parent using flexbox rules, if you go to print it, it will fucking
i forgor 💀
and give it a height of minimum content height. The solution is to ALSO give it height: 100%;
Google completely unhelpful (I guess it's too specific and most people don't write web services specifically made for printing out?) but luckily it only took me like 3 guesses to figure out on my own.
But I could have easily seen this completely pissing me off to the point of quitting. FireFox doesn't have this issue.
RELATED TANGENT RANT:
Why the fuck is the default to use headers, footers, margin, and no background images (colors) ?!?!?!? The default printing for browsers COMPLETELY FUCKS UP THE PRINT
God FUCKING damnit.14 -
That feeling when a backend dev (me) fixes frontend at night!
Feeling so happy this footer stays down there!!!!!!3 -
News sites with infinite-scrolling are so damn annoying.
A new random article I am not interested in suddenly loads under the current news article when skimming through it by dragging the scroll bar, and then throws me far down into unknown territory due to the sudden change of the height of the page.
It also happens similarly on Imgur photo galleries: when I drag down the scroll bar to quickly seek through the images, the "explore posts" section suddenly loads hundreds of "trending" and "viral" (uninteresting junk and spam) photos under the gallery, and since this adds lots of height to the page, I get pulled right into it and my window is full of such posts. Both distracting and memory-consuming.
YouTube's infinite scrolling comments and video lists are acceptable as of writing, since they are on-topic, and no off-topic "trending" spam, and they do not load too much at once, which does not throw me down too far.
Quote from https://elite-strategies.com/infini... :
> The footer of a website is like the shoes of a person, it ties the whole outfit (or website) together. Footers are awesome because it gives you a chance to tell people where to go when they reach the bottom of the page.1 -
The process of making my paging MIDI player has ground to a halt IMMEDIATELY:
Format 1 MIDIs.
There are 3 MIDI types: Format 0, 1, and 2.
Format 0 is two chunks long. One track chunk and the header chunk. Can be played with literally one chunk_load() call in my player.
Format 2 is (n+1) chunks long, with n being defined in the header chunk (which makes up the +1.) Can be played with one chunk_load() call per chunk in my player.
Format 1... is (n+1) chunks long, same as Format 2, but instead of being played one chunk at a time in sequence, it requires you play all chunks
AT THE SAME FUCKING TIME.
65534 maximum chunks (first track chunk is global tempo events and has no notes), maximum notes per chunk of ((FFFFFFFFh byte max chunk data area length)/3 = 1,431,655,763d)/2 (as Note On and Note Off have to be done for every note for it to be a valid note, and each eats 3 bytes) = 715,827,881 notes (truncated from 715,827,881.5), 715,827,881 * 65534 (max number of tracks with notes) = a grand total of 46,911,064,353,454 absolute maximum notes. At 6 bytes per (valid) note, disregarding track headers and footers, that's 281,466,386,120,724 bytes of memory at absolute minimum, or 255.992 TERABYTES of note data alone.
All potentially having to be played
ALL
AT
ONCE.
This wouldn't be so bad I thought at the start... I wasn't planning on supporting them.
Except...
>= 90% of MIDIs are Format 1.
Yup. The one format seemingly deliberately built not to be paged of the three is BY FAR the most common, even in cases where Format 0 would be a better fit.
Guess this is why no other player pages out MIDIs: the files are most commonly built specifically to disallow it.
Format 1 and 2 differ in the following way: Format 1's chunks all have to hit the piano keys, so to speak, all at once. Format 2's chunks hit one-by-one, even though it can have the same staggering number of notes as Format 1. One is built for short, detailed MIDIs, one for long, sparse ones.
No one seems to be making long ones.6 -
!rant
Tl;Dr: I ate shit for 3 months and finally got rewarded.
If you read my last rant you might remember that for the last 3 months I was tasked with a formal QA of some hundred word documents. (Checking headers, footers etc.)
This is almost over (8 days left)... Finally...
Today I had to present the work I did to the head of IT. The presentation went fairly well and at the end she offered me that she would be willing to get me a job the city where I'll be moving to study.
I have only met her 4 times during the year that I worked there but someone or something must have convinced her to care.
So it's seems like I'm not going to have to bother with all the usual HR bullshit and will have the opportunity for a steady income during the next 3 years.
Today was a good day. -
http://bit.ly/2fme7PU
Check out this article I wrote on Jekyll. There's a tutorial in progress there too :) Jekyll is a static site building framework that allows you to dynamically allocate headers, footers, etc. Change a header once and it updates across all pages. I have a tutorial in progress there too :)3 -
A mix of both python 2 and python 3. 4 entry points (although, this was done for the sake of microservices).
All in 1 big monorepo. Hosting a site in mostly static form (i.e each page had it's own index.html with completely different headers and footers, no templates).