Why the fuck are all templating engines called after synonyms of the same thing?

Laravel has Blade
ASPNET has Razor
Node has Edge

I've been using dotnet and aspnetcore for years. I've heard people complain about MVC but I never really saw the problem. The controllers are easy to set up for basic endpoints, I have my domain models and DTOs, and our views I guess is our standalone webpage just consuming jsons.

Only now I'm having to work with an *actual* aspnet MVC stack - server-rendered cshtml and all - and it's dawning on me like a truck what people were actually referring to.

Out of all the issues I've had so far, they have all been due to black box enigmatic voodoo because don't worry about it, the framework takes care of it - it should just work. But what if it doesn't? I have no idea because the trail ends at the bit that should just work.

I should know better than to criticize an entire framework and paradigm made by devs with vastly superior experience and expertise than me, and my issues are absolutely due to being new and unfamiliar with this, but imagine coming up with an architecture to obsessively separate the MVC concerns, then you make cshtml.

I have a 3 freaking professional experience as a .NET developer and was freaking able to deliver successful projects. My experience is .NET freaking windows form. And for every freaking time that someone would call and interview me they do freaking ask if I have a freaking ASP.NET MVC experience and I don't freaking have! BUT I DO KNOW HOW TO BUILD USING THE FREAKING FRAMEWORK.

The freaking problem is my 3 years of experience is from winform, but i do freaking know how to use the framework.

How do I freaking get a job as a freaking MVC dev if no freaking employer wants to a hire a freaking C# dev with lead dev role but no freaking experience with ASPNET MVC!

IDEs should be more transparent as possible. The code you see in course editor should be exactly what we see when inspecting via browser tools.

I'm looking at you ASP.NET and VS!

I'm interested in learning c#(aspnet cire, wpf, uwp etc, all the stuff I can do with it). Does anyone have any recommendations in where and how to start? I'm familiar with the basic concepts of programming, and I work as a front end developer, but I really want to expand my knowledge. Any advice would be great!

The bug: Some string values for an identifier property in the data objects are being sent from our frontend prefixed with a '0'. Sometimes. When it happens, it usually gets stripped away again by the time it's passed to our backend. But not always.

This 0 is never explicitly set anywhere. I even searched for a few variants of " = 0" in both the frontend and backend projects without receiving any results. You might already be suspecting where this is going.

So it turns out.

The data object which holds this value is being initialized in the aspnet (don't ask) backend and passed to the frontend, which then hydrates it. This value is always an integer number, albeit incidentally so which is why string is used as the actual type. When this object is initialized, it's hardcoded with an anonymous type where this property is set as int because I guess someone figured "it's always an int though". Being a typed language, primitive scalars can't be null objects which means the property's value becomes the concrete int 0.

Okay weird. I can think of better ways of doing this but let's just set it to string as I can't start overhauling things right now. Let's just go find where this value is somehow concatenated into the incoming parameter.

You see, this happens because at the point where the frontend sets this value, it may be an int or string depending on where it came from, and I guess someone figured that in order to cast it to string you just go prop += arg seeing as the prop is empty string and all. Because explicitly casting it or - as much as I get a rash whenever I see it - going prop = "" + arg would be too verbose and unoriginal.

Bonus round: How come the 0 only sometimes made it all the way to our backend? The thing is that this bug has been fixed before. The fix is that because this string is "always" an int, you can parse it to int before passing it to the backend in case it has leading zeroes. This path is only taken in certain views because someone forgot to copypaste their fix into all the places this is repeated.

Sometimes you find a bug and you are just somehow more grumpy after fixing it.

Hey guys i am a javascript web developer who loves his stack lot sadly in my internship i was forced to learn php and Laravel and build a full stack website with auth cruds with predefined templates in less than two weeks .
i have to say Laravel sucks comparing it to something like aspnet, Nestjs, Nextjs or Express i found myself overwhelmed with learning in a very short period and what makes things worst is the fact that no one in the agency i am in is helping or speaking with me i asked help from a Senior guy and he was like "i am too busy"...
I also can't quit since this internship is for school purpose so yes rip for me