• 0 Posts
  • 16 Comments
Joined 3 years ago
cake
Cake day: December 25th, 2023

help-circle


  • The first apple device I recall was the Apple II.

    Please help me out: I can’t recall a single thing where Apple ever was cheaper than the competition.

    Their selling point was “works better” and then became “everyone be different (in the same way though!)”.

    What set their devices apart was the smoothness in which everything worked. First the devices and later their ecosystem. I despise vendor lock-in and never went for them because of that but I can see the appeal.

    Price though? This meme is the first time I’ve heard of that argument, someone please help me out.





  • Which are? I’m not joking, “GitHub broken” and “Google has issues” are not arguments against a better encryption default.

    The submodule argument is transitional at best.

    As for the pro side (note that this is my opinion, I’m not deeply involved in the discussion - and with not deeply I mean “not at all”):

    The case the author aggressively ridiculed ("I don’t use GPG to trust, I trust the GitHub authentication!) is one that anyone would have if they’d want to stay safe from centralized systems.

    Another is upstream availability: once an algorithm is identified as broken (no matter how small) usage drops rapidly - there’s a reason why no one uses md5 anymore although it “would be fine” for purely collision mitigation.

    And then there the simple fact that the integrity hash is a security feature, not purely anti collision (as the author also describes). Just because they (nor I!) can’t see an attack vector at the moment doesn’t make this less of an issue.

    In short: it’s the other way around: you’d need way stronger arguments than “there will be a transition pain” to knowingly compromise your security.




  • For me it’s the exact extreme opposite than your first point: The LLMs as death of copyright could be an actual food thing.

    The issue im struggling with is the ecological and economic harm. It feels a bit as if the steam machine would’ve been invented but you’d throw in babies in addition to coal.

    For the plus sides you’re right (as in: I agree so it must be ;) )b- with one minor exception: the vibe coding part is not bad in itself. I actually used vibe coding as a very hard exercise: develop something and find ways to estimate its quality and performance but you are not allowed to look into the code! It’s a fun brain teaser because it forces a pure outcome-perspective. The code itself is irrelevant for this, it’s the mental training that’s really interesting.

    Oh except people who publish vibe coded stuff as a cool new project without disclaimer. Or as PRs. Or as … Well anything where do see itself is actually important.






  • Sorry but you’re finding patterns in the wind.

    The Linux kernel dev and the LF (famously l, in the past) are independent of each other - with the LF being the slower one.

    So if you want to forcefully find a connection then it’s “Linus stand made the LF take on AI”. But even then it’s … Well just another conspiracy: two (of … “All”) institutions talk about the biggest tech hype since .com.

    Oh and to be very clear: The LF and with that the AAIF is a corporate organization whose sole purpose is that everyone (read: every corporation) benefits from Linux.


  • I’m experimenting a lot with goose, recently return on by the AI arm is the Linux foundation. It’s not yet mature enough to recommend it as a daily driver for non fanatics though for agentic stuff.

    Trying it as a daily driver by now :D

    It’s less about the tool though in my opinion but about the process. If you want to be a programmer then you need something integrated into your dev environment in my opinion.

    My focus is seeing how far I come with focussing in being a software architect who only has really weird junior devs who read a lot of books but lack any understanding.

    Which is … quite close to real life ;)

    I’m splitting by now my projects: agentic ones and “my” dev ones, treating trm differently helped me tremendously: different focus and I need a different skillset.