5 ms·

The article describes significant time savings from these changes.

jongjong 4y ago
All the issues mentioned are related to the usage of shitty frameworks and build tools. The problem is not caused by a single regex; the real issue is likely that a regex is being created too many times in a loop instead of being created once and re-used. Related to neglected time complexity. > Config parsing as a whole takes 4.3 seconds WTF! If parsing a config file takes more than 20 milliseconds, you've got some serious issues with your project... There is no excuse. Even if your project is highly complex and feature-rich, you can just break it up into smaller sub-projects. This article doesn't give any useful info because the project it's analyzing is just so bad. It's like watching a turtle complete a 100-meter race and then taking away the lesson that crawling on one's stomach isn't a great strategy for a human to win the 100-meter race at the Olympics. Duh! The whole project is a giant flaming pile of garbage. There is no interesting lesson to learn from it. Functions named 'monkeys' or 'perItem' or 'strongRound'?... Class named 'ConditionalRuleset' (WTF is a conditional ruleset, why would any project need it??? This abstraction makes no sense). What about 'isBlockIgnored(ruleOrDeclaration)'? Sounds like unnecessary complexity bloat when devs keep inventing new abstractions to give themselves more billable hours of work. I would jump dump all these bloated libraries and frameworks and start the project from scratch.
- dottedmag 4y ago
  20ms for config parsing is eternity, really.
  - jongjong 4y ago
    Over 3 seconds for booting up is fine, heck, sometimes a few minutes is OK, but just to parse the config file? No way. If it takes that long to parse, it's not even a config file; it's a monster. I bet it has many other problems beyond performance.
- enapupe 4y ago
  your comment is sort of selfish because you don't seem to understand a good portion of the JS ecosystem is based on top of the libraries the author has touched. welcome to the real world
  - jongjong 4y ago
    I know much of the JS ecosystem sucks. Don't blame me for industry leaders brainwashing and coercing us into using these horrible frameworks and libraries... And then making it into a mono-culture which shuns all alternatives. You don't have to use them; you can find a different job at a smaller company. There are still companies doing it right and there are still good, lightweight tools out there; they're just hard to find.

All the issues mentioned are related to the usage of shitty frameworks and build tools. The problem is not caused by a single regex; the real issue is likely that a regex is being created too many times in a loop instead of being created once and re-used. Related to neglected time complexity. > Config parsing as a whole takes 4.3 seconds WTF! If parsing a config file takes more than 20 milliseconds, you've got some serious issues with your project... There is no excuse. Even if your project is highly complex and feature-rich, you can just break it up into smaller sub-projects. This article doesn't give any useful info because the project it's analyzing is just so bad. It's like watching a turtle complete a 100-meter race and then taking away the lesson that crawling on one's stomach isn't a great strategy for a human to win the 100-meter race at the Olympics. Duh! The whole project is a giant flaming pile of garbage. There is no interesting lesson to learn from it. Functions named 'monkeys' or 'perItem' or 'strongRound'?... Class named 'ConditionalRuleset' (WTF is a conditional ruleset, why would any project need it??? This abstraction makes no sense). What about 'isBlockIgnored(ruleOrDeclaration)'? Sounds like unnecessary complexity bloat when devs keep inventing new abstractions to give themselves more billable hours of work. I would jump dump all these bloated libraries and frameworks and start the project from scratch.

dottedmag 4y ago
20ms for config parsing is eternity, really.
- jongjong 4y ago
  Over 3 seconds for booting up is fine, heck, sometimes a few minutes is OK, but just to parse the config file? No way. If it takes that long to parse, it's not even a config file; it's a monster. I bet it has many other problems beyond performance.
enapupe 4y ago
your comment is sort of selfish because you don't seem to understand a good portion of the JS ecosystem is based on top of the libraries the author has touched. welcome to the real world
- jongjong 4y ago
  I know much of the JS ecosystem sucks. Don't blame me for industry leaders brainwashing and coercing us into using these horrible frameworks and libraries... And then making it into a mono-culture which shuns all alternatives. You don't have to use them; you can find a different job at a smaller company. There are still companies doing it right and there are still good, lightweight tools out there; they're just hard to find.