Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Get a devDuck
Rubber duck debugging has never been so cute! Get your favorite coding language devDuckBuy Now
Today is one of the days where I want to quit.
Oh wait, I own the company.
Anyone want to buy me out? :P47
> had an exam with a friend
> we both go to comp sci college
> had to write a fucked up algorithm in matlab
> he hates matlab
> he completes the task
> the variable that outputs the result is called holocaust
> he gets sent to dean
GF: Did you watch a movie while you were sleeping?
ME: (Syntax Error): How could i watch a movie while sleeping?
GF: No, the name of the movie is "while you were sleeping"
ME: oh, you forgot quotes for string13
This one time, a client wanted a complete overhaul of her website.
I asked her for the credentials to the VPS, She gave me some random crap to try, cause clearly the site hadn't been touched since 2003 (and boy was it fugly).
Me: Maam, these aren't the correct details.
She sends in more crap to try...2 days pass with this back and forth.
Client: "contact steve, he should have the login details"
Me: ****Calls Steve *****
Me: "Maam, he says the login details are in your mail"
Client: "well, I don't remember this fact. Steve handled everything.
Hack into the website and then reset it.
The Russians did not need login details to hack into America's system. So please, do what you have to do to get us moving."
No jokes...that was the exact crap that came out of her fingers22
* phone conversation with Dad*
Dad: What are you doing?
Me: Busy creating website.
Dad: So, if I type " www", will I be able to see it?
Me: *explaining website hosting and servers for 15mins straight*
Dad: Huh. You do learn something in college then.
*Sets VPN to france*
*Start receiving french ads*
Sure why not lol8
I got a work on legacy code. The app really depends on a library that was last updated on 2009. The website docs also missing
--- HTTP/3 is coming! And it won't use TCP! ---
A recent announcement reveals that HTTP - the protocol used by browsers to communicate with web servers - will get a major change in version 3!
Before, the HTTP protocols (version 1.0, 1.1 and 2.2) were all layered on top of TCP (Transmission Control Protocol).
TCP provides reliable, ordered, and error-checked delivery of data over an IP network.
It can handle hardware failures, timeouts, etc. and makes sure the data is received in the order it was transmitted in.
Also you can easily detect if any corruption during transmission has occurred.
All these features are necessary for a protocol such as HTTP, but TCP wasn't originally designed for HTTP!
It's a "one-size-fits-all" solution, suitable for *any* application that needs this kind of reliability.
TCP does a lot of round trips between the client and the server to make sure everybody receives their data. Especially if you're using SSL. This results in a high network latency.
So if we had a protocol which is basically designed for HTTP, it could help a lot at fixing all these problems.
This is the idea behind "QUIC", an experimental network protocol, originally created by Google, using UDP.
Now we all know how unreliable UDP is: You don't know if the data you sent was received nor does the receiver know if there is anything missing. Also, data is unordered, so if anything takes longer to send, it will most likely mix up with the other pieces of data. The only good part of UDP is its simplicity.
So why use this crappy thing for such an important protocol as HTTP?
Well, QUIC fixes all these problems UDP has, and provides the reliability of TCP but without introducing lots of round trips and a high latency! (How cool is that?)
The Internet Engineering Task Force (IETF) has been working (or is still working) on a standardized version of QUIC, although it's very different from Google's original proposal.
The IETF also wants to create a version of HTTP that uses QUIC, previously referred to as HTTP-over-QUIC. HTTP-over-QUIC isn't, however, HTTP/2 over QUIC.
It's a new, updated version of HTTP built for QUIC.
Now, the chairman of both the HTTP working group and the QUIC working group for IETF, Mark Nottingham, wanted to rename HTTP-over-QUIC to HTTP/3, and it seems like his proposal got accepted!
So version 3 of HTTP will have QUIC as an essential, integral feature, and we can expect that it no longer uses TCP as its network protocol.
We will see how it turns out in the end, but I'm sure we will have to wait a couple more years for HTTP/3, when it has been thoroughly tested and integrated.
Thank you for reading!14
Well I was in search for an internship and there was this Remote one posted online giving Rs1000(14$) for a month.
All he wanted was a fully functional clone of Coursera with hosted on AWS with videos of around 2-3TB streaming from S3 in a month :)
I asked him about his AWS costs and he replied - "Use the Internship money I'm giving you it won't cost much."24