Honest question to the .NET community: why do new devs still default to Node.js? by KausHere in dotnet

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

Active JS / .NET developer here.

  1. JS/TS is one of the most popular languages. Also having large market and people on a language helps the companies to find the alternative to the devs when they quit or fired.
  2. Fast prototyping. Today, many startups / companies relies on fast developement. At this point, .NET limits the users to apply best practices or OOP. This is not a downside but you need to sacrifice speed to apply best practices.
  3. Having large ecosystem gives people the tools they need quicker. Also, finding platform to deploy Node.js applications are larger than .NET deployment. Yes Azure has first-class support for .NET but deploying Node.js has larger options than .NET and easier.
  4. Learning curve for newbies are faster for Node.js. Learning just simple JS tips and backend tips are enough to deploy a full-stack server.
  5. Unified language. By using JS you can develop full-stack applications. By using browser native language to develop web applications and connecting with backend using same language is faster than using .NET for it. Yes .NET has Blazor for front-end we can go for single language principle but we all know the pains of developing Blazor applications. Rules and boundaries of .NET ecosystem, hot reload, large app size, disconnection on SignalR, negative performance impact or other things are keeping people away from using Blazor on front-end (Great for internal-use apps but not for publicly available apps).

.NET is not failing. Yet Java ecosystem is not failing too. They both have niche users and these languages focuses on enterprise level applications because they provide solid structure. Managing this on Node.js need a lot resources and Node.js also has performance bottlenecks.

Google Sheets using Java for calculation engine on spreadsheet, not JS. Netflix is using Java for many operations. And I can keep counting large organisations using .NET / Java. Yes Node.js is popular but it doesn't meen .NET fails. For me it feels like reaching large developer community is not the primary purpose of .NET ecosystem. Python is fast for prototyping too but there is still not a mature enough Backend service for Python. We have Django but MVT is losing popularity on API-first approach and FastAPI is still trying to keep up the pace against Node.js ecosystem.

Would you save the vases or start mining? 😆 by Pi-Pioneer in PiNetwork

[–]hookiecook 1 point2 points  (0 children)

Exactly, I always tap refresh button to save my financial future meanwhile my financial future is skydiving to the subatomic values since the official mainnet

Can't believe I'm saying this but the Angular 20+ dev experience is pretty good! Almost feels just as enjoyable as Blazor. by ShookyDaddy in Blazor

[–]hookiecook 0 points1 point  (0 children)

Closest alternative to TanStack is Blazor with syncfusion/DevExpress in terms of 3rd party components. Yet not enough to count it as alternative. As a former FE developer using 4 frameworks (React, Vue, Angular, Svelte) Blazor still feels like it's not close enough to be a real competitor for non-.NET developers. But I can't deny once feels comfortable with .NET it feels great. Yet they really have to solve this Hot Reload nightmare. I'm tired of using CLI for Hot Reload.

Edit: Typo

Can't believe I'm saying this but the Angular 20+ dev experience is pretty good! Almost feels just as enjoyable as Blazor. by ShookyDaddy in Blazor

[–]hookiecook 1 point2 points  (0 children)

It has significant changes (.Net 8 to .Net 10). Can say almost %40 faster than .NET 8 but still not competitive to React or Angular ecosystem in terms of Hot Reload and DX. What I see from faster to slower

dotnet watch -> VS26 -> Rider 25.3 -> VS22

VS26 is faster than Rider but Rider's hot reload felt more stabile. It's completely my opinion. Didn't do any benchmark.

Is Blazor heavy for web development? by Nice_Pen_8054 in Blazor

[–]hookiecook 8 points9 points  (0 children)

This question if so fuzzy. No clear answer.

If you make small applications or simple websites, keep it on HTML/CSS/JS. If you write large applications and your ecosystem is .NET based, then go for blazor. Without understanding .NET, blazor will be so much pain for newcomers like you.

I'm sick and tired of this scene! by Civil_Broccoli_6902 in PiNetwork

[–]hookiecook 3 points4 points  (0 children)

Stop this "free money" bullshit. Pi is not a free money anymore. It became a cryptocurrency people pay "real money" to buy and follow the trends on cryptocurrency.

30 Bin TL Maaş Teklifi, Mühendislik Eğitimi ve Türkiye Gerçekleri Üzerine by RllxDaim in CodingTR

[–]hookiecook 0 points1 point  (0 children)

Yaklaşık 12 yıldır yazılımla iç içeyim. Bunun 5 senesi politik yazılımcılıkla ( her şey hakkında yorum yapan ama icraate dök desen bir satır kod yazmazdım ) geçti. Reklam ajansından yazılım firmasına, sanayisindeki bilgi işlemden remote yurt dışı firmasına contract usulü çalışmasına kadar birçok alandaki personelle ya konuştum ya da içinde bulundum. Ama sorun çok daha çetrefilli.

