tsergiu

Thanks for the feedback! There will be a ui overhaul once all the major features are done. That will be in a few months.

Debuggex already covers 4 and 5.

Real-time unit testing is actually the next major feature planned (I expect the release to be in about 4-6 weeks). That will cover 2 and 3.

1 will be improved in the very near future.

grep has a very different purpose. Here's just one use case that it's not good at:

I see a regex in some code that I don't own. What does the regex do?

Indiegogo allows Canadians to participate :)

I'd love to learn more about your use case and what's important in such large scale operations. Can you please email me at debuggex@toarca.com?

Thank you! Yup, it's currently coded by hand. I'll find a more scalable way as more pages need to be added to the site. You can see that e.g. the blog post is just a page with a unique link.

Hey Randle,

I read your blog post, and have kept named groups on my mind. Support for more languages is planned. However, I should note that it will be a premium feature.

I really appreciate the continued support.

There's no need to be so aggressive.

I think you misunderstood my argument. That may have been entirely my fault; I'm still learning to write.

Small and simple problems are rare in large markets because everybody is chasing after them. The low-hanging fruit get picked very quickly, and you need to produce more to reach the bleeding edge.

By contrast, smaller markets have more low-hanging fruit simply because there are not as many people picking them.

Heh, your browser does most of the hard stuff :) I'm not quite sure what others are doing that it's slow.

Some very useful suggestions. Thank you.

The permalinking is very rudimentary and was put up quickly so that it worked for "most cases". I wanted to focus on building the actual debugger. This will be fixed in the near future.

Ok, I am convinced. I'll add the links :)

Ah good point. I thought I had labeled it "US Phone Number" at one point. I'll try to find another example of similar difficulty.

This was somewhat intentional. I had a larger plug at the beginning initially. I decided it did not seem genuine enough, and would take away from the content.

I've loved working with angular. My only complaint is that the current docs are somewhat lacking, but it seems that will soon be addressed: https://plus.google.com/112439678898563138768/posts/LfWvcFfq...

Yes, I am planning to monetize. I have a few ideas for to do that as it approaches the end of beta, but I'd love to hear any suggestions you have.

Thank you for the support :)

Thanks for the feedback. I'll fix this as soon as I can.

Thank you. Let me know what I could do to make it even more fun :)

Thanks for the support!

Thank you. Share generously :)

Thanks for the support. May you catch many more!

Thanks. Your support means a lot :)

Thanks for the feedback. I'll keep that in mind for upcoming releases.

There will be support for different flavors of regexes in an upcoming release.

Thank you for the feedback.

The regex reference is only temporarily there. It'll eventually be replaced by a much better feature which is in the pipeline. I'll play around with the css to make it better.

I've played around with the positioning a bit, and it definitely needs iteration. However, an upcoming ui change will drastically change the demands on the ui, so it doesn't make sense to optimize that yet.

I'll replace the Lato font. I agree it looks terrible on windows.

Thanks for all the feedback!

Not sure what kind of formatting hn does, but that should be / ^ ( a * ) * $ / inside the match (remove spaces).

Sorry for the delayed response. Spent all day yesterday responding to feedback. The reason this crashes is due to the internal javascript engine.

In order to ensure that my engine (I simulate a kind of NFA) matches what javascript's engine matches, every time I match on my engine, I also try to exact match using javascript's engine. Unfortunately, javascript's engine always uses backtracking, even when it doesn't need to. Obviously this code should have been turned off for production, and I'll fix it on the next push.

To replicate the crash on your own, try typing: 'aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaab'.match(/^(a)$/) in your console.

Thanks for the feedback. Will fix it immediately.

Yup, it just didn't make it into the first release. Will definitely be in a future release.