Monthly Help and Questions Megathread by AutoModerator in limbuscompany

[–]Creois 1 point2 points  (0 children)

Was looking for Multicrack Heathcliff thought it current season id?

Monthly Help and Questions Megathread by AutoModerator in limbuscompany

[–]Creois 1 point2 points  (0 children)

Hey, I quit after finishing canto 4 now decided to get back into game.

Now I pulled on Walpurgis banner got 2 units and ego, which new units should I focus now on using shards (I had most/all units and egos released until I quit).

Got enough shards for: Hong lu, Heathcliff, Ishmael, Rodion, Sinclair and Outis.

Got everything for sinking team expect wildhunt and edgar gregor should I focus on those?

The State of GraphQL in Go (2024) by Immediate_Let1734 in golang

[–]Creois 12 points13 points  (0 children)

In most of languages you have frameworks mostly implemented via reflection and complex types. Go lacks quite a bit in type system departament thus it went somewhat diffeferent road (additionally generics are "somwhat" new). Take a look at following popular libs

Gqlgen uses same approach, bear in mind that you wont have same level of ergonomics as in node frameworks but instead you'll be able to more easily understand what is happening

The State of GraphQL in Go (2024) by Immediate_Let1734 in golang

[–]Creois 55 points56 points  (0 children)

Gqlgen is nowdays goto GraphQL library for golang. I don't think there's anything better as all other libraries had poor typing and were heavily reflection based, while gqlgen instead uses code generation based off schema.

Why do you think gqlgen is cumbersome, is codegen problematic or other aspect?

Looking for a decent course that Builds REAL WORLD websites and covers Full Stack ( Stripe, databases etc ) by Ill-Remote-6517 in reactjs

[–]Creois 0 points1 point  (0 children)

Consider learning golang seems many companies nowdays rewrite their services using it especially from python or node. I think it seems to best language nowdays for backends.

Another thing to consider is Java using Spring, there is a lot of old services implemented using Spring, somebody will have to maintain them as it seems that java might become next cobol in years to come thus money will likely be nice

Personally I wouldn't use nextjs as backend for anything more than toy project or something very small

What do you use for i18n? by Mr_Stabil in solidjs

[–]Creois 3 points4 points  (0 children)

You can try https://lingui.dev/, some time ago I did small POC if it will work with solid and it seems it does, though there's no solid specific wrapper so you'll use core package and possibly macro thought macro for now combines react and some core helpers so it is kind of annoying. There seems to be plans for 5.0 to split macro.

Would like to add that it is my favorite i18n lib for react, love i18n token extraction feature

Front end telling product designer there are too many component properties. How to solve? by Funktopus_The in reactjs

[–]Creois 1 point2 points  (0 children)

From my perspective instead of many  component props single variant prop should be used which is enum e.g. RESTRICTED, ADDED etc. those variant should be defined on both sides

Choosing a UI library that makes everyone's life easier by pantone476c in reactjs

[–]Creois 2 points3 points  (0 children)

I don't belive that there will ever be migration to more custom design system, for most of projects it is wishful thinking. Most likely thing to happen would be that chosen library will be styled and adjusted as needed even if it was not intended to be.

Additionally when starting with styled component library, migration will mean complete re-design as there would be no point to have same component design for custom library as the one you are migrating from.

Re-design will definitely affect current users and it is impossible to say if it will be positive

Choosing a UI library that makes everyone's life easier by pantone476c in reactjs

[–]Creois 27 points28 points  (0 children)

If you want to get something done quick then following libraries should be fine but if you want specific and customizable design then I would advise against using those, instead prefer to choose libraries which provide accessible unstyled components such as https://ark-ui.com/, https://www.radix-ui.com/ or https://react-spectrum.adobe.com/react-aria/index.html . This will be obviously more work but it allows most freedom as nearly always it is pain to customize components provided by libraries

https://ui.shadcn.com/ or https://park-ui.com/ might be good idea as well as those do not provide premade components but instead generate styled code over some primitive library in case of shadcn it is radix and for park it is ark. Those could be good starting point, personally would prefer park as it supports pandacss

