CUTCODEDOWN
Minimalist Semantic Markup

Welcome Guest
Please Login or Register

If you have registered but not recieved your activation e-mail in a reasonable amount of time, or have issues with using the registration form, please use our Contact Form for assistance. Include both your username and the e-mail you tried to register with.

Author Topic: Elementals 4, should I drop IE support entirely?  (Read 397 times)

Jason Knight

  • Administrator
  • Hero Member
  • *****
  • Posts: 714
  • Karma: +132/-1
    • CutCodeDown -- Minimalist Semantic Markup
Elementals 4, should I drop IE support entirely?
« on: 1 Aug 2020, 05:31:35 pm »
I'm tempted to drop support for IE entirely, and possibly any browsers that don't support at least ECMAScript 262.

This isn't just about how a quarter of the codebase is polyfills for legacy IE, it's also about how most modern scripts don't support it either (things I'd never use like arrow functions crashing IE by their mere presence) and how many of the new approaches -- like for/of -- are so brutally efficient compared to legacy methods.

Whilst there's a lot of new junk I see no legitimate purpose for other than making JS harder to use and maintain -- promises, import/type="module", arrow functions, endless "callbacks for nothing", etc, etc -- there are a lot of genuine improvements that make it harder and hard to justify continuing support for IE.

Particularly when the way I write pages it would/should gracefully degrade for non-scripting anyways on anything important. (since client-side nothing important should be scripted in the first place)

I dunno... are we there yet? Is it time to kick ALL versions of IE to the curb?
« Last Edit: 1 Aug 2020, 06:05:29 pm by Jason Knight »
I'll fix every flaw, I'll break every law, I'll tear up the rulebook if that's what it takes. You will see, I will crush this cold machine.

 

SMF spam blocked by CleanTalk

Advertisement