I had to click a few pages into their site for this
It's on the landing page in the "Extensible and Open" section too.
While Theia incorporates certain components from Visual Studio Code, such as the Monaco editor, it is independently developed with a unique, modular architecture, Theia is not a fork of VS Code.
I just tried using it with local Ollama AI - looks like the current version 1.60 has a regression breaking exactly that. And the 1.61 milestone with the fix is overdue. So, presumably the update with the fix should be delivered soon?
I changed the cargo home/cache directory so it's easier to clean up. The disk space pollution of Rust is insane.
I did a small project project that resulted in an 8 MB executable. And had dozens of gigabytes to clean up.
Even more confusing was how closing VS Code lead to 11 GBs being freed. I initially had three or four projects open for reference in APIs and API usage. But my primary partition ran full quickly. In the end I used Rover and minimized IDE usage to two instances. And after my work, removed target and cargo build data again so I actually have space to work with on my primary partition.
adding some clarifications to the winget portions:
However, the graphical windows for the various installed dependencies still show up, making it obvious that all winget is doing is run the regular setup scripts under the hood.
winget does some default best effort of and on common installer tech to show the least UI necessary. If a UI shows up after all, that indicates to me that the manifest (the article talks about Neovim) does not have the appropriate flags included, or that the installer that the publisher uses does not support it.
Most, but not overwhelmingly, of the stuff I install and upgrade does not show installer windows.
which often leaves your computer full of background processes that only exist to routinely check for updates to a lot of programs in the background
The services are not only for updating in the background and unprompted, but also for installing with admin permissions without asking the user for admin. Stuff installed into C:\Program Files is elevated on admin permissions rather than having user modify permissions, which is a security feature. A consequence is that a convenient update process needs a Windows Service that may install them without requiring the user to have and approve elevated permissions.
As a matter of fact, after installing Neovim, there was actually no way to run it!
This may also be an issue of manifest information for instructing the installer, or installer defaults. Or maybe the installer itself does not provide this?
Either way, of course these things are inherent shortcomings and efforts of integrating third party installers. I just wanted to clarify.
Regarding bad winget experiences: I assume this is not the case anymore, but installing a LibreOffice featureversion upgrade leading to an automatic system reboot without warning or confirmation sucked. lol This was relatively early on in the winget release cycles though.
[Nix] allows users to reliably reproduce the same state coming from any other state, which is also used for safe rollbacks.
What does that mean for configuration? How does configuration and customization play into Nix declarations?
I'm thinking of what would usually be in /etc/, and what classic package managers like apt/dpkg would deliver a default of but not replace if already existing. Where you make your specific program and service configuration that is independent of the theoretically immutable package program data.
It is not a generic term for source-available software, and never was.
The problem with that reasoning is that precedence and origin do not necessarily define language use after it. Language evolves. Society and communities make up new or change definitions.
Misuse of the term is evidence that it's not universally understood to be one way.
I think it's mainly because "open source" can be understood as accessible, readable source. And many people seem to intuitively understand it as such. The "free" terminology on the other hand has a more ambiguous meaning between freedom and no cost. And early on, the "freeware" terminology was established as a differentiation to "free software". "Open source" does not have such an equivalent established differentiation (like "source-available", which seems to be just not as prevalent, maybe because there have been much fewer products with that alone).
I understand the desire to correct, specifically with the established OSD. But I have to wonder if it will ever bear fruit, given these circumstances. And in consequence, whether it's even worth to point out.
While Thrive was originally widely inspired by Spore’s intended concept, we aim to portray a creature’s evolution in a fun and interesting way while remaining scientifically accurate. Evolution will play out on not just your own creature, but those around you, each competing to survive within the simulated environment.
What I would have liked it to mean: While coding, put on some music, and zone out to coding.
What it means now: Prompt an AI to generate working code and solutions.
I don't get where the "vibing" comes in. I guess you don't have to think about the technical details? And that's vibing? Maybe it's just unfamiliarity and lack of practice, but poking the AI via prompting and thinking about how you can influence it better doesn't feel like you could zone in to or "vibe".
Maybe it's about letting go of reasoning and just going for it? Vibing in the sense of going with the flow?
It's not the first terminology I find unfitting. I'm trying to accept that it is what it is, and that it just is what "we collectively" have decided to call it (or ran with).
It's on the landing page in the "Extensible and Open" section too.