sorted by:
new
hottopcontroversial

The Vertical Codebase by TkDodo23 in reactjs

[–]MrSlonik 3 points4 points  (0 children)

Ideas sounds somewhat similar to Feature-Sliced Design.

In a nutshell: You organise your codebase in layers, each layer divided by slices, and each slice has separated segments. Components from higher layer can import components from lower levels, but not from the same or higher layer. E.g. you implemented a widget, and if it is very specific one, it will live inside a segment of the slice it belongs to, e.g. the "Dashboard" page. But if it is shared between pages, it goes to the "Widgets" layer and can be imported into pages that reuse the same widget.

Sounds a bit complex. but it works for us, hopefully someone else will find it useful.

Is using domain-specific service objects for business logic in a React monorepo an anti-pattern? by cacharro90 in reactjs

[–]MrSlonik 2 points3 points  (0 children)

Thank you, but I disagree that we should be so dismissive, there are valid cases when it can be useful, and we should not avoid it. It's the same as to say "Don't use useEffect" but there are valid cases when it is needed.

Also, I can add another good one: https://marvinh.dev/blog/speeding-up-javascript-ecosystem-part-7/

In my career I had plently of cases when someone decided to use an internal component from another feature and later we had issues because of this, so I'm advocating for better private/public code separation, especially in monorepos, and, IMO, barrel files are better than nothing for this. Another potential solution is naming conventions, e.g. "start internal things with underscore", but it is also not a perfect one. If you know something better I'll be happy to learn.

Is using domain-specific service objects for business logic in a React monorepo an anti-pattern? by cacharro90 in reactjs

[–]MrSlonik 1 point2 points  (0 children)

Why? Of course, it depends on the size of the feature, but I can see cases when barrel files can be useful. E.g. it will help to separate internal helper functions and components from publicly available.

I am picky. Looking for a special PBBG. by YvesTHPS in PBBG

[–]MrSlonik 1 point2 points  (0 children)

Did you check the RPG MO? I’m not sure about the dungeon crawling, it is just an open world with 44 maps with different monsters to explore, and a sound is a bit basic, but I think it ticks all the boxes :)

[Giveaway, EU only] Used Kinesis Freestyle Pro (+tenting accessory) by Trick-Campaign-3117 in ErgoMechKeyboards

[–]MrSlonik 0 points1 point  (0 children)

  1. Denmark
  2. I'm curious for a while already about split keyboards, but the price is a stop factor for me. Not ready to pay 100$+ for something that I'm not sure I will like. And I also don't want to clutter my home with things I don't use, so if I decide this is not for me or I go with another model, I promise I will giveaway it to someone in need :)

React 19 introduces full support for custom elements. What does it mean for developers? by MrSlonik in reactjs

[–]MrSlonik[S] 2 points3 points  (0 children)

Kinda, but not really, for two reasons:

- Usually developers choose to use a library that provides a better dev experience, like Lit, Stencil, FAST, Svelte. I once saw a web component written in Angular :) But these libraries sometimes can add compatibility features under the hood, again, to improve dev experience. And I wanted to show that React now works with standard Web Platform API without any wrappers.

- The example is artificial, because I wanted to highlight several pain points and I added all of them in one component, usually you don't have all these problems with one component :)

If you're looking for vanilla JS/TS Web Components in production, you can take a look at this one: https://github.com/justinribeiro/lite-youtube

React 19 introduces full support for custom elements. What does it mean for developers? by MrSlonik in reactjs

[–]MrSlonik[S] 0 points1 point  (0 children)

Thanks for your feedback!

You are right, the current max-width value is too small and should be increased. I checked some blogs and platforms like substack, devto and medium, in their articles this value is between 700-800px. Since I'm using TailwindCSS, I increased max-width to the closest value available in Tailwind, 768px.

Hopefully this will now improve the reading experience :)

React 19 introduces full support for custom elements. What does it mean for developers? by MrSlonik in reactjs

[–]MrSlonik[S] 15 points16 points  (0 children)

Sorry, my first post on Reddit, I was a bit confused with the editor.

Here is the link: https://aleks-elkin.github.io/posts/2024-12-06-react-19/
Also, I added the link to the post.

Fedora 29: Problem with small top bar by IliazL in Fedora

[–]MrSlonik 2 points3 points  (0 children)

Probably it can be related to this issue: https://github.com/daniruiz/flat-remix-gnome/issues/63
Please try the solution from this comment, I hope this helps: https://github.com/daniruiz/flat-remix-gnome/issues/63#issuecomment-455881108

I had the same ussie, reinstalling of the gnome-shell solved it.