View Single Post
Old 09-25-2013, 09:21 PM   #45
user_none
Sigil & calibre developer
user_none ought to be getting tired of karma fortunes by now.user_none ought to be getting tired of karma fortunes by now.user_none ought to be getting tired of karma fortunes by now.user_none ought to be getting tired of karma fortunes by now.user_none ought to be getting tired of karma fortunes by now.user_none ought to be getting tired of karma fortunes by now.user_none ought to be getting tired of karma fortunes by now.user_none ought to be getting tired of karma fortunes by now.user_none ought to be getting tired of karma fortunes by now.user_none ought to be getting tired of karma fortunes by now.user_none ought to be getting tired of karma fortunes by now.
 
user_none's Avatar
 
Posts: 2,487
Karma: 1063785
Join Date: Jan 2009
Location: Florida, USA
Device: Nook STR
Quote:
Originally Posted by canpolat
One other option would be to drop cross-platform support and develop it only for GNU/Linux. That, I guess, would also simplify things for the core team.
I use OS X so dropping other OSs would mean dropping Linux. That said while Linux is not supported with binary installable packages it is still supported as a source build.

Cross platform support really isn't a big deal from a source level. Building packages is where the time is spent. The majority of the cross platform support comes from Qt. There is a surprising little amount of actual cross platform code in Sigil itself.

Quote:
Originally Posted by canpolat View Post
OK. Let's accept your argument and assume that C++ is not that popular after all (or it's not easy to attrack C++ developers). The thing is: at this point, we cannot really do anything about it. I don't see much point in focusing on something that cannot be really improved/changed. So, in essence, my suggestion is to strip Sigil off of its "non-core" features and keep the "core" and then add features as plugins.
A plugin interface is would be a valid solution to the C++ barrier. With a proper plugin interface plugins can be developed in languages other than C++. That said a plugin interface is the largest "pending" project. So that in itself isn't going to happen.

Quote:
Originally Posted by varlog
I was forced once to use C# for one of my trivialities - without knowing it, as usual. I hated it. My impressions: it depended very heavily on MS NET and tasted like some overblown degenerated spawn of Basic.
I've found C# to be Java but done right. I've only spent enough time to learn the basics of C# (enough to get by when needed) and I've found it very easy to work with. To the point that working on existing C# projects is very easy.

The big benefit to a language like C#, and Python is memory management. Not only do they (mostly) take care of it for you they hide pointers from the programmer so they don't have to learn about them. I'm amazed at the number of really good developers who work with languages other than C/C++ and they have no idea how to use pointers.
user_none is offline   Reply With Quote