Latenite 2: Directory structure and project management.

[Timendus]

What the hell? How do you get Java to be so buggy..? I use Eclipse fairly regularly nowadays, and I'm starting to appreciate it more and more. Same goes for Java as a language and as a system. I don't really understand how so many people can hate it so much

And please, don't integrate with Visual Studio unless you don't want me using it

[kv83]

How do we get Java to be so bugy? Shouldn't you ask that at Sun?

[CoBB]

Same goes for Java as a language and as a system. I don't really understand how so many people can hate it so much

For instance, deploying Java programs at different machines is often impossible without recompilation. I’m teaching Java in this semester (and did last year too), and you have no idea how much trouble we have getting the programs of students to run in the lab because of slight runtime version differences. And they aren’t even using third party class libraries, which could remove the option of recompilation as a last resort...

As for .NET, Mono seems to be still too immature to run complex applications (e.g. Winforms support is not too stable in my experience), but it is getting there slowly.

For the time being the safest and most portable option is still C/C++.

[benryves]

What the hell? How do you get Java to be so buggy..?

I have no idea, but it's not just me. I didn't install it on the university PCs, and didn't set it up on the work PCs. Older (pre-JIT) versions ran fine.

Same goes for Java as a language and as a system. I don't really understand how so many people can hate it so much

It's a good idea (both language and system) and can appreciate what it has done, but I do find the language rather ungainly and the runtimes (ignoring the above bugs) rather clunky. Put it down to MS fanboyism if you like, but ".NET" seems to be a lot better executed.

As for .NET, Mono seems to be still too immature to run complex applications (e.g. Winforms support is not too stable in my experience), but it is getting there slowly.

MS made some noise about releasing the source to the class libraries for VS2008, so hopefully support might get better. System.Windows.Forms is a bit of an odd one, as it relies on Windows-specific behaviour (window messages and the like) which have to be emulated on other operating systems (maybe it should have been Microsoft.Windows.Forms, in the same vein as other MS/Windows-specific stuff in the Microsoft namespace). I suppose WPF and XAML are easier to reimplement in any case.

[Timendus]

For the time being the safest and most portable option is still C/C++.

It's completely insane, but you're absolutely right...

So, you're not going to work with Java because apearently everybody hates it, which leaves .NET -- and hoping that Mono will get there "some day" -- or writing your IDE in C/C++ with some portable GUI library... In other words, it'll be .NET and I'll just have to keep working with a simple editor with improper syntax highlighting and a command line

[benryves]

Hm, portable GUI library and .NET are not mutually exclusive. (eg Gtk#).

I'm guessing the main reason the current Latenite doesn't work outside Windows is because it P/Invokes native Win32 functions, so it hasn't a hope in Hell of working on Linux.

[CoBB]

So, you're not going to work with Java because apearently everybody hates it, which leaves .NET -- and hoping that Mono will get there "some day"

Unless the app heavily relies on IE, in which case that ‘someday’ is pushed even farther...

I'll just have to keep working with a simple editor with improper syntax highlighting and a command line

Time to embrace Emacs.

[King Harold]

Just wondering, will this new directory structure include things like
\Local Settings\Application Data\Bee_Development\Latenite.exe_Url_3coraaogekaius1k1cbdalaw3s45y3tz\1.0.6.1

like Latenite now does?
I find "_Url_3coraaogekaius1k1cbdalaw3s45y3tz" somewhat odd..

[benryves]

That's automated by the .NET settings system. I don't pick those directories.