DeepL: AI 번역기 및 작문 도우미에 대한 리뷰
DeepL: AI 번역기 및 작문 도우미 제작자: DeepL
Cy "kkm" K'Nelson 님의 리뷰
5점 만점에 1점
Cy "kkm" K'Nelson 님, 3년 전The extension functionality is A-OK, solid 5/5. It's the implementation that kills it usefulness, and barely scrapes 0/5. I could go into the negative score numbers, but boy, where I would've stopped then...
I had to uninstall the extension because it throws its trash around all over the browser. It injects a humongous CSS stylesheet, 115KB(!) in size, into *every single open tab*, regardless of DeepL translation being ever used. I estimated that I used the selection translation pop-up at about one in every 500 to 1000 pages. This is a truly humongous waste of resources. The stylesheet contains 734 selectors, 2999 property settings and two @media width breakpoints. You'd have a hard time convincing me that this is a bare minimum necessary to display a simple pop-up box…
And then, in any case, a sensibly written extension would have delayed loading its CSS until it is actually needed, i.e. until it actually displays something. And load it into a sandbox, so that it's gone when the pop-up is closed: come think of it, DOM shadow roots were invented for a reason, and scoping resources in time was one of the two major ones. Now, the funny part, albeit not ha-ha funny: the extension does in fact use a shadow root for the pop-up, and… yes, you guessed it, loads another copy of its juggernaut CSS sheet into it. Why it also stuffs all this useless CSS everywhere it only can is beyond me, but loading the CPU with the browser's failing to match the extra 750 selectors every time the layout is recomputed—and "responsive" layouts on dynamically changing pages have to be deeply recomputed often!—isn't something I can use. I have better ways to waste my CPU than this extension.
As soon as the issue is fixed, I'm upgrading my rating to 5/5 not thinking twice. I hope that this is just an oversight, a bad design decision that could be soon reassessed and undone.
I had to uninstall the extension because it throws its trash around all over the browser. It injects a humongous CSS stylesheet, 115KB(!) in size, into *every single open tab*, regardless of DeepL translation being ever used. I estimated that I used the selection translation pop-up at about one in every 500 to 1000 pages. This is a truly humongous waste of resources. The stylesheet contains 734 selectors, 2999 property settings and two @media width breakpoints. You'd have a hard time convincing me that this is a bare minimum necessary to display a simple pop-up box…
And then, in any case, a sensibly written extension would have delayed loading its CSS until it is actually needed, i.e. until it actually displays something. And load it into a sandbox, so that it's gone when the pop-up is closed: come think of it, DOM shadow roots were invented for a reason, and scoping resources in time was one of the two major ones. Now, the funny part, albeit not ha-ha funny: the extension does in fact use a shadow root for the pop-up, and… yes, you guessed it, loads another copy of its juggernaut CSS sheet into it. Why it also stuffs all this useless CSS everywhere it only can is beyond me, but loading the CPU with the browser's failing to match the extra 750 selectors every time the layout is recomputed—and "responsive" layouts on dynamically changing pages have to be deeply recomputed often!—isn't something I can use. I have better ways to waste my CPU than this extension.
As soon as the issue is fixed, I'm upgrading my rating to 5/5 not thinking twice. I hope that this is just an oversight, a bad design decision that could be soon reassessed and undone.
리뷰 1,028개
- after a long surfing and browsing session the add-on starts using a lot of ram which it doesn't free itself and cannot be freed other than deactivating the add-on or restarting the browser. this is annoying, because it starts slowing down the whole system. it took me a long while to figure out what's going on; i started realizing in the processes tab, that my extension's / add-on's ram usage is growing and growing over time - even above 1GB (!). after i deactivated the add-on, the memory was freed again. this memory related bug needs to be solved by the developer urgently.
otherwise it does what it says - translates to a fine degree - 5점 만점에 5점Black Dodge Charger 님, 2달 전Excellent product made by DeepL. Very satisfactory. The only thing I wish DeepL would change is making it where you don't have to put in your credit card information to get the free API key.
- 5점 만점에 1점Firefox 사용자 18900004 님, 2달 전Ständig drängt sich dieses Icon DeepL Icon in den Vordergrund, wenn man es überhaupt nicht braucht. Nur beim Übersetzen von WordPress-Beiträgen im Gutenberg-Editor erscheint es nicht mehr. Das hat aber früher mal funktioniert. Erweiterung deaktiviert und schon ist wieder Ruhe eingekehrt.
That DeepL icon keeps popping up in the foreground when you don’t need it at all. It only stops appearing when translating WordPress posts in the Gutenberg editor. But that used to work. I deactivated the extension and everything’s back to normal.
Translated with DeepL :-) - 5점 만점에 1점Firefox 사용자 19911397 님, 2달 전
- 5점 만점에 5점Firefox 사용자 15300838 님, 3달 전DeepL is helping me incredably and it is so easy to use. One click website translation is just instant!
- 5점 만점에 5점locusta666 님, 3달 전
- 5점 만점에 4점Kathanaddaeus 님, 3달 전Pretty good translation. Only two hickups for me:
1. The context menu item is always present when right-clicking, regardless of any translation being available. If I click on an image, why is there the context menu entry with a single, deactivated item inside? If nothing is available, it should be entirely hidden, or at least configurable in the settings.
2. The window that opens seems to rarely not properly release all resources. Multiple translations in short succession occasionally break the windows (doesn't close, new ones open with a blank page or no more windows open) - 5점 만점에 5점John J. Freeze 님, 3달 전
- 5점 만점에 5점Firefox 사용자 16962838 님, 4달 전