tsergiu

10 ms·

91.
by tsergiu 13y ago
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.
92.
by tsergiu 13y ago
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...
93.
by tsergiu 13y ago
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.
94.
Why I am building a product with a tiny market(debuggex.com)
219 points by tsergiu 13y ago|116 comments
95.
Can your regex tester do this?(debuggex.com)
2 points by tsergiu 13y ago|0 comments
96.
by tsergiu 14y ago
Thank you for the support :)
97.
by tsergiu 14y ago
Thanks for the feedback. I'll fix this as soon as I can.
98.
by tsergiu 14y ago
Thank you. Let me know what I could do to make it even more fun :)
99.
by tsergiu 14y ago
Thanks for the support!
100.
by tsergiu 14y ago
Thank you. Share generously :)
101.
by tsergiu 14y ago
Thanks for the support. May you catch many more!
102.
by tsergiu 14y ago
Thanks. Your support means a lot :)
103.
by tsergiu 14y ago
Thanks for the feedback. I'll keep that in mind for upcoming releases.
104.
by tsergiu 14y ago
There will be support for different flavors of regexes in an upcoming release.
105.
by tsergiu 14y ago
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 position
106.
by tsergiu 14y ago
Not sure what kind of formatting hn does, but that should be / ^ ( a * ) * $ / inside the match (remove spaces).
107.
by tsergiu 14y ago
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
108.
by tsergiu 14y ago
Thanks for the feedback. Will fix it immediately.
109.
by tsergiu 14y ago
Yup, it just didn't make it into the first release. Will definitely be in a future release.
110.
by tsergiu 14y ago
Not sure what you mean. It's working for me. Can you describe what happens in more detail please.
111.
by tsergiu 14y ago
Sorry about the lacking support. The goal for the next release is to have full support for Javascript flavor regexes.
112.
by tsergiu 14y ago
But at least you can fix them quickly ;)
113.
by tsergiu 14y ago
Not in this release. It's exact matches only for now.
114.
by tsergiu 14y ago
Keep in mind that it doesn't support flags yet, which is why it wouldn't work out-of-the-box.
115.
by tsergiu 14y ago
I think you are missing lower case letters in your character sets. Besides that, apologies for it stretching sideways and making you scroll. Will be fixed in a future release!
116.
by tsergiu 14y ago
Multiple matches is planned for a future release. How would you recommend generating fail string? The space of failing strings is really large. From my discussions with users, they usually have a specific failed string and they want to see
117.
by tsergiu 14y ago
The current release only supports exact matches. Multiple matches are planned for a future release. However, if you use the slider to slide to just past the "s" in Nashville, you can see that the end state does indeed light up.
118.
by tsergiu 14y ago
Looking into it.
119.
by tsergiu 14y ago
That is a good visualization. However, it doesn't let you debug if there is a problem with matching a string. That was the explicit goal in building Debuggex. Linting is a planned feature for a future release.
120.
by tsergiu 14y ago
The text to match field is a text area; it will auto-expand as you type into it. However, only exact matches are supported for the first release. I wanted to get user feedback before I built any more features. I think I have an intuitive wa

More ›