MajorasMaskForever

@MajorasMaskForever@lemmy.world

• ⁨Comment⁩ on ⁨Production quality often has in inverse relationship to information quality in youtube videos⁩ ⁨⁨2⁩ ⁨days⁩ ago⁩:

  I feel the same way about Mark Rober. For me I think I’ve figured out that I don’t like how blatantly obvious it is that the only reason the video exists is to grab headlines and attention by being so outlandish. I figured that out when I couldn’t tolerate many LTT videos anymore but still liked other LMG channels and the WAN show

• ⁨Comment⁩ on ⁨Reddit says it is not covered by new Online Safety Code as it has moved its jurisdiction to the Netherlands⁩ ⁨⁨4⁩ ⁨weeks⁩ ago⁩:

  Why not Minot?

• ⁨Comment⁩ on ⁨Wells Fargo employee found dead in cubicle 4 days after she clocked in: ‘She was just lying on her desk’⁩ ⁨⁨2⁩ ⁨months⁩ ago⁩:

  If Wells Fargo had amazing management, was a massive and undeniable benefit to humanity, and every one of their employees loved working there, how precisely would that have changed the outcome here?

  The only two things that I can think of that would have changed what happened is 1) Security actively monitored every single person’s activity within the building at all times and make notes so one of the security team would notice that she’s been slumped over for a long time, and 2) management insisted that all team members are in office every single day to ensure that they all can see each other. In today’s work culture, I’d argue that doing either of those things is bad management.

  You say the point is that it happened at Wells Fargo, but let’s be more clear here: is your goal to find any reason to help justify your distaste of Wells Fargo?

  I do believe Wells Fargo has a lot to answer for, but let’s be honest and just in what we go after companies and people for. If we constantly attack entities we don’t like for anything that on first pass sounds bad, eventually we’ll have called wolf too many times and legitimate complaints will get ignored

• ⁨Comment⁩ on ⁨Wells Fargo employee found dead in cubicle 4 days after she clocked in: ‘She was just lying on her desk’⁩ ⁨⁨2⁩ ⁨months⁩ ago⁩:

  I really don’t think Wells Fargo has any blame in this, this just as easily could have happened to any company. Perhaps it is a problem with corporate America, but what would you say they’re actually negligent of?

  it may sound callous and cold, but logistics does end up asking strange questions like “What is a reasonable amount of time to notice that an employee passed away at their desk in a corporate office?” Or “How do we verify that every employee in the building is still alive?”

  It’s unfortunate and sad what happened to this woman, but I don’t see how Wells Fargo played any part in this other than to be a rage-bait headline

• ⁨Comment⁩ on ⁨Flat Earth is so yesterday⁩ ⁨⁨5⁩ ⁨months⁩ ago⁩:

  I’m not really feeling it

• ⁨Comment⁩ on ⁨Nearly all Nintendo 64 games can now be recompiled into native PC ports to add proper ray tracing, ultrawide, high FPS, and more⁩ ⁨⁨6⁩ ⁨months⁩ ago⁩:

  For graphics, the problem to be solved is that the N64 compiled code is expecting that if it puts value X at memory address Y it will draw a particular pixel in a particular way.

  Emulators solve this problem by having a virtual CPU execute the game code (kinda difficult), and then emulator code reads the virtual memory space the game code is interacting with (easy), interprets those values (stupid crazy hard), and replicates the graphical effects using custom code/modern graphics API (kinda difficult).

  This program is decompiling the N64 code (easy), searches for known function calls that interact with the N64 GPU (easy), swaps them with known valid modern graphics API calls (easy), then compiles for local machine (easy). Knowing what function signatures to look for and what to replace them with in the general case is basically downright impossible, but because a lot of N64 games used common code, if you go through the laborious process for one game, you get a bunch extra for free or way less effort.

  As one of my favorite engineering phrases goes: the devil is in the details

• ⁨Comment⁩ on ⁨Apple Vision Pro Owners Are Struggling to Figure Out What They Just Bought⁩ ⁨⁨9⁩ ⁨months⁩ ago⁩:

  I think part of the “what do I do with this” factor for the iPad was that Apple (and other companies still to this day) were so hell bent on making everything smaller and more compact that releasing a larger product was marketing whiplash. Not to mention that smartphones were being pitched as this “do everything device” so why would you need anything else?

  After you get over that marketing sugarcoating, it becomes pretty obvious what you’d use an iPad for. Internet and media consumption at a larger scale than your phone, easier on your eyes than a phone, but retains at least some of the lightweight smaller form factor that separates it from a regular laptop. Sure you didn’t have the stick it in your pocket advantage of a phone or the full keyboard and computational power of a laptop, but there was this in-between that for a modest fee, you could have the conveniences if you can live with/ignore the sacrifices.

• ⁨Comment⁩ on ⁨Apple employees outnumbered customers at Vision Pro launch in San Francisco's Union Square⁩ ⁨⁨9⁩ ⁨months⁩ ago⁩:

  I don’t think the MacBook Airs launch is a good comparison.

  Sure there was an early adopter tax on being one of the first “thin and light” laptops, but people already know what you can use a MacBook for, there was already a large value proposition in having a MacBook, the extra cost was entirely being more portable than it’s full size counterparts. Everything you can do on a Mac, just way easier to take on the go.

  I’ve read a few reviews on it, watched MKBHD’s initial review, and outside of a few demo apps they point to the vision pro having no real point to it. Which if true, then it falls in line with existing VR headsets that are a fraction of it’s cost and in a niche market, being three times the cost of your competitors is not a good position to be

• ⁨Comment⁩ on ⁨[deleted]⁩ ⁨⁨9⁩ ⁨months⁩ ago⁩:

  It’s IEEE misinterpreting the guys original paper.

  liuyang12.github.io/proj/privacy_dual_imaging/ (can’t find the full paper, but here’s the abstract at least)

  The paper author straight up says the light sensor is impractical to use as an attack vector, but when you use it in conjunction with other sensors you might be able to gleam more information than most might think. It leaves me with question of what other sensors can you combine to start getting behavioral information that is a security threat?

  I’ll say it worked for me. I read the IEEE headline, called bullshit, dug into it and yeah you can only get a tiny bit of information that you have to stretch pretty far to get useful conclusions from… But it’s more than the zero I initially thought. So props to the paper author, he met his goal. IEEE wanted sensationalized clicks, which they too unfortunately got.

• ⁨Comment⁩ on ⁨abandonware empires⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  I’m also curious how many people in this thread have ever been involved in product development and are actual trained/professional software devs. Because not only are some of these comments absolutely ridiculous from a business perspective, they make zero sense in a technical perspective too.

  Proprietary file formats show up because often times the needs of the system don’t line up with CSV, JSON, raw text or they hit some performance problem where you literally can’t write that much data to the disk so you have come to come up with something different.

  There’s also that a computer program in the last 50 years is, except for extreme circumstances, never truly on its own. That microscope control software is completely dependent on how Win95 works, is almost certainly reliant on some old DOS kernel behavior that was left over in early Windows, which Microsoft later completely ripped out starting with Win Vista (tossed back in for Win7 cause so many people complained, then ripped it back out in 8 which no one seemed to care about)

  And it’s not just Microsoft that pulls this, even Lemmy’s darling Linux has deprecated things over the years because even in open source projects it’s unmaintainable to keep everything working for forever.

• ⁨Comment⁩ on ⁨Goodbye Youtube and thanks for all the fish⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  Kinda hard to sell ads when everyone blocks them