• 0 Posts
  • 874 Comments
Joined 2 years ago
cake
Cake day: June 16th, 2023

help-circle


  • Well the problems to be solved aren’t necessarily the technical ones. Another way of “solving” the problems is to stop trying to use it in contexts where it’s limitations are more trouble than they are worth.

    Here it is being tasked with and falling to accurately summarize news, which is ridiculous because those news articles come with summaries already, headlines.

    So a fix may not mean fixing the summary, but just skipping the attempt as superfluous.

    There are uses for the state of LLMs as they are, but hard to appreciate when it’s being crammed down our throats relentlessly at things we never needed them for and watch them screw things up.






  • The thing is, for the Windows ecosystem, ARM doesn’t have a good “hook”.

    When tablets scared the crap out of Intel and Microsoft back in the Windows 7 days, we saw two things happen.

    You had Intel try to get some android market share, and fail miserably. Because the Android architecture was built around ARM and anything else was doomed to be crappier for those applications.

    You had Microsoft push for Windows on ARM, and it failed miserably. Because the windows architecture was built around x86 and everything else is crappier for those applications.

    Both x86 and windows live specifically because together they target a market that is desperate to maintain application compatibility for as much software without big discontinuities in compatibility over time. A transition to ARM scares that target market enough to make it a non starter unless Microsoft was going to force it, and they aren’t going to.

    Software has plenty of reason not to bother with windows on arm support because virtually no one has those devices. That would mean extra work without apparent demand.

    ARM is perfectly capable, but the windows market is too janky to be swayed by technical capabilities.


  • This sounds pretty plausible. The windows user is the least likely to understand the implications of arm for their applications in the ecosystem that is the least likely to accommodate any change. Microsoft likes to hedge their bets but generally does not have a reason to prefer arm over x86, their revenue opportunity is the same either way. Application vendors not particularly motivated yet because there’s low market share and no reason to expect windows on x86 to go anywhere.

    Just like last time around, windows and x86 are inextricably tied together. Windows is built on decades of backwards compatibility in a closed source world and ARM is anathema to x86 windows application compatibility.

    Apple forced processor architecture changes because they wanted them, but Microsoft doesn’t have the motive.

    This has next to nothing to do with the technical qualities of the processor, but it’s just such a crappy ecosystem to try to break into on its own terms.


  • Well, even a locally controlled bed would have “not worked” (well, it’s still a bed obviously, just not heating/cooling) in a power outage.

    Note our household got it when it was significantly cheaper (still expensive-ish, but not nearly as bad as now) and grandfathered into being able to use it without a monthly subscription. In a bit of bad/good luck, because replacements kept leaking, we got warranty-upgraded to the current offering. So get to know how the new stuff is without having had to pay as much or maintain a monthly subscription. When we bought it, at least, they had good warranty coverage for leaks.

    So I get to see how good the hardware design fundamentally is while also knowing how anti-consumer the business and software side is going.

    Ultimately when/if I lose sane access to the capabilities, I’ll probably start poking around to see about hacking at least the heating and cooling, since we did struggle to find a good comfortable design for such a thing before getting here. They really did at least nail the mattress pad part, and the heating/cooling is pretty good without being obtrusive. The vibration and sensors might be nice, but ultimately I don’t care too much about that.


  • Once that frustrates me greatly is eight sleep. My wife had been trying various products and unfortunately eight sleep was the best executed one. But they are openly hostile to local controls.

    From the time they have released people have been complaining over and over about zero local controls, suggesting buttons on the base, a remote, or even local wifi or Bluetooth controls and their people keep coming online and patronizing by claiming their engineers are working on it, but it’s hard. Truth is they are passing a fucking subscription plan to use your damn bed.

    Finally they came out with their local control “solution”. No, buttons should not be on the base, that would be inconvenient. No, a remote control would be too easy to lose. So they implemented super dodgy earbud type controls, two taps for a tick colder, three taps for a tick warmer. Ok, janky as hell, but finally, local controls. So you get things going and do the tap and long buzz meaning “reject” the request. Turns out the taps will only process if the cloud server says it’s ok, and the bed will usually be “off” and not receptive to taps unless you turn it on via Internet app or you have an Internet arranged schedule that has it on at the time you want to adjust it.

    It’s a shame since they otherwise had fantastic execution, but their monetization through an app strategy is maddening. So my home has one cloud based device and it pisses me off.


  • I have a stove with optional app support, but I tolerate it because the app doesn’t add anything. The local controls can do everything. If you use the app, you have to hit a button on the local controls anyway to confirm you are physically there anyway before it listens to the app for most things.

    The only thing that was somewhat convenient was phone notification when timed cooking was done, because the stoves own chime wasn’t that loud. However ultimately I stopped bothering and just set a phone timer when I set cook timer, because keeping the oven on the network was an active maintenance activity that wasn’t worth it.



  • jj4211@lemmy.worldtoMicroblog Memes@lemmy.worldCriteria
    link
    fedilink
    English
    arrow-up
    3
    ·
    6 days ago

    I’m my experience, even if you get caught. The exaggeration to get your foot in the door is expected, and everyone is expected to represent themselves deceptively well. Honesty in the interview when everyone can deal with nuance can work and might be appreciated, but definitely a little exaggeration in the resume unless you have ungodly actual credentials/connections.


  • jj4211@lemmy.worldtoMicroblog Memes@lemmy.worldCriteria
    link
    fedilink
    English
    arrow-up
    7
    ·
    6 days ago

    In my case, early in my career a contracting company lied on my behalf without telling me.

    So I’m in the “skills assessment” meeting and I’m confused when they started rattling off experience from my resume that I didn’t have. I asked if I could see their copy of my resume and said “ok they made this section up, but the rest appears the same, here a printed copy of my resume unmodified”.

    I was shocked and figured that was a way to tank any chance I had at the job, but they “hired” me and said people and contracting companies did it all the time, so it didn’t phase them, but admitted my resume as it was from me wouldn’t have even gotten an assessment.


  • jj4211@lemmy.worldtoMicroblog Memes@lemmy.worldCriteria
    link
    fedilink
    English
    arrow-up
    10
    ·
    6 days ago

    Get this all the time in software development, being given “requirements” and most of them are pretty stupid wishlist items.

    I constantly argue that that will not get a good outcome if they just call everything is equally a “hard requirement”.

    What they want to do is negotiate and start from an unreasonable anchor point. In my case I find it super tiresome because my stance is always the same, make a priority list and we’ll get as far as we can. But escalating and tying us up in meetings to try to argue for stuff you are just using as a negotiating tactic only gets in the way of us doing what we can. We are going to do what fits, and people are not going to work unpaid overtime or holidays just to meet some arbitrary deadline. If it doesn’t fit, well it won’t be long until the next window.

    My team has a very long history of ultimately exceeding the hopes of the folks asking for stuff and yet they continue to try to get us to commit to stuff we never will.



  • Maybe for some, but even if you have to keep it up because your work it relatives demand it, Windows ecosystem is essentially impossible to debug when it hits issues and you just have to take guesses as to why the obscure bad behavior is happening.

    Windows is better at not needing to be fixed or the first place by self healing, whereas with Linux distributions you have to know how to fix those issues, but once it goes beyond easy to fix issues, Linux is reparable but windows isn’t.

    If it isn’t blatantly obvious, it didn’t fix itself, and SFC didn’t fix it, then they always say reinstall…



  • There’s no confusion over the subject, just an expectation that the current SCOTUS could play the “Constitution doesn’t apply if the mother had no legal standing to actually be in the US” argument. That technically that hasn’t been established, and that there’s an implicit expectation that people giving birth in the US are legally recognized to be in the US, and all bets are off if the mother isn’t legally allowed in the US but gives birth in the US anyway. To the extent they seek being explicit about legal standing, they may point to the “and subject to the jurisdiction thereof” words as stating an illegal presence means that they are not subject to the jurisdiction of the US or the state.