• 6 Posts
  • 283 Comments
Joined 3 年前
cake
Cake day: 2023年6月18日

help-circle
  • I think that is kind of the main point of Rust, though.

    It’s pretty easy to make something in C++. But it will very probably have a lot of hidden issues with memory, undefined behaviors and the like. Rust doesn’t let you make those mistakes that much, and forces you to do it correctly and securely the first time, which is why it is harder to get into.

    They are mostly harmless and may never cause problems for you, but that’s how you get critical RCEs that are 8 years old in a software that’s now widely used.

    If you don’t need this kind “ease traded for security”, in my personal opinion I’d go with Zig instead.




  • I can’t wait for companies to finally price out most of developers out of AI use, especially the FOSS ones.

    I just hope most of them won’t get too addicted to the tech crack they are getting free/cheap samples of currently, and will be able able to find back their motivation and skill to work without a feel-good dopamine machines.

    Also, lol at all the coments being like “if you’re 100% against the tech crack, you’re delusional. The cat is already out of the bag, it makes you way better at coding, if you use it responsibly!”

    The problem isn’t that it’s not somewhat good, the issue is that soon you won’t be able to afford it, while also being addicted and dependant on it. But I’m sure y’all are able to use crack responsibly and will be fiiine.




  • I’m mostly ok with it, paradox of tolerance and all that, plus that’s just a common moderation and since I’m not using DMs, I don’t care about that either, but seeing the reaction of others - have you cosidere not scanning DMs in the first iteration at least? Even if DMs are public thanks to how I presume activitypub works, it’s not something you can easily get to or understand as an average user, and reading the sentece “we will scan your DMs” will upset a lot of people, regardless of context.

    From the PR standpoint, I don’t think it’s worth it, and it’d be better to just leave it on reports.

    You will get headlines “Programmers.dev scans your DMs”, and people will not care or know how do they actually work on Fedi.



  • You can do a task pretty well if you nudge the AI, have it write an exact explanation about every part of the architecture, code and data flow it’s working with and throw relevant files into context, and correct anything that’s wrong before you send it to do the task. You still have to review, but I didn’t have to correct much in my experience.

    But that burns like 20$ of tokens per task, at current prices that are way below the costs AI companies are paying.

    While it does help me, especially with parts of the codebase I’m not familliar with, it’s not sustainable, and it’s actively and very quickly robbing me of my skills and knowledge. It’s really a bad idea to use it, in two years time you’ll be royally fucked once they raise prices to recover the trillions they are loosing right now.

    So, however tempting, I simply don’t use it. I won’t throw away years of college and experience just to do a task a little bit faster today.






  • I’m mostly interested in how will they handle giving the info to apps. If it’d let me to block or fake the request depending on what I currently need (just prompt me every time an app asks, and let me choose the bracket), I’m good.

    Tbh, most sites that are slowly getting targeted by age verification laws are things I’m kind of addicted to and have been trying to drop for a long time. A “scan your face or id” dialog would be a good reminder to finally cold turkey it. It’s one of the things I hate more than however much I need their platforms.


  • I mostly work in gamedev where they aren’t that much feasible so I don’t have much real experience working with them and I might be wrong but from when I looked into it a while back, it’s basically just a docker container that you specify in a .devcontainer file (at least for VSCode, but other IDEs probably have something similar) and when you need to develop, compile or run your code, it runs it in the container. It also doesn’t have to run locally on your machine, if you can run docker somewhere else (i.e on a more powerful shared server).

    I can see several advantages (but I never really tested it in practice, so I’m mostly guessing) - containers are usually quick to start, you have the same and stable and replicable dev/build environment for all devs (since you just commit .devcontainers), so there aren’t some hidden dependencies and “works on my machine” shouldn’t happen too often. It also helps you keep your OS clean, so you don’t end up with 5 versions of python, 3 JDKs and 20gb of random NPM packages installed in your OS after 5 years of development - which is the most important advantage for me.



  • Managing centralized security and device management correctly on multiple OSes must be a nightmare. From EDRs to app and device provisioning.

    You should do dev work in devcontainers anyway.

    Not that it’s an excuse or that I’m happy with that, but I can totally understand why companies do that, and tbh I’d rather see a properly secured than have the option to run Linux.

    But I’m biased, because I used to do Red Teamings, and the things I’ve seen…