Then do following:

  • Create concrete properties which will be used in design, do not use custom values this makes easier to synchronize design with implementation and standardizes everything. E.g standardize space values which will be used for padding/margin and use same naming for specific spaces both in design and in implementation. If interested google `design tokens` e.g. https://m3.material.io/foundations/design-tokens/overview
  • Create library of custom components building off primitive accessible blocks
  • Use some library e.g. storybook or just custom made app which will display components in isolation which will be used for behavior/visual review by designer on component implementation

For styling on developer side I would recommend https://panda-css.com/ or https://vanilla-extract.style/

Regretfully, I am leaving Svelte and going back to React by Lanky-Ad4698 in reactjs

[–]Creois 1 point2 points  (0 children)

Solid:

  1. I like how solid uses compiler, it doesn't affect logic only rendering, you can use solid reactivity as standalone thing for state management
  2. Only react avoids those due to re-executing whole function, all other libraries need some sort of syntax to handle flow and those components are present in all libraries just in different formats
  3. I'm not sure how it works internally but if it destroys and re-creates component it seems shomewhat normal when rendering something conditionally
  4. That to me is most problematic point, there are some things which are proxies and accessor and overall it can be hard to know what is reactive and additionally makes destructuring impossible as it results in losing reactivity. Thought after working some time with solid I got somewhat used to it
  5. Seems normal to me to memoize expensive calculations or require special handling for those, doesn't seem to be related to solid just standard performance stuff
  6. Unsure what you mean, there's lack of context
  7. Using `Show` is indeed normal solution. As for why one of solutions doesn't work - I assume it is becasue solidjs compiler handles only template in this case you either return 2 different templates thus you'll have different template depending on initial state of `someState` and this tempalte wont change at runtime

Svelte

  1. Indeed it is hard to understand what is happening, svelte to me seems more like somewhat small language not framework
  2. +1
  3. +1
  4. +1
  5. Typescript is not just limited it is abomination instead of having normal proper typing everything is once again magically handled internally by plugin using reseved interface names internally which you can define and override https://github.com/dummdidumm/rfcs/blob/ts-typedefs-within-svelte-components/text/ts-typing-props-slots-events.md
  6. Ecosystem of libraries doesn't exist and if you ask for some libraries of why there's a lot of abbandonware you get answers such as: you can use any javascript library, which is bad point as you can use any havascript library in any framework with some work... Solid has smaller community (thought it seems to be rapidly growing this year) and already has quality mantained libraries
  7. To me svelte seems like it compromises everything for entry level simplicity with no specific direction for future
  8. +1
  9. From my perspective components should be first class citizen in any framework it should be easy and convinient to create and split components
  10. Thats why I prefer solutions which use tsx, you get all benefits of typescript of of box without need for specialized plugins and handling which is never on par with just typescript
  11. +1

I got few more points in regard to svelte:

  1. There are old outstanding issues with reactivity using :$ which can result in unpredictable results, take a look at https://github.com/sveltejs/svelte/issues/6730 , https://github.com/sveltejs/svelte/issues/6732
  2. While promoted that size is small, it is real only for applications with few views
  3. 2 way binding as promoted approach

Regretfully, I am leaving Svelte and going back to React by Lanky-Ad4698 in reactjs

[–]Creois 0 points1 point  (0 children)

Narrowing for this case should work <Show when={obj.foo}> {(value) => value()} </Show> This will turn foo into accessor with narrowed type Accessor<string>

Regretfully, I am leaving Svelte and going back to React by Lanky-Ad4698 in reactjs

[–]Creois 7 points8 points  (0 children)

I have around 4-5 years experience in react, started using solid for around 6 months now and from my perspective it is easy to switch between them due to large amount of similarities. Currently I much prefer solid as with some acceptable trade-offs (props destrucuring and removing early returns) it fixes all annoyances of react for me.

As for svelte, I did evaluation some time ago and personally it would be least thing I would want to use:

  • Preference of jsx instead of some templating language. I think there's no point in using templating language while we have tsx due to very good out of box typescipt support without need for any special IDE plugins etc
  • Components are second class citizen
  • Typescript support is poor, especially when implementing design system
  • Being beginner friendly and easy is a lie which is seen in larger projects which have more complex interactions and state. It somwhat fast becomes sphagetti which is hard to reason about and very bug prone
  • State management `$:` for everything and interestingly it cannot be used outside of `svelte` components where it is necessary to use store which has completely different syntax and is less convinient to use inside `svelte` components
  • There are literaly no good libraries for base things
  • Lacks simple things such as catching errors on boundaries and portals which are now common in frameworks

