Try the Openfire Jabber/XMPP server. Have your own server for the office, and if your company has > 100 employees, create groups of each department and auto-share the group roster to the group. So when people join/leave the company, the roster updates for everyone. Jabber is awesome.
Re:your first sentence is technically flawed
on
Ubuntu on a Dime
·
· Score: 1
I thought the purpose of very small corporate quotas was to limit the available audit trail for Wrong Doings.
Last I checked, no one* uses PGP. You can use PGP with gmail just fine (save your attachments, copy/paste the ascii armor, connect over imap(s) with another client, etc).
You might want to check out echelon. It doesn't really matter where your plaintext mails are stored anyway if they are all read in transit.
However, if you and all your friends use a single mail server, and all connect over imaps/https/smtp-tls, then you just have to worry about the malware/keyloggers employed on their hardware.
It's cool netflix has Heroes available for streaming, but the discs are still unavailable for Heroes Season 4. Very frustrating to see the Play button only.
Maybe it's changed from FF 3.0 to 3.5, but I grew tired of clicking twice for flash content that I wanted to see. One click for NoScript and a second click for FlashBlock.
I try to keep my browser lean (and lean still means ~10 extensions, mostly for web dev). NoScript + CookieMonster + RefControl seems to work good enough for me.
That's a cool idea... until the motivation for efficient computing dwindles because the more "user time" the software burns, the more the vendor will charge.
In the case of VMWare, perhaps they could charge you based on the number of startup instances per time period. (But then every time you reboot a VM for maintenance, you get charged, so the incentive for security is diminished. Though one could try ksplice.)
typeracer is also a great competition for the office workplace. it's great to see how well the "mad chatters" do, because error free gives a higher score. I would like to see less formal paragraphs to type, something that looks like chat between two people.
We have had a LOT more success with rails, than failure. And we're getting a LOT more done now than before when doing struts/JSP/JDBC style dev.
I'm curious if you have ever tried Apache Wicket. Wicket is yet another framework for Java, and it requires your team to have a solid level of OO programming knowledge because every web page is a hierarchy of components, and to customize behavior, you need to @Override various methods.
I just finished my first iteration of a decent-sized project using Wicket that used many of wicket's components like repeating list/grid views, a custom session with different user types/roles, and some custom components to deal with "edit vs view" modes.
We integrated this project into an existing Spring MVC + regular servlet/jsp web app. Instead of custom JDBC as we did previously, we used hibernate annotations which means no XML nor direct SQL.
Writing wicket was fun; I've had more fun in 3 months of wicket than 2 years of "regular" java. The learning curve was steep, as I spent days solving what later seemed simple problems, but I learned a lot. Future iterations of this project will be quick. Overall, I say medium to large projects will take much less total time from concept to stable delivery using wicket versus other java web methods.
I've not tried Ruby, ROR, JRuby, nor Grails, so unfortunately I can't compare wicket to any of them. But it sure beats Struts, Spring MVC, and JSTL/JSP. Wicket does not allow any logic in the view -- you use plain xhtml+css (with a wicket DTD while designing for validation), and use java code to do everything else, including ajax. So a web+css+javascript master can bust out a prototype/mock-up, and a few wicket programmers can tie in the back end logic. When maintaining, the web designer can open the plain html+css (in their favorite editor) and modify it as needed, without any code in the way.
Wicket is a neat technology, with great security (url encrypting, server-side validation with ajax) and good performance.
First two sections are not going to happen in large organizations.
What you say is sad but true in my experience at the companies I have worked for.
The first two sections are essentially: (1) the business strategy for your particular product, and knowing your human resources (team); (2)/really/ thinking about the future, not just how you will sell it; why you would need to scale.
The following question is somewhat on topic as this book appears to be targeted to decision makers at the company, which usually means high-level product/project managers and "directors" or "VPs" of technology/software engineering.
Question: Why do company decision makers not rely on pooling the collective input of their subordinates or teams, and instead make rapid and unfaltering business and technical decisions that are not forward-thinking?
Perhaps they are marking wise decisions for the company, so they can make money in the short term and grow the business, which allows them to fund new projects and so on. But I read on Slashdot all too often where management's short-sightedness to choose one specific technology, seemingly without consent of other knowledgeable employees (yet lower on the decision chain), cause headaches for the actual implementors down the chain.
Say these decision makers dictate no application caching and choose a commercial database offering for vertical performance scaling, instead of adding caching and partitioning data on free databases for horizontal scaling. Yet if they would have asked the collective software engineers and low-level management for input, the decision would have been reversed. Will a book like this even help those types of high-level decision makers, say VPs of Tech: brought in from outside the company to grow the business away from the previous [multiple] VPs' mistakes?
I really wish PHP was more like a Java application server -- where it would perform like you said: "allow you to instantiate your classes and their data upon startup, and then call methods per request, without having to instantiate all the classes over and over again in each request."
Not having a shared memory pool (without memcached) and having to re-instantiate the same classes on every load really pains me.
Take the task of initializing a logger in PHP -- you create the "object", which loads its configuration of where to write the log file, and then inside your page you call log.debug() or log.error() or whatever, which writes to the log. Unfortunately, every time your PHP page is requested, it does the same startup tasks each time! (e.g. new Logger() writes "application started" each time to the log.) What a waste. If only mod_php would somehow keep those objects in memory, referenced from your page that lives in memory, and you could call the same log.info() method over and over again without creating a new instance of the logger.
I would definitely use PHP if it behaved like an application server.
You can run multiseat anywhere with a recent xorg (not just fedora). I run multiseat on Ubuntu 9.04; only had to edit xorg.conf and gdm.conf. Though I do have two video cards.
You are correct, you cannot move windows between separate X sessions. But you could use synergy to access both seats with the same keyboard/mouse.
Unfortunately, if you just have a dual-head video card, I believe you need to run xnest or something similar to have separate X sessions on two monitors. However, having two video cards is easy.
I had multiseat working in Ubuntu 8.04, and it's working now in 9.04. I only had to modify xorg.conf and gdm.conf. (Though it did take several hours to get all the usb devices worked out, as well as the console-kit sessions.)
I have two monitors on a single pcie nvidia card as Seat0, and a single monitor on a second pcie nvidia card as Seat1. Two usb keyboards, and two usb mice. One computer.
If I want to connect all 3 monitors, I login (as two different users) to both seats, and run synergy.
As long as you don't mix spaces & tabs, variable-width fonts will display just fine. All the more reason to use tabs-only, since you can define its width much more easily than a space. (And variable-width font spaces are usually narrow).
function foo(param bar) { \t if (bar is not null) { \t\t print(bar); \t } }
And if you prefer to look at 2 or 4 spaces per tab, you're hosed. Tabs-only is best. Then each person can set the level of indent they want to see. As long as you don't mix spaces and tabs, you're fine.
Instead of sshfs+cp, if you want to perform incremental backups without wasting space (duplicating storage), you might try rsync with hardlinks. It appears back-in-time can do this also.
The Great Firewall would of course block access to Google's "frontend" servers. The government could take over control of the google.cn domain, as well as force ISPs to change DNS entries.
Slashdot Mirror
Re: IM
Try the Openfire Jabber/XMPP server. Have your own server for the office, and if your company has > 100 employees, create groups of each department and auto-share the group roster to the group. So when people join/leave the company, the roster updates for everyone. Jabber is awesome.
I thought the purpose of very small corporate quotas was to limit the available audit trail for Wrong Doings.
Last I checked, no one* uses PGP. You can use PGP with gmail just fine (save your attachments, copy/paste the ascii armor, connect over imap(s) with another client, etc).
You might want to check out echelon. It doesn't really matter where your plaintext mails are stored anyway if they are all read in transit.
However, if you and all your friends use a single mail server, and all connect over imaps/https/smtp-tls, then you just have to worry about the malware/keyloggers employed on their hardware.
* = not statistically significant
Correct - that is definitely a misquote.
I'm curious, did your coworkers have the same movies at the top of their queues? "Very long wait" seems indicative of "very popular movies".
It's cool netflix has Heroes available for streaming, but the discs are still unavailable for Heroes Season 4. Very frustrating to see the Play button only.
Maybe it's changed from FF 3.0 to 3.5, but I grew tired of clicking twice for flash content that I wanted to see. One click for NoScript and a second click for FlashBlock.
I try to keep my browser lean (and lean still means ~10 extensions, mostly for web dev). NoScript + CookieMonster + RefControl seems to work good enough for me.
That's a cool idea... until the motivation for efficient computing dwindles because the more "user time" the software burns, the more the vendor will charge.
In the case of VMWare, perhaps they could charge you based on the number of startup instances per time period. (But then every time you reboot a VM for maintenance, you get charged, so the incentive for security is diminished. Though one could try ksplice.)
typeracer is also a great competition for the office workplace. it's great to see how well the "mad chatters" do, because error free gives a higher score. I would like to see less formal paragraphs to type, something that looks like chat between two people.
Duh, they wanted to make browsing Slashdot even prettier!
Now, this is not to nit-pick - but I can see that your use of "suck[s]" is incorrect.
In your example, you opted to use the verb "sucks" with an object, yet you failed to produce the object.
"Adobe sucks really big." is missing an object, perhaps you mean: "Adobe sucks a really big dick."
Your second example tries to use the verb "suck" without an object, yet you failed at that too.
"Adobe does suck really big." might be: "Adobe does suck really hard." Or perhaps: "Adobe does suck my really big dick really hard."
Even in slang, you may simply end the phrase with "sucks" as in: "Adobe sucks."
Welcome to English.
We have had a LOT more success with rails, than failure. And we're getting a LOT more done now than before when doing struts/JSP/JDBC style dev.
I'm curious if you have ever tried Apache Wicket. Wicket is yet another framework for Java, and it requires your team to have a solid level of OO programming knowledge because every web page is a hierarchy of components, and to customize behavior, you need to @Override various methods.
I just finished my first iteration of a decent-sized project using Wicket that used many of wicket's components like repeating list/grid views, a custom session with different user types/roles, and some custom components to deal with "edit vs view" modes.
We integrated this project into an existing Spring MVC + regular servlet/jsp web app. Instead of custom JDBC as we did previously, we used hibernate annotations which means no XML nor direct SQL.
Writing wicket was fun; I've had more fun in 3 months of wicket than 2 years of "regular" java. The learning curve was steep, as I spent days solving what later seemed simple problems, but I learned a lot. Future iterations of this project will be quick. Overall, I say medium to large projects will take much less total time from concept to stable delivery using wicket versus other java web methods.
I've not tried Ruby, ROR, JRuby, nor Grails, so unfortunately I can't compare wicket to any of them. But it sure beats Struts, Spring MVC, and JSTL/JSP. Wicket does not allow any logic in the view -- you use plain xhtml+css (with a wicket DTD while designing for validation), and use java code to do everything else, including ajax. So a web+css+javascript master can bust out a prototype/mock-up, and a few wicket programmers can tie in the back end logic. When maintaining, the web designer can open the plain html+css (in their favorite editor) and modify it as needed, without any code in the way.
Wicket is a neat technology, with great security (url encrypting, server-side validation with ajax) and good performance.
First two sections are not going to happen in large organizations.
What you say is sad but true in my experience at the companies I have worked for.
The first two sections are essentially: (1) the business strategy for your particular product, and knowing your human resources (team); (2) /really/ thinking about the future, not just how you will sell it; why you would need to scale.
The following question is somewhat on topic as this book appears to be targeted to decision makers at the company, which usually means high-level product/project managers and "directors" or "VPs" of technology/software engineering.
Question: Why do company decision makers not rely on pooling the collective input of their subordinates or teams, and instead make rapid and unfaltering business and technical decisions that are not forward-thinking?
Perhaps they are marking wise decisions for the company, so they can make money in the short term and grow the business, which allows them to fund new projects and so on. But I read on Slashdot all too often where management's short-sightedness to choose one specific technology, seemingly without consent of other knowledgeable employees (yet lower on the decision chain), cause headaches for the actual implementors down the chain.
Say these decision makers dictate no application caching and choose a commercial database offering for vertical performance scaling, instead of adding caching and partitioning data on free databases for horizontal scaling. Yet if they would have asked the collective software engineers and low-level management for input, the decision would have been reversed. Will a book like this even help those types of high-level decision makers, say VPs of Tech: brought in from outside the company to grow the business away from the previous [multiple] VPs' mistakes?
I really wish PHP was more like a Java application server -- where it would perform like you said: "allow you to instantiate your classes and their data upon startup, and then call methods per request, without having to instantiate all the classes over and over again in each request."
Not having a shared memory pool (without memcached) and having to re-instantiate the same classes on every load really pains me.
Take the task of initializing a logger in PHP -- you create the "object", which loads its configuration of where to write the log file, and then inside your page you call log.debug() or log.error() or whatever, which writes to the log. Unfortunately, every time your PHP page is requested, it does the same startup tasks each time! (e.g. new Logger() writes "application started" each time to the log.) What a waste. If only mod_php would somehow keep those objects in memory, referenced from your page that lives in memory, and you could call the same log.info() method over and over again without creating a new instance of the logger.
I would definitely use PHP if it behaved like an application server.
You can run multiseat anywhere with a recent xorg (not just fedora). I run multiseat on Ubuntu 9.04; only had to edit xorg.conf and gdm.conf. Though I do have two video cards.
You are correct, you cannot move windows between separate X sessions. But you could use synergy to access both seats with the same keyboard/mouse.
Read more about generic multiseat here:
http://blog.chris.tylers.info/index.php?/archives/14-Multiseat-X-Under-X11R6.97.0.html
You are on the right track... you are describing something similar to "Multiseat X".
Read more here: http://blog.chris.tylers.info/index.php?/archives/14-Multiseat-X-Under-X11R6.97.0.html
Unfortunately, if you just have a dual-head video card, I believe you need to run xnest or something similar to have separate X sessions on two monitors. However, having two video cards is easy.
I had multiseat working in Ubuntu 8.04, and it's working now in 9.04. I only had to modify xorg.conf and gdm.conf. (Though it did take several hours to get all the usb devices worked out, as well as the console-kit sessions.)
I have two monitors on a single pcie nvidia card as Seat0, and a single monitor on a second pcie nvidia card as Seat1. Two usb keyboards, and two usb mice. One computer.
If I want to connect all 3 monitors, I login (as two different users) to both seats, and run synergy.
As long as you don't mix spaces & tabs, variable-width fonts will display just fine. All the more reason to use tabs-only, since you can define its width much more easily than a space. (And variable-width font spaces are usually narrow).
function foo(param bar) {
\t if (bar is not null) {
\t\t print(bar);
\t }
}
And if you prefer to look at 2 or 4 spaces per tab, you're hosed. Tabs-only is best. Then each person can set the level of indent they want to see. As long as you don't mix spaces and tabs, you're fine.
Instead of sshfs+cp, if you want to perform incremental backups without wasting space (duplicating storage), you might try rsync with hardlinks. It appears back-in-time can do this also.
This article is great:
http://www.sanitarium.net/golug/rsync_backups_2010.html
Agreed, rsync would be more efficient. No need to move messages to local storage.
The Great Firewall would of course block access to Google's "frontend" servers. The government could take over control of the google.cn domain, as well as force ISPs to change DNS entries.
Physical access to hardware not required.
The government still controls the .cn TLD, and they could take over the domain or remove it from the root zone at a whim.
Uh, how would that get them past the Great Firewall?
I thought it was ID10T (eye dee ten tee).
Oh, so it's plain ol ice beer. Gross.
If they find some antarctic strain of yeast that could withstand 32% alcohol, let me know!