Regexp find/replace is an indispensible tool for refactoring large chunks of code.
-
-
Replying to @ejpbruel @RReverser
Guess who gets to write a regexp engine then :) i don't use it.
1 reply 0 retweets 0 likes -
Replying to @rikarends @RReverser
Theres zero added value to writing your own regex search engine, given that ripgrep exists. The algorithms are known to be optimal and well understood. At best, you end up spending weeks reinventing the wheel, so thats actually negative value.
1 reply 0 retweets 0 likes -
Replying to @ejpbruel @RReverser
Compiling ripgrep takes 73 deps, and 50 seconds for a debugbuild. There goes makepads depcount.
2 replies 0 retweets 0 likes -
Replying to @rikarends @RReverser
This is why people use libs like ripgrep despite their high dep count. Your only alternatives are: not implementing a feature many of your users consider basic, or wasting a lot of time and money rolling your own.
2 replies 0 retweets 1 like -
Yep. Not using dependencies feels good, but is not doing your users a favor. Users matter more than your aesthetic sensibilities.
2 replies 0 retweets 0 likes -
Also compile time is NOT an aesthetic sensibility. Its a direct compute cost paid by all CI, users that build your sw, and yourself many times over.
1 reply 0 retweets 4 likes -
I get it, but also not having regex refactoring is also a cost paid by even more people (your users).
2 replies 0 retweets 0 likes -
I know i do see your point, i also see however if i would have followed this way of working makepad would be 450 deps and 15 minute buildtime today. Which i think sucks.
1 reply 0 retweets 2 likes -
Replying to @rikarends @pcwalton and
Btw rusts regex lib makes makepad go 23->31 deps and 32->35s compiletime release. Ripgrep has many more deps i wouldn't need, so its not that bad. I'll think about it.
2 replies 0 retweets 0 likes
ripgrep is split into libs, so you can depend on them piecemeal if you like. It would still increase your dep count tho. Also, regex shouldn't increase your dep count by 9 on its own. I think it's at most 6: regex, regex-syntax, memchr, aho-corasick, thread_local, lazy_static.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.