Ford Fusion is a horrible car and Coldfusion makes me shiver when I remember about it… but hey, I guess we can try to fight that dark background.
So I’m more or less neutral for now, but would accept Fusion if everybody else like it.
What will be the file extension?
*.fus?
As long as it’s not *.fuss …
Are 3-letter-extensions still necessary? I guess not, because “.html” is also widely accepted.
I suggest we just go for “.fusion”. As far as I have seen so far, that isn’t used by anyone.
for Fusion
Regarding the file extension: what about .fsn? Or just .nf for Neos Fusion. I think shorter is better (less typing, more space in editor tabs, etc.).
1 Like
… oh and we have an epic chance for code refactoring:
rename \TYPO3\TypoScript\Core\Runtime to \Neos\Fusion\Reactor …
6 Likes
+1 for Fusion
Oh please please, let’s have a shorter extension name, two letters is ideal
Root.f
Why is everyone so possesed with letters. You know that IDs have auto complete and such. You can even configure a new filetype for php storm with hte right ending. The amount of times you need to type fusion vs f or nf or somthing is ideally once a year. This is for me a non argument.
@christianm yeah, I agree. But if everyone turns out to hate a descriptive file extension like “.fusion” I’ll give in …
.fs = Fusion Script?
together with refactoring to Neos\Fusion\Reactor(\Core?) 
Let’s not call it a script, it’s not a scripting language really. But .fs would still work as an abbrev for FuSion.
I’d prefer .fusion but would be ok with .fs as well