Follow Slashdot stories on Twitter


Forgot your password?
Compare cell phone plans using Wirefly's innovative plan comparison tool ×

Comment Re: Outsourcing vs Inhouse (Score 1) 221

I am not sure what you are objecting to: The idea that customers don't have firmly stated requirements when they sign an outsourcing contract? The idea that good contractors should work with customers to clarify, elaborate, and refine requirements, resolving conflicts between stated requirements when they occur? The idea that contractors shouldn't blame the customer if they don't get a sufficiently complete set of requirements? The idea that an MVP can be deployed to help advance the overall contract's progress?

Conflicting requirements are a different problem than being unable to provide requirements (or articulate them correctly). It's lucky when a customer empowers exactly one person (at least for a given scope) to resolve such conflicts. More often, for the political reasons you mention, the customer wants to have too many cooks, and they spoil the requirements soup.

Comment Re: Outsourcing vs Inhouse (Score 1) 221

"The customer('s management) couldn't provide requirements" is the excuse of incompetent contractors out to bleed the client dry. The customer almost never has very clear or necessarily realistic requirements -- if they knew enough to create those, they'd probably be able to do the work in-house. Good contractors need to be good at eliciting requirements, and be able to build a set of requirements that will support at least a minimum viable product.

Comment Re:When everything you do (Score 1) 531

No, that's the weakness of optimizing your data store for simplicity and then sticking with the choice for decades after people identify scalability problems. The format you choose for storing email is not a "component".

Also, databasing email doesn't break "everything but MTAs". Commonly used MUAs use IMAP or something web-oriented to talk to the mail store, so they never know about the change. You're asking for an MDA change, so of course the MDA will change -- but not break.

Comment Re: Linux is far worse than Microsoft (Score 1) 531

Do you have numbers or case studies to support your claim about the "on average" outcome? You're talking about a business model of moving valuable (or even critical) information into a third party's control, where you still have the same number of internal end users, the same operational requirements, the same amount of data stored -- but you now have to control the pipe to and from that service, trust in the vendor's employees, and live with their deployment schedules and glitches.

It's like owning your own car versus relying on public buses. You may feel like you're saving money by taking a bus, but you're more exposed to strangers peeking in, it doesn't cover most of the world, you have no real input on available destinations, and you're at the mercy of a third party to go anywhere at all.

Comment Re:When everything you do (Score 1) 531

Yeah, I get that you don't like email, but basically the entire stack of brokenness that you are complaining of there derives from the fact that mbox is a terrible format for storing email with concurrent read/write access. It's almost impossible to design a good software stack on top of a fundamentally mistaken architecture.

Comment Re:When everything you do (Score 2) 531

I was using the common CS definition of component. The lines are not arbitrary at all.

Your misinterpretation of what I said is the ridiculous thing here. The number of bugs reported doesn't indicate why it's a failure of software design -- the nature of those bugs do. But you'd have to do what I said, and look at several of them to follow the finger-pointing and confusion about root causes, to know what I meant.

The fact that systemd has now centralized and complicated a fragile arrangement does not make it an improvement.

Comment Re:When everything you do (Score 2) 531

Having robust, testable, easily isolated components is even more important when you have a complex system -- and the way you get those is by defining the one thing that each component should do, and making it do that thing well.

Have you ever tried to debug something that has both complex components and complex interactions, either between the components or with external entities (people or machines)? Very frequently, if the designer decomposed it well, the nature of the failure will make it pretty obvious which part is failing. systemd fails in that department; just look at a few of the thousands of bug reports against it.

Comment Re:Wrapper, not replacement (Score 1) 531

Do you even Linux, bro? It was handling hot-swap just fine before systemd came along. You didn't even show that you knew about how distros handled it (without needing arbitrary init scripts or the like) before, and your comment about runlevels suggests that you fundamentally misunderstand them.

The only thing you mentioned that could be improved is handling network changes -- but that's something that applications have to do, based on their own patterns of network usage and how they can recover from a change in transport. systemd can't fix that.

Comment Re:"Hey, watch this!" (Score 1) 124

Computers would be so secure if people just didn't try to use them!

It's silly to blame security problems on the fact that people are involved. Developers and admins blame users when those developers and admins can't be bothered to design (or deploy) practices and procedures that address the blind spots and habits that users pick up when they use a system.

Comment Re:Bad decission (Score 1) 95

The Stessmen v. American Black Hawk decision was from the Supreme Court of Iowa, so it has, um, limited applicability in California. But you're right that video recording public events is pretty much fair game.

In California, it is fair game to record a conversation held in public -- the state's wiretapping law only covers "confidential communication[s]", which specifically excludes conversations in public gatherings, proceedings of the government that are open to the public, and "any other circumstance in which the parties to the communication may reasonably expect that the communication may be overheard or recorded".

And since you asked, Illinois's Supreme Court decided that the state's wiretapping law was unconstitutional because it banned recording even overt conversations. Many courts have held that wiretapping laws do not protect police from being recorded while they are performing their duties -- including at least one in California.

Slashdot Top Deals

"Truth never comes into the world but like a bastard, to the ignominy of him that brought her birth." -- Milton