I used Photoshop a long time ago on Macintoshes. It was supremely intuitive to use. GIMP today is much worse than Photoshop of old. I've recently paid the Adobe tax (wife has a business that requires it) and the new Photoshop is a nightmare. Current versions of GIMP and Photoshop are both non intuitive and break the expected select/act behavior.
The same is true of illustrator. The current interface is very unclear. I purchased a book to get past the initial confusion.
I don't understand the rationale. They don't explain it. The manuals should perhaps start with a "Look it works like this and here's why" section. It's so much easier to follow the logic of a UI when you understand what the rationale is.
Provided it is CPA and KPA secure (chosen plaintext attack, known plaintext attack) then it's as hard as brute forcing the keys.
However the ANSI X9 series crypto specs and the PCI-DSS stuff, the banks and card processors use are hardly the best available. They might be secure, but without specifics of what crypto profiles the devices were using, you cannot be sure.
As a Brit, yes, the US Office was indeed better than the UK once. The UK one was sufficiently cringeworthy that it was a chore to watch.
But the American Coupling was vastly worse than the UK Coupling. With the same script no less. The UK Coupling was possibly the funniest series ever in any universe.
It seems to work a lot better than applications on win8. The crushingly dump tile/desktop dual personality of Win8 is not keyboard/mouse friendly. The GUI is full of little traps (don't drift to close to a corner!) that will launch you into tile mode. It's then several hunt and clicks to get back to where you were. I'm typing on a Win8 machine right now and I've installed programs with the sole purpose of making the GUI operate like Win 7 and disabling the tile mode traps.
Android pretty much does what you would expect. The mouse works like a mouse and the keyboard injects characters at whatever the current focus is.
But I maintain that it's still not easy. Look at any mildly non trivial example in the linked page, I.E. 23-1 onwards and the code starts to get out of hand. It's not short, clear and readable.
In my caveman mode of CLI use, I use tee liberally to log points along a pipeline. But when things start turning meshy or tree-y, I use IPC. Python has excellent IPC support.
Arse. 35 years are farting around with unix CLIs and I never knew you could do "thing (cmd arg) (cmd arg)". "thing (cmd arg)" I'm completely familiar with.
It's still nothing like a CSP transaction model which is trivial with a few lines of your favourite scripting language.
Imagine for a moment how many children are growing up now with iPads and Android tablets and probably won't be using keyboards at all. Using the command line is as arcane as using punch cards, and inevitably they will be phased out.
For every ipad waving shop assistant scanning the barcodes on products, swiping your card down the side thingy and selling you the goods, there a poor sod somewhere with a keyboard typing in the product descriptions and barcode numbers so they can be printed on labels to be transacted keyboardless later. The keyboard is still part of the process, it has just been removed from the sight of the consumer.
If you are limited to commands that contain only five lower case letters, then the number of possible commands is something like 26 to the power 5 which is over 10 million. It would be difficult to navigate through that many icons. The point-and-click method of using icons is just not as efficient as an alphabet with letters that make up words that make up a language.
Right, but sometimes you might confuse the yyymy command with the yymyy command and that really sucks.
I shit you not: this morning, one of my neck beard coworkers did a command-line sql query ('select * from table') piped through cut, sort, and uniq. Because, hey, 'distinct columns, i, actually, want' and 'order by column' is too much work.
The point is, the best tool for the best job. Sometimes that's the command line, sometimes it's a text editor with regular expressions, and sometimes it's spotify.
I don't know what spotify is. Have I been missing a trick? I usually use the command line, but from time to time I've found a GUI IDE to be nice, like when writing Macintosh applications back before System 7. Will spotify make me a better programmer?
The whole process will never be secure, since humans are involved and implementations will always have holes, but we do have the mathematics to define algorithms that are known secure in very specific ways and we know how to turn that math into algorithms that we can implement. The least we could do is the crypto bit, since it's not that hard to get right just once for the security of everyone using payment cards. Instead we get a whole bunch of stupid PCI-DSS rules that do nothing to enhance the security of payment card transactions.
My understand is not that they like card fraud, but they do *really really* like the current situation regarding liability. I.E. The banks carry none of the liability. If they are provisioning strong crypto and credentials to ensure secure transactions, the liability landscape changes in way that are bound to be worse than the current optimal (as far as the bank is concerned) situation.
Slashdot Mirror
Never used Manga Studio. Is it useful for non Manga things? God I need a decent bitmap manipulation package. Photoshop isn't it.
Um, I do.
I used Photoshop a long time ago on Macintoshes. It was supremely intuitive to use. GIMP today is much worse than Photoshop of old. I've recently paid the Adobe tax (wife has a business that requires it) and the new Photoshop is a nightmare. Current versions of GIMP and Photoshop are both non intuitive and break the expected select/act behavior.
The same is true of illustrator. The current interface is very unclear. I purchased a book to get past the initial confusion.
I don't understand the rationale. They don't explain it. The manuals should perhaps start with a "Look it works like this and here's why" section. It's so much easier to follow the logic of a UI when you understand what the rationale is.
Of course it could just be bad design.
Touche
Provided it is CPA and KPA secure (chosen plaintext attack, known plaintext attack) then it's as hard as brute forcing the keys.
However the ANSI X9 series crypto specs and the PCI-DSS stuff, the banks and card processors use are hardly the best available. They might be secure, but without specifics of what crypto profiles the devices were using, you cannot be sure.
No, the cheese has culture. Literally.
As a Brit, yes, the US Office was indeed better than the UK once. The UK one was sufficiently cringeworthy that it was a chore to watch.
But the American Coupling was vastly worse than the UK Coupling. With the same script no less. The UK Coupling was possibly the funniest series ever in any universe.
YMMV
Probably won't be able to disable SecureBoot. That's what makes it better!
If it is a certified for Windows 8 x86 machine then it MUST be possible to disable SecureBoot. But you probably already knew that.
But I want SecureBoot, provided I control the keys.
It seems to work a lot better than applications on win8. The crushingly dump tile/desktop dual personality of Win8 is not keyboard/mouse friendly. The GUI is full of little traps (don't drift to close to a corner!) that will launch you into tile mode. It's then several hunt and clicks to get back to where you were. I'm typing on a Win8 machine right now and I've installed programs with the sole purpose of making the GUI operate like Win 7 and disabling the tile mode traps.
Android pretty much does what you would expect. The mouse works like a mouse and the keyboard injects characters at whatever the current focus is.
But I maintain that it's still not easy. Look at any mildly non trivial example in the linked page, I.E. 23-1 onwards and the code starts to get out of hand. It's not short, clear and readable.
In my caveman mode of CLI use, I use tee liberally to log points along a pipeline. But when things start turning meshy or tree-y, I use IPC. Python has excellent IPC support.
Arse. 35 years are farting around with unix CLIs and I never knew you could do "thing (cmd arg) (cmd arg)". "thing (cmd arg)" I'm completely familiar with.
It's still nothing like a CSP transaction model which is trivial with a few lines of your favourite scripting language.
That joke was clearly not nearly obvious enough.
Er.. the both-options/tooltip thing was a joke to illustrate how crappy GUIs are.
Anything more than one tee gets out of hand.
Named pipes are not exactly a command line feature.
Both are great, but they only go so far.
A modern GUI would provide a search feature and offer you both versions with tooltips(r) to guide you to the correct choice.
Your notion of "worth" is kind of amusing.
Imagine for a moment how many children are growing up now with iPads and Android tablets and probably won't be using keyboards at all. Using the command line is as arcane as using punch cards, and inevitably they will be phased out.
For every ipad waving shop assistant scanning the barcodes on products, swiping your card down the side thingy and selling you the goods, there a poor sod somewhere with a keyboard typing in the product descriptions and barcode numbers so they can be printed on labels to be transacted keyboardless later. The keyboard is still part of the process, it has just been removed from the sight of the consumer.
If you are limited to commands that contain only five lower case letters, then the number of possible commands is something like 26 to the power 5 which is over 10 million. It would be difficult to navigate through that many icons. The point-and-click method of using icons is just not as efficient as an alphabet with letters that make up words that make up a language.
Right, but sometimes you might confuse the yyymy command with the yymyy command and that really sucks.
I shit you not: this morning, one of my neck beard coworkers did a command-line sql query ('select * from table') piped through cut, sort, and uniq. Because, hey, 'distinct columns, i, actually, want' and 'order by column' is too much work.
The point is, the best tool for the best job. Sometimes that's the command line, sometimes it's a text editor with regular expressions, and sometimes it's spotify.
I don't know what spotify is. Have I been missing a trick? I usually use the command line, but from time to time I've found a GUI IDE to be nice, like when writing Macintosh applications back before System 7. Will spotify make me a better programmer?
But pipes suck big donky balls when you want to connect things in a tree rather than a linear list.
Mind, IDEs don't connect anything to anything.
Sometimes you just need to get off your arse and write a program so the command line doesn't need to be too clever.
The whole process will never be secure, since humans are involved and implementations will always have holes, but we do have the mathematics to define algorithms that are known secure in very specific ways and we know how to turn that math into algorithms that we can implement. The least we could do is the crypto bit, since it's not that hard to get right just once for the security of everyone using payment cards. Instead we get a whole bunch of stupid PCI-DSS rules that do nothing to enhance the security of payment card transactions.
My understand is not that they like card fraud, but they do *really really* like the current situation regarding liability. I.E. The banks carry none of the liability. If they are provisioning strong crypto and credentials to ensure secure transactions, the liability landscape changes in way that are bound to be worse than the current optimal (as far as the bank is concerned) situation.
Or the banks could switch to chip and pin cards and upgrade the crypto sufficiently to make it secure.
Not since Noddy Holder verbally omitted the apostrophe in a song.
.
Not universally. In my business environment, everyone has notebooks, but everyone has a docking station, keyboard, mouse and monitor too.
You can attack old school bioses as well. Just flash it.