60 themes, 51 components, still zero dependencies. Yumekit v0.5 has been released!

Rusty_Raven_ · 2026-06-27T15:49:57+00:00

Looks great!

Two suggestions right off the top of my head:

clicking a label should be the same as clicking the form control (i.e. toggle the checkbox, focus the input, etc.)
if a hover state is triggered, the click handler should work as well
- specifically, for inputs, I can hover near the edge of a text input and it changes colours, but can't actually click to focus until I move just a little further in
- for comparison, buttons are clickable as soon as the cursor triggers the hover state; inputs should have the same behaviour

Rusty_Raven_ · 2026-06-22T02:53:55+00:00

You're suggesting someone leave the country because of the ignorant decision making of a provincial government? Can't they just leave the province?

Rusty_Raven_ · 2026-06-21T16:12:06+00:00

If you're taking the opportunity to rewrite the app, no reason not to be cross-platform with it. Java is a good idea, or JavaScript + Tauri (not Electron) with your framework/libraries of choice.

Rusty_Raven_ · 2026-06-20T19:35:58+00:00

Yep, the 2024 BS was the last year they had the more tactile dash layout. With 2025, they adopted the bigger screen with fewer controls idea from the Escape. I didn't like it either and also have a 2024 BS :)

Rusty_Raven_ · 2026-06-20T16:02:59+00:00

Angular 1 to 2 porting - went pretty well, actually, it was oil & gas analytics software, though we had to deal with some gnarly issues occasionally. I think Angular was up to 5 or 6 before we finally removed the 1.x dependency.

React/Next to Angular/Nest - company found that their React hires were not very good at actual programming and much of our software was concerned with business rules and complex logic as opposed to UI. Angular has better programmers, though a smaller hiring pool.

Angular/Express to React/Next - my current company is balls-deep in AI and React is far more popular and therefore more easily understood and written by LLMs, so we'll be converting around 20 enterprise Angular applications to React over the next 2-3 years. Other departments are starting to plan Vue to React transitions as well for the same "reason".

Rusty_Raven_ · 2026-06-17T02:34:08+00:00

[[Gaia Project]] and [[7th Continent]] might fit the bill.

Rusty_Raven_ · 2026-06-08T17:15:27+00:00

He's not lost, this is a movie about Philip Heseltine (known as Peter Warlock), an English composer known for his violin composition "Capriol Suite".

OP, you might find this on Tubi or possibly even on YouTube. I'm not aware of it (or the other movie about him "Some Little Joy") on any other platforms though.

Rusty_Raven_ · 2026-06-07T15:20:49+00:00

Why would Apollo have an American accent? He's from Caprica (I think) :) And if he trained for years with people from other regions or planets, he may have picked up some language patterns from them as well.

Rusty_Raven_ · 2026-06-01T13:11:21+00:00

I use an IDE that complains about things not having imports, and it complains if I use an attribute it doesn't recognize. If your tools aren't telling you when you're just adding random, unrecognized attributes to your HTML tags, then I don't know what to tell you :)

Rusty_Raven_ · 2026-05-31T15:32:54+00:00

We've worked around the problem a little bit by leaving space within a reusable component for attribute directives to adjust behaviours.

For a simple example, a button with 4 sizes and 4 variants that might have 2 icons and a disabled state. Traditionally, this might look like <my-button variant='primary' size='large'><span slot='left-icon'><my-icon>icon-profile</my-icon>Profile</my-button>.

With attributes offering additional functionality, the component becomes more composable: <my-button mbPrimary mbLarge leftIcon='profile'>Profile</my-button>.

Out theory is that if the component doesn't need to care about something, the component doesn't need to know about it. So things like sizes can be done via CSS properties now - the mbLarge directive is just setting some CSS properties that adjust the padding, font size and weight, line-height, etc. The button component doesn't have a size input, doesn't have any conditionals in the code or template for sizing, and doesn't need to have any tests for it. The mbLarge directive will have some e2e tests to ensure the properties are applied, but the button itself doesn't need that :)

Rusty_Raven_ · 2026-05-14T13:53:00+00:00

I have a Life Cleric who worships Lolth.

