Slashdot is powered by your submissions, so send in your scoop

 



Forgot your password?
typodupeerror
×

Comment Re:More error checking (Score 1) 241

Another favorite in embedded systems: lock the 4K page at address 0x00000000 so the processor halts execution when someone ends up dereferencing a NULL pointer.

Frequently have to move the IVT around to make this work, but well worth it.

Comment Re:Slightly off thread I know... (Score 1) 87

As a slightly off thread, I always wondered why Intel bought windriver. One of the issues we have is that finding someone who knows the OS well is difficuilt because there is no way of getting exposure to it unless you have a lot money.

Intel has loads of cash and a near monopoly on processors in most major market segments. They need somewhere to grow and PCs and servers isn't it. The big segments they are weak in are mobile (or more generally, low power) and networking.

VxWorks is very common in networking equipment and in embedded (low power / low processing capability) systems.

I can see where WindRiver looked attractive to Intel. Of course, the risk is that they scare traditional VxWorks customers off by focusing WindRiver too heavily on x86 processors.

Comment Microsoft (Score 1) 355

> Gates put his operating system within reach of every school kid in America for FREE. That is exactly why Microsoft has a monopoly today!

Um, no. That has virtually nothing to do with MS's dominance in the market.

Probably the biggest single factor was getting PC makers to pre-load Windows on computers. Most folks just use what the PC had on it when they bought it. That created a huge market for application developers.

Comment Re:Buying a house under the patriot act (Score 1) 239

The requirement to show where your down payment came from aren't new to the Patriot Act. I had to do that when I bought my first house 15+ years ago. Theoretically, they want to know that you can actually afford the house and aren't being given the down payment from sources of income other than your own - well, that or at least that you were willing to sit on the external funds for a few months before buying the house.

Comment Re:Looks like a hype (Score 2) 525

A big part of the problem is customers complain mightily when network devices congest (drop packets). Congestion is easily monitored. Additional latency is much harder to measure and most customers are less likely to notice it.

Less support calls == better margins

For some devices, it's clear that the engineers that built it don't understand networking very well and that's where the problem crops up. For others, it reduces pain on the field support organization so, in some ways, customers are doing it to themselves.

Comment Re:Yes, I do. But people don't call me one. (Score 1) 736

Well, there's always the hierarchy inside development itself. Even ignoring the whole "architect" thing and just sticking with programmers/developers that primarily write code, you have: internal application developers (generally lumped in with IT) maintainance coders (aka "sustaining engineers") - in both the IT and non-IT camps UI developers product developers systems/kernel developers embedded systems developers firmware / board bring-up etc. Not necessarily ordered here, but there tends to be a pecking order towards the alpha geek. Not that anyone outside of the software development community would realize this, but at most companies, it's there.

Slashdot Top Deals

"Ninety percent of baseball is half mental." -- Yogi Berra

Working...