C#
I have experience in game development for 5 years in C# and have a coding background of around 7 years. I want to choose a mobile application tool, but I am confused about what to choose between android native or Flutter.
- Present: Flutter is very performant ( it exports native ARM ) for apps created today in iOS and Android and large corporations are starting to support it for development.
- Near Future: Share source code with mobile, web, and desktop ( Linux support on the way )
- Future: It is the UI framework for the upcoming Fuchsia Google OS
Flutter is the best if you want to easily and quickly get an application for multiple operating systems from a single code base... however if you want to develop games specifically you should opt for android native. Even if you only want to develop an app for Android Flutter should be the best choice.
Visual Studio 2019 keeps rendering only part of my project. I changed from 200% dpi to 100% and it is still doing this. Any ideas?
Razer Blade Stealth Intel 7th gen i7 8550u
A little more info, I'm trying to make my GUI my self in WPF C# so I turned off FormBorderStyle
I have Windows 10 Pro Installed which Home is usually the go-to.
I'm going to uninstall and reinstall and see if that does anything. Fingers crossed, I was looking for a more concrete solution though. :x
I am working on a new project and need advice on which front-end technology to use. The back-end is all written in C# MVC and Microsoft SQL Server databases. In the current project, we are using the same technology stack for the front-end; we are using cshtml (razor) with jQuery.
If you are used to use JQuery, Vue.js more similar to Jquery because you only can import a CDN and start to work. Vue is really flexible and you can use it wherever you want.
In other hand, if you have time to learn and install a new framework as React, use it. React works with a standard and several conventions in his code, then is really easy integrate new libraries and plugins .
this is not entirely correct. just like vuejs, reactjs can work with just the referenced script (tag). so you dont need a build pipeline in either. you massively miss out on features and DX though.
the notion that react has several conventions / a standard is also slightly incorrect. out of all choices, react is the least opinionated. its as close to "true" javascript, as it gets. there is no official state-management, routing, etc. so this is all your choice.
vuejs on the other hand takes some decisions off you (benefitial to new developers). there is an official routing library, an official state management lib: vuex, and an official way to approach styling. you get the point.
both are absolutely great choices. while you'll find more resources and a larger community with react, vuejs typically does some quality of life "magic" for you. its pure taste.
if your html markup comes from razor, I'd recommend globally registered Vue components though. I've successfully used this stack for 4 years. (content from sitecore cms rendered through razor, enriched with vuejs components)
in any case, you will want to try to remove jQuery, if you pick a frontend library, as you should not mix two ways to modify the DOM. it wont break but its unnecessary bloat.
Hi
I’ve been using Django for the last year on and off to do my backend API. I’m getting a bit frustrated with the Django REST framework with the setup of the serializers and Django for the lack of web sockets. I’m considering either Spring or .NET Core. I’m familiar with Kotlin and C# but I’ve not built any substantial projects with them. I like OOP, building a desktop app, web API, and also the potential to get a job in the future or building a tool at work to manage my documents, dashboard and processes point cloud data.
I’m familiar with c/cpp, TypeScript.
I would love your insights on where I should go.
Spring Boot is the lightweight of the Spring framework. I used the Spring framework before, and I fall in love with the Spring Boot. I also use .NET core, but still, I like Spring boot the best. If you have time then you should experience both. You are more than halfway in gaining experience. My suggestion is always to try to learn many things as you can.
Hi there. I'm looking to build an employee time tracker web app. This should also be optimized for mobile. I'm trying to figure out what the best stack is for this. I have knowledge of Java, JavaScript, some C#. I don't mind learning a new language for this purpose. Any help or advice would be really awesome! Thanks.
Hi Otensia! I'd definitely recommend using the skills you've already got and building with JavaScript is a smart way to go these days. Most platform services have JavaScript/Node SDKs or NPM packages, many serverless platforms support Node in case you need to write any backend logic, and JavaScript is incredibly popular - meaning it will be easy to hire for, should you ever need to.
My advice would be "don't reinvent the wheel". If you already have a skill set that will work well to solve the problem at hand, and you don't need it for any other projects, don't spend the time jumping into a new language. If you're looking for an excuse to learn something new, it would be better to invest that time in learning a new platform/tool that compliments your knowledge of JavaScript. For this project, I might recommend using Netlify, Vercel, or Google Firebase to quickly and easily deploy your web app. If you need to add user authentication, there are great examples out there for Firebase Authentication, Auth0, or even Magic (a newcomer on the Auth scene, but very user friendly). All of these services work very well with a JavaScript-based application.
Hi Stephen. Thanks for the suggestion! I am slightly worried about the non-blocking I/O model of NodeJS. Do you think that microservices (child processes) would improve that?
As you have knowledge of Javascript, I would go towards Vue/React in Frontend and Node (with suitable framework) with backend. From my point of view Java would be too bloated for suggested kind of an app. I myself use PHP as a backend a lot and React as frontend but moving thoughts towards full stack javascript world.
I've read a few forums claiming that full-stack Javascript applications suffer from speed issues and with handling heavy computing. I don't expect this particular project to have significantly heavy processes but the speed does concern me a little. Do you think that would be an issue?
I need some advice to choose a language for back-end development. Right now, my REST APIs were created by using Flask/Django, and I'd like to create a more reliable and more efficient API with static typing. On the one hand, Go is young, very light, and syntax like Python's, but C# has a large number of libs and more built-in methods. Which is the best solution today?
It depends.
From times to times I asked or was asked that same question. Technology aside, it's important to consider the skills and expertise that the dev team has. Whether you use language A,B or C or framework X,Y and Z, if your team has a strong background and experience with something make it count too.
I would recommend Go simply because as you mentioned, it's super light. No need to bring in the whole .NET suite to get a simple REST API up and running. Even if your API is a bit complex, Go should be able to handle it.
Hi All, I am working upon developing a C# based windows service to work as a TCP server using Visual Studio 2019 as a development studio while using .NET Core 3.0.
As its a background application, therefore, I am up on to add tracing and logging feature into it and want to write to 'text file' my trace and log outputs.
By my research, I came upon 2 potential tracing and logging frameworks and on the verge to choose 1, therefore Serilog OR NLog.
Anyone here who can help me out by his/her experience of 1 framework being better than other.?
I'd suggest Serilog, as it provides semantic logging, has a large amount of sinks (Locations to log to). Out of the box supports logging to text files, which is your requirement. Well documented and supported. Add it together with a product like Seq and you have a robust application logging platform.