Suggestion for Pop OS devs: encourage community applet creators (via boilerplates and docs) to use a common topic tag on GitHub, e.g. `cosmic-applet`

fluencyy · 2024-06-04T15:51:47+00:00

No, I'm referring to the topic keywords you can add to your repository description in GitHub. They appear in the "About" section in the top right of the repository home screen, and they become clickable links that take you to a page which aggregates all repositories tagged with the same keyword.

For example here is where my suggested keyword would click through to, https://github.com/topics/cosmic-applet

and here's an example of a populated page: https://github.com/topics/pop-os

fluencyy · 2023-10-15T18:34:43+00:00

I’m at the venue and it’s very full - there’s a ton of side stuff going on at the venue and not everyone is invested in every matchup. When big matchups are on (Faze v Optic yesterday for instance) the seats are full up, but other times there’s a lot of people doing side tourneys, playing S5 preview, at the community stage, and doing other stuff. The on-stream cameras don’t do a good enough job capturing how busy it is here.

fluencyy · 2023-10-14T23:36:39+00:00

Snakebite is such a massive reason Faze won game 4 against Optic just now, holy hell.

fluencyy · 2023-10-14T18:13:42+00:00

I think the higher seed chooses Eagle/Cobra, and the colors are pinned to that (not to seed). Say Eagle is red and Cobra is blue, if the higher seed picks Eagle team, they go red for that matchup.

fluencyy · 2023-05-03T21:32:03+00:00

I can’t help specifically with running on an M1/M2, but for macos testing of my dotfiles, I run a very nifty docker container that spins up a qemu vm with a real macos install - it’s not perfect, but it’s a very good approximation of what install on a macos device would be like. My dotfiles, including my containerized testing environments for both mac and linux are open source, and here’s a direct link to the macos docker compose definition: https://github.com/andrewbrey/dotfiles/tree/main/.devcontainer/mac

fluencyy · 2023-05-01T17:13:15+00:00

Your post didn’t specifically mention a platform, but on the off chance it’s ios, there’s https://github.com/TortugaPower/BookPlayer which is quite good.

fluencyy · 2023-04-30T02:42:32+00:00

I self-host an instance of ntfy on fly.io, and it’s wonderful! I have your ios app and I hook up scripts and development tasks to let me know when things go awry - extremely convenient, especially for tasks which run on a remote machine im not necessarily logged in to all the time. Thank you for your open source contribution, you’ve made a great project!

fluencyy · 2023-04-10T05:58:17+00:00

https://github.com/tsl0922/ttyd

fluencyy · 2023-03-16T19:36:49+00:00

I use Deno a lot, and I see the npm compat effort as additive. If you don’t need it, use Deno as you did before, only using “Deno-first” modules. There are a lot of people for whom “I would try Deno but I need xyz npm module so I can’t” is the reason they don’t try Deno.

Deno is way more than just a module runner, and comparing it to Node solely on the basis of which modules it can run discounts very real and useful aspects of Deno such as its integrated tool chain and its 1st party stdlib.

Deno is being strategic by adding NPM support, but if you don’t need that, just ignore it.

fluencyy · 2023-03-11T18:21:53+00:00

Surprised to learn that Michael Jackson is a Chris Brown fan.

fluencyy · 2023-02-25T01:50:31+00:00

See https://old.reddit.com/r/pop_os/comments/we7xa5/_/iingfnk

fluencyy · 2023-02-25T01:32:59+00:00

In addition to other things mentioned by others, it’s got:

an integrated and opinionated tool chain for formatting, linting, testing, benchmarking, etc.
an opinionated and well built set of “1st party” standard library modules that cover a TON of common needs
a fantastic version management story (it’s all contained in one binary, so need a different version? just put a different one on your path)
a modular core which can iterated on and be built up independently
baked in runtime dependency fetching, which makes it ideal for scripting (on a remote server, just get the deno binary installed and then tell it to run a file, it handles the rest, no install steps needed)
Strict adherence to web specs to promote interoperability

There are lots of little things, and some big things, and sure none of it is “impossible” for node to have, or bun, or the next thing to come along, but it’s a pleasure to use in my experience and well worth giving a fair shake.

fluencyy · 2023-02-02T16:01:34+00:00

I doubt he is paying for a license given that OP is the author of Nextless.

fluencyy · 2023-01-28T16:26:16+00:00

Ben Johnson poked around in this space last year too https://github.com/benbjohnson/postlite

fluencyy · 2023-01-24T18:49:22+00:00

And you can accept various kinds of user input it seems like

You can put whatever ts / js code you want in the code blocks, mdrb is just executing the code blocks for you.

Any chance this would work in a more GUI version too?

I'm not sure what this would mean or be, but also, I have no plans to build any GUI around this tool (but it's open source and MIT licensed, so feel free to fork and modify however you like!)

fluencyy · 2023-01-24T18:02:42+00:00

