We plan to write our own EPP solution in our company, now we choose which language / technology to use. Architecture is a client-server application. OS - Windows, DBMS - MSSQL. We make the application primarily for ourselves, but in the future, perhaps, we will sell and implement our solution to other customers, so perhaps we will make the application for Linux. Now we choose between C ++ (Qt) and Java (jni) (both for client and server applications). Development in C ++ seems to us more time-consuming, but the result is more productive and flexible, the development on java is seen as easier and faster. And what do you think, what technology is better to use? Can you have a howling option?
Almost always cheaper and faster to find an existing application.
now we choose which language / technology to use.
No that isn't how it works. FIRST you decide what the system will do. You define the principle business features and prioritize those.
You only need to 'choose' technologies to meet those needs. Most of the time, if you have enough business experience, the technologies you already know will be sufficient.
Development in C ++ seems to us more time-consuming, but the result is more productive and flexible,
Architecture and design makes systems flexible not technologies. And correctly doing architecture/design requires experience in doing that and also an understanding of what the business needs. And for a future product understanding the industry, not just the company, is required.
Can you have a howling option?
In general without knowing specific business needs a C#/MSSQL or Java/MySQL will work as base if you are familiar with one of them. There is cloud based support for both.
1) I don't think this is the correct forum for this question.
2) What you usually see in the movies is mostly not related with what the world of computers really is. I.e. tapping the keyboard for a second and getting pictures zoomed and the pixels cleaned up
3) If you want to learn knowledge about computers, you should learn about computers. Movies won't give you the knowledge about them
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
I'm working on a WPF app hitting SQL through a Web API.
What's the right way to handle a concurrency violation? Do I need to check the timestamp myself in my DAL's update methods? Or will SQL throw an exception? If I have to check it myself, is throwing an exception the best way? What exception(s) are used for this?
What I'm really interested in here is the full workflow from the time the user clicks Save to either the data is saved or a violation is handled in the front end?
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
Yes, since you do not know wheter the old record has been modified, or even still there. Would obviously not be happening often, since mostly there's not a lot of people working on the same record at the same moment.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
I've read the docs and it seems that processes writing to a single log file requires socket implementation. Really? is it not possible to create a static singelton class and logger instance, in a module, and import that single instance object into each module as the logger and use that? In either case, how might this be done simply and without extravagance.
Hi everybody. I have a question about Memento pattern.
Let's suppose we have a class which's state has to be saved and later restored, and we resorted to the Memento pattern for that.
What if the state includes resources that have to be explicitly released (like file handles, OpenGL textures etc)?
Should I make them part of the saved state? This necessitates to handle memento objects in a special manner: if memento was restored, then it's up to the originator class to handle the resources, if memento is dropped, then it has to clean up itself. Pretty entangled logic.
How would you implement Memento when state has resources to be released?
Should I apply Memento at all when object state includes OS resources that have to be released?
You "save" things that may change. You don't simply save "everything" related to an object instance; things like "resources" are usually "common" to the class / assembly and are not "saved" for each object.
"Saving" is independent of any "cleaning up" you do "after" saving (key data).
"(I) am amazed to see myself here rather than there ... now rather than then".
― Blaise Pascal
Last Visit: 31-Dec-99 18:00 Last Update: 24-Jul-21 14:14