DConf 2013 keynote

[Nick Sabalausky]

On Tue, 14 May 2013 08:46:29 +0200
Jacob Carlborg <doob at me.com> wrote:

> On 2013-05-13 23:52, Nick Sabalausky wrote:
> 
> > Hmm, yea I've looked at that before. There's some nice things about
> > it, but honestly, I can't stand non-native UIs (both looks and
> > behavior). Plus the settings don't seem to work (tried changing
> > one, saved, restarted, and it had no effect), and the text seems a
> > little blurry, and I'm kind of uneasy about relying on
> > closed-source for something I rely on as much as a text editor.
> > Don't like being completely at some company's mercy for any
> > changes/fixes I may need.
> 
> There are two kind of settings. System wide settings and user
> settings. I don't know if that had something to do with it.

Hmm, yea, I don't know. I first opened the user settings, saw
it was nothing more than a blank configuration file (aside from an empty
JSON object) and didn't deal with it further. Then I went to the
"default" settings, changed "remember_open_files" from true to false,
saved, exited, checked task manager to make sure it wasn't still
running, started it again, and it auto-opened the default settings file.

I did grab the "portable install" version of it, maybe it's just broken
in that? Or maybe it's just that one setting that doesn't work. I
don't know, I haven't investigated further.

> Don't
> know about the text, it looks good on Mac OS X.
> 

It's possible that one could have just been my imagination, maybe
because of its default color scheme being lower-contrast than I'm used
to, or because it's bold and I'm used to non-bold. I dunno. OTOH, I
have noticed Apple seems to like heavy anti-aliasing (or at least
heavier than I like), so maybe you're just used to it ;)


> > If all you're doing is passing a few switches to a DMD/RDMD call,
> > then having both BAT and shell is absolutely trivial. I do it all
> > the time myself:
> >
> > 1. Replace the shebang line with @echo off
> > 2. Replace "$@" with %*
> > 3. If you invoke anything in the current dir, remove the prefixed ./
> > (or change it to .\)
> 
> But there's still two files that needs to be maintained.

True, but they're very small, few in number, and updated in lockstep.
So it's entirely feasable and nowhere near as painful as, say, C/C++
headers.

But that said, yea, I'd also certainly prefer only having one file to
update.

> Then you
> need some linker switches, which are system specific. I'm not that 
> comfortable with the linker on Windows so I'm not sure I always get
> the flags correctly. That's why I really would like to have a build
> tool that handles this. It should have a system independent way of
> specifying common flags, like which libraries to link with.
> 

Yea, I agree. (Although that's orthogonal to "IDE-based building" vs
"CLI-based building": In either case, having to specify
linker-specific switches manually is bad, and having it nicely
abstracted (when possible) is good.)