Revoliqo logo

Revoliqo

Web App

Stack Decisions

Application and Data

(8)
React
TypeScript
CloudFlare
C#
Microsoft SQL Se ...
.NET Core
Material-UI
Entity Framework ...

Utilities

(2)
Postman
Netlify

DevOps

(2)
GitHub
Visual Studio Co ...

More stacks from Carlos Iglesias

Want more information about this stack?
Avatar of ciglsias
Software Engineer ·

MySQL and Postgre both are great and awesome and great support, community, support. Whatever will be good. Postgree have some little advantages.

6 upvotes·1 comment·88.5K views
Wassim Ben Jdida
Wassim Ben Jdida
·
August 16th 2021 at 3:41PM

Thank you so much carlos for responding ! for Golang, do you suggest we go with a web framework maybe like Martini, Gin... or just use the builtin net/http ?

·
Reply
Avatar of ciglsias
Software Engineer ·

React + Firebase is an awesome combination. Add Typescript and even better.

5 upvotes·1 comment·8.3K views
raphaelaudet
raphaelaudet
·
July 22nd 2021 at 8:11AM

Firebase will definitely be faster than typeorm. Typeorm seems pretty state of the art for js or ts stacks but I have been missing a lot of feat I got in other lang.

·
Reply
Avatar of ciglsias
Software Engineer ·

C# and Python are both great languages. With great communities, libraries, frameworks, opportunities. I think it will be the same in a near future.

It’s matter of your likes, and your next jobs.

Dot net core is a little faster on performance. Python more popular with dynamic types. Probably the most lovable language.

READ MORE
3 upvotes·224.5K views
Avatar of ciglsias
Software Engineer ·

Mobile Native Development Apps will never die. Cross Plataform like React Native only exists to save time and costs for startups mainly, which is extraordinary, and indispensable often of course. But when the App get popular enough, it will probably will move to Native Development. Several improvements.

READ MORE
3 upvotes·97.7K views
Avatar of ciglsias
Software Engineer ·
Recommends
on
Material-UIMaterial-UI

It is normal. A perfect UI Framework for your needs does not exists. As long as the overrides aren’t too large, it really worth it. It saves not only CSS, also Components features and some browsers compatibilities issues.

Try to keep it simple, maybe the changes are not always needed. They look pretty good by default. And match a whole design.

The other way is (having a professional designer design) from scratch, which is a lot of extra work. (If you don’t have such profesional, don’t even try it). But if it’s mandatory a fixed desig, very different from Material UI, go for it.

Finding another UI Framework, probably less wide/mature than Material UI for React, will requires changes too.

Of course try to reuse components. Check the Theme for custom colors, ...

I hope it helps. This is my opinion. I have used Material UI for a couple of projects, happy doing it.

READ MORE
3 upvotes·1 comment·1.1K views
Vidit Kothari
Vidit Kothari
·
March 6th 2021 at 6:52PM

A thing about web dev that fascinates me so much is the 'context'. What you use, where you use, how you use and why you use depends on the context: requirement of the client, developers' comfort/skill level, priorities like performance or semantics or agile development.

I have tried Material UI, Bootstrap and Semantic UI. Among these I find the look of Semantic UI a bit more modern, professional, featured and distinct But it isn't always about looks. Though I like Semantic UI a lot I don't keep it in priority unless I'm the only one working on a project. "Why?".... because it has not been in active development for a while. Though it looks stable but it's build setup is outdated and throws error when adding it as npm dependency.

Coming back to the primary concern, I think there is almost always a situation where you need CSS customization. So be it Material UI or Tailwind, there is a strong possibility of us needing to write custom CSS.

Far as I'm concerned, I prefer reading the MaterialUI guidelines and implementing the design using Tailwind CSS (for the most part).

·
Reply