|Beroep||Researcher, Software Developer|
|Gebruiker sinds||March 5, 2007|
|Aantal ontwikkelde add-ons||2 add-ons|
|Gemiddelde waardering van de add-ons van de ontwikkelaar||Waardering 4 van 5 sterren|
In wat meer detail…
Ph.D. in Theoretical Comp Sci from the Technion, in the field of Property Testing. Now working in the nascent Heterogeneous Computing group of Hua Wei research's Shannon Lab.
A while ago I got hit on the head after an anti-war demo in Tel-Aviv, which is a good excuse to not respond too quickly to user requests :-) Be patient with me, I'll get to your bug as soon as I can spare the time.
I used to be a broke struggling PhD student, and now I make a reasonable salary, so - donations will be pooled and passed onwards to (local) worthy causes, be it other Free-and-Open-Software initiatives, refugee relief (or legal defense), support for political prisons, etc. So, do consider donating if you find my extensions useful.
Door mij gemaakte add-ons
Zoek en verwijder berichten die identiek zijn aan andere berichten in uw mailmappen (ook wel duplicaten genoemd)
Use the better alternative to this extension! Waardering 1 van 5 sterren
This extension has been effectively abandoned by its author for almost 2 years, without significant updates. It is also not free software, so the code cannot be used elsewhere.
For this reason I have fully rewritten a dupe removal extension of my own, which is actually free software:
Remove Duplicate Messages (alternate)
It has seen more active development, has a richer feature set (which proerly includes the features of this extension) and for which issues can be opened on Mozdev's bugzilla and addressed within a reasonable amount of time.
This is a nice Greasemonkey script, not an extension Waardering 2 van 5 sterren
The extension works as claimed. However, it is basically a Greasemonkey script, coupled with a copy of some of the GM code to make it work independently. I do not see a reason why this kind of a GM script should become its own extension. Author is free to do as he pleases but I do not believe this should be supported by making this extension public.
- Regular expression used to detect Hebrew should be more tersely and clearly constructed.
- A single letter should probably not suffice to RTL an entire paragraph or line; try an entire word, or at least a sequence of characters
- Poor coding style in various places, such as defining a function named '$', adding to the regexp prototype a method named 'loc', testing for 7 regexps instead of testing for their '|'ification, etc.
- If one uses an independent extension rather than a Greasemonkey script, why keep the images used as "data:/..." strings rather than as chrome files (or a single file)?
- Empty chrome/ directory and a content/ directory outside it
- Use of spaces and tab characters inconsistently