>One of the many lies in Silver Lake and WP Engine’s C&D was their claim that Automattic demanded money from them moments before our CEO Matt Mullenweg gave his keynote at WordCamp US.
>That is not true. Automattic asked for a verbal agreement that WP Engine would give some percentage of their revenue back into WordPress, either in the form of a trademark agreement or employee hours spent on core WordPress.
I'm not laughing. The whole Wordpress ecosystem was shown to instead be the personal fiefdom of a vindictive fool. A fool willing to completely destroy the reputation and trust of the ecosystem for what looks and smells like a personal vendetta.
The whole idea of the separate entities of Wordpress.org, the Wordpress Foundation (which we learned is somehow not the same as Wordpress.org) and Wordpress.com (through Automattic) is nothing more than a smokescreen. If you're in the business of competing with Automattic in delivering Wordpress hosting, start building an exit plan.
> >That is not true. Automattic asked for a verbal agreement that WP Engine would give some percentage of their revenue back into WordPress, either in the form of a trademark agreement or employee hours spent on core WordPress.
In the term sheet, it's phrased as:
> Commit 8% of its revenue in the form of salaries of WP Engine employees working on WordPress core features and functionality to be directed by WordPress.org.
So, pay for employees to be directed by WordPress.org (not Automattic or WordPress Foundation, apparently just Matt).
Adding to the strangeness, as the owner of WordPress.org, is Matt violating the trademark owned by the foundation or is there another undisclosed licensing agreement?
Well, it is true that money wasn't the only option.
And the quote is out of context.
The article also gives a timetable of conversations that happened between Automattic and WP Engine well in advance; therefore, the demands shouldn't have been a surprise, as claimed.
vk.com and telegram have nothing in common, except the founder. Durov was forced to sell his part in the vk.com and telegram development started after that as a response.
You conveniently forgot about the second part of that comment. Durov was forced out of the country and had to cell vk.com for peanuts because of his refusal to cooperate with the government. He is still pissed off at the country at large (not just the government) and refused to add the Russian translation for years, for example, despite it having absolutely nothing to do with Putin.
Since he is Russian in origin, it's okay to throw baseless accusations at him and spout nonsense like "maybe they're FSB agents" or "maybe they hired an FSB agent without knowing it". You see it here everywhere, and HN is one of the better sites in that regard. Well, maybe Signal has hired an NSA agent and doesn't know about it either? How does that sound?
> Durov was forced out of the country and had to cell vk.com for peanuts because of his refusal to cooperate with the government.
It wouldn't be the first time a cover story was ever used.
> Well, maybe Signal has hired an NSA agent and doesn't know about it either? How does that sound?
You should presume they're trying. I, frankly, presume they've succeeded, either in placing an agent or by compromising something, in virtually every prominent messaging platform.
Cutting off access to purchased game in countries where you cannot create a PSN account and you can no longer refund the game, because most likely you've played more than 2 hours. PSN isn't even available in every European country, despite the game being sold globally.
And if an email isn't much, then an kernel anticheat won't change much privacy-wise either.
Snap taking a dump into the output of "mount" alone is reason enough for me to hate it. I want to see my drives, not that three bundles of libraries are separately mounted into "firefox snap dir" and three others into "snap base package dir" or whatever. There are other offenders, but Snap is the worst. I resort to "df" these days, but it doesn't show filesystem type and mount flags.
No way. Flatpaks are clearly represented in the software shops of their adopted distros (I use Fedora and Pop!_OS, both of which use Flatpak).
From the software shop GUI, I can choose flatpak or dnf/apt from the dropdown. From the command-line, flatpak has its own commands (vs. apt silent under-the-hood behavior).
Flatpak is better than Snap. I use Flatpak for commercial software (Discord, Steam, etc.), but it remains my choice as a user.
The point is totally different: the purpose of both is upstream-managed distribution, consider individual distro like a container ship to be loaded, something not to care about, a commodity.
We know the arguments: often distro packagers are late to update, some projects are very complex to be packaged and demand gazillion of resources to be built, upstream devs on contrary will surely keep they project package up-to-date, sandboxing is good for safety etc. BUT we also know the outcome: 99% of such packages are full of outdated and vulnerable deps, they are themselves mostly outdated, since they are not packaged by the upstream devs who just publish the code as usual, and they have many holes punched here and there because a browser that allow to download some files but you can't open them in other apps is useless, as a pdf reader who can't read a file because it's outside the right place. Beside that you get a 30+Gb desktop deploy instead of a 10Gb, dab performances, polluted home directory, very scarce ability to automate AND all of them still need a classic package manager since they can't handle the base system.
So why them? Because SOME upstream do not want to allow third party distribute their binaries, they are commercial vendor. They NEED such system to sell they products ensuring they can work as a cancer in an open ecosystem, not designed to be a ship for something but a unique individual desktop anyone tune as he/she want.
That's why they are crap.
The next step to classic package management is the declarative/IaC one, like NixOS or Guix System. Those who want Snap, Flatpack, Appimage, ... just want Windows, with all the bloats and issues of Windows.
Just like they wasted time and effort on Unity and shuttered it in favor of Gnome, and they wasted time and effort on Mir and shuttered it in favor of Wayland, and they wasted time and effort on Upstart and shuttered it in favor of systemd.
Canonical will fail once again, but only after jerking the community around for multiple years.
> Just like they wasted time and effort on Unity and shuttered it in favor of Gnome
Unity served well for years, it would have needed a rewrite anyway for the post x11 era, so indeed there have been wasted resources, but experiments are also important in technology, and many still love what was (is) the unity user experience.
> and they wasted time and effort on Mir and shuttered it in favor of Wayland
Mir is still there and it's used. It's now a Wayland compositor but it maintains its API, the different communication protocol doesn't change its purposes.
> and they wasted time and effort on Upstart and shuttered it in favor of systemd.
When Upstart started and was used no systemd existed or was designed, so it served many well for years. Not a waste.
They didn't invest much into Upstart at all, and quickly announced a switch after Debian adopted systemd.
They still maintain Mir, as a Wayland display server.
Unity was one of the most popular desktop environments and brought Ubuntu users a lot of value over the years. It even influenced the design of GNOME 3.
I didn't understand much of the unity hate, especially compared to things like gnome 3. Really wish I could have HUD, combined titlebar/top panel, and typo-resilient search back. The latter two are possible with gnome extensions but don't work quite as well.
It's not so much hating what they do but the manner in which they do it. CLAs and not contributing upstream from the get-go means Canonical's special stuff cannot go further than Canonical.
Community forks of e.g. Unity have cropped up that ditch the CLA. Open source is open source, after all.
That said I do agree that the CLA has doomed most of their projects from gaining considerable adoption in the wider Linux community. At least while Canonical is still running the project.
Yeah I'm generally critical of Canonical for these moves, but Upstart is one I actually think was good and well done, as was their decision to move to systemd. Upstart was more pre-systemd anyway. IIRC Red Hat also used Upstart for a major release as well before moving all the way to systemd.
Yeah this is exactly it. I don't really give a damn about snaps. But when I use apt to install something, and the OS silently installs a snap version instead, that's not acceptable to me. I'm not going to ever use Ubuntu again where I have a choice, personally.
Been running both nomad and k8s in prod for the last few years. Nomad has been stable and reliable to the point of replacing k8s in some projects because of how easy it is to work with and onboard developers.
Opera was the most popular browser in Belarus in late 2000s. Happened mostly because of word of mouth and bunch of features that allowed to save data when browsing. Most users at that moment had metered connections like 800 megabytes per month, but up to 100mbit/s or really slow 30kbit/s but unlimited.
Opera had useful data saving features and an efficient compression, which is also why Opera Mini (with the old engine Presto) was very popular on mobile for a long time. I used it on Symbian...
Surprisingly simple and low footprint solution and genuinely pleasant to work with, since it is very similiar to managing a Systemd service.
[1]https://github.com/JanMa/nomad-driver-nspawn
reply