Misuse the trademarks licensed to one of their competitors while relying on that competitor to provide them infrastructure for software updates and provide product improvements.
Adjusting their product names sounds like a small change they could have made to avoid antagonising a close partner.
Running their own plug-in mirror infrastructure is something companies often do to reduce the risk from relying on a third party.
Similarly having some stake in the development of WordPress reduces risk of them being shut out if there is a license change that necessitates a fork.
Less about caving in on wishes as more that it's risky to choose both to rely on a third party and wind them up at the same time.
> Misuse the trademarks licensed to one of their competitors while relying on that competitor to provide them infrastructure for software updates and provide product improvements.
> Adjusting their product names sounds like a small change they could have made to avoid antagonising a close partner.
WP Engine updated everything that was potentially infringing two weeks ago:
I had a similar experience in 2015: a doctor was trying to prescribe a choice between Venlafaxine (Effexor) and Duloxetine (Cymbalta) as third line ADHD medications. I was astounded that they didn't know that brain zaps were a common side effect and brought up some papers to show them. They apologized and indicated that they would likely stop prescribing them.
I was skeptical when they mentioned that other doctors had been promoting these drugs at gatherings, but what irritated me most was that they didn't have access to the research discussing the known side effects because the journals were behind a paywall. A willingness to pirate / use Google scholar to bypass paywalls shouldn't have been necessary to know about safety issues for a drug.
Nah. Safari did plenty of monopoly abuse and sneaking into installs, but still never got big on Windows. At some point the user experience does matter.
Office use is actually where you are highly likely to have a lot of applications open at once (lots of web tabs, mail client, document editor, excel and maybe some PDF views) but do not need a whole lot of performance either in single thread (for blocking UI change/computations) of multithread for parallel tasks.
You just need to be able to load all the apps at once in RAM and let them sit there as long as possible. The actual computation needed for those workflows is pretty low once the apps are loaded. It's all a trickle of mini task depending on the user interaction. Sometimes you need to export/convert something, and it takes longer but it is not very problematic.
In fact, RAM is a pretty big determining factor in your experience, especially if you use the office suite or google tools. Apples knows this, and it is exactly why they sell such a low amount of RAM at entry level. They want people to pay up or use their (inferior) tools.
Their entry level MacBook are a terrible choice for office, in fact you are unlikely to either need or use all the computer power they sell in the marketing, but you are highly likely to feel the pain of too little RAM with the relentless message asking to close some apps.
The fact they came out to justify their choice is just the hammer driving the nail. It is all expected behavior from the greediest corporation on earth...
Battery life is significant worse with 32GB ram and laptop reviews often place heavy emphasis on battery life. By offering an 8Gb base model for reviews the manufacturer ensures their laptop will score well in reviews, even if users end up buying a higher spec laptop. It also allows users who want to multitask less to get more out of their laptop.
On desktop the impact of power consumption is lower, so it is better to offer a slightly higher spec base model.
Unlocking the password manager means I need to type a master password in while in a public place. Feels higher risk when it is an unimportant website but potentially gives access to all websites. Still better than the passwords being accessible on disk but having individual passwords would reduce the impact of any password leak.
I have this InputStick USB [1] dohicky that I keep with my keys shows up as a generic USB keyboard when plugged in but is also an encrypted Bluetooth dongle (part of pairing allows you to configure a shared encryption key so that only devices that know the key can use the stick, and only sticks with the key are recognized by the client apps). There's a plugin to Keepass2Android that I use to type passwords from my phone. I use that to unlock my password manager (using a giant untypable passphrase). So entering mosterous passphrases is very easy... bot only if you can unlock my phone and use biometrics to open Keepass2Android.
It really is dumb that phones can just generically play USB HID (without running custom kernels)
It's every two weeks. If your threat model involves being spied on over the shoulder for your master password while in a cafe you "just" need to ensure you enter your password in a safe location every two weeks.
Our machines always had Cookie Pal [0] installed on them, and it allowed per domain settings for rejecting cookies and control over third party cookies [1].
> Cookie Pal includes the following features:
> Automatically and transparently accepts or rejects cookies from all or specified servers without user interaction.
> Cookies received from unspecified servers can be automatically accepted or rejected without user interaction, or the user can be asked for confirmation.
> "On the fly" adding of servers to the accept from and reject from lists, allows you to manually accept or reject a cookie the first time it is received and then have it automatically accepted or rejected every time it is received thereafter.
One of the founders listed elsewhere on that page was a mentor on an accelerator I took part in. We went over our business in depth, he eventually became a supplier to us, then we became his largest customer. One day he abruptly stopped providing the service, and then relaunched his business trying to copy us instead.
We out executed, but I'd advise caution with mentors. Some were great help, this one was malicious.
Adjusting their product names sounds like a small change they could have made to avoid antagonising a close partner.
Running their own plug-in mirror infrastructure is something companies often do to reduce the risk from relying on a third party.
Similarly having some stake in the development of WordPress reduces risk of them being shut out if there is a license change that necessitates a fork.
Less about caving in on wishes as more that it's risky to choose both to rely on a third party and wind them up at the same time.