@AC: you sound like Apprenda in NYS ...
28 posts • joined 2 Mar 2007
To the poster worrying about the lifetime of an SSD drive, any modern filesystem should be managing the lifecycle/wear of individual sectors of the drive in such a way that the drive ought to outlast most warranties. We've had plenty of these sorts of discussions on the Eee boards.
One of my client sites was hit by a 20 minute scan Saturday morning, attempting just about every type of injection I can identify, along with both Windows and Linux directory traversal sites. Unfortunately I only have limited access to logs due to host configuration, so the only data I captured was via invalid querystring. I'm not sure what other avenues were explored.
The work product of a recently converted COBOL programmer, I can say with complete confidence, this writer has no clue what they're talking about.
Multiple exit points are debug hell. They are a major source of obscurity. They require substantial knowledge transfer between developers to understand. They make future development more difficult. They make porting between client and service paradigms EXTREMELY difficult.
Single exit point here.
I took continue to suffer memory leaks with FF. Several different machines, some XP, some Vista 32, some Vista 64. It's nowhere near as bad as it was in 1.x, or the early releases of 2.x, but it's definitely still a problem. Sure, I have a lot of tabs open, but no reason FireFox should a) take up 300mb+ to begin with nor b) have a disproportionate affect on system performance at that level, not when I have 2GB-4GB backing the machine. Various other pieces of software will perform pisspoor, or not at all, until I kill the FireFox process, when the memory use climbs like that.
Thanks for the laugh.
Yes, virtual machines (bytecode, not OS image, since you weren't clear and the uninitiated might be unfamiliar) are draining the world of all its power. :rolleyes: My electric bill shoots right up when I'm writing and running C# instead of C++. Yep. Dang.
Please, do tell, what serious compiled OO language exists out there other than C++ that doesn't live on a VM these days? One that's been proven scalable and commercially viable? One with any kind of support of the kind require to make for a serious development platform?
PS Java runs natively on Sun equipment. Huge financial and similar datacenters run Java natively to begin with. And they're the big fugly monsters under discussion here to begin with.
CSS is no panacea. You have to totally restructure the flow of many applications in order to present, and allow the management of, information in a way that makes sense, and doesn't totally piss off the user.
Yes, you can use CSS to optimize a layout for various clients, but once you start to deal with any real sort of volume of information, you have to start to refactor the GUI.
The decision to support mobile for key elements of the enterprise must be driven by need. You don't throw a data-storing communications device to any rank and file. If your IT staff, sales staff, writers at a newspaper, doctors, lawyers, investigators, etc. have a real need for mobile, if mobile offers a real business benefit, then you have to be willing to invest properly to support it. You also have to expect your employees to be adults -- if they're not, why are they working for you to begin with?
Well thought out policies have to be put in place, trained for and enforced with a reasonable amount of discipline. Camera? Sure, but with a rigid policy around that -- as long as the enterprise doesn't have large amounts of visually sensitive information, R&D, manufacturing processes, whatever that are relatively easily documented by a camera.. Bluetooth? Absolutely -- why not? Especially for headset use, GPS devices for staff on the road, so on and so forth. Headsets should in fact also be provided with any phone device. Again, some policy in place here, especially concerning transfer of data from company equipment to any mobile device or accessory. SDIO? I'd love to be able to lock it down, and/or be able to use strong encryption so that any company data that leaks onto an SDIO card only does so in an encrypted form. QWERTY keyboard? Sure, why not? Especially if the employee is sending/receiving a lot of company mail and/or text. At this point, all phones should be at least GPRS-capable, if not full 3G/HSPDA. Large screens should be available to any employee who spends time on the road, or needs to manage, massage or present any amount of data.
That said, many of these data-transfer policies apply just as equally to USB drives and MP3/multimedia players that also have the ability to store large amounts of potentially sensitive information.
I'm sure other presence-management/mobile-management suites offer similar capabilities, but one feature of note from the Vista/Exchange 2007/Office 2007 luncheon Microsoft gave a few months ago that interested me was the ability to remotely wipe the data on a phone in the event of lost data. I think this sort of capability is crucial -- terminated employees, stolen devices, I can think of any number of scenarios where being able to wipe the data on an MIA mobile device provides serious CYA insurance.
As a 28 year old American, who has owned four cars, all stick, I can assure you that manual transmission driving skills are alive and well in the US. Recently, however, dealing with a 45 minute commute down a 3 lane highway that was packed bumper-to-bumper at 6am, and would come to a complete stop in places if you were unlucky enough to still be on the road come 7am, I have given serious consideration to going over to an automatic -- at least for my daily driver.
I have yet to see the Office suite on a Smartphone ... on PocketPCs, sure -- but never on a Smartphone. What's the point of a fullblown office sweet if you don't have a keyboard or thumbboard? ClearVue is common on Smartphones, however, as it's more of a viewing product than an editing product, last I knew.
... just looking to pass the buck. They want developers to say, "it's ok if your next browser doesn't work with anything I've designed for your previous browsers." They're not trying to fix, or avoid, the problem, they're simply looking to be let off the hook. They need to have the balls to just DO IT -- and take what flack comes with it. It sounds like Trident needs to be revamped from the base up, in order to come into compliancy with standards. A refreshed, standards-compliant Trident would mean it would be difficult to support OLD MSIE pages -- but this shouldn't matter. Since everyone has a FF and MSIE version these days anyways, an MSIE that is standards compliant should be able to render the existing FF versions just fine. A minimal change for developers -- simple removal of the special case.
I work at an insurance company where we are moving away from mainframe technology onto x86 server blades, using Java and .NET. I don't think anyone here would agree it's easy to do much with the mainframe -- VSAM file storage is a big feature killer -- and it's certainly not cheap to buy or maintain -- TCO is the big wallet killer.
Heard of the Vardy Foundation, now known as Emmanuel Schools? The overly religious "founder" put down a relatively small proportion of startup costs, the UK paid for, and continues to pay for, the rest, and the "founder" is allowed to set up the board, and therefore influence the curriculum, to his personal standards:
Biting the hand that feeds IT © 1998–2022