Comment Re:PR Giveaway (Score 1) 168
Why? It's a country looking to lead the world in censorship, to protect protect politicians and religious sensibilities.
Hang on, we're still talking about India here, right?
Why? It's a country looking to lead the world in censorship, to protect protect politicians and religious sensibilities.
Hang on, we're still talking about India here, right?
Fully rectified 240V AC RMS is already very close to 380V DC
Uh, no. No it isn't. Not even vaguely, in fact. 240V effectively *is* the DC equivalent (ignoring rectification losses), the PMPO (ie. peak voltages your 50 or 60hz sine wave actually hits) will probably be around 380v though. If you want 380VDC, then you need the same or more AC.
If you could program one language, you can program in any language. It's inherent on the Turing-completeness of programming languages. It's all just a matter of syntax. Sure, mastering a language takes time, but you've probably see already much things and that means you can easily apply what you know to the knew languages.
See, I agree with you 100%, more if I could. In my years developing, most of the languages I now use to program are not the ones I was employed to do, but ones where I've been dropped into a project, had to hit the ground running and learn on the fly. It's not difficult, once you know the concepts of *how* to program.
But. Try going in to a job interview and saying "No, I don't have 5 years of this language, but give me a week, some small changes to work on and access to google and I'll be able to program it as well as most of your other developers". It may be true, but it doesn't wash with HR people or project managers. They have a ticksheet of skills and levels and they don't care a damn how easily transferrable any of them are - if you don't have it exact, tough.
But that's not primarily what's holding back a 1.0 release. The real thing I
want to do first is to sort out the data storage: there are quite a few
features on the wish list which would require a revamp of that, such as
- ability to store some settings in HKEY_CURRENT_USER and others in
HKEY_LOCAL_MACHINE, so that a sysadmin could set up some default saved
sessions and a default host key cache which would then be the starting point
for each user's personal configuration
- inheritable saved sessions (so that when I change, say, my font preference
in Default Settings it automatically propagates to all my other sessions
_except_ those in which I've specifically asked for a non-default font)
- storing configuration in a disk file as an alternative to the registry (so
that people can carry around PuTTY plus their config file on a USB stick)
- ability to configure all PuTTY's options from the command line (rather than
having to do a lot of them by the cumbersome method of creating a saved
session and using -load).
Now I'm not saying I want to have _implemented_ all those features before 1.0,
but I want to have made a commitment to a data storage format which is capable
of supporting them. Currently PuTTY's data storage only tries to be upward-
compatible, meaning that you can upgrade PuTTY and it'll still work with your
old settings. Use an older PuTTY with newer settings, and you're on your own.
My goal is that within the 1.0 series, the data storage should be compatible in
_both_ directions. (Not because I anticipate people deliberately downgrading
PuTTY, although it's been known occasionally, but because I can easily imagine
people using different versions on two machines which happen to be sharing a
network-stored configuration.)
Saliva causes cancer, but only if swallowed in small amounts over a long period of time. -- George Carlin
