I'm the author of vleam[0], which enables Gleam usage in Vue SFCs.
If there's one thing I missed building the LSP is an awesome-list, where I could find stuff like Multispy -- LSP resources weren't easy for me to navigate as a beginner.
1,334 karma · joined November 6, 2013
I'm the author of vleam[0], which enables Gleam usage in Vue SFCs.
If there's one thing I missed building the LSP is an awesome-list, where I could find stuff like Multispy -- LSP resources weren't easy for me to navigate as a beginner.
You seem to have misunderstood me.
Lack of knowledge does not imply you can coerce transparency.
Not sure how your reply related to it.
Stop using force to make people do things you deem right out of thin air
Edit: this is reiterated by OP in a sibling comment, guess I framed it correctly?
You probably know a lot of things I don't, and some things that I can never know. That does not allow me to compel you to tell them to me.
Yes, even if I really want to make some impossible to define metric, like efficiency, look better.
Edit: I've read the readme, hoping for a take from anyone who gave it a try
https://wiki.archlinux.org/title/ASUS_ROG_Zephyrus_G14_(2022...
Also NixOS has a nixos-hardware repository with configurations for some laptops:
https://github.com/NixOS/nixos-hardware/tree/master/asus/zep...
Reasonably legible if you ever programmed anything
ActivityPub is a federated social networking technology popularized by Mastodon.
Account portability is the major reason why we chose to build a separate protocol. We consider portability to be crucial because it protects users from sudden bans, server shutdowns, and policy disagreements. Our solution for portability requires both signed data repositories and DIDs, neither of which are easy to retrofit into ActivityPub. The migration tools for ActivityPub are comparatively limited; they require the original server to provide a redirect and cannot migrate the user's previous data.
Other smaller differences include: a different viewpoint about how schemas should be handled, a preference for domain usernames over AP’s double-@ email usernames, and the goal of having large scale search and discovery (rather than the hashtag style of discovery that ActivityPub favors).
https://blog.nestful.app/spontaneous-productivity/
In short: Almost nothing is scheduled. The "what do to" is decided upon at the moment of doing. Defining granular enough tasks is a valid replacement to Pomodoro.
This means a tool that always tells you "what's next" is needed, which is why I built https://Nestful.app.
Nestful is undergoing heavy refactoring this month, and while data is safe and stable, features and bugs are not. If you like the idea but find the instability troubling, send a support request mentioning this and I'll waive a couple of months of payment.
I'm in the same boat, looking for as light as possible with a much battery as possible, was banking on the 16 yet we get 9 hours instead of (an assumed) ~10-11, and 2.1/2.4kg.
Somehow the Thinkpad Extreme X1 and the new Zephyrus G16 have similar CPUs, dGPUs, a >90Whr battery and they weigh less than 2kg.
Where's most the weight going? Will I be able to buy a FW 16 and eliminate weight to achieve similar specs? Literally asking about using a "stripped down version".
If anyone is interested in my resuming them, let me know at contact at weedonandscott dot com
[0] https://www.reddit.com/r/vfx/comments/11s08ne/your_opinion_o...
[1] https://www.reddit.com/r/gamedev/comments/11s5haf/what_do_yo...
This isn't bad -- it drives storytelling innovation
Spectrum OS is trying to do that, but is still has a long way to go
Edit: Tip 2: the screenplay looks nothing like a screenplay
I've been on Linux for more than a decade, and even with advancements like Flatpak, Linux is very far from the protections Android, iOS, Mac and Windows have.
After a bit of research I've figured that main need for this kind of focus is fear of the document changing too much, to the point where the current idea for an edit will no longer relevant.
Apps such as OP try to solve it by hiding the problem, while with FileMonger the writer gets a guarantee that they can revert to any save at any time, if document indeed changes too much (it usually doesn't).
If you've mentioned vim and technical writing you're probably writing plain text files and are knowledgeable enough to use manual version control like git when necessary, which is why this baffles you.
I thought this was the working assumption.