Hey guys. I have been using Homesite for 20+ years...
# ide
g
Hey guys. I have been using Homesite for 20+ years. But new servers use TLS 1.2 so it simply won't work any more. Any tips for getting used to Coldfusion Builder 2018?
a
Hey fellas (also FAO @websolete / @Jim Priest). Don't forget to use threads. Also... 100% agree: swerve CFBuilder 2018 and use VSCode. Well... indeed... the current version of CFB is atop of VSCode anyhow. Why would one start using an out of date text editor? (ie: CFB2018)
g
I just googled for CF Builder. Is 2018 the latest Adobe has? Did they kill it?
I know I'm off in my own little world still using Homesite. But it was a solid editor. Did what I wanted. I don't like to be forced into another development process by my editor. I develop locally, use source control, deploy from SVN to a staging server, test, and then copy with BeyondCompare from staging to production.
I have used Eclipse, CF Builder, Sublime Text and other things to develop locally, but always had Homesite open with a solid FTP client to see or tweak code on staging or very rarely on production.
a
It's just that the CF team are not as good as they could be at keeping their docs up to date. The current version of CF Builder is discussed here: https://helpx.adobe.com/coldfusion/coldfusion-builder-extension-for-visual-studio-co[…]-started-coldfusion-builder-extension-visual-studio-code.html I guess it somehow did not occur to them to update the actual product page too? Ping @Mark Takata (Adobe) The risk you have with using obsolete software is you are kinda obsoleting yourself as well. If you need to shift environments, it's not gonna reflect well on you that you are using such dead tooling - which is really really inferior to current-technology products - for what I assume is your day-to-day work Also, unless yer cranking it yerself (which I doubt) HS ain't gonna have in-built support for anything added to CFML since whenever it was discontinued (CF9 by the looks). That's really out of date.
m
CF Builder is EoL, it is missing all of the language features and capabilities in 2021 and 2023. You will want to use VS Code. We have a CF Builder extension for it, which is free. I personally like it a lot and use it daily. Some folks don't like it, which is fine as there are other CF extensions available as well (plus we are working on improvements). Here's the thing with FTP: just use an external tool. I too was a huge fan of the built-in FTP (Dreamweaver was my jam) but there's just no tooling available that works like that. And the modern way of working is in Git anyhow. Just gotta adapt. 🙂
g
So the FTP-simple with VS Code isn't good?
a
@Mark Takata (Adobe) so the VSCode plugin is not "known" as CFBuilder? So that's why the CFB page on the Adobe website doesn't mention it (it's all about CFB 2018). Either way, it's not as helpful as it could be in regards to locating what Adobe is recommending for typing in CFML code. One shouldn't have to already know what to look for in order to find it 😉
m
It is known as (deep breath) The Adobe ColdFusion Builder Extension for Visual Studio Code.
😄 1
Which is... yeah. lol
We should have named it something easier, but Builder was already an approved name.
So here we are.
Gus, yes, FTP-simple is... um, not really very awesome. I've heard once you get it running, deal with issues, set it up, get authentication going, etc then it is OK. I never got that far. Several hours of frustration in I threw up my hands and installed FileZilla. 20 seconds later I was connected to my server.
a
TACBEfVSC Maybe ThAdCoBuExFoViStCo Rolls off the tongue. Even easier if drunk. And let's face it... 11:36am, I probably am...
m
I was gonna suggest SodOffAdamYaWanker.dev and then we could have an online editor too. thoughts? 😛
a
#seemsLegit
😂 1
And... seconded re just using FileZilla if one needs to use FTP.
m
Yeah, it just works. Supports all the latest secure FTP stuff. Good product for folks still needing FTP.
💯 1
a
On a side note...I really don't like having deployment tooling coupled to my text editor. I like to have a distinct "mind gap" between the tasks of "writing code" and "deploying code". They should not be coupled. Too easy to get lazy and dev on prod, instead of deploy to prod.
👍 1
m
Agreed. There's significant advantages to a tiered, layered system with code safety baked in, even for single devs. Fun story, I once was developing a simple app that had a form on it. It was "production" (meaning, live) but no one could have known it was there. Suddenly I started getting hit by a bot sending spam messages through the form fields. No clue how it found it. I had absolutely no filtering, safety, etc. "Security by obscurity". Learned my lesson. I was so young. Anyhow, a week later now and I feel like I'm a better dev 😉
a
BAHAHAHAHAHAHAHAHHA
m
(that did actually happen like 15 years ago or something like that. scared the living daylights out of me)
a
I can imagine
j
It's 2023. Please don't use FTP. SFTP. SSH. FTPS. Something with an "S" in it.
m
I just print all my code out on paper & mail it to the server farm where they OCR it back in. ;)
😆 3