I enjoy reading your blog, keep on writing
Moderators: fgagnon, nikos, Site Mods
- pschroeter
- Silver Member
- Posts: 283
- Joined: 2007 Jan 27, 00:46
I enjoy reading your blog, keep on writing
I have read a few of your blog entries and I think you have a pretty good knack for making computer technical topics accessible. I hope in one of your future articles you cover the Windows Registry. After Microsoft's strange ideas of how computers should interact with their users, I sometimes get the feeling that the Registry is the source of of many computer problems at their most basic level. I can't understand why on earth it is necessary in the first place. I cannot understand why everything a particular program needs can't be stored in one spot, in the program's folder. Why are program installers and the add/remove control panel necessary? Maybe I just made more than one suggestion for future blog topics.. On the a 1 to 10 computer nerd scale I rate a solid 5, but reading your blog is raising me towards a 6, so please keep writing your blog.
Paul A.
Paul A.
- FrizzleFry
- Platinum Member
- Posts: 1241
- Joined: 2005 Oct 16, 19:09
is there a hidden agenda here?
first of all, the registry provides easy ways to have tree-like (nested) storage of settings, whereas INI files are flat. Then, the way x2 currently does "layouts" means that we'll need a ridiculously complicated INI file or series of INI files to store all the parallel settings. Finally, as long as there's a combined 21 day trial + unlocked version in one file, x2 would have to hit the registry (& other parts of the PC) regardless of INI files.
first of all, the registry provides easy ways to have tree-like (nested) storage of settings, whereas INI files are flat. Then, the way x2 currently does "layouts" means that we'll need a ridiculously complicated INI file or series of INI files to store all the parallel settings. Finally, as long as there's a combined 21 day trial + unlocked version in one file, x2 would have to hit the registry (& other parts of the PC) regardless of INI files.
- FrizzleFry
- Platinum Member
- Posts: 1241
- Joined: 2005 Oct 16, 19:09
- FrizzleFry
- Platinum Member
- Posts: 1241
- Joined: 2005 Oct 16, 19:09
-
- Silver Member
- Posts: 281
- Joined: 2006 Dec 29, 12:56
- Location: Utrecht, NL
Hi all,
I second what pschroeter said above. The blogs are great - entertaining and informative. If anyone hasn't read them you should. My favorite blog quote:
"...surely "explorer" and "efficient" in the same sentence is a contradiction in terms."
LOL! So true! I mean seriously, do their in-house developers/admins use explorer? It's obviously as dumbed-down as possible, as with most of the built-in tools in windows. That's ok for the masses, but for people who want to efficiently get work done, there is X².
Thanks nikos!
I second what pschroeter said above. The blogs are great - entertaining and informative. If anyone hasn't read them you should. My favorite blog quote:
"...surely "explorer" and "efficient" in the same sentence is a contradiction in terms."
LOL! So true! I mean seriously, do their in-house developers/admins use explorer? It's obviously as dumbed-down as possible, as with most of the built-in tools in windows. That's ok for the masses, but for people who want to efficiently get work done, there is X².
Thanks nikos!
Actually, the defacto (and recommended by MS) standard for storing configuration information nowadays is a structured XML file located in the folder of the logged in user. Flat INI files are a relic from the past (as is the registry actually).nikos wrote:i was thinking about writing a class that makes registry and INI files behave similar (it's not rocket science but neither trivial) but then thought that registry will have to be used somehow anyway so it would be a futile exersice!