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
-
"It must work in IE6, we still use it in our offices."
While developing a JavaScript web app for a bank with 10 000+ employees. In 2014.8 -
Had a request from a client once, "I'd like that our site supports only IE10 and above. However if the visitor uses older IE version, say IE6, things should look and work the same as IE10".10
-
Best and worst customer I've had: A bank.
Great because they had so much money for projects.
Unbearable because everything needed to work in IE6.6 -
Good news everyone. As of 30th June 2018, PCI compliance demands a minimum of TLS v1.1. Meaning it's illegal for your website to support IE6-1011
-
We've started a new betting system in our office. Every time you lose a bet, you have to optimize atleast one project for Internet Explorer 😂7
-
Hello, I just want to let you know I'm working on a 15 year old product and it is currently in production.
It uses Angular.js and one of the earliest versions of React.js. I cannot use ES6, we don't have Babel, no JSX syntax, no CSS preprocessor. No webpack.
I must support browser since IE6 with an ES3 syntax. (luckily I got some some polyfills for an ES5 syntax)
When I build a component I have to call React.createClass and React.createElement.
The render() function is basically a nested pile of React.createElement.
There is no documentation for this product, no tests, no anything.
I had to reverse engineer it in order to understand how it works.
The code base uses mixed programming styles and naming conventions, plus thousands of little js files.
Oh and obviously no hot reload, every time I make a change I have to restart everything.
Please, send help.
I'm in danger.
Sincerely,
An underpaid developer
....
I'm not crying, you are crying...19 -
Me: the websites now works on all devices.
Client: now make it work on IE6.
*1 week later*
Me: the site now works on IE6 too.
Client: awesome, now make it work on Netscape navigator 56 -
Last year a random company hired me to develop an Angular app. One of the main requirements was that it needed to be compatible with IE6 cus thats what they were using internally... I accepted the offer...5
-
My gf said some of Japanese companies specifically ask developers to code for IE6 and IE6 only. 🕺
Glad that I don't have to work for them.5 -
Tomorrow is the day I have been waiting for my entire career...
Tomorrow Microsoft stops supporting Internet Explorer! 🥳14 -
"I want it looking and working exactly the same in IE6, IE7, IE8, IE9, Chrome, Safari and Mobile...."
Oh wait, that happened...9 -
FUCK Android, whoever invented this piece of shit should be really proud of themselves... And yes, this rant comes from an iOS developer who's working on a project in react-native... Why the fuck everything should always work on iOS but the same thing is fragile as shit on Android? Why the fuck there's a thousand of different versions of every Android package and every single one breaks another? Why the fuck Android is so fragmented... If this piece of shit is the definition of "openness" then I'd really prefer the "closeness" of iOS... Totally reminds me of how much I hated IE6 back in the web development days73
-
Here Ye, Here Ye.
There end is near!
Microsoft announces the GOD DAMN FUCKING END for Internet Explorer 11 in 2022.
Let's all celebrate this happy day 🍻
https://blogs.windows.com/windowsex...
5 -
We (as new hires) had to add a fallback logic for input validation on every input element using only JSP and Spring controllers just because the client still uses IE6 and fucking disables Javascript!!5
-
Had a blast from the past the other day. Testing an issue with an AngularJS app in IE11 on a project managers Surface.
Nothing works. Just a blank screen. I open the JavaScript console to hundreds, maybe thousands of errors. They all seem eerily familiar, but I can't place them. It's like something from a past life.
Then I see one that brings the issue into sharp focus.
"{{variable_name}} is a reserved word"
No it isn't, I think. That hasn't been a reserved word in JavaScript since...
Me: "Is your browser in Compatibility Mode?"
PM: "Yeah, it's for one of our legacy programs"
Me: "You need to turn that off to test this app. It thinks you're using IE6, so it's having a 2 decade old shit-fit. I haven't seen those errors since I was a teenager making crap on Geocities"
I never thought an error message could make me feel so old 😩 -
We need you to support IE7, IE8, IE9, IE10, Firefox, Chrome, and Opera. Also since the customer may one day want to use tablets start thinking about that. And if possible don't break IE6 compatibility.3
-
Never thought I'd say this but...I wish IE6 was back for Outlook.
//After Outlook 2003, Microsoft decided that MS Word was a better renderer for emails than IE6 was, what the hell Microsoft?! Get it together man.4 -
Wow...lets a minute to appreciate the unsung hero's that revolted and went on to lead and win the battle against IE6.**shiver**
https://blog.chriszacharias.com/a-c...
The majority of you will not understand or be able to appreciate the gravity and extent their actions had on improving quality of life for web developers globally... that is the true gift & legacy of their noble deeds.
and yes it was that bad... no, actually it was even worse - the best words i can use to describe (attempting) development in IE6 is that it felt like we were imprisoned in the software equivalent of a concentration camp where they had perfected the cruellest form of torture, where they allowed us to develop amazing next level experiences in modern browsers just so they could watch all hope drain from our faces as we were forced to destroy them, tearing out the magic in the name of IE6.10 -
A bit of an anecdote here:
The project I am working on at my internship has to function perfectly in IE11.
There are users using it on fucking IE6, but no one paid extra for IE6 support.
Meanwhile, Microsoft themselves doesn't support IE11 anymore.8 -
What browsers do front end devs here normally test on? I test on Firefox and Chrome because...that's all I use, but what about Edge/Safari or god forbid IE11?
I'm more familiar with backend dev ops so my testing consisted of checking Firefox a lot. :P
6 -
I regret moving to backend. I loved the days when I used to write lines of code and refresh my browser for the changes to be displayed on the screen. I loved seeing the output of my code, the code flow, the light weight text editor, the visual satisfaction and the chrome debugger.
Now I am fucked up, I am working on creating microservices for restful api. I am hating everything about it. The fact that I should compile the entire war, manually copy them to a webapp folder, restart my tomcat and wait for 5 minutes just to see my code, and the text editors are just a pain in the ass, the debugger sucks too.
I was so looking forward to being a backend Dev because I thought Java was cool and I also was fedup with cross browser optimizations on the front end. Now I would gladly write a streaming service foe ie6. Spring has fucked me up so hard
God save me from this mess.6 -
So we're about to launch the annual financial reports for a multi-billion corporation, but as usual, they're late at providing us with the information we need.
Recently they thought they had been hacked, so they blocked our access to their servers, which we need to upload the annual reports! Oh, the lovely hierarchy in large companies.
But hey, they finally decided to drop IE6 support, so that's a win1 -
Why tf does IE6 not support js classes?! What in the actual fuck is up with that so called browser? We need to sink that motherfucker to the bottom of the gulf.14
-
Hey, I have a cool idea about a new way to solve a problem our users are having!
Type type type, now I have a working prototype! Show it to the team, everyone loves it. Polish it a little, it works really great!
Now let's test it on an iPad like the ones our users have... Nope, nothing works, undefined is not a function.
F*CK YOU SAFARI, you're why we can't have nice things. 😤 -
Chrome...
Chome what the hell is this?
In Firefox with my default theme I can tell which tab is open and which one isn't. In Chrome, you put !!white as a highlight over gray.
You have actually managed to design a UI element almost on the same level of terrible as IE6-11, almost.
3 -
At one of my first jobs, we were tasked with building a new website for the company. Since we were the first in-house web development team (everything done prior to us had been contracted out), we had NO relevant software or tools available to use because the company had never needed them before.
On top of that, our computers were on complete lockdown: we had no permissions to install anything ourselves, and any software installation requests had to go through a formal review process that took a minimum of a few months for approval.
So: for the first couple of months, we coded everything in Notepad (!) on Windows (so no autocomplete, no syntax highlighting, etc.)...and tested only in IE6, the sole browser we had at our disposal 😮2 -
Hey,, fellow ranters, if you have some free time and want to interact with shitty Korean sites (yes, i am cozyplanes) that support all the way down to IE6, this is the chance for you!
Help me find a school code that is somewhere in the JS,
If you are interested, see comments below, and drop me a line here!10 -
Of all the browsers required to complete mandatory classes online for the USMC you would think they would support a modern browser and no IE6 or flash heavy courses only...2
-
Just got my hands on a fresh installation of windows XP... With IE6. I guess it's time to have fun with the caniuse stats :)1
-
Unpopular opinion. IE6 stuck around for so long because it was the best browser in its time. It's horseshit today but only because that generation liked it so much they couldn't bring themselves to leave it.8
-
Nothing infuriates me more than how Safari on iOS supports less standards than IE6. How can we live in a world of standards with Apple giving us the middle finger.2
-
GWT... And you know what is worse than that... SmartGWT.
Combine it with a client in government sector in French speaking African country who has an iPhone for 'his testing' and wants site to show french text on IE6 and newer because it's a government project and that's where shit must run.
Those who created it, I appreciate their intentions. But, you write things in Java, compile it and then separate the UI part and backend part. And if something breaks, which happens in most of the cases, no you can't just right click and 'inspect element'. Because it is IE 7! Now you try it out again, compile it, place it separately and wish your luck, which also sucks most of the time.
...and yeah, don't forget to clean cache in browser. I remember the time when to refresh content on Facebook, I used to clean cache and then refresh.
I'm a backend developer now, shit still sucks, but at least a lot of things are logical. I have a very high respect for UI developer, I really do, especially those who develop for Internet explorer. -
Wanted for once use FireFox for dev / tooling.
Welp, it only took 1 page load to see why devs don't use it :
There is NO information on how long an ajax request took.
A lot of useless stuf like "Destination IP" (Who the fuck cares?) or "Initiator" (I already know where it started, I want to iknow how long it took).
That concludes my try to work with a non chromium browser and i'm sad. because chromium is a new IE6.
Don't belive me ? Look how websites manages checkboxes. Yes that's right with ::before and ::after.
These pseudo elements SHOULD NOT work in <input>. But they do in chromium. Which basicly a deal break to use firefox for our users.
Fuck you chromium. IE6 bis i'm gonna call you now
And FireFox : Please, just COPY dev tools of chromium, yours are unusable.
Ok, I feel better, going back to my bug.2
Top Tags
Weekly Rant
View