• 0 Posts
  • 13 Comments
Joined 1 year ago
cake
Cake day: July 29th, 2023

help-circle

  • I switched from Copilot to Codeium after only a couple of months of Copilot use - just based on the cost since currently I’m just a hobby coder.

    The main difference I’ve noticed is that Codeium doesn’t seem as smart about the local context as Copilot. Copilot would look at how I’m handling promises in a project, and stick to that, whereas Codeium would choose a strategy seemingly at random.

    A second, and maybe more telling example, is that I do my accounts using ‘plain text accounting’ in VS Code. This is a very niche approach to accounting software and I imagine is hardly in the training sets at all - there certainly would not be a lot of public domain text accounts in the particular format (BeanCount) I use in public code repositories. Codeium doesn’t make any suggestions for entries as I’m entering transactions, whereas Copilot would see that the account names I’m using are present in another file in the project and suggest them, and very quickly figure out the formatting of transactions and suggest them correctly.




  • thirdBreakfast@lemmy.worldtoLinux@lemmy.mlyour favorite homelab applications
    link
    fedilink
    English
    arrow-up
    17
    arrow-down
    1
    ·
    edit-2
    7 months ago
    Infrastructure:
    • Proxmox VE - everything’s virtualised on Debian, mostly in docker inside LXC’s for neat backup/restore and moving between nodes
    • NGINX Proxy Manager - in front of most of my homelab services so they have https certificates
    • Tailscale - access everything, everywhere, including on phone, securely
    • Uptime Kuma - monitoring, with ntfy notifications
    • apt cacher NG - unnecessary caching of apt updates
    Apps:
    Currently in testing on the dev server:
    • neko - virtualised browser. Been experimenting with this in a container with a VPN for really simple secure browsing - ie launch it, do your online banking and then destroy the container.
    • Dashy - I go through periods of wanting a pretty home page with all my services, set it all up, then fail to actually use it and eventually delete it, then hear about another cool one…
    • Sharry - securish file sharing. I don’t love just emailing my accounts off to the accountant.
    • LimeSurvey - survey software (like Survey Monkey) - just something I’m testing for work
    • Omada controller - I’ve got a TP-Link switch and WAP that don’t really need centrally controlled, but you know, can be.
    • A couple of development environment LXCs I use VS Code in

    I still have not landed on a music system. I’ve put some of my library on Jellyfin, and tried a couple of apps with, but haven’t hit on a good combination yet. [edit:formatting}






  • For anyone without the inclination to wade through 47 pages, here’s what they say about HTMX, which they’ve classified as “Assess” rather than “Trial” or “Adopt”

    htmx is a small, neat HTML UI library that recently became popular seemingly out of nowhere. During our Radar discussion, we found its predecessor intercooler.js existed ten years ago. Unlike other increasingly complex pre-compiled JavaScript/TypeScript frameworks, htmx encourages the direct use of HTML attributes to access operations such as AJAX, CSS transitions, WebSockets and Server- Sent Events. There’s nothing technically sophisticated about htmx, but its popularity recalls the simplicity of hypertext in the early days of the web. The project’s website also features some insightful (and amusing) essays on hypermedia and web development, which suggests the team behind htmx have thought carefully about its purpose and philosophy.




  • I’ve been around - did COBOL at uni. DOne a lot of commercial work in Delphi and C++. I loved the few months of Swift I tried, but started on webdev 6 months ago. I felt really unsafe in JS, and was looking forward to moving onto Typescript. But, as time’s gone on, I’ve found JS just seems to work how I think it’s going to. I haven’t run into problems with types at all. I assumed I’d end up on a complied language for server side, but the Node ecosystem’s so mature it’s just been efficient to stay in JS land.

    If I was going to teach kids to code, this is where I’d start. Low friction to get going, and powerful enough to run most of the world. Bountiful resources to learn and get support.