The world as we know it is ending!

F U Facebook!

https://forbes.com/sites/...

PSD2 is into effect in the Netherlands.

Because let's enable others to fuck over other peoples privacy!

Back to cash as much as possible it is.

Fucking hell 😡

Well here's how I see things going:

Intel and AMD ditch their assembly architectures for Scratch, because drag and drop is very popular lately.

The Boolean is renamed to the biggot by SJW leaders for only supporting binary views.

You must first ask consent to add an item to a linked list, because forcing two items together promotes rape culture.

Apple removes the "h" and "7" keys on all laptop models and gives no reason for their actions.

Linus Torvalds grows an extra middle finger, and it still isn't enough.

Nintendo makes Mario gay and Luigi black to be more inclusive.

LG makes a curved monitor that curves away from you rather than towards you. People buy it in confusion.

Everyone makes the same ad revenue on YouTube, and it is rebranded to OurTube. Luckily, they were able to keep the color scheme.

People finally realize that machine learning is just math, and stop using it everywhere. (Just kidding lol)

AMD and Gucci merge. Nobody understands why.

TOP 10 PROGRAMMING BEST PRACTICES

#1 Start numbering from 0.
#10 Sort elements in lexicographic order for readability.
    #2 Use consistent indentation.
#3 use Consistent Casing.
#4.000000000000001 Use floating-point arithmetic only where necessary.
#5 Not avoiding double negations is not smart.
#6 Not recommended is Yoda style.
#7 See rule #7.
#8 Avoid deadlocks.
#9 ISO-8859 is passé - Use UTF-8 if you ▯ Unicode.
#A Prefer base 10 for human-readable messages.
#10 See rule #7.
#10 Don't repeat yourself.

--- 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!

The creation of an e-ink usb stick showing how much space is in use was to this day one of the best things lexar ever did.

I laughed harder than I should have.

Why Apple developer are up at night?

Machine Learners :D

Never let customers define the priority levels. It will end in:
- Normal (never used)
- High (used for small text changes)
- Higher
- OMG fix now
- Highest
- the World is ending if this doesn't get fixed now
- different existential plane of priority
- Priority ∞ + 1

I saw Mr Robot and Gilfoyle from Silicon Valley at the office cafeteria today.

"happy" holidays (found on instagram, credit to shitheadsteve)

—_(*_*)_—

People who send an email saying "I'm getting an error message".

WHERE DID YOU GET IT?!

WHAT IS THE FUCKING ERROR MESSAGE?!

OH NO SURE LET ME LOOK IN MY CRYSTAL BALL, I'LL HAVE IT FIGURED OUT FOR YOU IN NO FUCKING TIME.

😡

If you refactor code and make it worse, did you refucktor it?

I would do this, if I had a job

:D :D :D

Lets all help them share their startup

OMFG! LMAO! Adobe!

I'd be really happy :)

I don't understand why so many people fight this war of tabs vs spaces. My colleagues elegantly solved the problem just not using indentation at all

System.out.println("lol");

I hate it when I run out of internets.

Probably the funniest phishing test I've ever seen.

Dear people who complain about spending a whole night to find a tiny syntax error; Every time I read one of your rants, I feel like a part of me dies.

As a developer, your job is to create elegant optimized rivers of data, to puzzle with interesting algorithmic problems, to craft beautiful mappings from user input to computer storage and back.

You should strive to write code like a Michelangelo, not like a house painter.

You're arguing about indentation or getting annoyed by a project with braces on the same line as the method name. You're struggling with semicolons, misplaced braces or wrongly spelled keywords.

You're bitching about the medium of your paint, about the hardness of the marble -- when you should be lamenting the absence of your muse or the struggle to capture the essence of elegance in your work.

In other words:

Fix your fucking mindset, and fix your fucking tools. Don't fucking rant about your tabs and spaces. Stop fucking screaming how your bloated swiss-army-knife text editor is soooo much better than a purpose-built IDE, if it fails to draw something red and obnoxious around your fuck ups.

Thanks.

Every new product these days has the tag line "powered by AI"

FUCK OFF

No it isn't.

A mass of "if" statements isn't AI!

I did a fucking scientific study about fucking rants and found a fucking high correlation between the usage of "fuck" and the number of fucking upvotes.

HE:"Hey I improved my code"

ME:
*opens the file*
*Sees random static allocations*
*Code is as verbose as before*
*Down to 2600 lines from 2800ish*
*Still doesn't do shit properly*

"Uuuh what exactly did you do?"

*Starts noticing the lack of namespaces*

HE: "I used this using namespace std to write a bit less"

ME: "Can I pay you yoga lessons so you can taste your own cock and show your parents how good you are at it?"

Working at PornHub

devRant just hit 50,000 downloads on Android (fancy new store badge, yay!). Thank you everyone for being part of this community and spreading the good word! @dfox and I have some fun new features in the works, exciting times!

Your profession changes how you think.
Coding did the same for me. Some good, some bad.

The good:

I know which problems in life are worth trying to solve.

And I'm very good at solving those problems.

I can analyse a situation accurately. I don't get emotional and panic.

I can immediately identify logical flaws in people's thinking.

I can identify biases in others and myself.

The bad:

I tend to follow simple instructions to the letter and rarely improvise based on reality.

When my wife tells me her problem I try to solve it instead of empathizing - which is what she really wants.

I haven't developed street smarts or the ability to convince people with anything other than logic - but people are more emotional than logical.

I'm not good at small talk.