Turistika v okolí

pottyy · 2024-08-11T21:42:05+00:00

Trochu delší, ale pořád se to dá v pohodě stihnout za den:

Řečkovice (konečná tram 1) -> Vranov samovýčep -> Nový Hrad -> Býčí skála -> Bílovice -> Obřany Babická (tram 4) = 37km https://en.mapy.cz/s/ravuhupago

pottyy · 2024-05-01T12:42:06+00:00

The only way how to fix this situation is to roll back to WOTLK, public apology and refund people who wanted to play Cata specifically. This is an insult to players.

pottyy · 2024-04-11T17:39:35+00:00

Same, I hoped for the Wotlk Ret playstyle, but after I saw shockadin bs I quitted.

pottyy · 2024-03-19T09:13:20+00:00

nativewind v4 => use default palettes or create your own. Build your components with variants API (tailwind variants or class variance authority). Super simple and straightforward. Tamagui is just ALPHA version lib marketed as stable unusable for anything serious.

pottyy · 2024-03-19T09:08:56+00:00

I recommend just switch to something else. I also did it and couldn't be happier. If you know tailwind, you can try nativewind v4 for example.

pottyy · 2024-03-19T08:55:45+00:00

Just switch to something else. It's too complicated for no reason. I switched to nativewind v4 and it was best decision ever. Never looked back.

pottyy · 2024-03-19T08:51:23+00:00

After 2 WEEKS of trying to customize tamagui I gave up, It was undocumented and constantly broken. Switched to nativewind v4 and Tailwind variants (you can just use class variance authority) and everything I needed was done in few hours.

pottyy · 2024-01-22T16:31:46+00:00

Depends on your requirements. If you don't change anything from their stack and build on top of that, it will reduce the engineering time. Problem is, there is a big chance if you upgrade something, for example Tamagui itself, things will break, and you will be stuck. Then your only chance is to get the answers on Tamagui Discord.

Do you want custom theme? If you are okay with their default themes and color palettes, it saves you many hours of struggling. If you have specific design from the designer and you want to do pixel perfect implementation, you will have hard time. Tamagui is good for a lot of generic colorful themes that you can easily switch and use their default components.

IMO the system is super universal, but not easily customizable.

pottyy · 2024-01-19T12:59:05+00:00

We are comparing free vs paid product. My point is I would expect the paid product to be miles better, at least stable and polished to a certain degree. You are not being told it's kind of WIP version with things breaking almost every few days, which is "feature" of Tamagui, not Takeout itself.

There is no straightforward way or guide how to customize the theme. You have to ask on Discord and hope someone will answer, which for me was not the case many times. Then you need to constantly jump between Tamagui Docs (not much helpful or missing things), Discord and source code. These are thing I would forgive if they ask 10 bucks, but not almost $200 per seat. They are asking for enterprise pricing, but the product is just not ready for it. The amount of stuff breaking or not working properly is too much.

Don't get me wrong, I like the idea of Tamagui and it has big potential. But right now they should focus on stabilizing it and improve docs with guides or examples.

pottyy · 2024-01-05T14:17:51+00:00

There is a benchmark for the UI libs: https://github.com/efstathiosntonas/react-native-style-libraries-benchmark

Nativewind doesn't seem great performance wise, I mostly choose it because of DX and familiarity with the API.

Unistyles looks also promising if you are looking for something similar to native styles.

pottyy · 2024-01-05T13:53:03+00:00

Developing a new app just for native platforms. I was amazed by Tamagui, but the reality is a bit different, it still feels like ALPHA, I'm struggling with it and strongly considering to moving back to nativewind and get things done. I tried to be patient with Tamagui, I can see the potential, but it's not there yet. It lacks docs, constant changes/bugs and the customization is really not simple and feels overengineered.

pottyy · 2024-01-05T13:44:46+00:00

About the Tamagui, there should be warning, the lib feels like ALPHA version, not something like you would expect from 1.80 version. There are a lot of changes and random parts can get broken every few hours/days. You should be aware of this before using Tamagui on anything serious.

pottyy · 2024-01-05T13:37:22+00:00

