Skip to main content

Awaiting Sedna

According to Craig, Sedna Release Appears to be Imminent...

This is, of course, great news for FoxPro developers as they have been waiting (im) patiently for it since October when they released SP2. I had noted it on an earlier post and asked around, finding out that Sedna got put behind VS2008 and SQL 2008 in the "release" queue. (Good to see that Craig is providing more details on it, although an updated EULA from Legal certainly isn't something I hoped to see - what new things could they have possibly put into it from June's CTP?)

But since then, a few regression bugs were found in SP2. I can appreciate wanting to close the door on new VFP development - but with some of the fairly major bugs that were introduced, I hope that either:

a) Sedna includes some fixes for it in the xBase apps (I'm not sure how that would work but if the report Preview engine controls how data is displayed, maybe it could)

b) Sedna includes some hot-fix DLLs

One can only hope.

I am definitely looking forward to some of the new pieces (including the ones they haven't spoken about).

Bill Kuhn notes in his comment on Craig's post that if Sedna is going to require SP2, " Sedna might as well stay off the market until SP2 is usable." I think that may be a bit harsh - as some of the new bugs may not affect the type of application everyone might be building but the one that Cathy has definitely affects how desktop applications that produce reports work. If Microsoft can release patches to fix Office 2003 and then reset them pretty quickly, (and this product is scheduled to be dropped from support by 2014 - one year earlier than VFP 9) - then one can hope they do fix it promptly.

Comments

Popular posts from this blog

FoxInCloud Stats

FoxInCloud sent this link a while back about their statistics regarding visits to their site:

http://foxincloud.com/blog/2017/12/27/VFP-community-lessons-from-foxincloud-site.html



What's interesting here is the breakdown of people. Yes, I think it's understandable that the Fox community is getting older.

Another factor is the growth of the mobile and web environments taking over development. These environments really do push people towards the newer non-SQL or free SQL/hosted environments but more towards hosted storage options like Amazon and Google. A tool like FoxInCloud that helps MOVE existing applications to the cloud inherently competes with those environments.

But FoxInCloud also allows developers to extend their application further by giving them a starting point using Javascript and the basic CSS (such as Bootstrap). If you're not rebuilding your application from scratch, it's certainly a great step forward.

Well, that explains CodePlex...

In a move that will be sure to anger open source (or rather anti-paid software, anti-Microsoft open source)  zealots, Microsoft is planning to buy GitHub.

A year ago, I mused about why Microsoft would shut down CodePlex and how the world needs competing source code repositories to be strong. I'm not the only one per this Slashdot article :
"...people have warned about GitHub becoming as large as it did as problematic because it concentrates too much of the power to make or break the open source world in a single entity, moreso because there were valid questions about GitHubs financial viability...." - Jacques Mattheij

I will be interested in seeing this play out - whether developers jump ship or not. Have all the efforts Microsoft has made in pushing towards open source be seen as genuine or will all the zealots jump ship or maybe even attack?

Microsoft's comment about why they shut down CodePlex referred to how spammers were using CodePlex. Well, GitHub has its own …

The World of Updates Today

I just received an update for Office 365. It certainly includes some cool features - including starting in one environment and picking it up in another environment. In recent years, I've certainly enjoined the use of Continuity on a Mac and in fact, I feel spoiled being able to start a message in one environment (even Google) and then finish it off on another.  This has become some pervasive when we were reviewing our most recent backlog at a client site, a similar feature was added to the current workload.

But with web applications, the trend is to reduce the amount of software on a client machine. I used to have automatic backup for all of my machines (thanks Carbonite!) but these days, many of my machines don't need anything beyond the core OS and some basic applications. Certainly that's the feeling with Chromebooks and even the lightweight aspect of many iOS apps. The functionality is mostly in the cloud.

When you upgrade your system, you expect it to a big update. So…