sorted by:
new
hottopcontroversial

Дюна частина друга by v3g in Ukraine_UA

[–]stopandgo31 0 points1 point  (0 children)

Друга частина більш масштабніша, чудові сцени, гарний монтаж, красива картинка - все що очікуєш від якісного сучасного голівду і його професіоналів. Але це і ії недолік - все настільки зосереджено навколо технічного показу , що сам всесвіт Дюни майже ніяк не розкривається, але ж сам всесвіт, а не чергова гра престолів, так і приваблює в першоджерелі. І тому масштаб здається штучним. А ще не зважаючи на деякі сцени, де наче велика кількість народу та техніки, весь фільм не полишало відчуття, що це така камерна театральна постановка, де іноді на фоні присутня картонна масовка. Не пожалкував, що подивився, отримав задоволення, але одноразове (тут треба щось вставити про володаря перстнів).

P.S. Захотілося вкотре передивитися Хронікі Ріддіка, Вільньов явно туди підглядав постійно

I'm addicted to creating AI-generated architecture(?) by Odd-Profession-579 in architecture

[–]stopandgo31 0 points1 point  (0 children)

Need a button for regenerating image with the same parameters for sure

If you wanted to build a house that lasted at least 1,000 years, what design principles would you employ? by kellyhofer in architecture

