I really don't understand the "Components" chapter. XAML has both declarative approach and components.
Besides if anybody is into Delphi, there is also RemObjects worth looking at.
Why I Choose Delphi
111–120 of 307 posts
Re: Why I Choose Delphi
#112Earlier quoted context omitted.
We could have something like that if Web Components were actually a thing, but they are only properly supported on Chrome.
It's time we just make wasm render raster and vector graphics directly and throw the DOM away, i'm sick of it already.
I firmly believe that once WebAssembly matures, we will have the renaissance of browser plugins, just wait for it.
There are already people playing with prototyping language runtimes into it.
Re: Why I Choose Delphi
#113Last time I used Delphi was to build Knuth's Mix simulator in 2004, as a high school summer project. Me and my partner didn't even know about VCS system and used floppy disks to exchange code - and still, Delphi felt had this air of outdated technology around it. May be it was fascination with mighty and power C++ that so many beginner programmers have (before they learn to effective instead of smart). May be - because Pascal was the first language they tough as at school and it was much easier to understand than some Lisp dialect they introduced later on. But even then, the system felt so easy, so un-exciting...
Which are exactly the feelings I search for today when I'm researching frameworks and languages.
Re: Why I Choose Delphi
#114As someone who maintains an unknown but very large(several MLOC) free Pascal code base, I must say that I can't see much reason in the Pascal hate. Sure, I would love to rewrite the whole thing in Lisp (which is the language that lets me keep my soul), but we are all in all still very happy with the current code base. A complete recompile is less than 20 minutes, and then about half that time is spent in guile for ma…
Yep. We had a 250k line codebase ten years ago that took 20secs for a full rebuild in Delphi. You could code like a demon. Even 17 years ago it had awesome reflection that let you do some really efficient (lines of code) stuff with generating classes on components.
Re: Why I Choose Delphi
#115Earlier quoted context omitted.
Nothing's wrong with C#. When it came, it was a "better Java" in many respects, and that was a niche that was desperately begging to be filled. Over the years, it became even better at it.
I'm sure there's nothing wrong with it. It's just me being old school and curmudgeonly - not really hot on runtimes and complex dependencies. Although of course, if I really need it, Nim will compile my wonderfull code to js. Otherwise just singe, compact, standalone executables for any platform I care to imagine. And yes, the language itself is a joy to code in. Which is opinion, not fact, I realize that.
Would you compare Nim to DLang (honest question)? If yes, how?
I've been watching both and just waiting for an opportunity/excuse to build something using one of them
Re: Why I Choose Delphi
#116I just tried using Lazarus, I found it quite fun to use. I understand where the author is coming for when it comes to RAD. It is extremely easy to use. It feels like C# but compiles down to native code that runs on all platforms.
Re: Why I Choose Delphi
#117Native Windows COM applications is one area Delphi was really good at. If that's what I was building I'd probably use Delphi. That was Delphi 7 though. I'm not sure where it's went since.
Re: Why I Choose Delphi
#118[deleted]
Re: Why I Choose Delphi
#119Earlier quoted context omitted.
Delphi still has an advantage over .net - no dependencies, you can ship a single exe without worrying about dll's, which makes it great for sme's
You can ship it as a single executable if you statically linked midaslib. Most data processing needs that.
No need for the .Net-runtime on target computer? Or more like a runnable jar-file that "only" depends on an installed jvm?
Re: Why I Choose Delphi
#120The IDE is just so far behind the competition. Crashing all the time an slow. Theming support ist very limited (to date). Delphi Code Insight ("Intellisense") is slow and sometimes just refuses to work and is generally not on par with other offerings. Error Insight (the wiggly red lines thing) is even worse. Delphi still uses a single pass compiler which makes for great compilation speed but seriously limits the lang…
> The IDE is just so far behind the competition. Crashing all the time an slow. Theming support ist very limited (to date). Delphi Code Insight ("Intellisense") is slow and sometimes just refuses to work and is generally not on par with other offerings
I'm 100% with you. That's why I switched from Delphi IDE to Visual Studio Code with OmniPascal (www.omnipascal.com). It's much nicer to work in a state-of-the-art editor.