In that sense, I think building software can definitely be called engineering. You are applying practical knowledge to design and build software/systems.
Now, if we continue:
Are we applying scientific principles? To be honest, I didn't study long enough to know if what we do is considered scientific. But essentially you define software and how it is supposed to act, in order for the software to work under specific conditions (and unexpected ones perhaps).American Engineers' Council for Professional Development engineering definition posted:
This is what you do when writing software. You write a spec, you refine it, you write it, you test if it works, and if it does, you ship. Sure, you might have bugs, but other fields have that problem: bridges have been built that couldn't handle enough load, specifications are sometimes inaccurate leading to decisions being taken on the fly to deal with this, etc.
Maybe I'm not understanding the definition of engineering, but it seems exactly like what I do.
as a hobbyist programmer, I don't mind the general sense and feel of the editor, and I'm assuming (or suggesting) that the colors of the UI can be changed with some built-in options. I don't think I'd keep things transparent and quite so glowy, but it's certainly something to bear in mind.
when there is some kind of build released for that, I'll give it a try. keep up the good work!
When I download a IDE, I don't want to spend the first hour changing the theme to something my eyes can bear.
'It's adjustable' isn't an excuse. It should be appealing on the first sight. That's how you get people to download your IDE.
I think they'll deliver an alternative light theme at launch, if not, I'm sure we can come up with something.
Waterfall-like development processes are unavoidable in hardware because it is exceedingly difficult to go back and fix something once you've gone and set up a factory or, worse, once your product is actually out in consumer's hands. You can't 'patch' hardware like you can patch software.
So you're forced into this rigid development process. But it's a terrible thing, and software engineers shouldn't opt to emulate it just because that's how it's done with hardware.
Ah, I get you now, I was thinking in marketing terms, apologies.
I graduated with a major in Management & IA, so you can see where I'm coming from.
You might want to change the Java text icon from JAV to JAVA.
JAV is a commonly known acronym for Japanese Adult Video.
Thought you should know.
New screenies on facebook:
I think a light theme won't be a problem now.
JPEG, truly the best image format for screenshots. The IDE is looking good apart from the first shot, which probably intends for your eyes to melt out of your face.
It looks alright, however hard to say without trying it. And yeah bud, what's with the absolutely crap image quality?
The 'minimalistic' theme actually looks alright.
Aside from the 'HARDCODE' backdrop/watermark. Unnecessary, IMHO.
It could maybe use some subtle differentiation between elements, though. As-is, it all sort of blends together into one homogeneous lump. And please, dear god, no neon borders. That isn't what I mean by 'subtle differentiation'.
In my opinion, if this does become free, it would be nice to have as open-source as an entirety, and not as a partially open-source project.
I can assure you will more than likely have more assistance from some other devs (if hosted on a repo somewhere publicly).
I'd think that you'd squash more bugs in the long run with it being completely open-source, rather than just part of it.
This is simply an opinion however, so take it how you'd like to.
Apparently your hard work lessens if you make it open source.
Imho open source projects are more successful in the psychological way. People get to learn from your code' and praise you for it. Just look at eclipse, it's open source and it has all those awesome plugins.
Not to be a stick in the mud, but OP seems to have disappeared, which is weird considering their Twitter and Facebook are constantly being updated.
We are hard at work on the IDE, we will answer questions as time allows. You can follow our FB page and Twitter feed for development progress (we will soon have a development blog up too). We will update the OP on occasion with new information and announcements, so keep checking back.
PS: Update posted, it is a bit overdue, most of this was completed a little while ago.
So where's that list at? I don't mean to detract from the main topic of the thread, but you've been "compiling" this list for days now. It shouldn't take you days for something like that, especially when you used it to big up your own IDE.
We have been asked by a select few for a list concerning our a line on our website that everyone seems to have taken the wrong way. For those that don't know what was said we stated that we think most other IDE's are badly designed. This was mostly with concern to the user interface and interactive side of the IDE. We originally stated that we would compile a list, and we have actually done this. Its currently 1800 words long, and we were going to post it here to actually just get this over with. Now heres where things are going to change slightly. Firstly after a very long meeting we have decided to NOT post it here because we (to be blatantly honest) are tired of everyone thinking we are bashing other IDE's, and we don't want everyone to take this the wrong way again. If you think we are bashing other IDE's then you are very wrong. We love netbeans, we love coda, Textmate, sublime text and most IDE's that exist. We didn't even mention names in that line and so you cant really say that we are bashing your favorite IDE, because we are not. We generally love most of the features that all these IDE's provide but we find each IDE lacking in other areas. *
On a side note regarding the entire design of our IDE. Firstly, its a work in progress and by definition, it means we are literally still changing and working on the physical design and operation of the application itself. ALSO it seems everyone has major issue with the transparency. Now if you look at the very first post, it was stated (also in comments and other posts on many other social and internet based networks) that the user interface can 100% change with respect to every single pixel - including alpha masks. This means that you can make theme that really suits your style of work if you don't like any of the included themes. And yes, you can turn of the hardcode branding, as (we hope most developers know) these things are literally adjustable with a simple boolean. So please, if you don't like it, just turn the feature off.
While we welcome contructive criticism, we will be ignoring any issues that we have already addressed. We do take the comments into account, and will continue to do so as well as implement of some of your suggestions (as the new themes have shown). *But if you honestly hate the IDE, then thats fine, no one is forcing you to switch and forcefully use it. We do however think that if you give us a chance to think differently and really come up with something that could change the face of programming, then you might be pleasantly surprised. Again, its a work in progress, and progress can only be achieved when everyone is willing to provide constructive feedback.
We'd love your contributions to help us make an IDE that you WANT to use.
Kind regards, The HardCode team.
Wait.. So you compiled a detailed list of design flaws in IDEs, but you're not going to post it because you don't want people think you're bashing other IDEs? That makes no sense.
The request of the list has nothing to do with bashing, it has to do with providing evidence behind claims.
On top of that, you've just clarified that you're not bashing anything yet you've kept the main statement in the first post, showing you obviously don't care that people misinterpret your statements as long as they're not bashful on your standards. Is it possible that the list itself is bashful?
All I want is the statement I bolded to be backed up. Could you send me a PM with the list, seeing as I'm the only person who cares?
If I were to sum up the above post, it'd be that it just responded to my statements with a quote to the section of post I was critiquing, and saying that I should re-read it to answer my repetitive questions.