• 0 Posts
  • 24 Comments
Joined 2 years ago
cake
Cake day: July 3rd, 2023

help-circle
  • I won’t buy my wife a Cricut for the same reason, it is a closed system that the company can decide to nickel and dime at will.

    Surprised that they switched to Evil mode so soon, now everyone talks about this, and just a few days ago nobody cared and those who did were the loonies talking crazy.

    Presumably now that the security keys are known, it is possible to jailbreak your printer and never deal with Bambu ever again.


  • I think everyone with a 3D printer starts like this (it is a self-replicating hobby after all!), but eventually I grew out of it. Making your own better printer out of the one you already have is awesome, I’m glad I did it! You learn so many new ways of failing, sometimes it’s a miracle these things work at all.

    For me though I managed to stop after 3 printers (gotta have a backup while working on the downed printer!). I mostly use my printers for functional stuff though, complimenting my other hobbies when I need something super specific. It’s great to have the skill to troubleshoot when things go wrong, but also great to just hit Print and know it will work! I am thankful for the CAD skills I picked up with this hobby.

    For the first year or two I was just constantly upgrading this or that on my lousy printer, then getting new problems due to those upgrades… I’m glad I don’t do that anymore 🤣

    Thankfully my « printing trinkets » phase did not last too long. So many benchies…


  • it’s not an optimization if you don’t measure an improvement.

    This, so much. I often see this at work, theories about this and that being slow, or how something new « should » be better. As the resident code elder I often get to reply « why don’t you measure and find out »…

    For some reason it seems nobody uses sampling profilers anymore, those tell you exactly where the time is spent, you don’t have to guess from a trace. Optimizing code is kind of a lost art.

    Sometimes I wish compilers were better at data cache optimization, I work with C++ all the time but all of it needs to be done by hand (for example SoA vs AoS…). On the upside, I kind of have a good job security, at least until I retire.


  • It is exactly my case, as HomeKit by itself is way too limited for automations.

    All of my HomeKit devices are actually exposed through HomeBridge, so I can still use HomeKit stuff if needed, and devices that do not support HomeKit can still be added to HomeKit.

    My current challenge is on the Smart Dashboard side, I don’t really want to buy a Google Pixel Tablet for this, and the Nest Hubs I have don’t really integrate with HomeAssistant except through Google cloud services.

    HomeKit dashboard is fine but too basic.


  • I am not convinced bots would fill the list with hypothetical purchases, I don’t think scalpers are interested in waiting or having money tied up in backorders.

    The point is to eliminate the scalper advantage by ensuring one can buy the product « at some point ». If you need it by Christmas or whatever then you are kind of screwed.

    I remember for the SteamDeck OLED, stock was enabled in waves over at least a month, so even though the first batch was sold out in minutes, there was no rush to refresh the store page to try and finish the transaction before it ran out. This is in direct contrast to (say) the PS5 which sold out in minutes then still wasn’t available anywhere over a year after it launched.

    I don’t really understand how Valve solved the problem, it should have followed the same pattern of being sold out in minutes then scalpers would be the only option for months, but interestingly that’s not what happened.


  • It seems everyone forgot that not too long ago, you could back order something and the store would call/ship whenever they got it.

    Just let me give you my credit card number in exchange for a spot in the waiting list, then the scalpers lose and I get my new launch thing whenever they get around to it. But no, that would be too simple, gotta get the crowd riled up and race for the available units!

    I suppose this could be abused like everything else but it wouldn’t be worse than what we have now with fucking scalpers buying up the little stock that trickles in via automated bots.

    It’s not about getting your fix sooner for the new shiny, sometimes you really need a new GPU to replace the one you’ve had for 5 years! Why should you settle for the previous generation if the new one just came out and you are willing to pay launch MSRP for that privilege (not 2-3x MSRP for scalpers!!).




  • fulg@lemmy.worldtoTechnology@lemmy.worldWhat Ever Happened to Netscape?
    link
    fedilink
    English
    arrow-up
    36
    arrow-down
    10
    ·
    edit-2
    4 months ago

    They became a poster child for why you should never “start over from scratch” even if your current codebase is awful. Because when you do that your competitors keep going, then they have years on your now stale product. Netscape lost all on their own…

    Also: selling a browser? Man, the 90’s where wild.








  • Vulkan and DirectX could already share shaders, because the input for both was already HLSL. The difference is the intermediate representation of the compiled shaders that will now be the same in the future (SPIR-V for both).

    The real winners here are driver programmers at NVIDIA/AMD/Intel, since they will no longer have to develop support for both DXIL and SPIR-V (which are similar in concept but different in implementation). How much of that will be true in practice remains to be seen, but I am hopeful.

    There are tools to analyze, process and transform SPIR-V bytecode already, presumably those will work for DX12 shader model 7 too. It might make performance analysis easier, same with debugging via a tool like RenderDoc that supports SPIR-V but not DXIL.

    As for the overhead of DirectX, with DX12 this is largely not true anymore, both are high performance APIs with comparable overhead (i.e. as little as possible).



  • I remember your previous post, congrats on not giving up.

    Whipping up a script to solve a very specific problem is super satisfying, but I found that anything you write quickly becomes a liability. Debugging Perl can be super difficult, especially when returning to something you wrote a while back.

    Personally I grew tired of the punishment and left it all behind! If I need a quick script I’ll use Python instead, and if it doesn’t work I can use a real debugger to fix it.

    In any case it’s always fun learning new things, I hope this experience ends up being useful to you in the future and you get to easily solve a problem that stumps everyone else involved.

    Cheers!