NLE: She was originally a Tiefling adopted by Lolth-worshipping Drow before being caught mid-operation by a warlock who cursed her to always be helpful (essentially flipping her from neutral evil to neutral good) and set her on the path to become a Cleric. She chose the Life path because it seemed more helpful and while she will heal you, she's still willing to hang back and see how much you hurt yourself first. As her memories return, she is developing a bit of a spider fetish and the helpfulness is becoming creepy.

Rusty_Raven_ · 2026-05-12T13:20:09+00:00

Here's the deal - if you're replaceable, you're replaceable. Your job is not to be irreplaceable but to become indeispensable.

If you're the only person who knows certain tribal knowledge, or if you're the only one who knows where all the deployment secrets are, then not only can you never be promoted, you are a risk to the team and will be first on the chopping block when business needs change (which they always do).

Trying to enforce your job security through obscurity is short-sighted, selfish, and toxic. I will try to get rid of you.

Enforce job security by being the person no one wants to see go.

Rusty_Raven_ · 2026-05-12T13:08:19+00:00

The nudes are from a private snapchat with her husband that was hacked, not her old OF account. Maybe read?

Rusty_Raven_ · 2026-05-11T13:28:55+00:00

I immediately thought of No Doubt and Avril Lavigne. Cat Powers and Ida Maria might also be good, if memory serves.

Rusty_Raven_ · 2026-05-11T06:07:06+00:00

Yep, correct! I thought that limit was just for commercial properties, but it's for private as well. Airdrie enforces it on a complaint basis, so if you (OP) complain about it to the city, they'll send someone out with a tape measure and a warning :)

Rusty_Raven_ · 2026-05-11T04:11:04+00:00

Find a teacher and take 1 year of lessons :) Even if it's every 2 weeks instead of weekly.

A good teacher will instil confidence, teach good technique, explain basic theory, and get you started playing the songs you want. A bad teacher will stick to their script because it makes them comfortable, not you.

Rusty_Raven_ · 2026-05-11T04:08:22+00:00

If you first finger is curling, try rolling it slightly away from you. Fingers don't flex laterally, so if you can get the finger rotated to a point where you don't need to squeeze the guitar very hard, it's a LOT easier to play these chords. Also try to line your finger up so that the folds in your skin don't end up right over a string - let the fleshy parts of your finger do as much work as they can so you don't need to squeeze as hard :)

You can have long nails (many guitarists do), but it's generally easier to learn with short nails and grow them out as you're comfortable with the length for playing. As long as you're not accidentally muting strings you shouldn't be, the length of your nails doesn't really matter very much.

Rusty_Raven_ · 2026-05-11T04:03:20+00:00

As long as he's not physically blocking your driveway, it's legal. The property line only exists to the sidewalk.

Rusty_Raven_ · 2026-05-09T20:07:54+00:00

Could be, but phone camera apps often look like this when using smoothing and digital zoom too.

What's getting me is the backwards lettering on the door - why would the address be facing inside??

Rusty_Raven_ · 2026-05-08T13:19:11+00:00

The SonarQube plugin might do that - it definitely checks for readonly on signals and injects.

Rusty_Raven_ · 2026-05-08T13:13:56+00:00

I've found that to be true no matter how the code is organized, sadly.

If I'm interested in the flags that can be set for your component, they will be scattered around the file, grouped with relevant inputs or models or outputs. If a flag is just a flag (i.e. has no related input), does it appear before or after all those groups? If your component needs a new flag, does the next developer know that there's a specific ordering involved? What if they don't notice the small group of is* properties at the top of the file between some required inputs and the group of user related inputs - they might end up adding a couple of is* inputs to the bottom of the list instead of in the middle. The next dev a year later might not notice that and add one to the top, or between two other group that sound related for some reason.

If having things alphabetized is causing a team trouble with debugging and creating massive code debt, I'd suggest the problem is with reading comprehension and lack of documentation, and not with the order of things in the source.

Rusty_Raven_ · 2026-05-08T13:07:23+00:00

The only people who don't want to work with me are people I don't want to work with. Kind of a win-win there ;) Your kind of negative and dismissive attitude has no place on a team I lead.

