• 83 Posts
  • 82 Comments
Joined 2 years ago
cake
Cake day: December 2nd, 2024

help-circle


  • Altman can try to hype up how everyones going to subscribe to them someday all the while their subscriber base is being eaten up by competitors.

    https://www.wheresyoured.at/openai-projects-chatgpt-plus-subscriptions-to-drop-by-80-from-44-million-in-2025-to-9-million-in-2026-made-up-using-cheaper-subscriptions-somehow/

    Local stuff. I still believe the small parameter, ~1B free local, ones will suffice for the vast majority of how people use LLMs and there’s still going to be a few years of improvements there until investments dry up. Eventually I bet more and more phone companies will include one of these small ones out the box. Pretty much like a nice search engine that works offline like if you’re out on a major hike. Cloud stuff, there’ll be stuff like Proton’s Lumo where they’re taking free open weight stuff and piecing them together for users.

    OpenAI’s thing is they’ll make up for falling subscribers with advertising. So pretty much we’re advancing fast in the search engine race of the 90s/early aughts. We’ll at least have Gemini. ChatGPT maybe ends up crashes in value someday and bought up by Microsoft or some other company. Deepseek, Qwen, Kimi. Claude like ChatGPT maybe survices or crashes and gets adsorbed by another company. Proton continue to exist as the company making AI products out of free stuff. Eventually the pace of improvements moves at a crawl and it’s pointless to be paying for the best paywalled stuff. Just use the free stuff like how everyone mostly uses free search engines









  • It is impressive how I almost always hear about Claude stuff for paid programming services and never copilot. Normal search engine replacement stuff, I’ll hear almost exclusively about people using ChatGPT and Gemini. Then people self hosting, I’ll hear all the free stuff like Deepseek, Kimi, Qwen, …

    People just talk trash about copilot. I swear even Proton Lumo gets less heat and when people want upgrades, they’re all urging Proton to add the latest Deepseek, Qwen, Kimi, etc models to their algorithm. Microsoft has got to have one of the most hostile to themselves customer base to be rivaled only by companies like Oracle








  • I and I imagine barely anyone ever heard of Codeberg until the past year like me when I made an account and the website was loading at a snails pace. Github, Gitlab, and Bitbucket are way more established.

    Every employer I’ve worked for either uses Github, Gitlab, or Bitbucket in that order of commonality. Then any that self hosts uses Gitlab either free or Ultimate. I imagine anyone writing pipelines would like to stick with what they’re comfortable with. I imagine migrating gitlab ci to foregejo actions can be annoying especially on huge projects unless you’re already using something like Tekton to build out your own CI pipelines. How I see my project managers use Gitlab Ultimate features to link together issues, milestones, commits, merge requests, branches, epics, create filters for the issues boards, etc - I’m impressed.

    A lot of co-mingling between different groups within the organization to create some levels of siloed operations. There’s stuff like sharing user databases between Gitlab and other products that aren’t gitlab. API stuff where you make a gitlab account and it propogates to other services and that even includes stuff like group management in gitlab and other services non-gitlab. A bunch of stuff that I barely have to work to achieve like getting sonarqube or other services to easily integrate into Gitlab pipelines and create conditional actions in them and the merge requests comments to notify developers of findings. I have no doubt used very little that’s out there that offers easy integration into Gitlab and Github workflows.

    Our pipeline inserts milestone links into our changelogs. We use the Gitlab project wikis and release pages. We use the gitlab package and container registries. Self hosting runners is super easy. There are a lot of 3rd party services that host github and gitlab runners that are really click and they’re ready to go. I don’t have enough experience with Codeberg yet but Gitlabs CI file text editor and the browser embedded VS Code I find very useful.

    On Gitlab, these are very useful. I’d want something similar on codeberg rather than dealing with all that myself along with other key/token management

    https://docs.gitlab.com/ci/variables/predefined_variables/

    For the most part, I would expect people to go where they’re most familiar and at work they’ll be most familiar with Github and Gitlab and if you want your code to be seen, you’ll go where the bulk of developers are







  • I think first would be wait to see how well it can be decoded/transcoded on CPUs for peoples current equipment. Won’t be able to have as many concurrent streams as codecs with hardware support. AV2 hardware is probably years away. I’m certain AV2 hardware will succeed unlike VVC which had a blip of support with Intel then abandoned the next generation of Intel chips. I’ll switch to AV2 once it has similar adoption to like AV1 today so like 8 years from now I guess. I’m guessing similar amount of time for hardware support to be as ubiquitous. Not sure if it should be quicker with how dead in the water VVC has been for 6 years or slower because people upgrade hardware less frequently now and honestly h.264 is still good enough and AV1 is really good enough so any rush to AV2 will mostly be hyperscalers trying to cut down on bandwidth and storage costs


  • I’ll try it. I still want to make a move off of vs code/codium. I keep zed and lapce installed to keep an eye on but at work everyone uses vs code and its familiar to everyone. I don’t know why more people don’t give lapce a try or more attention. Zed seemed like it would be corporatized in some way since the beginning. I can see why editors like Kate aren’t super adopted with the lack of plugins like vs code but it seemed like Lapce has a pathway to be as extensible






  • I suppose so. I’d rather they spell it out for simple readability. Like I don’t know what Krita means but easy to read. Kate text editor may mean something, I don’t know. Kdenlive is easy to read. Don’t know what the ‘den’ part is supposed to mean

    Apparently it’s “KDE Non-Linear Video Editor”. At least kdenlive is easy to read in my opinion











  • commander@lemmy.worldtoLinux@lemmy.mlLinux and RISC-V by 2030
    link
    fedilink
    arrow-up
    3
    arrow-down
    1
    ·
    3 months ago

    It shouldn’t be hard by 2030 I imagine; particularly if you primarily or exclusively use open source software. The RVA23 chips announced I usually see people comment them as having synthetic benchmark scores at about the Apple M1 level. I regularly use a laptop with a Skylake dual core in it and a Raspberry Pi 5 run off a microsd rather than a m.2 NVME hat. With that in mind, if RISC-V designs don’t get any better than that in the next 4 years, they’ll still be better than hardware that I will still be using. I still use a Raspberry Pi 3. At work every now and then I’ll throw a gitlab runner on a 10 year old desktop to have another thing building when things are busy

    There are RISC-V developer boards today with PCI-E slots that you can throw in pretty much any AMD graphics card. The big distributions Debian, Fedora, Ubuntu, Red Hat - they all support risc-v. felix86 is equivalent to box64 and FEX for x86 to ARM:

    https://felix86.com/felix86-26-04/

    Software support is solid already today. It’s hardware availability for the announced RVA23 designs that’s not mature yet. 4 more years and I imagine in most cases the experience of Linux on RISC-V hardware not being much different than on ARM or x86 hardware