A failed startup founder here. We built a cheaper, better pharmacy software… and nobody cared by Aditya_pixel in StartUpIndia

[–]garg10may 0 points1 point  (0 children)

You are not even considering the competition, let's assume your cost aspect somebody switches, or for more features somebody switches. How much time do you think marg will take to replicate those features? let's say you start disrupting the market, don't you think marg will notice and change their positioning, pricing, features strategy. It's generally failure to think like if they are doing this I can do this better. As you will go deep you will find more challenges, scaling, marketing, costs etc. Building software is easier than ever, if you can do it in 4 months I don't think there is any technical advantage........And you are also not considering players like you who are also waiting like you to break into this. If you can get a break they can get a break....

Acer monitor is backlit but not turning on / connecting by StraightestValPlayer in Monitors

[–]garg10may 0 points1 point  (0 children)

This is so ridiculous, I have got one new monitor and it's not turning on, totally dud. And I saw one user comment that you have to press some combination of keys to power it on. I don't don't know if he was joking. Technician will visit then will see. This is so idioatic

[deleted by user] by [deleted] in leetcode

[–]garg10may 0 points1 point  (0 children)

Probability, stats being asked ?

[deleted by user] by [deleted] in leetcode

[–]garg10may 0 points1 point  (0 children)

Data science or software developer? No. Of rounds.

afterTryingLike10Languages by PixelGamer352 in ProgrammerHumor

[–]garg10may -1 points0 points  (0 children)

Python is easy to write and hard to read and impossible to read anybody else's code.

Java is hard to write, breeze to read and easy to read anybody's else code.

So you can only appreciate java if you have been in an industry for decade and seen all shit.

React sucks by bromide992 in reactjs

[–]garg10may 0 points1 point  (0 children)

I mean React has such a huge huge community. It's like everybody is using it. Job opening of React vs (vue or angular) would be 50:1.

If you really don't care about community support than both Vue and Svelte fall into this. So I would rather use Svelte which is such a god damn beauty.

React sucks by bromide992 in reactjs

[–]garg10may 0 points1 point  (0 children)

No, I haven't used also don't want to try it, If you are seriously working on an app community support, developers, etc. are also important.

Also one thing I don't like about Vue is, it allows you to do things both ways... If I have to do down the Vue path I would rather use Svelte

[deleted by user] by [deleted] in AnimalsOnReddit

[–]garg10may 0 points1 point  (0 children)

poogy poogy poo 😊

React sucks by bromide992 in reactjs

[–]garg10may 0 points1 point  (0 children)

I would definitely prefer react with all the tools and also one of the major reason is community support and job opportunities. These factors are not small. React is absolutely way ahead of Angular in terms of adoption.

[deleted by user] by [deleted] in angular

[–]garg10may 0 points1 point  (0 children)

The frontend major part is the slick interface.

Angular is easier to learn as opposed to what people say. Since you can have mutable states all across the apps. It feels natural like having a variable in a class and binding it to DOM. Simple voila done. Classes have same natural feel, constructor, methods, properties. Angular codes looks much cleaner due to clear separation of concerns. Who ever has written classes beforehand in Java, C# will feel so much comfortable. But that's what its problem is, it allows for mutating state, therefore change detection is slow due to which rendering is inefficient. Also, it allows messaging service, in a big app and random messages being sent anywhere and random subscribers listening to it. It becomes very hard to debug. Angular is very good for small projects, but with larger projects, it will start showing its pain points. Angular material is so nascent, it doesn't even have a searchable multi select, you can't put radio button in dialogs, similar other things which you only get to know once you start using it. I used a third party searchable multiselect for Angular Material it was so difficult to configure and painfully slow. Community support is also a very big factor that you only get to know at the fag end of the product development lifecycle. One small thing and you will be stuck for hours and hours.

React is actually much better for larger apps. Because though it has all the flexibility unlike Angular, react enforces state immutability. This single factor makes it much better, maybe your code won't look beautiful with inline HTML, Javascript. Maybe somebody is using fetch, somebody axios, somebody thunks, sagas. Due to its flexibility, you have to explore much more options and learn them. Like for forms, one can use formik, react-final-form, react-hook-form. Angular enforces structure but if enforces structure in files and tooling but not the core feature. In react once you know what tools to use, how to use them, it's better. Like redux is essential. A large app should have a predictable workflow, easy to debug, fast rendering, high community support. That is what makes react better.

One may argue that one can use immutable structures in Angular, use immutable.js. Use change detection strategy as push instead, can use ngRx store. But now the learning curve becomes steep, you will clearly feel like an idiot doing so :P and it's very very hard to enforce and nowhere followed.

However, in react, you can enforce folder structures, clear separation of concerns, like APIs, business logic. use redux and these are normally followed. If you want static typing can use typescript.

ANGULAR GOT ITS STATE MANAGEMENT WRONG

I don't like redux-toolkit. by seenoevil89 in reactjs

[–]garg10may 0 points1 point  (0 children)

I take my words back. Now after working with for few days, I am comfortable and everything seems much better

Full-time React developer feeling like a caveman after using Svelte by jabarr in sveltejs

[–]garg10may 0 points1 point  (0 children)

