[Looking for Charlie's main web site?]

It's looking like cf2020 will be cf2021, if I'm reading things right

Note: This blog post is from 2020. Some content may be outdated--though not necessarily. Same with links and subsequent comments from myself or others. Corrections are welcome, in the comments. And I may revise the content as necessary.
As much as many have been referring to the new release (known for now as "Project Stratus") as "CF2020", it's looking like it may be instead "CF2021", if I'm reading the tea leaves right. And maybe it's only the name, not the actual release year. Let me explain (Hey, the bright side is that "2020" as a year is one many want to forget.)

[....Continue Reading....]

Related Blog Entries

Comments
Considering that CFNext or Project Stratus or CF2020 or CF2021 is such a HUGE change, I am not surprised or even disappointed that it's taking a little bit longer to get everything completed. I'd rather it get done right than rushed and buggy.
Great to hear from you, Wil, and hope you're on a road to recovery.

And yep, on your observation there. Just to be clear, that's indeed why I had said, among the other things:

"I'm sure most would rather see it "come out only when it's ready". And this next release is indeed quite a substantial one, as I hope to talk about in upcoming blog posts, or which you can find out about yourself at prerelease.adobe.com."
To Wil's last comment, I went ahead and tweaked the post to put a new subhead in ("Should be well worth the wait"), just before the text I quoted. That should help it stand out more clearly.
Guess they also have to look at it from a marketing perspective - can't actually do any sort of conference / tour currently so why not wait another 3-6 months and keep fine tuning things.
Good possibility, Jim.
Heh, here's to wishful thinking. Perhaps that will give them time to also get a VSCode extension complete. ( more complete, out, something along those lines )
# Posted By John Farrar | 10/8/20 12:08 PM
That's another great point, John. Yes, I agree.

And for those who have not heard, Adobe has mentioned in recent presentations that they DO plan to rewrite CF Builder from Eclipse to VSCode. They admitted that it would not likely make it out with Project Stratus.

So yes, perhaps if things with Stratus are delayed beyond that timeline they had in mind for the VSCode-based builder when they said that, maybe they could come out at the same time. They also said they foresaw it coming out in stages, with more features to come later.

Finally, to head off the inevitable (off-topic) question: yes, they said that their PLAN is to create BOTH an extension (for people already using VSCode) AND a complete white-labelled version of VSCode (for those who do not)--just like they did with CFBuilder as built on Eclipse, which offered both ways of implementing it.

And I'm sure some will have more questions or want to make comments (for or against their plan), but this isn't the right place for that. (I don't mind that John brought it up, but I'm just saying I have shared here all I know.) It would be better to raise a question about this on the prerelease.adobe.com site (in the Project Stratus site for now, or later when perhaps they create a prerelease for the VSCode version of CFB.)

Or maybe someone will come out with a post on it before then (whether someone at Adobe, or someone else, or I). My point is that either of those would be the place to discuss this tool further, rather than this post.

And if anyone DOES create a blog post or a discussion thread in the Stratus prerelease, feel free to share the link here. (Yes, after the prerelease such a discussion thread will no longer be accessible, but by then there should be new more official word from Adobe.)
Copyright ©2024 Charlie Arehart
Carehart Logo
BlogCFC was created by Raymond Camden. This blog is running version 5.005.
(Want to validate the html in this page?)

Managed Hosting Services provided by
Managed Dedicated Hosting