IE and Edge Compatibility

Most people use Chrome, Firefox, Safari, or sometimes Opera. Webkit browsers are more or less the same too, so not a big deal. So you're really just dealing with webkit and Firefox. IE and Edge are a pain in the ass. Very few people use them. Do web developers have to cater to IE and Edge users and ensure that their sites render properly in these shitty browsers? Or should you just do a user agent check and then send an alert box telling them to use a real browser instead?

Most people just compile down to JavaShit from an intermediate language. The transpiler usually handles all the browser compatibility. Like webpack’s env configuration flag.

>>2
but IE isn't standards-compliant and shit that looks fine is Firefox or Chrome is often completely broken in IE because it's shit

>>3
If you use TypeScript for example, you can target even ES3, which guarantees compatibility with IE9: https://www.typescriptlang.org/docs/handbook/compiler-options.html

That just leaves CSS and HTML.

For CSS, you can use stuff like SASS + SASS vendor mixins to generate CSS for all browsers. Plus with Bootstrap type libraries you can minimize the amount of CSS you have to do in general, and it all works across environments.

For HTML, you just have to not rely on html5 elements or use a JavaShit library like https://modernizr.com/

Nobody writes JavaShit/CSS/HTML by hand anymore; that's why IE isn't a problem anymore.

>>4

Nobody writes JavaShit/CSS/HTML by hand anymore

even frontend SPA frameworks have compatibility issues with shitty browsers

http://cyborg.blogspot.com/2018/09/pmpj0912.html

IE is the only widely used browser left that still has a remotely sane UI.

Edge is a dumbed-down Chrome clone for retards.

>>7
so you like trucks, like redneck rap, think climate change is made up, and use IE

hmmm...

>>7
💩

>>9
💩 💩💩💩💩
💩 💩
💩 💩
💩💩💩💩💩💩💩
💩 💩
💩 💩
💩💩💩💩 💩

don't take this too seriously, I'm just shitposting