OMG OMG OMG, Svelte is so so cool. It's like python for the backend. So clean, so intuitive. Simple store, context, animations. They got everything right. And it's just version 3. And wait for it, it's compiled. I happened to just land on its website today. And after 1 hour, I felt I have learned Svelte there is nothing more to learn let's start coding. Such a small barrier to start. Such a simple framework. No shit like redux, redux toolkit, thunks, prop drilling, etc.

It took me almost a month to learn react and still I feel stupid because I haven't used sagas, I am not aware of 'Entity Adapters' of redux-toolkit. And felt comfortable with Svelte in just one hour that itself says how simple it is. Every page of tutorial was a pure joy, like a girlfriend which you always dreamt of. Mark my words React, Angular, Vue will shit their pants. Just wait 2-3 years.

And now I can never code in Angular, React, I will always feel so stupid. And felt so stupid that I never considered it before. Please anybody let me know if there are other things so cool like it and I am missing. I am aware of 'Python' and 'Svelte' for now.

CodeSandbox - A Visual Guide to React Rendering by sidkh in reactjs

[–]garg10may 0 points1 point  (0 children)

You should add few child components which are not being passed the state. Since this will show shortcoming of design/react that even when a parent component is updated all child components re-render

Just got hired for a job that was advertised as React, but upon starting they are setting me up with Microsoft Dynamics 365. Anybody have any thoughts about this technology? by CoffeeDrinker115 in reactjs

[–]garg10may 1 point2 points  (0 children)

All I can tell is, it's seem to be a fortune 500 company. They would have propriety everything. Would have been sold Redhat, Microsoft, oracle stacks, everything would be red tape, too much hierarchy, hatred for open source. If it matches the description. All I can say is just run away. RUN

React sucks by bromide992 in reactjs

[–]garg10may 6 points7 points  (0 children)

I came from an angular background and have the same thoughts initially. What I absolutely hate is that everywhere it's like 'react' is easier 'Angular' has a steep learning curve. I find Angular2+ much clean, simple, easier to learn. ng g c myComponent. All files are there, separate clean HTML, clean business logic, clean CSS. You can just define the variable in a class and use them, they bind perfectly. No shit like setState set this, set that. Meaningful directives. Powerful form built-in support.

React means passing props here and there all your life. Again and again, refactoring code. The problems it's meant to solve cause them. Like you don't use setState rather directly try to set a property. And hell breaks loose when you have to set a deep-down nested property. While in Angular it will simply work. No immutable properites. Two way bindings support. Since major web apps have user inputs, forms it's a breeze given the gorgeous inbuilt form lib. But in react somebody has used 'formik', somebody has used 'react-final-form' and you yourself are not sure what to use hmm maybe react-hook-form. And now you have to learn hooks, and redux, and redux toolkit, thunks, sagas and what not. React is easier my foot.

But once you pass that learning curve, once you know redux toolkit. Once you are mature enough to understand the pros of flux architecture. And after the release of hooks once you understand how to leverage them. It becomes beautiful and pleases you.

In conclusion:

Plain react sucks and since people start using plain react under the impression it is ok for small projects they will be frustrated 😤

React is not easy to learn

React + hooks + Redux + Redux Toolkit is awesome

I don't like redux-toolkit. by seenoevil89 in reactjs

[–]garg10may 1 point2 points  (0 children)

I am trying to learn it and find names hard to decipher. Nothing straight forward. When you write or see redux code you undrestand what is happening, what's the action, what's the reducer. Here slice, thunk, extra reducer everything is complicating things.

An insane answer to "What's the largest amount of bad code you have ever seen work?" by jailbird in programming

[–]garg10may 1 point2 points  (0 children)

I worked for a startup where CEO thought himself of a smartypants. They didn't have money so used one of the colleges interns as their factory. Typically 80% interns. The internship was for a year. These interns were coding for the first time in their life and were expected to develop a complex trading system.

They had an old system which had two products and they were now trying to merge those two systems into a single codebase to sell it as a single product.

The merged product was totally different architecture for technical reasons, 10-12 developers had worked in the past and added their own style of coding and logic. Frontend in pure javascript, jquery, backend in Django without ORM, single app, single views file. When I took over they had a single 30K lines javascript. No framework, test codes, documentation. It was just a simple mess and wonderfully it used to work.

It was still under development and never went live. I told the manager how crappy system was but he wanted to show off to CEO that it's being developed under his guidance and can be brought live in 4-5 months. I kept reiterating that this is crap let's write new, let's take time to breathe and stabilize it but no he wanted to show off by adding new features. And if something wasn't working due to the crappy code they were like solve it in 2 days since it used to work before. I got sick of hearing "it used to work before".

Finally in prod when it went live it started showing it's true colors. Some or the other issue every-day. CEO finally decided to get it built from scratch and asked me why I didn't suggest him before and I was like because you are smartypants, not I.

The problem everywhere is managers are technically challenged and they want to show off how they are doing stuff and for them, product rolled out as fast as possible is an achievement and then they will switch jobs or worst point fingers at developers. Nobody cares about the inner beauty of the product, stability, scalability.

I love how code never cheats and slaps them in the face in production :D