2024-05-27 10:25:17 - Paul D. Foy -
I am having to write to ameliorate my stance. My difficulties were caused by not having looked at my original work for several years and then wanting to enhance it. This is still possible my difficulties having been caused by inexperience in the new areas. And in fairness Microsoft advises you that one is programming in ways which are exposed to older Windows features but which are not supported by these older features. So the onus is on you to robustly structure your program so that this is accounted for. Fair enough but in my case what a job and with such a small team - difficult. The task will be to create a robust, self contained program (for the non software engineer) which has some longevity. The issue then will be on the age of the Windows operating stem on which it will still run going forward. I can vouch going back about 12 years with my current offerings successfully. Can't go back to Windows 95 - I haven't got one - it's no longer practical to own one. Let's hope this situation improves. I was tending an allotment with barely changed equipment for 25 years, my mother even longer. Growing you own food (we don't have a well!!) and your lifetime is the ultimate test of longevity (not for how the landed gentry use to think though!).




2024-05-21 13:54:36 - Paul D. Foy -
Announcement - I am officially retired.




2024-05-21 13:52:07 - Paul D. Foy -
Microsoft will support 4. 8 going forward but if you want to do anything new you've got to ditch it. You can't carry on using it with the new stuff or enhance it into the new stuff. You can only do new what they want to do not build on what you've done. This is all very well but I'm bound to your operating system (or only a very small number of practical others) so I don't have any choice but to align with that platform so I don't appreciate the discourtesy of being straight jacketed into what I can do. Unfortunately most of my other countrymen are a load of wimps who can't get together to do any better anyway, preferring to play football or rugby rather than work together - just get at you at work - so I'm stuck with it.




2024-05-21 03:17:09 - Paul D. Foy -
Microsoft's strategy is less giving than this - more American colonial power. It is not easily possible for a third party to build a business on Microsoft technologies without the business continually re-aligning itself with the latest Microsoft technologies. Thus I cannot use . NET framework 4. 8 and expect to be able to give it to someone who is building on a subsequent . NET framework version ad infinitum. I have to be continually updating my product to align itself with the new framework. All the distinguishing features of the dll that I sold are in the graphics and these are precisely the features that have been made redundant in subsequent . NET versions. It's not just an arms race in military technologies but an arms race in being able to do peaceful positive innovative things (unless you are closely aligned with the big providers). This is not an ideal state of affairs - it is putting pressure on resources and putting pressure on having to be continually doing nugatory things like keeping up with the tech rather than doing more enjoyable things (if you don't enjoy doing the keeping up, or haven't the time to, that is). I'm now thinking Facebook's chaos comes as the price of independence - not so bad then.




2024-05-20 14:47:59 - Paul D. Foy -
This blog and its functionality was completed in a few weeks. During this time the blog was always live the new functionality being added in different stages. At any one time the old functionality was never down and you could always peruse it. If you wanted to imbibe any stage of the new functionality you could only do so by contributing at the level of the new functionality, not retrospectively. I observe (by my own attempts at development) that this seems to be the strategy of Microsoft. However I also observe that attempts to keep up to date with developments by the core providers (Microsoft) are difficult and certainly require the skills of a software engineer. It would be very difficult (for example) for a historian, seeing a weakness in a diagram to dive into some software, some old software to have a better stab at it. So this is not very good. It is deskilling things in some sense but in favour of the skills of the software engineer. Some providers solution (Apple) is to deskill the software knowledge yet at a considerable financial penalty and lack of flexibility to the user. I challenge anyone to use this blog and give me the challenge of coping with increased traffic or newly required functionality.




2024-05-02 08:57:57 - Paul D. Foy -
The irritating insertion of spaces feature mentioned in one of the post comments has now been fixed. So the blog is totally autonomous and you can create textual posts or comment on them to your hearts content without any intervention from Company staff.


Post a comment:

Name:

Password:

Comment:
Enter comment here ...