limonfiesta

Rise of Skywalker was the last Star Wars property I’ll ever watch. I haven’t even watched the originals ever since then.

Others are free to feel differently, but Disney killed Star Wars. I’m not even angry, I don’t feel anything about Star Wars anymore, aside from apathy.

Pretty much all enterprise security software companies have endpoint clients for Linux, desktop and server.

However, most of those will be exclusive to their business channel products.

No, because the barrier to entry for car manufacturing is significant.

If the other major car manufacturers weren’t already working a similar advertising system/platform, they’ve already scheduled multiple meetings to catch up.

This isn’t a problem that will be solved by the market and competition, only by regulation.

And I don’t consider tech savvy users learning how to hack and disable these features as a resolution, it’s just mitigation.

Generally the elastic or usage/volumetric type billing structures are used on SaaS/cloud products, not on-prem.

Although it’s entirely possible that elasticsearch, and other vendors in the space use that pricing model for their on-prem customers.

Regardless, that’s even more of a reason why it would be very difficult to give a quote without being first having a presales meeting with a solution architect or knowledgeable rep.

This company may be dogshit, but seat count is the standard licensing structure for most employee facing business software, including on-prem.

Most business software licensing/CRM tools requires that information to generate a quote, as price will be dependent upon several factors, including volume licensing tiers i.e. volume discounts.

Sometimes, licensing structures are simple enough that an employee or rep might be able to give you a quick ballpark without that information, but that would be the exception, not the rule.

And all of that is assuming that pricing is only based on seats, when there could be a whole lot of other variables that would be required even for their system just to generate single quote e.g. core count, support terms, etc.

To be clear, none of that means anyone should trust, or switch back to, elasticsearch. It’s just a minor peak into the mundane horrors of business software licensing.

Every home should have an auger, but a plunger will work quicker, easier, and cleaner, 99 out of 100 times.

Everyone hating on that setup are a bunch of morons.

There’s a good reason to put your patch panels on a separate rack then all of your switches like that, because eventually you’ll have to roll them around. At which point, you’re going to need some slack in the lines, like when you’re hooking up a tow line to your hitch.

That’s all I see here: preparedness. Separate racks for switches and patch panels, and a lot of slack for when you got to roll them around, or some shit I don’t know.

I just know that I see foresight and planning when I look at that picture, not sure why everyone else doesn’t.

Currently, hydrogen production requires more energy to produce the equivalent amount of hydrogen.

Which is why it should not be produced on a fossil fuel based grid, but is perfect for stored portable energy on renewable grids. For example, converting excess wind and solar power to hydrogen fuel.

It sounds like Estonia is on the right track, and intending to leverage their access to water and other renewables to generate “green” hydrogen. This sounds great, I hope they can pull it off.

What do you mean go wrong?

All of the “consequences” that would arise from a program like this, are intentional.