Mastodon

  • 0 Posts
  • 33 Comments
Joined 2 years ago
cake
Cake day: July 27th, 2024

help-circle














  • reply from Peter Hutterer

    Not to dunk on his achievements, but his argument is basically that it doesn’t matter because the end user doesn’t see any libwacom branding.

    However, when they upgrade their package, it will show the Wacom name. I don’t think it’s unreasonable to rename the project to something which is more descriptive, especially since it contains way more than Wacom code.

    I can understand both sides. I also think that you shouldn’t bow to corporate interests in general, for example to marketing departments of any company.

    However by keeping the Wacom name you’re basically giving them special treatment just because they came first. Vendor neutral projects should be named vendor-neutrally, IMHO.




  • No one does that in a project they’re building for themselves.

    Speak for yourself, I always did that and I found it easier with LLMs nowadays.

    I hate most AI shite with a passion but when it helps my colleagues write commits which are more than “add stuff”, “fix some things” I’m fine with it.

    I rarely use AI to generate code, usually only when I need a starting point. It’s much easier to unfuck AI code than to stare blankly at a screen for an hour. I’d never commit code I don’t fully understand or have read to the last byte.

    I hope OP is doing the same. LLMs fail at 90% of coding tasks for me but for the other 10% (mostly writing tests, readmes, boilerplate) it’s really OK for productivity.

    Ethics of LLMs aside, if you use them for exactly what they’re built for – being a supercharged glorified autocomplete – they’re cool. As soon as you try to use them for something else like “autocompletion from zero” aka “creativity”, they fail spectacularly.