yes, so export the binary file to text files.. not difficult
It is if the logged system won't boot any more.
The NEXT step in opacity beyond binary files is to do something like embed them in an all-in-one database a la the Windows Registry. Ever tried to restore a single application AND its runtime settings and context on a Windows system when the app kept all the goodies in the Registry?
Do that, and even exporting the binary to another binary-compatible system for conversion (if one is handy) is going to be frustrating. As it is, conversion to text already adds a step which may be ill-appreciated when you're operating in a panic environment.
I worked with binary log files in OS/2. I don't want to do that again.
behave like Boston did after the Marathon bombings... HIDE IN YOUR HOUSE AND TREMBLE IN FEAR.
Because having the streets awash in people while a manhunt is in progress does what?
Sometimes one's place in the militia is out of the way of the people trained to do the hunting. Stay home so the fugitive(s) stand out. Fondle your gun collection if you like instead of trembling. Hell, if the bad guy attempts to break in, shoot him. Just don't muddy the waters. If you feel that staying out of the picture is too cowardly, get trained and deputized.
Here's the example that we both really understood. She wanted some field added to some web application. In her head, it's a simple field... you know like adding a new column in Excel.
"All You Have To Do Is..."
The most deadly words in Information Technology.
A lot of the missed deadlines and cost overruns are because of the AYHTDI effect. Because people won't believe that the jobs isn't as simple and straightforward as it appears in their pointy little heads. They forget - and worse yet - the DEVELOPERS forget that computers are STUPID. And that you have to allow extra time and effort to take what's a simple job for humans and make it simple enough for computers.
And to compound the issue, no one wants to hear a reasonably accurate resource estimate. They'll pressure you until you give one that they can believe, no matter how unrealistic it is.
That, indeed is one advantage of the Agile approach. By breaking up the project into smaller milestones, it means that the amount of estimate deflation in absolute terms is reduced. And it means that people don't expect it to be perfect within 6 weeks.
I'll save the maintenance cost rant for another time. The deadly phrase there is "If it ain't broke, don't fix it".
Grid based layout is a standard of just about every UI engine for a reason we like stuff to line up, we like stuff to scale gracefully, and grid based systems work very well for both. "But.. but.. in html tables were made for text" I can hear some web dev whine. That doesn’t mean the whole concept of grid based layout should be tossed out and replaced by the clusterfuck that is CSS layout.
Simple things like a complex form, which would be trivial with a grid (and are trivial with tables) are an epic pain with CSS layouts. And what great benefit has it given us? Panels that float around the screen (and break if something is resized, zoomed in, or a block of text is larger than expected).
And detaching content from style epic failure. The oft referenced CSS Zen Garden is to me an illustration of exactly how CSS failed at this goal. The layout is still being largely defined by the HTML. You can only _somewhat_ adjust how things are positioned in relation to each other with CSS, which requires you to have multiple layers of nested <div id="random_section_that_you_might_use_for_something_or_not"> to give the kind of flexibility that CSS Zen Garden does. Actually take a look at the HTML for those pages. This is not an example of how things should be done.
Well, after all, it's Cascading style Sheets. There's nothing in CSS itself that actually bounds an area - it has to borrow a container from HTML, be it DIV, TABLE, BODY, or whatever and define space within or relative to it.
I never bought into the "don't use tables" nonsense myself. Tables provide abstract organization of layout. It's a lot cleaner to apply some CSS to a table than to shoehorn it in to a whole lot of divs just for maintaine Ideotlogical Purity..
lol "Syntax that every programmer uses to make their program readable is unreasonable as a semantically meaningful syntax"
Come on, python's got its problems, but forcing you to lay out your program in a naturally readable way to compile isn't one of them.
For example, duck-typing might be one of the worst ideas in the universe, because it's doing the exact opposite of the whitespace thing. It's decoupling easy-to-make mistakes with the output of compiling of your code.
But this whining about whitespace just comes off as having never actually tried it.
No, whining about whitespace is what you do when people use tab characters.
Because python treats tabs and blanks as identical characters, but they don't indent the same. Especially when fed to different formatters.
It's quite easy to create a python program that when printed or displayed looks perfectly fine but is a total train wreck when executed because of these literally invisible differences.
The only thing that makes it even remotely tolerable is that most editors have a Python mode that's sensitive to such misdemeanors.
That's just it you can hire those jobs out as needed. You call them as needed as they are small shops like yourself.
We don't have an IT tech on site. we pay someone to monitor for viruses, and provide updates and to watch backups. They don't have access to the main database itself just the files. We call them when we add or remove employees. We talk to them maybe twice a month.
people on slashdot say they can replace half the managers they work for with a script. They never realize what that actually means when you do though.
The flip side is the old Economies of Scale. A small business won't need these people full-time, but will generally pay a retainer plus fees to ensure service when needed. A large business needs people like that more often, so it's cheaper for them to have full-time in-house employees do it.
Oh wait. That was last millenium. I meant to say "it's cheaper for them to have people in a Third-World nation do it".
However you aren't the one who gets to define "innocent".
No, society does.
Of course. "Society" is just another way of saying "other people with more power than you," where "power" can be political or financial or even just the power of being in the majority—none of which justifies the violation of your rights as an individual.
The joke's on him. He thinks he's "Society". Society might think otherwise.
Well, when you invent the grandparents that don't need tech handholding, I'll be lined up outside your store to buy a pair!
Meanwhile, I just spent a weekend hanging a TV from a wall for a relative who's actually pretty handy, but will be recovering for surgery for some time. People will always need help of one sort or another from one another, and there's always ways in which skilled labor can make each of our lives better.
Robots will replace unskilled labor - and more power to them - but those jobs suck anyway.
Hanging a TV from a wall isn't skilled labor. And, in fact, a TV-hanging robot would probably not be a bad thing to own, if you're Best Buy or somebody like that.
Wait and see what Japan does over the next few decades. They have a high proportion of baby boomers heading into retirement, with longer life expectancy than ever before, and low fertility rates. There should be far more people leaving the workforce than entering right about now. My guess is the people who still work by 2025 work will have to pay more tax than they do now to cover social welfare for those that don't, and the people without work will have to learn to live on less (smaller apartments, fewer gadgets, public transport, etc...) so as to be a smaller burden on those that still work. Less consumption all around. Probably need an entirely new economic model to keep a country running like that.
You picked a bad set of examples.
Japan is famous for small aparments, intense use of public transport, etc. Gadgets, on the other hand...
In the future I expect more and more small businesses and boutiques. You can run a small yet profitable business with just two or three people.
Never mind that you are operating in a high-failure part of the private sector with people that cannot really afford to fail. That, and you have no scale to offset purchase costs, especially those relating to benefits.
You don't need an army of accountants, managers or other people who provide only a drain on resources for no increase in value.
Just try and run a small business without retaining an accountant or lawyer. Or these days, a computer tech.
Yes, you can do it all yourself, but if you do, you won't have time to do what you do well. And you'll have a half-rate accountant, a failure for a lawyer and an incompetent security menace for a computer tech, unless you happen to have talent in those fields.
Only if you don't like the benefits coming from economies of scale. Those disappear even in the ACA.
Considering that one of the primary ideas behind the ACA was to scale up the insured base to be the entire nation instead of merely those who are employed by large companies, something's gone wrong with the economies of scale part, then.
This tired old quote is always posted without any thought or analysis. It's dumb. We trade liberty for security all the time. The police are allowed to arrest people based on probable cause.
It's not dumb. It's precise. essential Liberty. For a little safety.
Ben Franklin was a model businessman and knew that you shouldn't sell cheap things that are dear. You won't be able to buy them back at the same price.
You are correct on the last, but not the preceeding items. I had the opportunity to talk about it with Carl J. Sasserath himself. IIRC, he was actually inspired by Smalltak, but don't take that as immutable truth.
The Amiga's OS consisted of several layers. The Exec, AmigaDOS, and the GUI, which internally subdivided into the layer and window systems. Everything was very modular.
AmigaDOS was indeed written in the "British Cruddy Programming Langue" based on a thesis project named Tripos. However, it was jammed on top of Exec, which was written in C. The results were occasionally awkward, as BCPL used word-based addressing and C was byte-based. Plus the BCPL and C stacks grew in opposite directions.
The C compiler used was Green Hills C, cross-compiling off Sun or Apollo Unix machines (again, memory is hazy here). Manx was the first C compiler native for the Amiga, followed by Lattice C. Manx was probably a Macintosh port, as it worked with 16 bit integers. Lattice worked with 32-bit integers, which was a more natural fit for the machine. Eventually, the 2 compilers adopted support for each other's word sizes and all became happy (more or less). By that point, Commodore was doing native development and no longer needed to cross-compile.
The Amiga OS source code had no embedded assembler that I'm aware of. Embedded assembler is a hallmark of complex monilithic systems. Exec was very minimalistic and so far as I am aware, the assembler components (primarily scheduler and interrupt services) were all separate source modules. The C compilers did add pragma directives to allow passing parameters in registers instead or (or in addition to) on the stack, support for volatile variables (for memory-mapped I/O devices) and similar.
C++ first began to get public notice about August 1986, which is when Amiga computers began to hit the street in quantity. But despite not being written in C++, Amiga's Exec mapped very well to it.
Check out the Wikipedia entry for Carl Sassenrath. I believe it has a link to a BYTE magazine article that discusses this.
An interesting thing about the Amiga's OS was that you could run a workhorse machine with GUI in 6MB of RAM. The equivalent port of Linux to the Amiga required 16MB. However, the Amiga's OS didn't support virtual memory, as the earlier Motorola 68000-series processors didn't have an MMU.
How many datacenters are there up and down the west coast of the united states? We have 4.x quakes several times a year. What's the big deal? Hell, there was a 7.0ish here in Tacoma about 10 years ago.
This is Bangladesh. Remember how buildings in Bangladesh are? In a country noted for corruption?
Add anti-virus. Have "fast search" caches begin to populate themselves. Other "services" begin to chime in. System maintenance services run. It's a wonder Windows ever actually gets to a usable mode at all.
Your server isn't getting games installed on it, which put all kinds of settings in the registry, then removed later when the game is old and tired, leaving behind cruft (including DRM bullsit) in the registry.
When a program is UNinstalled, all traces of it should be gone. Apple took a different approach, which arguably works far better. Even if stuff is left behind, it just takes up a bit of disk space, and doesn't affect the system at all.
You'd think so, but it's pretty common to uninstall a broken program, then re-install it. Keeping the old parameter settings makes it easier (sometimes!) to re-install, since you don't have to set it all up from scratch. Network settings are a case where I often benefitted from this behavior.
Then there's shared files and components such as DLLs. It's often quite difficult to reliably determine when the last using application has been removed, especially if people have been brute-forcing stuff instead of using the control panels and installers that keep count.
Still, I wouldn't mind having a "nuke" option that would at least remove all the files that belong exclusively to the app for cases where there's no possible reason why they would ever be referenced again. Murphy notwithstanding.
Slashdot Mirror
Put more simply:
Corporations allow a privileged few to speak twice when ordinary people can only speak once.
And to say things that not all of the members of the corporation might agree with.
You mean like the common American 'Rent a Cop' who wears his government supplied uniform and weapons while off shift?
Locally, he also wears his duties and responsibilities along with them. Just on someone else's dime.
BTW, you forgot the car. He (or she) usually gets to keep the car, too.
yes, so export the binary file to text files.. not difficult
It is if the logged system won't boot any more.
The NEXT step in opacity beyond binary files is to do something like embed them in an all-in-one database a la the Windows Registry. Ever tried to restore a single application AND its runtime settings and context on a Windows system when the app kept all the goodies in the Registry?
Do that, and even exporting the binary to another binary-compatible system for conversion (if one is handy) is going to be frustrating. As it is, conversion to text already adds a step which may be ill-appreciated when you're operating in a panic environment.
I worked with binary log files in OS/2. I don't want to do that again.
behave like Boston did after the Marathon bombings... HIDE IN YOUR HOUSE AND TREMBLE IN FEAR.
Because having the streets awash in people while a manhunt is in progress does what?
Sometimes one's place in the militia is out of the way of the people trained to do the hunting. Stay home so the fugitive(s) stand out. Fondle your gun collection if you like instead of trembling. Hell, if the bad guy attempts to break in, shoot him. Just don't muddy the waters. If you feel that staying out of the picture is too cowardly, get trained and deputized.
no it's not a real war. Copying a Word document is completely unequal to dropping a bomb on a village or shooting somebody in the head.
Shame on you for equating the two - stop being a sociopath.
True. The pen is mightier than the sword.
User Identified.
Welcome, Stephen Hawking.
Here's the example that we both really understood.
She wanted some field added to some web application. In her head, it's a simple field... you know like adding a new column in Excel.
"All You Have To Do Is..."
The most deadly words in Information Technology.
A lot of the missed deadlines and cost overruns are because of the AYHTDI effect. Because people won't believe that the jobs isn't as simple and straightforward as it appears in their pointy little heads. They forget - and worse yet - the DEVELOPERS forget that computers are STUPID. And that you have to allow extra time and effort to take what's a simple job for humans and make it simple enough for computers.
And to compound the issue, no one wants to hear a reasonably accurate resource estimate. They'll pressure you until you give one that they can believe, no matter how unrealistic it is.
That, indeed is one advantage of the Agile approach. By breaking up the project into smaller milestones, it means that the amount of estimate deflation in absolute terms is reduced. And it means that people don't expect it to be perfect within 6 weeks.
I'll save the maintenance cost rant for another time. The deadly phrase there is "If it ain't broke, don't fix it".
Grid based layout is a standard of just about every UI engine for a reason we like stuff to line up, we like stuff to scale gracefully, and grid based systems work very well for both. "But.. but.. in html tables were made for text" I can hear some web dev whine. That doesn’t mean the whole concept of grid based layout should be tossed out and replaced by the clusterfuck that is CSS layout.
Simple things like a complex form, which would be trivial with a grid (and are trivial with tables) are an epic pain with CSS layouts. And what great benefit has it given us? Panels that float around the screen (and break if something is resized, zoomed in, or a block of text is larger than expected).
And detaching content from style epic failure. The oft referenced CSS Zen Garden is to me an illustration of exactly how CSS failed at this goal. The layout is still being largely defined by the HTML. You can only _somewhat_ adjust how things are positioned in relation to each other with CSS, which requires you to have multiple layers of nested <div id="random_section_that_you_might_use_for_something_or_not"> to give the kind of flexibility that CSS Zen Garden does. Actually take a look at the HTML for those pages. This is not an example of how things should be done.
Well, after all, it's Cascading style Sheets. There's nothing in CSS itself that actually bounds an area - it has to borrow a container from HTML, be it DIV, TABLE, BODY, or whatever and define space within or relative to it.
I never bought into the "don't use tables" nonsense myself. Tables provide abstract organization of layout. It's a lot cleaner to apply some CSS to a table than to shoehorn it in to a whole lot of divs just for maintaine Ideotlogical Purity..
lol
"Syntax that every programmer uses to make their program readable is unreasonable as a semantically meaningful syntax"
Come on, python's got its problems, but forcing you to lay out your program in a naturally readable way to compile isn't one of them.
For example, duck-typing might be one of the worst ideas in the universe, because it's doing the exact opposite of the whitespace thing. It's decoupling easy-to-make mistakes with the output of compiling of your code.
But this whining about whitespace just comes off as having never actually tried it.
No, whining about whitespace is what you do when people use tab characters.
Because python treats tabs and blanks as identical characters, but they don't indent the same. Especially when fed to different formatters.
It's quite easy to create a python program that when printed or displayed looks perfectly fine but is a total train wreck when executed because of these literally invisible differences.
The only thing that makes it even remotely tolerable is that most editors have a Python mode that's sensitive to such misdemeanors.
That's just it you can hire those jobs out as needed. You call them as needed as they are small shops like yourself.
We don't have an IT tech on site. we pay someone to monitor for viruses, and provide updates and to watch backups. They don't have access to the main database itself just the files. We call them when we add or remove employees. We talk to them maybe twice a month.
people on slashdot say they can replace half the managers they work for with a script. They never realize what that actually means when you do though.
The flip side is the old Economies of Scale. A small business won't need these people full-time, but will generally pay a retainer plus fees to ensure service when needed. A large business needs people like that more often, so it's cheaper for them to have full-time in-house employees do it.
Oh wait. That was last millenium. I meant to say "it's cheaper for them to have people in a Third-World nation do it".
However you aren't the one who gets to define "innocent".
No, society does.
Of course. "Society" is just another way of saying "other people with more power than you," where "power" can be political or financial or even just the power of being in the majority—none of which justifies the violation of your rights as an individual.
The joke's on him. He thinks he's "Society". Society might think otherwise.
I guess I was surprised that Adobe has an ereader app. Yet another reason to not use Adobe's products.
Overdrive.
Adobe's e-reader REQUIRED if you want to check out e-books from most libraries.
Well, when you invent the grandparents that don't need tech handholding, I'll be lined up outside your store to buy a pair!
Meanwhile, I just spent a weekend hanging a TV from a wall for a relative who's actually pretty handy, but will be recovering for surgery for some time. People will always need help of one sort or another from one another, and there's always ways in which skilled labor can make each of our lives better.
Robots will replace unskilled labor - and more power to them - but those jobs suck anyway.
Hanging a TV from a wall isn't skilled labor. And, in fact, a TV-hanging robot would probably not be a bad thing to own, if you're Best Buy or somebody like that.
Wait and see what Japan does over the next few decades. They have a high proportion of baby boomers heading into retirement, with longer life expectancy than ever before, and low fertility rates. There should be far more people leaving the workforce than entering right about now. My guess is the people who still work by 2025 work will have to pay more tax than they do now to cover social welfare for those that don't, and the people without work will have to learn to live on less (smaller apartments, fewer gadgets, public transport, etc...) so as to be a smaller burden on those that still work. Less consumption all around. Probably need an entirely new economic model to keep a country running like that.
You picked a bad set of examples.
Japan is famous for small aparments, intense use of public transport, etc. Gadgets, on the other hand...
In the future I expect more and more small businesses and boutiques. You can run a small yet profitable business with just two or three people.
Never mind that you are operating in a high-failure part of the private sector with people that cannot really afford to fail. That, and you have no scale to offset purchase costs, especially those relating to benefits.
You don't need an army of accountants, managers or other people who provide only a drain on resources for no increase in value.
Just try and run a small business without retaining an accountant or lawyer. Or these days, a computer tech.
Yes, you can do it all yourself, but if you do, you won't have time to do what you do well. And you'll have a half-rate accountant, a failure for a lawyer and an incompetent security menace for a computer tech, unless you happen to have talent in those fields.
Only if you don't like the benefits coming from economies of scale. Those disappear even in the ACA.
Considering that one of the primary ideas behind the ACA was to scale up the insured base to be the entire nation instead of merely those who are employed by large companies, something's gone wrong with the economies of scale part, then.
This tired old quote is always posted without any thought or analysis. It's dumb. We trade liberty for security all the time. The police are allowed to arrest people based on probable cause.
It's not dumb. It's precise. essential Liberty. For a little safety.
Ben Franklin was a model businessman and knew that you shouldn't sell cheap things that are dear. You won't be able to buy them back at the same price.
If you aren't doing anything illegal online (pirating, illegal pornography, planning terrorism) these laws won't affect you
Remember, innocent people have nothing to fear.
However you aren't the one who gets to define "innocent".
You are correct on the last, but not the preceeding items. I had the opportunity to talk about it with Carl J. Sasserath himself. IIRC, he was actually inspired by Smalltak, but don't take that as immutable truth.
The Amiga's OS consisted of several layers. The Exec, AmigaDOS, and the GUI, which internally subdivided into the layer and window systems. Everything was very modular.
AmigaDOS was indeed written in the "British Cruddy Programming Langue" based on a thesis project named Tripos. However, it was jammed on top of Exec, which was written in C. The results were occasionally awkward, as BCPL used word-based addressing and C was byte-based. Plus the BCPL and C stacks grew in opposite directions.
The C compiler used was Green Hills C, cross-compiling off Sun or Apollo Unix machines (again, memory is hazy here). Manx was the first C compiler native for the Amiga, followed by Lattice C. Manx was probably a Macintosh port, as it worked with 16 bit integers. Lattice worked with 32-bit integers, which was a more natural fit for the machine. Eventually, the 2 compilers adopted support for each other's word sizes and all became happy (more or less). By that point, Commodore was doing native development and no longer needed to cross-compile.
The Amiga OS source code had no embedded assembler that I'm aware of. Embedded assembler is a hallmark of complex monilithic systems. Exec was very minimalistic and so far as I am aware, the assembler components (primarily scheduler and interrupt services) were all separate source modules. The C compilers did add pragma directives to allow passing parameters in registers instead or (or in addition to) on the stack, support for volatile variables (for memory-mapped I/O devices) and similar.
C++ first began to get public notice about August 1986, which is when Amiga computers began to hit the street in quantity. But despite not being written in C++, Amiga's Exec mapped very well to it.
Check out the Wikipedia entry for Carl Sassenrath. I believe it has a link to a BYTE magazine article that discusses this.
An interesting thing about the Amiga's OS was that you could run a workhorse machine with GUI in 6MB of RAM. The equivalent port of Linux to the Amiga required 16MB. However, the Amiga's OS didn't support virtual memory, as the earlier Motorola 68000-series processors didn't have an MMU.
If you want to know why C++ sucks for operating systems design, look at COM.
If you want to know why C++ is great for operating systems design, look at the Amiga Exec.
Which actually was written in C, but mapped flawlessly onto C++.
COM isn't object-oriented. You never actually had a handle on the object itself, just an interface.
I take it you missed this "minor" incindent, then:: http://www.theguardian.com/wor...
Anyway, good building standards don't count if you can easily bribe the inspectors.
How many datacenters are there up and down the west coast of the united states? We have 4.x quakes several times a year. What's the big deal? Hell, there was a 7.0ish here in Tacoma about 10 years ago.
This is Bangladesh. Remember how buildings in Bangladesh are? In a country noted for corruption?
I was totally good with storing private customer data in Bangladesh before.
How good are you about your own private data being stored in Bangladesh?
Whoosh!
Anyway with a username like "sociocapitalist", shouldn't you be advocating storing information wherever it's cheapest?
Add anti-virus. Have "fast search" caches begin to populate themselves. Other "services" begin to chime in. System maintenance services run. It's a wonder Windows ever actually gets to a usable mode at all.
Not really. It's just bad design.
Your server isn't getting games installed on it, which put all kinds of settings in the registry, then removed later when the game is old and tired, leaving behind cruft (including DRM bullsit) in the registry.
When a program is UNinstalled, all traces of it should be gone. Apple took a different approach, which arguably works far better. Even if stuff is left behind, it just takes up a bit of disk space, and doesn't affect the system at all.
You'd think so, but it's pretty common to uninstall a broken program, then re-install it. Keeping the old parameter settings makes it easier (sometimes!) to re-install, since you don't have to set it all up from scratch. Network settings are a case where I often benefitted from this behavior.
Then there's shared files and components such as DLLs. It's often quite difficult to reliably determine when the last using application has been removed, especially if people have been brute-forcing stuff instead of using the control panels and installers that keep count.
Still, I wouldn't mind having a "nuke" option that would at least remove all the files that belong exclusively to the app for cases where there's no possible reason why they would ever be referenced again. Murphy notwithstanding.