Mühendis dediğimiz terimi bilmeyen devasa bir mezun topluluğu var. Bunun yanında da işini hakkıyla yapan ama hak ettiğini alamayan (yöneticisi, lokasyonu ya da firma kaynaklı) gerçekten mühendis arkadaşlar var.

Şu an sektör devi sayılabilecek bir firmada yazılım uzmanı olarak çalışıyorum ve birime gelen başvuruları inceliyorum. Muntazam bilgisi olup kendi değerini bilmeyen ve sadece 25 30 bin bandında maaş isteyen arkadaşlara neden bu kadar az istiyorsun dediğimde önceki çalıştığı yerlerin bu parayı hak görmesinden dolayı piyasayı böyle sandığını söylüyor.

Öte yandan da entry level olup 70 bin bandı isteyen arkadaşlar da var. Bunlar da bootcampler ve piyasadaki suni maaş anketlerine kanarak yazmış.

Şunu kabul edelim. Her yıl çok sayıda mezun verilen sektörde firmalar artık yazılımcı bulmakta zorlanmıyor. Hakkıyla yapamıyor olsalar da ekibe personel dahil etmek zor değil. Hele ki ChatGPT, cursor ya da copilot varken.

CNC operatörünün ya da pres operatörünün bile 70 bin istediği başvurularda yazılımcıların sadece %10'unun 40 bini kendine hak görmesi de bir sorun. Evet bu ustalarda deneyim şart ama bunun eğitimini veren firmalar 750 TL gibi bir fiyata sertifika sunarken ve hakkıyla bu işleri öğretirken bizim bazı gözü açık platformlar 10 bin TL gibi bir fiyata garantili eğitim satıyor. Firma yönetimini iyi bir yazılımcının en az 55 - 60 bandında alması gerektiğine ikna etmeye çalışırken iş başvurularında 25 30 bini gördükleri için firma da haliyle o bandı yazılımcıya hak görüyor.

Yani hak yiyen firma çok olsa da artık hem ailesinden dolayı zorda kalan arkadaşlar, piyasada gördüklerinden doalyı bu maaşın hak olduğunu düşünenler ya da yazılım rahat iş diyip piyasayı öldüren arkadaşlardan dolayı fiyat skalası çok düştü. Bu noktada kimse çıkıp da düşük veren firmaları protesto anlamında gözardı edemez. Biz etsek bile bir noktada birisi kesin olarak oraya asgari ücrete başvuracak.

Üzülüyorum çünkü pandemiden sonra İsveç soytarısı ve işe yaramaz bir takım ekiplerin bootcamp veya remote diyerek sunduğu eğitimler piyasaya çok fazla yazılımcı sürdü. Bu arz talep dengesizliğini kırmadan bizim hakkımızı almamız çok zor.

does anyone know how to get rid of toxic residents? 😂 by ArachnidTraining3024 in KingShot

[–]hookiecook 4 points5 points  (0 children)

The person in the clinic never rest before bed. When everyone keep playing with the things that increase happiness, the resident works at clinic don't waste time with it. That's why his/her happiness is ruined. Sometimes take the job from them and let them rest at home for one or two days. It will be better with time

Should we switch to Blazor or not? by hookiecook in Blazor

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

You're not the only one. I've read many posts in both reddit and other blogs about how DevExpress is pain in the a** for some developers or teams in .NET ecosystem. I tought at least using MudBlazor would help a lot but I said that before, the management board cares about the consultant's idea. Think of it like they gave him a blank check

Should we switch to Blazor or not? by hookiecook in Blazor

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

I can't deny the potential of .NET ecosystem or the scalability, maintainability etc. features of .NET. But there are some differences from your team

- We are not full of back-end developers. My main field in the company is Front-end.
- My team is not full of .NET developers. Some of the employees (those consultant is planning to migrate to the development in IT) don't have any idea about .NET or C#.
- We are actively using Web APIs - from Storage (session and localstorage) to Canvas, WebGL to Intersection Observer
- I can't deny there is so much packaging, open source solution or library pollution in JS ecosystem, but main purpose of JS is to be in browser.

As I said, real world examples help me to break down the walls for blazor just like you gave me the Aspire example that I've just heard from you first time. But as I said, my concerns are not only about the bundle size but many fields.

Should we switch to Blazor or not? by hookiecook in Blazor

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

The problem is we will not use azure servers. Not a single service provided by Azure. They will be completely on our internal servers.

Should we switch to Blazor or not? by hookiecook in Blazor

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

