|
Front end:
JavaScript (Angular, React)
Middle: C#, and Node...try it out with EdgeJs and you can have Node consume C#.
Backend: Sql Server, but starting to move towards Cassandra and Redis.
|
|
|
|
|
C#, WPF, and Syncfusion controls for professional, modern looking application. 
You can also use MahApps.Metro. I have used them both.
They are needed because Windows' standard WPF appearance is really ugly, and it's too much of a hassle to skin them yourself.
|
|
|
|
|
I would say there are 2 competing trains for thought for this question.
- Use the best tool for the job.
- Use what you know the best.
As a project, you can assess that maybe C# with .net would be the best fit. However, when you look at the skill set of your team and find they lack the knowledge. You are left to either train them up, which may take some time to make it error and bug free, or hire in the staff.
Conversely, if your team says, well we can make that in Java, in X time, for Y budget, and it wont look as different. They have the knowledge to make it far less error prone and bug free.
mixing the two: deciding on what language or tools to use should be weighed against Skill, Knowledge, Suitability
C# reduces knowledge requirement to get program written (such as memory management)
C or C++ may be closer to the OS, hench can write higher performance code, at the cost or requiring a higher knowledge of the language.
|
|
|
|
|
I'm a former aerospace engineer that of course had a background of BASIC in high school & FORTRAN in college. In the early '90s I took a course through my place of work in C, and the utter elegance of that beautiful language completely captivated me. I went on to learn C++, which I also found elegant, even the tricky parts. I then learned VC++ and became completely smitten by the idea of how easily I could develop a regular Windows app, and decided to switch careers into software development. When .NET came out, while I had a few issues with some of the hokey aspects of C# like the fact that a fundamental object is passed by value whereas any other object is by reference and some peculiarities of callbakcs, I did like the way that abstract classes & virtual functions were done, and of course the memory management - but I what I really liked was the way that it set up the forms & data binding in a very elegant way as opposed to the kludgy way that VC++ did it. I now consider myself a .NET C# developer, albeit "early retired" since there seems to be no market demand for this skill anymore.
|
|
|
|
|
I recently converted my laptop to an SSD (from HDD) and I'm realizing the benefits every day.
Android Emulator
I hadn't given it extra thought but I started a new Android project and started the emulator the other day and it started so fast I wondered how it was possible.
Then I remembered, the entire Emulator OS is really virtual memory (run from disk for the most part).
I just started my emulator running Android Lollipop and the Google API and it goes from zero to fully started in about 5 seconds.  It was probably somewhere around 1-2 minutes with the HDD.
If you're an Android dev and running emulators like this (and you have an HDD), you really need to consider converting to an SSD.
|
|
|
|
|
I have a spare machine with 80G hard drive and loads with Visual Studio 2017.
I want to use SSD to improve the performance as you did.
diligent hands rule....
|
|
|
|
|
I doubt you'll find a single member of this site who will argue against adding an SSD to their system! Having said that, one or two will turn up...
Sudden Sun Death Syndrome (SSDS) is a very real concern which we should be raising awareness of. 156 billion suns die every year before they're just 1 billion years old.
While the military are doing their part, it simply isn't enough to make the amount of nukes needed to save those poor stars. - TWI2T3D (Reddit)
|
|
|
|
|
David O'Neil wrote: Sudden Sun Death (SSD)
Is that really what I want to add to my system?
Software rusts. Simon Stephenson, ca 1994. So does this signature. me, 2012
|
|
|
|
|
Quote: Having said that, one or two will turn up...
See! I jinxed myself! 
Sudden Sun Death Syndrome (SSDS) is a very real concern which we should be raising awareness of. 156 billion suns die every year before they're just 1 billion years old.
While the military are doing their part, it simply isn't enough to make the amount of nukes needed to save those poor stars. - TWI2T3D (Reddit)
|
|
|
|
|
It all depends on cost vs capacity vs speed of access.
For portables and desktops, I agree that an SSD is the way to go. This is not necessarily the case for a home/office NAS, and is far from being trivially true for a datacentre.
There's still plenty of life in them old horse buggies.
[Full disclosure: my employer, Western Digital, makes both HDDs and SSDs]
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
Daniel Pfeffer wrote:
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
Does this mean that you are able to get "all of us" a huge discount on HDD's and SSD's? Maybe even FREE SSD's for everyone that is a member of CODE PROJECT!!!!?? 
-Randy
|
|
|
|
|
Sorry; it doesn't work that way. I can only purchase a limited number of devices every month, and they may only be used for non-commercial activities. Selling them on is a definite no-no!
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
ssd. Bah Humbug! Bring back core memory.
Sin tack
the any key okay
|
|
|
|
|
Modernist! Bring back the Jacquard Loom!
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
David O'Neil wrote: doubt you'll find a single member of this site who will argue against adding an SSD
I agree.
David O'Neil wrote: Having said that, one or two will turn up...
You definitely know this site. Or people. Or People of The Internet (PITs)
Here they come.
|
|
|
|
|
I still don't trust them 
|
|
|
|
|
raddevus wrote: goes from zero to fully started in about 5 seconds
I'm glad I don't do any Android development then. My initial thought when reading that particular bit was that anything that requires a whole 5 seconds to load from an SSD is a massive pig.
|
|
|
|
|
That's funny. It is an entire OS starting up though, so...
How fast does your phone actually start? At least 5 seconds, I'm guessing.
If your using an iPhone -- a lot, lot, lot longer time.
|
|
|
|
|
So does the whole emulated OS have to start from scratch every single time you want to start your app?
|
|
|
|
|
dandy72 wrote: So does the whole emulated OS have to start from scratch every single time you want to start your app?
Great question. No, it doesn't actually. But the initial time to start was painful in the past (without SSD).
Once you have the OS running on the emulator you can just deploy you app over and over without having to restart the OS.
The newer versions of Android Studio even has a cool feature that does a hot update so that your app recompiles and does an instant update to the emulator without the long wait of copying and installing the .APK (android installation package for the app).
|
|
|
|
|
University of Michigan unveils 1,500-pound Rubik's Cube[^]
This is insanity. Pure Insanity.
What do you get when you cross a joke with a rhetorical question?
The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism.
Do questions with multiple question marks annoy you???
|
|
|
|
|
Exercise for the body and mind - bro, do you even twist? 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Solved in 7 seconds 
|
|
|
|
|
Imagine how big it would be if it included equipment to solve it like this one[^] (from an earlier news item, if I'm remembering correctly). (At those speeds, the centripetal forces would probably explode the cube at that size, without a heck of a lot more engineering!)
Sudden Sun Death Syndrome (SSDS) is a very real concern which we should be raising awareness of. 156 billion suns die every year before they're just 1 billion years old.
While the military are doing their part, it simply isn't enough to make the amount of nukes needed to save those poor stars. - TWI2T3D (Reddit)
|
|
|
|
|
As I recall, they had to create a low-friction cube for the robot, so I guess the university students have to roll their mega cube back to the lab for a couple more years 
"When you don't know what you're doing it's best to do it quickly" - Jase #DuckDynasty
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