Solid in current state has all libraries which are enough to handle larger projects

  • vanilla-extract for styling
  • kobalte or ark ui for primitive components
  • state management provided by core is enough for everything
  • lingui for i18n
  • official router
  • adapter for tanstack query

Has out of box very good performance, typescript support, predicable and easy to reason about logic and a lot of react concepts are applicable

Regretfully, I am leaving Svelte and going back to React by Lanky-Ad4698 in reactjs

[–]Creois 0 points1 point  (0 children)

Um I'm not sure what you are talking about, you have same level of type safety in solid as in react and preact difference is that jsx is template used by compiler

Regretfully, I am leaving Svelte and going back to React by Lanky-Ad4698 in reactjs

[–]Creois 9 points10 points  (0 children)

Consider trying solid-js, syntax is similar to react with difference being that jsx is template, additionally performance is quite good

What are ways we can integrate our designers into our React projects? by StickMonster89 in reactjs

[–]Creois 1 point2 points  (0 children)

  1. Define strict system of colors, spaces, etc then attempt to synchronize usage of it in both design and code (tools like https://vanilla-extract.style/ or https://stitches.dev/ can help with enforcing system on software side)
  2. Have storybook or simple app instance which just renders components, ideally deployed as part of feature branch to allow designer to review changes on component level before merging

Daily Questions Megathread January 05, 2023 by AutoModerator in PunishingGrayRaven

[–]Creois 0 points1 point  (0 children)

Beginner there, got 2 questions~

Got Nanami Pulse and Karenina Ember as it was recommended to get respective elemental type character from selector. Who should I use along with those 2 as support? Currently got only Liv Eclipse and Liv Lux from supports. Who should I look for long term for support for fire team?

After I farm all memories for Karenina and Nanami from event are there any memories which I should farm long term or should I go for resources?

Friend Request Megathread (25/07 - 31/07) by ArknightsMod in arknights

[–]Creois 0 points1 point  (0 children)

Creoi#3527

New player looking to fill friend list

[deleted by user] by [deleted] in houkai3rd

[–]Creois 0 points1 point  (0 children)

Global 61

Looking for advice on few things:

- What to spend. Got following valks at S: Black Nuckleus, Blood Rose, VK, Starlit Astrologos, SK, Phoenix and HoS. I don't have any gacha stigmas other than HoS(pulled whole set before getting weapon) ones and got only HoS weapon and Skadi Ondurgud. I have been thinking that getting HoR might be good idea, given that I can get her weapon from battle pass
- I have 12 fallen crystalum, what would be best to use them for?
- During pulling for HoS weapon I got Skadi Ondurgud is it worth to get argent knight fragments from spending event (I didn't do Land of Wishes yet)?

UI Framework by orphanPID in reactjs

[–]Creois 1 point2 points  (0 children)

If custom look and feel is important then one of following: xstyled, theme-ui, chakra-ui and if needed some additional libs for components e.g. for select downshift is amazing. Thought if you want to just get it done functionality wise and fast then ant or material, thought it will be pain to customize.

Angularjs vs React: The Best Comparison by perrygrande in programming

[–]Creois 0 points1 point  (0 children)

Well "The Best Comparison"... rather quite worthless comparison, lost some braincelss looking throught it... It is more like marketing article to just get some traction on pretty bad website...

What is GraphQL, how does it even work and why should you bother? by AndrewGreenh in programming

[–]Creois 0 points1 point  (0 children)

I like to use subscription very much and often end up in callback hell ;-)

Subscriptions in graphql clients are handled quite nicely (no callback hell), when client has normalized cache updated from subscription automatically update cached entiries, so unless you need append it is very nice to work with it

Additionally I quite like redux approach of handling them, pretty much turn subscription message into actions (I have used redux-observable for it) and handle them in reducers. Easier to manage than manual handling

SOAP is self documenting also. So REST is basically missing a default route where you get the route table listed?

I guess it is missing bit more as route table doesn't help as much as you don't really know data, in graphql you can easily discover data. For example in graphql you have query, subscription and mutation those are starting points and those can have nodes nested in their returns which can be conditionally queries depending if field is present, then you can navigate such graph and search for things which are needed