Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
  • 0 Posts
  • 1.97K Comments
Joined 2 years ago
cake
Cake day: June 16th, 2023

help-circle
  • In general, ARM servers have had pretty tepid market demand. Ultimately they aren’t providing any benefits over x86, and folks are reluctant to leave the familiarity of x86 behind without really good benefits.

    To the extent there is appeal for arm, Nvidia is one of the better positioned arm vendors, and gigabyte is also a big player in that. But even then reports are that not even the promise of the most integrated Nvidia GPU experience has been enough to really motivate people to go for Grace either. Plenty of market for hopper and Blackwell, just not the grace variants.





  • Unfortunately, the incompetence doesn’t matter when they act on it and no one is willing to hold them accountable.

    Like recently how they admittedly deported someone they weren’t allowed to and even the supreme court unanimously ruled against the administration, but the administration just shrugged and ignored it, claiming that the court has no authority over what they consider now to be a sovereign El Savador issue.

    So if they ship off an inconvenient citizen to El Salvador, they claim it’s not their problem because it already happened…



  • I had been planning to, but being lazy about trying to enable my IDE setup but was giving it the benefit of the doubt. Your feedback resonates with how much I end up fighting auto-complete/auto-correct in normal language and seeing it potentially ruin current code completion (which sometimes I have to fight, but on balance it helps more than it annoys). I suppose I’ll still give it a shot, but with even more skepticism. I suppose maybe it can at least provide an OK draft of API documentation… Maybe sometimes…

    On the ‘vibe coding’, on the cases I’ve seen detailed, it seems they do something that, to them, is a magical outcome from technologies that intimidated them. However, it’s generally pretty entry level stuff for those familiar with the tools of the trade, things you can find already done dozens of time on github almost verbatim, with very light bespoke customization. Of course there is a market for this, think of all the ‘no code’/‘low code’ things striving to make approachable very basic apps that just end up worse than learning to code. As a project manager struggles to make a dashboard out of that sort of sensibility, a dashboard that really has no business being custom but tooling has fostered the concept that everyone has a snowflake dashboard, it’s a pain. But maybe AI can help them generate their dashboard. Of course, to be a human subjected to the workflows those PMs dream up is a nightmare. Bad enough already at my work there are hundreds of custom issue fields, a dozen issue types, and 50 issue states with maddening project to project unique workflows to connect the meaning of all this, don’t like AI emboldening people to customize further.

    The thing about ‘vibe coding’ is when they get stuck and they get confused/frustrated about why the LLM stopped getting them what they want. One story was someone vibe coding up a racing game. He likely marveled as his vision materialized. From typing prose without understanding how to code he got some sort of 3D game with cars and tracks and controls. This struck him as incredibly difficult otherwise, but reachable through ‘vibe coding’. Then he wanted to add tire marks when the player did something, maybe on a hard turn) and it utterly couldn’t do it. After all the super hard stuff, why could the LLM not do this conceptually much simpler thing? Ultimately spitting out that the person needed to develop the logic himself (claiming it was refraining to do it because it would be better for him to learn, but I’m wagering that’s the generated text after repeated attempts to generate code that the LLM just could not do).




  • I occasionally check what various code generators will do if I don’t immediately know the answer is almost always wrong, but recently it might have been correct, but surprisingly convoluted. It had it broken down into about 6 functions iterating through many steps to walk it through various intermediate forms. It seemed odd to me that such a likely operation was quite so involved, so I did a quick Internet search, ignored the AI generated result and saw the core language built-in designed to handle my use case directly. There was one detail that was not clear in the documentation, so I went back to the LLM to ask that question and it gave the exact wrong answer.

    I am willing to buy that with IDE integration or can probably have much richer function completion for small easy stuff I know to do and save some time, but I just haven’t gotten used to the idea of asking for help on things I already know how to do.



  • I understand it fine, and it’s not just a packaging phenomonon, all sorts of software developers have stopped trying to have consensus on platform and instead ‘just ship the box’. 99% of the time a python application will demand at least virtualenv. Golang, well, you are just going to staticly build (at least LTO means less unrelated stuff comes along for the ride). Of course docker style packaging is bring the whole distro. I’ll give credit to snap and flatpak that at least allow packaging to have external dependency packages to mitigate it somewhat.


  • I’d say actually a bit of the opposite. Generally speaking we don’t need a new package manager or init system, and better hardware support is almost entirely a kernel concern (one might make an argument that the loose bits of key management and tpm2 tools and authentication agents could be better integrated for “Windows Hello” type function I suppose, but I doubt that’s what the meme had in mind.

    Not really needing to reinvent the wheel on those, we got a variety of wheels, sometimes serving different sensibilities, sometimes any difference in capability went away long ago (rpm/dnf v. deb/apt).

    The best motivation I can think of at this point is to make specialty distribution that is ‘canned’ toward a specific use case. Even then it’s probably best to be an existing distribution under the covers. I think Proxmox is a good example, it’s just Debian but installer made to just do Proxmox. You want to do automated installation? Just use Debian and then add Proxmox (the official recommendation), because they have no particular insight on automated deployment, so why not just defer to an existing facility?

    The biggest conceptual change in packaging has been “waste as much disk as you like duplicating dependencies to avoid conflicting dependencies”, maybe with “use namespace and cgroup isolation to better control app interactions” and we have snap, flatpak, appimage, and nix very well covering the gamut for that concept.

    For init, we have the easy to modify sysv init, or the more capable but more inscrutable systemd. I don’t see a whole lot of opportunity between those two sorts of options already.


  • Revolvers aren’t exactly known for being stealth… It’s just too much risk to desecrate a grave of someone who was dead before most of those officers were even born that most folks have never even heard of. At this point even the oldest on the force would be a generation removed from any officers that were working in 1969.






  • jj4211totumblr"his grave is annually shot by local police"
    link
    fedilink
    arrow-up
    4
    arrow-down
    2
    ·
    4 days ago

    Eh, I think at least for the past few decades it isn’t actually too plausible.

    Any known discharge of a firearm by police requires some sort of review. While they may be super lax and claim all sorts of false rationalizations for shooting a living person, I think even they would be unable to come up with a rationalization for discharging at a headstone in a public area.

    Now if it is “take a whack at the headstone with a crowbar”, I could believe that, but I don’t think they’d risk shooting a headstone out of the blue.