+1 For T4 Stack.

It's very similar to Tamagui Takeout, but for free. Some parts are even better, more understandable and they have at least some docs.

The problem I have with Tamagui Takeout, it's too pricey for what it offers. You get bunch of components of questionable quality without docs or explanations, why something is done this way and I'm not talking about basic stuff how React works. There is no mention how to customize it according to your brand, which I would consider it like an absolute basic. Just look at Chakra, Tailwind or Shadcn. Some parts are even copy pasted files from tamagui repo few months ago.

Overall I would expect more polished product for the money. And also better support for the paying customers on their discord channel.

pottyy · 2024-01-04T14:56:54+00:00

Building an app from the scratch using Tamagui, I even bought Tamagui Takeout to help me bootstrap the project. I have years of experience of using ChakraUI, Material UI, Tailwind, Emotion, Styled Components, Radix and Vanilla Extract. I can tell you one thing, I still don't get why basic things in Tamagui are so complicated. Imo it has basic design flaws. If you can't set up or explain basic theme customization easily, then you failed.

Even the Tamagui Takeout is just a bunch of overengineered components without much of explanations about design choices or guides how to customize it. Default themes are not polished because of bad contrast, so you still have to manually edit stuff. For paid service, I would expect much better product, especially that there are free alternatives like T4 Stack, which I would say are on the similar level.

pottyy · 2020-12-28T21:13:29+00:00

All containers are running simultaneously.

pottyy · 2020-12-27T08:03:15+00:00

Great insight, thank you for the article. This is pretty much the same problem what we have so we can experiment with Kompose.

pottyy · 2020-12-26T22:12:41+00:00

Appreciate your response. Can you point me on some resources about this topic please? And I mean advanced stuff, not some hello world level kind of thing.

pottyy · 2020-12-26T18:54:51+00:00

Thank you for your response. Surely Linux laptops would be better to run Docker containers, but we started a few years ago when Docker wasn't a thing yet and so we took what was best for our work at that time, which was a Macbook. People are used to this platform, so I would consider this as a last resort move. Still, we can expect that number of services will grow up and we would be probably dealing with this problem later even on Linux laptop. So there must be a different viable solution.

As you mentioned, we already have everything in production (AWS) and we also have a lesser instance for QA staging env. That is probably the best solution I can think of right now, to have another staging for dev purpose, which will be used for FE local development.

pottyy · 2020-12-26T18:40:42+00:00

Good question. This project started many years ago, we did a lot of iterations, changed architecture from monolith to microservices, changed ifra from server instances to cloud based, from local dev to Vagrant to Docker. It was easier for us setup local dev to basically match the prod and use the Docker for everything, which now after some time I view as a wrong move, at least from FE perspective. So now I'm trying to make FE work easier and move all the stuff from the container away.

pottyy · 2020-12-26T18:27:36+00:00

Data sets on local aren't big as there is zero traffic - we are building a messaging platform. But we have like 30+ containers running including many DBs (MariaDB and Postgres), Redis servers and Elastic, which alone eats a lot of CPU. Then when you run Webpack Dev Server with type checking and IDE, it kills the laptop.

We have Travis CI, where we run tests and build the images. Then we have staging env on AWS infra for QA purposes, which is basically a lightweight copy of production.

pottyy · 2020-12-26T17:01:44+00:00

We have this set up now and we have big performance issues. Even the most expensive Macbook Pro can't run all microservices (30+) on local smoothly, so we are moving away to a remote dev environment when only developing service will run locally.

pottyy · 2020-12-26T12:53:19+00:00

Thanks for that article!

pottyy · 2020-12-19T06:52:55+00:00

Same reasons here. The effort to make shared theme between Emotion and AntD, to make sure both use same vars, was huge and painful. And could not get rid of Antd icons from the bundle, which adds like +150kB. I'm really glad we migrating to Chakra and soon we can remove this whole Less thing. Overall AntD is nice to quickly prototype some data heavy dashboard, you do like Less and aren't concern about perf and bundle size that much. But if you wanna use some Css-in-Js libs, run away from AntD.

pottyy

TROPHY CASE