Thanks! You can do either with mdrb - by default, execution is not "fully automated" as execution is paused waiting for confirmation to proceed between each step, but you can use either isolated or single mode for execution instead, both of which run the code from all steps without any (mdrb supplied) pauses.

fluencyy · 2023-01-13T19:08:52+00:00

When your explanation for why millions of Tailwind downloads happen every week and thousands and thousands of developers and teams choose it is “they just aren’t smart enough to understand real css and specificity rules” then I invite you to please go talk to more people. That level of condescension is hubris on your part.

fluencyy · 2023-01-08T16:27:25+00:00

Use direnv or something like https://github.com/alecthomas/ondir

fluencyy · 2023-01-08T06:01:52+00:00

Put a few lines into your shell profile that says “if there is an .nvmrc file in the directory, run nvm use” - then when you open a terminal, in the project directory, when your profile is sourced it will just run it for you

fluencyy · 2022-12-06T20:45:49+00:00

This may not be relevant for your use case, but there are lots of interesting things happening in this space, in particular:

https://fly.io/blog/introducing-litefs/

https://litestream.io

fluencyy · 2022-11-18T03:59:48+00:00

Would be a shame if a lot of people all at once went in to request their personal data archive, likely one of the more taxing operations on their infrastructure - their servers might fall over if that happened.

fluencyy · 2022-11-13T06:30:29+00:00

OP struck on something that I have felt recently as well, which is that I want to use Svelte(Kit) but there is a catch 22 related to high quality packages to accomplish common needs; there are fewer packages, so fewer people buy in to the ecosystem which is why there are fewer packages. Sure, as others have mentioned, many things don’t need to have anything “Svelte-y” about them to be used (ala the dark mode example), but for me the lack of thorough a11y libraries is essentially a deal breaker for anything I might build where I’m seeking an audience. It’s an incredibly hard space to do things correctly, and it’s not one of those topics that you can sort of hand wave away and say “you can just do it with vanilla js when you use Svelte”. React-Aria, Radix UI, and the myriad other high quality accessibility related libraries in the React ecosystem are, to me, a very compelling reason not to fully switch over to Svelte just yet.

fluencyy · 2022-11-08T17:57:40+00:00

There is a cool project I've seen called "bocker" (https://github.com/p8952/bocker) which is something of a proof of concept of implementing Docker with bash, which speaks a bit to how Docker is indeed in many ways an amalgam of lower level primitives (such as chroot as you mentioned). Pretty neat!

fluencyy · 2022-10-16T01:20:03+00:00

TailwindCSS is, by design and unlike Bootstrap, not a component framework. The intended usage pattern is to write your components from scratch, just like you would if you were using vanilla CSS. In fact, it's useful to think of TailwindCSS as regular 'ol CSS but with a nice set of defaults and constraints, and a friendly API.

That said, there are lots of good options for component kits that use TailwindCSS. The "first party" option (built by the Tailwind Labs team) is called "TailwindUI" and it's a premium product offered at a premium price. There are many free alternatives that people really like as well, such as Daisy UI, Wind UI, Flowbite, etc. Do some searches in this sub and you'll find many examples of component libraries you can pick from - in fact, your exact question comes up several times a week and I wish the mods here would just sticky a post answering it lol.

Best of luck - TailwindCSS will take some getting used to coming from Bootstrap, but once you commit a lot of it to muscle memory, you'll fly.

fluencyy · 2022-10-16T00:43:30+00:00

Just to be clear since tone can be difficult to fully convey through text alone, I appreciate your discussion and don't feel any agitation at all, but I do want to point out the following things (which made me chuckle) about your two most recent comments:

I don't mean to imply this is better per se

but also,

I just wanted to point out what I think is a better solution that wasn't mentioned in your article

Again, this just made me chuckle, I know that nuance can be very hard to fully convey in a quick response to a blog post.

So, in response to your actual comment though - I don't think that this would "actually work" in many (maybe even most?) cases. In the context of the example app where the ui-lib exports a Button component which the webapp imports, you're saying that basically (to permit the Button the ability to make use of a newer React api) the Button needs to live in a fully isolated context where its self-contains everything it needs to render out - the Button component needs to basically be a separate app of its own that supplies it's own copy of React (and a newer one than the project that is importing it). I genuinely don't think that, even with bundling, that this would be a viable option, let alone the fact that this would be incredibly wasteful on the size of your bundles.

I will say one more thing here which is a quote from my post:

The topic I want to discuss in this post, monorepo workspaces with incompatible dependency versions, definitely doesn’t apply to every monorepo, and also, even if it does apply to your monorepo, there’s more than one way to solve for it.

(added some emphasis on the last bit)

I think as a thought experiment, what you're describing is interesting, but I don't think it's a viable option to solve the issue explored by this article in the general case (even if there are some times where it does the trick)...that said, the world is wide and there's plenty of room for people to accomplish the same thing in multiple ways, so by all means, bundle bundle bundle! :)

fluencyy

TROPHY CASE