Dreamweaver dropped support for CF when it went CC. I still use CS5 because frankly CFBuilder sucks.
YES!!!! Totally agreed!!!!
These forums used to use a CF based forum application, now it's Jive which uses a JSP framework (which again sucks. but I regress). If Adobe does not use CF for their own customer facing portals, what does that say for CF?
I've been railing against JIVE almost since day one. But you highlight a strong point: If Adobe isn't using CF for the forum, that tells me that Adobe has no faith in CF.
Idea that I think would re-energize the CF faithful, dump CFBuilder and roll the functionality into Dreamweaver, either natively or as an add-on.
I'm not so sure that this would work. I think the majority of people who move away from CF are doing so because of price. I've seen licensing (for a new install, not upgrade) go from low-but-still-not-that-affordable (if I remember correctly, about US$500) to the current obnoxious price of US$4000 (or is it more?) for standard. Enterprise being, of course, much more.
I have suspected for a long time that Adobe is secretly trying to kill CF, and damaging wallets is a very good way to do just that. Kind of a war of attrition.
But I do agree that CFBuilder needs to go away, especially when you can't really use it on systems that are isolated from the internet (can't fully activate it without an internet connection, and I understand that Adobe has no intention of providing an offline way of activating CFB3.)
And as far as DW no longer having CF support, I'm actually okay with that (even though I'm using CS5, too) since Brackets has CF add-ons that will provide CF support. Now, Brackets isn't as good as DW, but it's a thousand times better than CFBuilder, IMHO.
^ _ ^
Okay, I looked it up.. standard is US$1500 according to the current buying guide. But I swear I saw new licenses going for over US$3000 at one time. Maybe that was the Enterprise price, IDK. Still, even US$1500 is ludicrous when ASP, PHP, Lucee, and others are free.
^ _ ^
1 person found this helpful
Thank you for your post. I am Rakshith Naresh, Senior Product Manager for ColdFusion at Adobe. The purpose of my reply is to address the concerns that you expressed in your post.
I know you probably can't answer this but what are Adobe's plans for ColdFusion?
Adobe will continue to invest in ColdFusion. We are currently working on the next major version of the product, code named Aether. With every version of the product we have seven years of support commitment. Five years if core support and two years of extended support. For instance, ColdFusion 2016 which was released last year has support till 2023. And ColdFusion Aether (to be released next year) will have support commitments till 2025. So just for the versions that we have and version being built we have support commitments till 2025. The key point that i want to highlight is, ColdFusion is not going anywhere!
ColdFusion is doing well and the business is growing. I do not know if you were a part of CFSummit 2016. in the keynote we stated that ColdFusion has had double digit growth launch over launch. Here is the link for the keynote slide deck.
Dreamweaver is run by a business unit different than ColdFusion business unit. The decisions made by DW product team is driven by the needs of their customers. Having said that, I do know that DW added some support for ColdFusion back into the product. Here is a documentation link that talks about this support. ColdFusion Builder is completely driven by ColdFusion business unit and we will continue to make it better. Can you tell me why you seem to hate builder? Have you tried using the most recent version? We have fixed the issues that were reported and improved the performance significantly. Give it a try and let us know your feedback.
The feature request form has been fixed. It now has ColdFusion in the drop down, Thanks for reporting. It was clearly an oversight.
CF Builder will continue to be supported and will not go away or rolled into DW. I just want to be very clear about that.
You will see adobe executives at CFSummit discussing about ColdFusion. I look forward to seeing you at the CFSummit.
RE: Can you tell me why you seem to hate builder?
Agree. CF users is professional and small business owner. We pay the $1000 instead of free ASP, PHP, etc. Adobe drops the customer service on CF will eventually kick CF faithful user to ASP, PHP, etc. It is painful but fact if Adobe keep hurt CF fan. We are business owner and can not suffer the risk. That is the price to love CF.
yes, if we stay with CF, how to resolve the installation and version compatibility issue. We are focusing on run our business and can not afford many labor cost and risk. If we switch the platform, tons of CF code need to be rewritten. That is bad !
From what I understand, most code written for Adobe ColdFusion (ACF) is compatible with Lucee. There are a few things that might need to be re-written. But unless your code was originally written for CF6MX, you shouldn't have to re-write ALL of your codebase.
^ _ ^
Great !. Most of our current code is coldfusion 10 based. The only concern
is the installation and running of lucee. Where I can find the related
package and installation instruction ?
On Mon, Jul 10, 2017 at 11:35 AM, WolfShade <firstname.lastname@example.org>
raksh naresh, I decided to force myself to use CFBuilder more to be able to provide you with additional feedback. A few things I did not realize CFBuilder did I found I like, but I still have quite a few issues. In no particular order:
- Global searching within a project is a pain starting with the fact that you can only expand one module at a time. It finds all the occurrences but I have not found a way to scan through all the hits for a specific pattern I'm looking for - I have to expand one module at a time just to see the match.
- The parenthesis and bracket helpers are great for typing code from scratch, but in my work I do quite a bit of cut & paste and adding a parenthesis to existing blocks is more keystrokes than the one-character the helper is saving.
- Same for single and double quotes.
- Most CF tag helpers seem to work fine but most CF function helpers don't seem to exist.
- I'm not a fan of the open module persistence. Not a big deal but forcing me to close modules from days past seems annoying.
- Somewhere I thought I found a code formatter, but all it seemed to do was remove blank lines. The Commands>Apply Source Code Formatting options of DW were much better.
- CSS coding, like JS coding, does not feel as refined as DW. Helpers are present but seem very finicky making the helper disappear to all but never return or "help" insert something I did not want.
That's all I have off the top of my head for now. #1 & #8 above force me to use DW the most. Hope this helps.
raksh naresh, Another update on CFBuilder...
By far, #1-3, and 5 on my prior list or issues with CFBuilder are my biggest peeves. With #1, global searching is basically useless in CFBuilder and I automatically open DreamWeaver CS5 for any searching. Assuming you can put focus on just the right objects to do a global search within a project, only being able to open a single hit at a time when making multiple edits is a real pain. Then re-searching but with completely different results (usually no results) because the object focus was not just right usually send me over the edge and my coworkers get a shower of colorful explicatives with Adobe as the focus point.
With #2 & 3, I find myself spending more time fighting with the editor than actually editing when updating existing code.
With #5, only the single level of tag auto-close seems to work. Example, typing: "<cfif ...><cflock ...>..</cflock></" - the </cflock> will automatically fill, but </cfif> will not. Then to make things really annoying, when <cflock> does close, it places the cursor just before the final > so if you are not watching the screen, this will be the result: "<cfif ...><cflock ...>..</cflock</cfif>>" or "<cfif ...><cflock ...>..</cflock</>>" if you thought auto-complete was going to help.
Please feel free to pass this along to your CFBuilder peeps. My recommendation if you are going to continue down the CFBuilder path, steal someone from the DW staff and incorporate his/her knowledge into the CFB editor usability design.
I must admit I have changed my view recently.
I think CF is a fantastic platform to be involved in & Actually while I hated CF builder to start with I have come to learn just how powerful it is, a lot of the hatred come from my own mid understandings & ignorance.
I think the lack of the design view put a lot of folks off, me too but really that was just a crutch. With coding I have learned 100 times faster and write better code.. the built in debugger is just brilliant.
I am choosing CF today for all my new applications. I think it has it all!
cfscript full unity is now just excellent.
I run my own agency and I learned after 20 years that a lot of the publicity on the internet about this and that etc. is just dribble and really only an illusion. Its easy for us developers to get caught up in this and I have seen me changing platform in the past because I felt pressure from online communities. Then I realised... CF does absolutely everything I need! why change?
Do what works best for you, technologies come and go but CF have stood the test of time.
Look at Microsoft:
asp is what you should be doing.
no don't use asp, use asp.net and web forms.
no don't use webforms any more, just maintain them, use MVC.
now umm mvc, asp.net core, web api, razor..
OMG.... the list is endless...
I see a bright future and I think the product is now fantastic.
you are building the right patters in any case..
It is very pleasing to know about your interest in CF Builder. We take this very positively. I would like to answer your queries -
1. Regarding Search in a project, I am not sure about what is your expectation. In any editor that I have seen, search works in a similar fashion.
We do have a toolbar which allows you to do such things. However, a shortcut for the same can be considered for enhancement of user experience.
3. We have never heard of performance issues with indentation. If there are, we would be keen to address the issues at the earliest.
4. Regarding Dreamweaver, we would say that the very purpose of its existence is different and that's why it exists. CF Builder stands to solve very different and unique problems that CFML developers face. Be it Security Code Analyzer or RDS Query Viewer or Phone Gap or Line Debugger or anything else, all our features are unique to CF Builder and designed to solve the fundamental problems faced by CFML developers and make their lives easier.
Adobe ColdFusion Team
Thank you for responding. I just happened to be browsing the new-fangled discussion board when I saw your reply. Anyway, matching your bullets…
1. Global search: I just upgraded my PC which required a CFBuilder reinstall and this corrected a big portion of the issue I was experiencing. Prior to the reinstall my search result tab somehow got detached from the default panel making it a dialog window. Whenever I searched and drilled down to a hit, the search result panel would be hidden by the editor panel. This made it extremely difficult to go to the next hit – I was having to re-search to find the window which got complicated further because the object focus was now changed. As long as the tab is in the default location, global search is workable. The only issue currently is going from one module to another within the search results closes the previous module. I would rather they stay open so if I open 4 modules with hits, all 4 editor tabs are available.
2. Shortcuts: No, I was not talking about shortcuts, instead the manual typing to change code.
Example, current line: variables.x=”<p>Hello World!</p>”;
Change to: variables.x=formatter.text(’<p><span class=”text-muted”>Hello World!</span></p>’);
3. Tag indent performance: I may be able to setup a Webex session or something similar if you PM me.
Again, thank you for taking time to address my issues.