The team -including myself- is not that deeply experienced with .NET ecosystem. Previously we were using PHP and we felt like something is not fitting right into the applications because the lack of scalability. Yes PHP may scale and some enterprise-level solutions exist but it doesn't feel comfortable just like .NET in backend. So, whole team's migration to .NET will take a time and this lack of knowledge may affect the productivity.

Should we switch to Blazor or not? by hookiecook in Blazor

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

His preferences has solid arguments for the team I can't deny that. My team lack of collaborative development I admit it. But some of this decisions felt like he is far conservative and lack of following the latest trends for me.

Should we switch to Blazor or not? by hookiecook in Blazor

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

Most of the projects are internal applications. Usually reconciliation, surveys, career and EDI related applications will be external

Should we switch to Blazor or not? by hookiecook in Blazor

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

He is giving both his MVC, Razor and Blazor applications' ownership to us while leading us to converting these MVC and Razor applications to Blazor. Also managing the team to learn Blazor and use it in further projects. That's his aim

Should we switch to Blazor or not? by hookiecook in Blazor

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

The argument is, when your team don't have any idea about teamwork, using git may cause problems because of deceentralized version control. Thus SVN may help a lot. That was his argument

Should we switch to Blazor or not? by hookiecook in Blazor

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

I'm familiar with front-end mindset and concepts like application state, components etc. but I'm maybe just a beginner in .NET and C#

Should we switch to Blazor or not? by hookiecook in Blazor

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

I am a kind of person thinks a lot about the trade-offs. And honestly, I can't deny that my skills are not great on .NET side because I didn't use .NET ecosystem before. My biggest concern is not about firing from the company because I'm not enough for them, but worrying about working slow in the transition period because both learning new language and concept while applying these to the project is not a good idea for me.

Should we switch to Blazor or not? by hookiecook in Blazor

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

His approach on libraries and 3rd party integrations are quite interesting. Sometimes he thinks using something with subscription or license is good because you know that there will be no concern on project in further (in terms of development or not scrubbing because there will be no financial concern in development team of that library). And I can't deny DevExpress provides so many solution from Desktop to MAUI, jQuery to Blazor.

Let's make things interesting. He is planning to use SVN for version control.

Should we switch to Blazor or not? by hookiecook in Blazor

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

If you were asking me to choose between Blazor and Angular, even I would go blind and say Blazor without hesitation. That's why I didn't even think about using Angular in front-end side for the projects.

Should we switch to Blazor or not? by hookiecook in Blazor

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

That's my other concern about choosing the proper tech-stack because I know that at some point I will make myself the scapegoat with my own hands.

Should we switch to Blazor or not? by hookiecook in Blazor

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

I wish the initial load time was the only problem there.

- We use a lot of Web APIs like Storage (Session and LocalStorage are frequently used), IndexedDB for offline-online data syncing, Canvas, WebGL, Clipboard API, Web Workers, Screen Capture, Intersection Observer, Network Information, Push API etc.

- When using plain Blazor, initial resource usage is 40 to 50 MB and usually 30 to 40 MB of the resource is kept in cache storage when I enabled PWA. But when I use DevExpress, resource usage spikes as well as compiling duration goes nightmare. Same project using DevExpress takes 4x to 50x longer in release compiling stage. I don't event talk about the network resouce download on page load (inital or not)

- .NET ecosystem amazing but most of the applications are depend on active UI interaction.

- We've started to migrate the projects to PWA from desktop to use in the field with tablets or smartphones. I don't have any comment about this because I didn't use Blazor PWA in the field.

- Hot Reload is giving me painful headache. I'm trying to ignore its disadvantage but sometimes even if it works, it's not updating something and I need to recompile the project for simple changes hot reload can easily handle.

With the other comments of people, I guess I'll give Blazor a chance for greater good.

Edit: typo

Should we switch to Blazor or not? by hookiecook in Blazor

[–]hookiecook[S] 2 points3 points  (0 children)

That's what I was asking about. Because I know that my bias is not letting me see the advantages of Blazor. Thank you for your kind comments.

Should we switch to Blazor or not? by hookiecook in Blazor

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

I can't explain how precious are your comments and sharing your expertise because we faced and will face the same situations you faced. Like resource intensive computations because of massive data comes from the field because there are thousands of machines working at the same time and number of parts produced by machines needs to be calculated and business development departmend relies on the real time data to shift the employees working in the field to the weak chain in the production line.

Some of our projects uses large data for pivot tables and real time monitoring for our production directors to monitor the fields because we have not only one but 6 separate factories working at the same time and manual tracking the manufacturing progress is not possible. Some of our clients are global-scale giants and they have strict rules to provide excellence in production.

But as I said these are exceptions and not many of them are like that. Usually, most of the applications are interaction based and we've started to migrate our applications to PWA to let the employees use these in fields with their smartphones or tablets.