limonfiesta

They aren’t poisoning the data with disinformation.

They’re poisoning it with accurate, but irrelevant information.

For example, if a bot is crawling sites relating to computer programming, or weather, this tool might lure the crawler into pages related to animal facts, or human biology.

I’m confused. Are you saying YOU can’t tell the difference, or that their is no technical difference?

Because, anecdotally, I’ve owned a variety of these devices, and I can absolutely tell the difference. Which sucks, because I bought cheaper devices hoping for reasonable parity of experience. I’m not saying my cheaper devices are bad, just that clearly the Shield TV performs better.

As to the actual specs, there is also clearly a real world difference between the bog standard Amlogic SoC (1/8, 2/8, 2/16), and the Tegra SoC.

It’s entirely reasonable to argue that the difference isn’t worth the extra cost, fine. But it’s dishonest to say there is no appreciable difference.

TBF I haven’t used the newer “low cost” Shield with the 2/16 Tegra SoC, so I can’t really speak to how it performs relative to something like Chromecast with Google TV.

Fuck me. You might be right, as I haven’t actually used the stock launcher since the big ad update years back.

I just remembered my original launcher having a lot of a Nvidia specific integrations, but I guess those could have just been bolted on at the system level.

I said Playstore Certified, and yes, they are mostly the same when you look under the hood, at least for those classes of devices, per generation.

Same, or similar SoC, with 2/8 (sometimes 2/16) specs.

Once you get up to the 4/32 range, you’re already looking around the same price (+/-) of a Shield TV.

Also, lol @ citing LTT, for anything. Just because a broken clock is right twice a day, doesn’t change the fact that it’s broken.

And for the sake of being fair, I didn’t even mention the 1/8 boards.

Yes, Google is an inextricably linked to all Google TV issues, but they didn’t force Nvidia to ruin the Shield TV’S launcher with ads, and other bloat.

At least, not as far as I know. If you have sources saying otherwise, I’d be happy to take a look.

As someone who owns both Nvidia Shield TV and standard cheap (Google certified) devices, all running Projectivy, it’s not really comparable.

The Shield runs smoother, has significantly less minor/annoying issues, and actually receives fairly regular updates.

Now, the new Chromecast with Google TV does get updates, but it doesn’t resolve the first two differences.

If you can’t afford, or justify the extra expense, for an Nvidia Shield TV, completely understandable. But don’t pretend that the user experience is the same, because it’s not.

I’d prefer AI cores, just like I prefer HW based AES instructions: present and up to my discretion as to how I choose to use them, or not.

Nvidia has destroyed the stock Shield TV experience with ads, but it’s easy to install custom launchers like Projectivy. The underlying system is still a privacy nightmare, but I don’t care that Nvidia knows what TV shows I watch.

I mean, I do care, just not enough to use something like Kodi as my primary TV interface. Maybe if I used any ad supported services I’d feel differently, but I don’t, so meh.

deleted by creator

What are the technical constraints on designing RISC-V chips with feature and performance parity to modern x86/ARM designs?

Just design constraints, not manufacturing, or adoption

Virtual Box is a Type 2 hypervisor, which means it’s running on top of the OS, and not directly on the hardware.

KVM is a Type 1, which runs directly on the hardware itself.

There are pros and cons to each, and VBOX is a great piece of software, but it is more resource intensive than other options available.

There’s plenty of good reasons to keep a windows device updated and available for use.

Honestly, I prefer that to spinning up a windows VM, especially if your needs include Windows software that interfaces directly with external hardware.

I realize that’s not an option for everyone, but for those who have an extra device available, or can afford a used laptop to keep in a closet, it’s well worth it IMO.

I’m going to go ahead and say that you do not want the Linux kernel running inside your head, under any circumstances.

We’re already at least one generation into womb to tomb data collection.

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.

Unless it’s for SMTP only, it’s probably a back end sever to some other front facing box, or service, that has IP addresses whitelisted for email.

I’m pretty sure I read one of his comments elsewhere talking about tunneling everything over SSH, so I assume that’s what he meant, but I could be mistaken.

Regardless, using an EOL distro as an internet facing SSH server that’s 8 years behind on SSH updates, is probably a bad idea.

We’re not talking about some punch card COBOL machine he jimmy rigged with network access, it’s an old Debian Linux box with SSH enabled.

It’s not like Metasploit would have a tough time finding unpatched vulnerabilities for it…

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.