Yes, the research document specifically mentions Foxit as well as Acrobat.
so, PDFs, not just one application.
Also, although they only fussed Word documents, they used a VBA binding. Somebody is going to try their tool on Excel.
2375 publicly visible posts • joined 6 Jul 2009
Yes, it's obvious that the are trying to recreate a phone interface as your desktop gui.
It became popular after Apple changed the osX vertical scroll bar direction to match that on the iPhone. Which you could sort of understand, because the iPhone and iPad were more popular than their desktop offering.
And understanding the design heritage, you can understand that it's a stupid idea, and it sucks.
The early MSDOS (and PCDOS) manuals were very good, "well-organised, covered so much stuff in a very readable manner and were full of examples and as much technical information as one could imagine."
As were many other op systems at the time. Of course, DOS (and many of the other op systems) were really simple, with nothing more complex in the MS DOS 2.x manuals than how to write a device driver using edlin and debug.
unix really was the standout exception, where (in spite of the man pages), the standard way of learning the OS was to learn at the feet of a guru.
It was a jury trial, with damages set by the jury.
Civil jury trials always can have odd results, and damages are always large, compared to judge-only trials, in any jurisdiction, not just Virginia, not just the USA.
It is one of the reasons so many large American companies are registered in Delaware (more companies than residents). Delaware doesn't have civil jury trials.
BASIC was never designed to help people become programmers. It was designed to allow other professionals to use computers without requiring programmers. It was the Google and the WWW of the day: the power of modern computing without the high-level specialists. The line-by-line compilation, the time sharing system and personal user terminals were the web browsers and AI of the day.
At the time there was a split between the SF idea of computers as intelligent thinking machines, and the real world idea of computers that they were big calculators, tabulators, or accounting machines. The world of computing laughed at Kemény for wanting to put computers into the hands of humanities and social science undergraduates: they laughed at Kurtz for thinking it was possible.
It turned out that that BASIC as a user interface was so good that it was adopted by people who's full-time job as 'programmer', with enterprise solutions written in BASIC, and applications written in BASIC for portability, but the intention of BASIC was to make computers available to musicians and anthropologists and authors and every other kind of liberal-arts undergraduate.
Somewhere around 50 years ago I read with interest a Bulletin Board thread discussing if computers should be turned of (saves thermal hours) or left on (saves start up stress). These threads used to run for weeks because users would only login perhaps once per week.
The thread was effectively terminated by two guys, who wrote, respectively,
1) I used to leave my computer on, then one day while I was working, the side of the monitor turned brown, smoked, and flamed. Now I always turn the computer off when I leave the room.
2) I used to leave my computer on, then one day while I was working, a gout of flame erupted from the power supply at the back and ignited my curtains. Now I always turn the computer off when I leave the room.
And ten years after that, I worked for a fire-alarm company, who reported that the most common cause of office fires was computers.
They use non-flammable plastic now, and computers sleep when not in use, but back in the day....
Back in the day, systems analysts used to use a pen to fill out coding sheets, passed to the key-punch operators to type out. Hence, languages like COBOL.
But c programmers didn't have to do that. They could hunt-and-peck directly on their dedicated serial-terminal. Hence languages like c, which saved keystrokes by using single symbols like }, found on the edges of the keyboards they were using.
And languages like Hare, using contractions like "fn"
Worker: "There is a problem here"
Management: "Don't talk to me until you have a solution:
Worker: "I've got a solution to this problem"
Management: "Don't waste company time working out a solution until you have approval from me"
Worker: "It would be good if something were different"
Management: "I like things exactly like they are, and I'm here until retirement."
It's much messier in AUS, but built-in call recording is clearly illegal.
The messy bit is that there is a whole bunch of hidden carve-outs that aren't mentioned in the telecommunications law.
For example, if you phone a police station, you are recorded. No message, not exemption shown in the telecommunications act, but the recording will be played in court.
Which is another messy carve out: in addition to the telecommunications act restriction on connected recording devices, there are a bunch of 'privacy' restrictions which are different in every state. The 'privacy' restrictions mean that you have to treat the data like private data, authorized and protected and not shared. Except when you got to court. Courts consider themselves above stuff like privacy laws, so that unauthorized recording which would be illegal in every other context, may be offered as evidence in court.
"It's insecure" is a myth perpetuated by the ignorant. It's prolix, and after being moved to tcp/ip, and having had encryption and authenticated added, it has high latency, which is an issue because it's prolix. Because it's prolix, and because the modern implementation has such high latency, it's been replaced by SMB2, which is less prolix, and has lower latency.
That means that the SMB1 servers and clients are falling out of support. The o/s version on my SMB1 NAS has been out of support many years: even on my ancient hardware, it's moved from 3.x to 5.x.
"Server falling out of support" is insecure, not "SMB1" is insecure.
And, as demonstrated here, most of the those SMB1 servers are appliances, and are the reason why MS has been slow to discontinue SMB1.
MS has native Network File System drivers, and I've had them installed since Win2K. I haven't used them for anything other than testing, since NFS is light-weight feature-poor Network system, but the feature has always been there for server systems, and sometimes for pro or home systems.
I think that NFS for Windows turned up even earlier, but I personally never ran earlier versions of NT, and I think it was originally developed by a third party.
Since some configuration variables (such as core.fsmonitor) cause Git to execute arbitrary commands, this can lead to arbitrary command execution when working on a shared machine.”
Git runs arbitrary commands from arbitrary locations.
Yes, it you want per-user config, it should be stored in protected per-user storage, and it you want arbitrary commands, they should be in trusted locations,
In a properly configured native program, the trusted locations would also be configured in trusted per-user storage. But the world does seem to be drifting away from properly configured multi-user PCs: most of my users consider 'sharing a PC' to be on a level with 'sharing a toothbrush' or 'sharing underwear'.
It's logistics. The whole point is to build without having any trades or special materials. This isn't about building a better building, or even a cheaper building: it's about building with generic material and generic labour, so that you don't have to store or transport particular items. Just like the whole of NATO uses one rifle bullet, so you never have the wrong bullet.
(because I've sometimes wondered).
On Windows, the name on an account (eg 'Administrator') is just a label. The domain administrator account is 0x000001F4. Knowing the SID, it doesn't really matter what the label is, any sophisticated attack can just use the SID and the password. For this reason, the general advice was always that changing the label on the administrator account to something else was probably pointless.
Is it the same in Linux? Is the name 'root' mostly irrelevant? Or is the string 'root' sort of equivalent to a SID?
(On Windows, well-known user names ('pi') should not be used for other accounts that are in an Admin group. random users ('pi') just have random SIDs:, but an easily-guessed account name provides useful information to an attack )
The enormously successful Windows 95, with the distinct window frames, was the result of usability testing. Which was vindicated by it's enormous success and popularity.
Steve Jobs famously didn't like the Win 95 UI, but he was hardly independent -- and even if he had been independent, examination of the Apple Mac OS UI indicates that, for him, it was more important to make the Mac screen 'look good', than it was to make the Mac screen 'work well'.
The Mac was justifiably popular for putting a good representation of the Page up on the Screen. People who had the job of publishing Pages thought that was important. Win95 sacrificed page publishing for clarity: even the fonts were designed to be pixel aligned /on the screen/ for clarity, sacrificing print design.
I was not a fan of Win95. There was a certain amount of general flakyness, demonstrated by the difficulty dong a first installation on a random generic PC. There was a reason for the Mac meme "it just works". But the UI was not one of the problems. The UI was provably superior to X-Windows and to the Mac, justifying the money spent on usability testing.
Fortunately, our eyes are sensitive to the energy emitted from the sun which reaches the surface of our planet: this enables us to use reflected light to see objects around us.
Naturally, solar panels use the same energy emitted from the sun. If you cover your windows with something that absorbs solar radiation at the same frequencies used by our eyes, where all the power is, then you don't have windows. You've just got solar panels.
Unfortunately, half of the solar radiation that reaches a building comes directly from the sun. If you cover the sides of building with solar panels, only the side that faces the sun will receive that solar radiation, and then only to the extent that the panels are broad-side on to the sun. When the sun is high in the sky, it's shining along the length of vertical panels, and they don't actually get much if any sun at all. At morning or night side panels might get some sunlight, if they face in the correct direction, if the sun isn't blocked by hills or other buildings, on a side which faces the sun, although not as much, since the sun has to shine edge-wise through the atmosphere. (We can see in low light conditions, but that's only due to the extraordinary sensitivity or our eyes: solar panels need actual solar energy to produce power).
The other half of the available solar radiation comes from the sky, but that's spread out over the whole sky, again, panels can only get energy from the part of the sky they see, and only to the extend that they are broad-side to that part of the sky. Vertical panels aren't good at that either.
If covering the sides of buildings with solar panels was a good idea, people would already be doing so. They don't because, although it is an /obvious/ idea, it is not a /good/ idea.
It was skedule in rural Victoria (Australia) when I was a kid, and the only person who said shedule in my high school was a teacher from NSW. That and ABC radio, which in the day was very BBC influenced (our capital city radio station was 3LO ...)
But at the time, society was dominated by people who used "American Pronunciation" and "American Spelling" as a guide to which British pronunciation and spelling to avoid, and that may have had an effect on which pronunciation of schedule came to dominate.
Well that linux protocol converter won't be running a current version of Samba.
You can understand why: SMB1 is a complex protocol, and over TCPIP the latency is bad. The only reason MS continued support was to support old unix implementations (they got a mega --- load of criticism for "breaking" open source when they defaulted to more robust authentication protocols), and Samba has reached the same point.
Yes, I had the MS NFS client running on Win98.
But it turned out the using NFS was actually more painful than installing and using the SMB1 client on linux (EEEBuntu) -- NFS doesn't support the record locking features provided by SMB1 -- so for us that was a dead end.
NFS is a very old protocol: there was also a NFS client for Win 3.11
But talk about 'noticing the rest of the world' !!!!
If Richard was not a London-Based London Journalist covering a foreign country, he probably would have noticed that the USA had it's daylight savings Y2K event several years ago, when, for the first time since introduction, the set-in-stone start and end date were shifted.
What they are looking at now is a Y2010 event. "Same as last time, only less important".
In days gone by, in the same country as the Article, we had a monopoly provider. A tech would come out and say 'that's not an equipment fault, it's a supply fault'. Days later, a line tech would come out as say 'no line fault, it's a handset fault'. Weeks later, a technician would come out as say 'that's an exchange fault'. Months later, the fault would mysteriously disappear -- only to resurface next year...
Meanwhile, in the USA, the almost-monopoly provider, AT&T, was notorious for service in the same line as 'I'm from the government, I'm here to help"
DAISY (A bicycle built for two) was one of the first piece of computer music ever generated, and was reported in scientific and technical journals at the time. As HAL's hardware was disconnected, it regressed both physically and mentally to a more primitive computer, doing more primitive tasks. 'Early computer development tasks'., not 'sales demonstration' tasks,
Dramatically, this was also a regression to a more 'child like' state, because 'Daisy' was, at the time of filming, a children's song.
>What changed was the move from coax<
His original had the separate cable interface device.
Metcalf was on record as saying that Ethernet had been invented, and invented, and invented, and that all of the inventors who invented subsequent versions were inventors who invented modern ethernet
Of course there are vulnerabilities -- well known and repeatedly documented buffer overrun errors on all kinds of read-only files, including unix script files. The file recognition system was a well known security vulnerability of unix systems -- so well known that it's been mostly fixed. It's been, what, a decade or more since the last known exploit.
Windows displays the Application right next to the filename in the column labled 'type'. It tells you, right there, what happens to them.
I can understand that people might want to be told twice. Might want to see '.xlsm' as well as 'Calc'. My like to see the file extension as well as seeing what will happen.
But if you can't see what's right in front of you, I can't say that I blame MS for that.
Enterprise installers, and home users, do have internet connections and MS accounts. People installing without internet connections are (1) Not enterprise, or (2) not advertising targets.
If this moves to release, expect MS to not care about the non-revenue-stream users they loose.