I like this meme. Essentially, current API let you express any operation measurement. If you know some case where this package does not work for you, you are welcome to issues.
vitonsky
joined 1 year ago
AGPL license. No, thanks
Thank you too π
Yes, Linguist use Bergamot translator that is embedded in Firefox. But translation in Firefox in beta stage, it does not have a lot of features and does not support a lot of languages yet. Linguist is a full featured translator that support a lot of translation modules and even custom translators provided by users. So Firefox translation is just a subset of features from Linguist, like Firefox ads protection is just a small subset of features from uBlock Origin.
But Firefox translator are technological breakthrough anyway, so we appreciate it.
Well, the Linguist is no have any public opinion. You are welcome to use the unique project who care about UX, and don't care about political views of their users.
Current plugin is just about force use aliases instead of relative paths (and back for deprecated aliases).
If you need to sort imports, you may try rule simple-import-sort/imports from https://github.com/lydell/eslint-plugin-simple-import-sort
It is very flexible, so you may customize your own groups. For instance, you may group aliases in one group and relative imports to another group. Check their docs
Could you elaborate your idea.
If i correct understood you, you want to use relative imports inside alias directory. This is possible, you may check test about it https://github.com/vitonsky/eslint-plugin-paths/blob/d5a307866df9cf460a50301820e12e3653eb1cca/src/rules/alias.test.ts#L36-L40
Is it that you need?
Sure, decision logs is just a step to fix a problems with decision making. Logs highlight a problems in decision making process and let you analyze a problems in your team. You still need an strong architect who may say "hey team, why your arguments so weak? it looks you are low skill engineers. make arguments more objective, or you will be fired" and then really fire weak engineers in team.
Exactly! I see how a mindset βwe delivered (shit) quicklyβ successfully reproduces itself, over and over in a lot of companies.
I think the actual reason is that business want to make money on promises right here right now. Business promises a lot of features to investors give money, and then business implement a lot of (shit) features. And then they continue kinda "okay, features broken, give us more money and we will fix it".
I hope you're right. The more people will save it, the more chances we have to find the source code later, or even find the community who will maintain the fork.
You can see the code of extensions, but it may be minimized, so it hard to known what the code do.
Extensions with label "Recommended" are pass the manual review of Firefox moderators, so you can trust them more than addons with no this label. However you still should keep in mind that any extension developer may be victim of complex scam attack.
The most probable reason usually is a not enough funding the developers
- Developer spend time on maintaining the project but users does not donate them
- Scammers offer to developer some integrations that not looks too suspicious and allow them to earn some money
- Developer agree offer and after some time scammers enables malware to hack extension users
To minimize the possibility of hijacking addons by scammers, we have to:
- conduct background check before install extension
- ensure the extension have github with open source code and developer are real person
- ensure development are active and developer have high engineering skill, check them respond on feedback and issues
- donate the developer if you like the product, to motivate them keep distance of scammers offers
view more: next βΊ
Definitely, you on the right way π