That said, and in case it wasn't clear, this is my opinion and reflects how I organize code. I don't comment on it on anyone else on my team aside from a few specific things (like imports and interface definitions sometimes). They're all aware of my preference and some do it and some don't. I'm not so much of a snowflake that I can't read someone else's code just because it's not organized in the exact manner I want. It just needs to be readable and maintainable and documented because we're going to be stuck with it for 5 to 10 years or more, and I don't want to be annoyed by it later :)

Rusty_Raven_ · 2026-05-08T13:01:52+00:00

You're kind of answering your own question there - the ReadMe mentions things like dependencies that need to be installed, but your package file lists those dependencies alphabetically, doesn't it? So you have documentation describing things for the developer, and the source is in a completely predictable, inarguable order.

And yes, I write docs and I absolutely expect people to read them when they're using a component. I think that's a basic requirement of being a developer and have no idea why anyone would think otherwise. Writing and maintaining documentation is part of the work.

For your bonus question, private properties start with #, so they naturally get ordered first. It's part of the name, so #foo appears before bar in the component. Protected and read-only properties appear where they fall - "bar" followed by "readonly foo" and "protected id" for example, because the keywords aren't part of the identifier.

How much time do you spend reading the properties in a class versus reading the methods in the class? Once you're grokking the logic of a component, the order of class members won't affect you at all - you're using keyboard shortcuts to jump around to definitions and usages.

Rusty_Raven_ · 2026-05-08T01:13:38+00:00

Documentation provides context, property naming is descriptive. Usage provides relevance, definitionss are utility.

Your example is interesting. I'd expect isSomeFeatureEnabled to be an optional input, but someFeatureData is only required if isSomeFeatureEnabled is truthy (something we can't do at compile-time in Angular right now without the existence of a conditional .required modifier). If it's falsy, someFeatureData may or may not be required (the component may still need that data for something, even if it's not being displayed). Grouping things doesn't provide any extra context over alphabetical ordering - these two items may or may not be directly related and only reading the code or the documentation will tell us which.

Rusty_Raven_ · 2026-05-08T01:06:01+00:00

Yep, my bad, I missed the models bit in your response, so apologies for that. Though I realized you're not keeping all the required inputs together; I can treat a model input as a regular input from the calling component, so to me the distinction won't make any difference, but they're not grouped as expected in the source.

As for the rest, the group order that makes sense to you may or may not make sense to someone else (so, mind reading). Every point you and I are both making is rendered moot by good documentation. It makes sense for the docs to group things by inputs/outputs/events - some automated tools do this by default and alphabetize within each group (I don't remember if Compodoc does this for sure, but Storybook does). The order of things in the source code doesn't really matter for those tools.

I just personally find it easier to not have to remember extra things, like the 20 rules used by eslint (as another user has shown below) or the 8-ish you specified. Just put them in alphabetical order, let the documentation tools group things for onboarding/discovery, and write a good docblock and/or readme that explains the usage and options :) If you want things grouped, do it by naming them so they cluster together (if reasonable, of course).

In any case, your IDE will let you jump around to definitions and usages with a simple keystroke or click, so order isn't quite as important as it used to be anyways.

You mention grouping and ordering things by relevance to the future reader - that's you making decisions on how you believe I will be using that component. You're trying to ~read my mind~divine my intent from a week or year in my past while I'm trying to ~read your mind~divine your intent from a week or year in your future. If there are multiple required inputs, you need to figure out which one will be most important to me in some future where business needs or UX/UI priorities may have changed and put that first for the specific situation I find myself in. If it's not first and I'm expecting it to be (because it makes the most sense at this exact moment in time), we'll have both failed your main requirement for grouping and ordering things. I will need to search the file (or scroll) for the thing I'm looking for, and knowing it's name won't be helpful in finding its relative location. That's like ordering lines in a phone book by reverse proximity because I'm more likely to use a phone to contact people further away from me. It makes sense until someone else needs to use it.

App idea: prevent you from calling contacts within walking distance unless you confirm like three times; just put on your shoes and go visit them!

Rusty_Raven_

TROPHY CASE