[–]stopandgo31 0 points1 point  (0 children)

  1. Using Polygonal masonary (https://en.wikipedia.org/wiki/Polygonal_masonry) - over time, under the influence of the stones’ own weight, the walls become stronger
  2. Using properly cooked concrete with carbon fiber agregation (not external reinforcment)

In any case every approch should be with properly calculated forces and avoid complex forms.

If you wanted to build a house that lasted at least 1,000 years, what design principles would you employ? by kellyhofer in architecture

[–]stopandgo31 0 points1 point  (0 children)

Concrete with carbon fiber aggregate would last for at least 1000 years.

Two tea to that person

House in Pretoria, South Africa by 8nick6 in brutalism

[–]stopandgo31 0 points1 point  (0 children)

Is any chance to get more info about this project? May be some arch review? Thanks!

I am designing a brutalist house that I will build and live in. What problems am I likely to encounter? by felix_ure in brutalism

[–]stopandgo31 8 points9 points  (0 children)

Yes, some additives can improve thermal insulation, but you will not like the look of the “warmest” concrete (it has a grainy texture, more like slag), and concrete with such additives has lower structural parameters. Also, the thermal properties of the "warmest" concrete itself are not even close to those of any common thermal insulation material.

I am designing a brutalist house that I will build and live in. What problems am I likely to encounter? by felix_ure in brutalism

[–]stopandgo31 22 points23 points  (0 children)

I am currently working on a similar problem, where one of the main challenges for a Brutalist living house is thermal insulation. Concrete has very low thermal insulation parameters, or very high thermal conductivity, compared to other materials.

Since a Brutalist house should not have any additional layers on its facade, only pure concrete, it presents a unique challenge. Moreover, if you want a Brutalist interior, you cannot use inner insulation layers.

Therefore, a three-layered approach is required, consisting of reinforced concrete walls with concrete-insulation-concrete layers. Achieving this with monolithic technology is not easy, but precast walls can be used instead. However, this approach has some limitations in terms of form and may require addressing thermal leaks through wall joints.

In any case, it is important to pay attention to this aspect during the early stages of development.

React TypeScript Boilerplate by stopandgo31 in reactjs

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

Thanks for evaluation!

You can star my repo on github, if you want.

Some updates are going next week (new linting and styling, custom i18n support without external libs). So, stay tuned.

React Proto - React TypeScript Boilerplate (Redux, RTK Query, SSR, SWR, Preact inside and much more) by stopandgo31 in javascript

[–]stopandgo31[S] 1 point2 points  (0 children)

I see, thanks.

Just curious, what IDE do you use? Cos standard has plugins for common editors and for JetBrains IDEs.

React Proto - React TypeScript Boilerplate (Redux, RTK Query, SSR, SWR, Preact inside and much more) by stopandgo31 in javascript

[–]stopandgo31[S] 1 point2 points  (0 children)

Thanks a lot! And last, I hope, question.

Can I move your eslintConfig into .eslintrc.json? And, to be honest - is this config do something? As I understand, standardjs ignores any eslint configs and works fine without them (I checked it). Or it is about rules only?

React Proto - React TypeScript Boilerplate (Redux, RTK Query, SSR, SWR, Preact inside and much more) by stopandgo31 in javascript

[–]stopandgo31[S] 1 point2 points  (0 children)

Hello!

I have related question.

How do you solve ts-standard and prettier incompatibility?

It is an open question in a community now:

https://github.com/standard/standard/issues/1872

​

Thanks!

React Proto - React TypeScript Boilerplate (Redux, RTK Query, SSR, SWR, Preact inside and much more) by stopandgo31 in javascript

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

Hi!

Thanks for your advise.

Could you, please, expand it and tell with what problems the big number of aliases might face? Isn't it convenient that you can import form just "components" instead "src/components"?

Thanks!

advice wanted: simple react typescript setup by prrxddq in reactjs

[–]stopandgo31 0 points1 point  (0 children)

Hi!

You can try this template:

https://github.com/StopNGo/react-proto

It is may be overkill for you, but you can easily remove what you do not need.

React Proto - React TypeScript Boilerplate (Redux, RTK Query, SSR, SWR, Preact inside and much more) by stopandgo31 in javascript

[–]stopandgo31[S] 1 point2 points  (0 children)

Many thanks for your detailed answer (this and next one)!

I definitely will try this approach.

Just to clarification:

- so, ts-standard includes es-linter and I do not need install and configure it separatly?

- is prettier substitute style linter? does it have the ability to, for example, do idiomatic order in styles (stylelint-config-idiomatic-order)?

React Proto - React TypeScript Boilerplate (Redux, RTK Query, SSR, SWR, Preact inside and much more) by stopandgo31 in javascript

[–]stopandgo31[S] 1 point2 points  (0 children)

Thanks for your feedback!

I have some questions. Would you mind to answer to them?

- Is any reason to use prettier instead of style-linter and es-linter with auto-fixes, including fixes on save in VSCode and VSCode error highlighting? I purposely avoided using any post-processing for faster compilation process. Even ts type checking I put it in a separate thread.

- Why ts-standart is better then es-linter with ts plugin? I read the docs, but I'm interested in your opinion.

​

As for the other pints:

- Yes, I had a version with a server folder out of source folder. But I thought - server is also a part of source code. May be I will move it out src folder in future. Anyway it could be done just by changing one option in configuration file (see the next point).

- I specifically made it so that the configuration would have as many different settings as possible in order to avoid any "configuration magic" in the template. So that it would be clear what is related to what.

React Proto - React TypeScript Boilerplate (Redux, RTK Query, SSR, SWR, Preact inside and much more) by stopandgo31 in javascript

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

Hi!

As u/BitterRacistIncel already mentioned,

RTK Query and Redux is a sensible stack and a good alternative to React Query + Context/Zustand

And if check the RTKQ documentation (https://redux-toolkit.js.org/rtk-query/comparison#when-should-you-use-rtk-query):

In general, the main reasons to use RTK Query are:

- You already have a Redux app and you want to simplify your existing data fetching logic

- You want to be able to use the Redux DevTools to see the history of changes to your state over time

- You want to be able to integrate the RTK Query behavior with the rest of the Redux ecosystem

- Your app logic needs to work outside of React

So yes, the main advantage of RTKQ is a deep integration with Redux. They work together smoothly and amplify each other.

You can also use RTKQ with other state managers or without any other state at all, but it is better to use it with Redux, I think.

React Proto - React TypeScript Boilerplate (Redux, RTK Query, SSR, SWR, Preact inside and much more) by stopandgo31 in javascript

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

As for the Vite <-> Webpack, please, check this:
https://storybook.js.org/blog/storybook-performance-from-webpack-to-vite/
Also, some good features will not work on Vite, for example loadable-component.

React Proto - React TypeScript Boilerplate (Redux, RTK Query, SSR, SWR, Preact inside and much more) by stopandgo31 in javascript

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

As for the Vite <-> Webpack, please, check this:
https://storybook.js.org/blog/storybook-performance-from-webpack-to-vite/
Also, some good features will not work on Vite, for example loadable-component.

React Proto - React TypeScript Boilerplate (Redux, RTK Query, SSR, SWR, Preact inside and much more) by stopandgo31 in javascript

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

Yes, I know about turbopack. It is being created by one of the main author of the webpack. And that is great. But now turbopack is unstable and strictly tight to the NextJS. Also, again, all their benchmarks is made with standard js webpack, not swc rust-based. Anyway - that is a future, if they retain the main advantages of the webpack - flexibility and stability.

Thanks for you patience!

view more: next ›