I'd say I would rather have Peter's job after he gets promoted. Forget about any and all work responsibilities, go fishing if you want, tell the people higher up how stupid the organization is, fat paycheck on friday.
...90% of the time it is not needed, and it always makes expressing a concept ten times as verbose. In a few, very few, cases it is essential to getting things done, but if you have to ask if you need it you probably don't.
Just like (misused) xml it makes people look productive without needing to be productive. Avoid using it at all costs, in conversations rephrase it in normal language before agreeing/disagreeing, and in general make everyone be explicit about what they mean. As long as you are able to get valuable work done and always ask for clarification "so everyone is on the same page" no one will really be able to object, and eventually people will just stop so they don't have to constantly repeat themselves.
I want to know who has a job where they have so much extra time on their hands that they can debug the source code of their database product.
I would guess that this is more a theoretical reassurance than an in-practice feature. Theoretically if the db broke and I had absolutely no other recourse I could debug it myself. In reality there are a lot of other options to fix the situation faster, but having that last resort available is nice.
I could actually see Google responding to this by using their dark fiber to start an ISP. At that point it would make this whole system confusing as hell, and Google could start charging verizon et al for access to their pages. I'm sure there is a lot of useful data that could be gathered from having direct access to the content of every request someone makes on the internet. At that point I am not really sure which I would rather have, degraded bandwidth for extortion purposes or snooping on my internet traffic for ads.
The problem with that argument is that the options that don't really matter are different from person to person. KDE does not require you to spend hours tweaking the config, it does supply a default. If you don't like it, change it, but at that point you are not talking about the time required to get into a grunt-and-click state.
Well... he did wrote fetchmail... oh never mind...
You forget that he is also the father of open source software, an expert on the art of hackerdom, and I think he helped Al Gore invent the internet. (how else would he be able to write fetchmail and become a computer rockstar?)
Incorporate my work into your product, save millions, don't give a dime back, fine, whatever, it is your right within the license.
Get a ton of money for a support contract then send your client, not support staff, not in house developers, your client to the dev mailing list for a fix, on a project where you have not shown the least bit of good will, fuck you.
Plus, the helpdesk ends up with LEGITIMATE user issues, not 'Wah, I don't want to read the onscreen directions, you do it!'.
So how do nightly images fix stupid users? I am pretty sure that reading any kind of directions is a sin according to Moronotology, and would like to know if you have found a caveat to this.
That's exactly right. See, how things work is that there are three, strictly seperate, formally defined, qualities of life. You have:
Third world countries: Where people are dirt poor, bath, cook, and wash their clothes in rivers of pee and chemical waste, eat dirt pies for lunch and crow for dinner, suffer from rampant disease and have doctors who couldn't find their own assholes with two hands, a map, and a guide.
Developed nations: Where everyone has more or less every need fulfilled, access to the education system is plentiful, and 2-story ranch houses grow on trees, so people give them away to keep them from cluttering up the yard.
The super rich: I have no idea what really goes on here. I have heard tell that they have copyrights and patents on entire colors and smells, enabling an experience of the world that the rest of us simply cannot comprehend. They also have pills to make their farts smell like flowers.
Or maybe there are people who are above the "I-lived-on-earth-and-all-I-got-was-this-distended -stomach" level but not quite ready to move to the suburbs. Perhaps, just perhaps, this laptop is meant to help them develop further so there are more people capable of helping out the extreme low end of poverty.
Then again that makes for a crap sound bite, so maybe you are right after all.
You would think so, but countless cases of "Just click ok to get it off the screen" say otherwise. If IE starts requiring people to perform an additional step to authorize the crap that they want, and they hear some other browser does not, they may well decide to pack up and head to less mentally demanding pastures.
I just picture Taco in a bathrobe and slippers shuffling into "Slashdot Central" when Zonk and the others are out of the room and sitting down and submitting articles until they come back in, slap his hand and lead him back to his room to up his medications.
Some of the OpenSSH freeloaders, like Apple Computer and The SCO Group, are notorious for reaping financial rewards from selling open source software bundled with their proprietary products.
that was written by Jem Matzan, not Theo. Learn to read.
Even if the community would have found another SSH solution, is it really too much to say thank you about it? What about not being popular as a personality makes Theo's work not useful to the community? OpenSSH is a useful tool. Theo is just trying to point out that, as citizen of the open source world, a lot of big names are taking and not giving. Yes, it is their right, no, they are not obliged to help out in any way whatsoever, but it still is a crap way to treat the people around you.
If you can show a customer why product X is better than product Y and how that difference benefits THEM, you'll be able to close the deal.
I agree completely. That said, a suit and tie usually does not hurt. If it buys me credibility with management weenies who actually will object to something because the salesman "didn't look professional" then I will go ahead and suffer through it. Outside of situations like that though, a good salesman should be able to make a sale based on their product, not their clothing.
Why should a C++ program NEVER overload the plus and minus signs? Code taht requires a static definition of addition is clearly making incorrect assumptions about how the language is used, so I'd place the blame there.
The point is that there is very little reason WHY this change would be necessary instead of making a function that accepts these objects as arguments. What is really so different between push(item, array) and array.push(item)? What possible use could it have that is worth breaking looping over items in an associative array? The problem that prototype has is it is trading a useful language feature for dubious benefits.
The ability to extend basic primatives is awesome, but I want to control when that happens.
I believe that everything that is not content, will be delivered using an AJAX based interface in the near future.
Dear god I hope not. AJAX is awesome when the application logic is relatively minor and the feature requirements are low. Gmail is great except that it does not support a lot of the collaboration features that make outlook/groupwise essential for office environments. Writely may work well for high school homework papers but try using it for a college thesis, much less putting together business documentation.
Ajax will probably take over some of the home versions of productivity tools. It does not have the power to handle the feature requirements of anything bigger than that.
I would say that most of the really big number time comparisons are to java, specifically to J2EE. Compared to PHP, especially PHP under a decent web framework, it does not have the same kind of productivity gains. That said ruby on rails is probably a better environment simply due to the quality of the languages involved.
Re:Zope - What RoR wants to be when it grows up.
on
Ruby On Rails Goes 1.1
·
· Score: 2, Insightful
Zope is awesome for the things that zope already does. Extending it involves crawling pretty far into the zope system though.
...when you could just make those images larger and set them as a background for the text? Only reasons I can think of to not do it is that it might require a different color for the link text, and you would waste some space making all the links the same length as the text of the longest one. That said it would take up a lot less space than the current idea.
Wonder if permanent marker will work well on the screens?
You already are in the produce department. See how well the thing holds up under heavy tomato shelling. If that doesn't work, move up the ladder of heavy ordinance: apple, potato, coconut, pineapple, watermelon.
What does it say about this concept that my first thought was of the most entertaining way to disable it using whatever is handy?
If rebooting a machine causes you problematic service downtime, your environment has fundamental problems that need to be addressed.
I would love to live in fairytale land where servers grow on tress, redundancy is easy, and both sessions and data seamlessly switch from one box to another when a system disappears off the network. Until then rebooting a machine will cause service problems of some magnitude. If unrelated services on a system have to be brought down because of fixes applied to a single service that is entirely unacceptable. The answer here is to fix the rebooting, not the possibility of it causing a service interruption.
The difference between restarting some network service that everyone uses, and restarting an entire machine, is usually a matter of semantics.
Semantics and the potential three to four minute time delta while the system starts up, checks its ram, runs other diagnostics, etc. Then there is the additional time to restart the service, plus any other services running on the box. With server hardware and a decent service load you could be looking at 5-10 minutes of downtime while the server reloads. Replication and load balancing are not solutions to everything, especially when you have to buy licenses.
The Real World is interested in *service* uptimes, not *server* uptimes. Scheduled maintenance, patching, etc of servers - assuming your environment is properly designed - should not have any impact on *service* availability.
Again we are back to the fairy tale world of infinite environment construction resources. Given piles of cash to estables X-level of redundancy I could guarantee that service uptime is just about entirely independant of server uptime. Too bad not everyone lives that way. I'm happy that you seem to be so sheltered though.
Slashdot Mirror
I'd say I would rather have Peter's job after he gets promoted. Forget about any and all work responsibilities, go fishing if you want, tell the people higher up how stupid the organization is, fat paycheck on friday.
It used to, but no wanted to be responsible for Integrating changes.
Just like (misused) xml it makes people look productive without needing to be productive. Avoid using it at all costs, in conversations rephrase it in normal language before agreeing/disagreeing, and in general make everyone be explicit about what they mean. As long as you are able to get valuable work done and always ask for clarification "so everyone is on the same page" no one will really be able to object, and eventually people will just stop so they don't have to constantly repeat themselves.
I would guess that this is more a theoretical reassurance than an in-practice feature. Theoretically if the db broke and I had absolutely no other recourse I could debug it myself. In reality there are a lot of other options to fix the situation faster, but having that last resort available is nice.
I could actually see Google responding to this by using their dark fiber to start an ISP. At that point it would make this whole system confusing as hell, and Google could start charging verizon et al for access to their pages. I'm sure there is a lot of useful data that could be gathered from having direct access to the content of every request someone makes on the internet. At that point I am not really sure which I would rather have, degraded bandwidth for extortion purposes or snooping on my internet traffic for ads.
The problem with that argument is that the options that don't really matter are different from person to person. KDE does not require you to spend hours tweaking the config, it does supply a default. If you don't like it, change it, but at that point you are not talking about the time required to get into a grunt-and-click state.
You forget that he is also the father of open source software, an expert on the art of hackerdom, and I think he helped Al Gore invent the internet. (how else would he be able to write fetchmail and become a computer rockstar?)
Get a ton of money for a support contract then send your client, not support staff, not in house developers, your client to the dev mailing list for a fix, on a project where you have not shown the least bit of good will, fuck you.
So how do nightly images fix stupid users? I am pretty sure that reading any kind of directions is a sin according to Moronotology, and would like to know if you have found a caveat to this.
Or maybe there are people who are above the "I-lived-on-earth-and-all-I-got-was-this-distended -stomach" level but not quite ready to move to the suburbs. Perhaps, just perhaps, this laptop is meant to help them develop further so there are more people capable of helping out the extreme low end of poverty.
Then again that makes for a crap sound bite, so maybe you are right after all.
More evidence that at least half of the commentary on slashdot is actually handled by bots. That said it does make for a good code checking system.
Awesome, so we are just now catching up to the fun level of games from ten years ago. Its Lisp all over again.
You would think so, but countless cases of "Just click ok to get it off the screen" say otherwise. If IE starts requiring people to perform an additional step to authorize the crap that they want, and they hear some other browser does not, they may well decide to pack up and head to less mentally demanding pastures.
I think you misspelled world of warcraft.
that was written by Jem Matzan, not Theo. Learn to read.
Even if the community would have found another SSH solution, is it really too much to say thank you about it? What about not being popular as a personality makes Theo's work not useful to the community? OpenSSH is a useful tool. Theo is just trying to point out that, as citizen of the open source world, a lot of big names are taking and not giving. Yes, it is their right, no, they are not obliged to help out in any way whatsoever, but it still is a crap way to treat the people around you.
I agree completely. That said, a suit and tie usually does not hurt. If it buys me credibility with management weenies who actually will object to something because the salesman "didn't look professional" then I will go ahead and suffer through it. Outside of situations like that though, a good salesman should be able to make a sale based on their product, not their clothing.
The point is that there is very little reason WHY this change would be necessary instead of making a function that accepts these objects as arguments. What is really so different between push(item, array) and array.push(item)? What possible use could it have that is worth breaking looping over items in an associative array? The problem that prototype has is it is trading a useful language feature for dubious benefits.
The ability to extend basic primatives is awesome, but I want to control when that happens.
Dear god I hope not. AJAX is awesome when the application logic is relatively minor and the feature requirements are low. Gmail is great except that it does not support a lot of the collaboration features that make outlook/groupwise essential for office environments. Writely may work well for high school homework papers but try using it for a college thesis, much less putting together business documentation.
Ajax will probably take over some of the home versions of productivity tools. It does not have the power to handle the feature requirements of anything bigger than that.
I would say that most of the really big number time comparisons are to java, specifically to J2EE. Compared to PHP, especially PHP under a decent web framework, it does not have the same kind of productivity gains. That said ruby on rails is probably a better environment simply due to the quality of the languages involved.
Zope is awesome for the things that zope already does. Extending it involves crawling pretty far into the zope system though.
...when you could just make those images larger and set them as a background for the text? Only reasons I can think of to not do it is that it might require a different color for the link text, and you would waste some space making all the links the same length as the text of the longest one. That said it would take up a lot less space than the current idea.
That depends, can all the other darts point to the one in the bullseye and say: "Hey, look at the cool thing he did."?
Just make sure to avoid wrinkles and smooth the edges down, otherwise that would just be sloppy work.
You already are in the produce department. See how well the thing holds up under heavy tomato shelling. If that doesn't work, move up the ladder of heavy ordinance: apple, potato, coconut, pineapple, watermelon.
What does it say about this concept that my first thought was of the most entertaining way to disable it using whatever is handy?
I would love to live in fairytale land where servers grow on tress, redundancy is easy, and both sessions and data seamlessly switch from one box to another when a system disappears off the network. Until then rebooting a machine will cause service problems of some magnitude. If unrelated services on a system have to be brought down because of fixes applied to a single service that is entirely unacceptable. The answer here is to fix the rebooting, not the possibility of it causing a service interruption.
The difference between restarting some network service that everyone uses, and restarting an entire machine, is usually a matter of semantics.
Semantics and the potential three to four minute time delta while the system starts up, checks its ram, runs other diagnostics, etc. Then there is the additional time to restart the service, plus any other services running on the box. With server hardware and a decent service load you could be looking at 5-10 minutes of downtime while the server reloads. Replication and load balancing are not solutions to everything, especially when you have to buy licenses.
The Real World is interested in *service* uptimes, not *server* uptimes. Scheduled maintenance, patching, etc of servers - assuming your environment is properly designed - should not have any impact on *service* availability.
Again we are back to the fairy tale world of infinite environment construction resources. Given piles of cash to estables X-level of redundancy I could guarantee that service uptime is just about entirely independant of server uptime. Too bad not everyone lives that way. I'm happy that you seem to be so sheltered though.