Please create an account to participate in the Slashdot moderation system


Forgot your password?
Get HideMyAss! VPN, PC Mag's Top 10 VPNs of 2016 for 55% off for a Limited Time ×

Comment Re:Country? [Re:As a C programmer] (Score 1) 201

You design in location A, and you can manufacture *anywhere*. It helps if manufacturing is closer to location A during design, because you're more interested in quick turnarounds than in lowest possible cost. Once you're building in bulk it's not that important. And countries that are currently big on manufacturing cheaply are not very good at designing well. And the big design places are still the US, Europe, Korea, Japan. Those are where the big headquarters are, but not necessarily where the stuff gets put together.

Comment Re:Numbers are easy to manipulate (Score 1) 49

I asked some friends once why they had Comcast. They said its cable service sucked, they said its internet service sucked, they said its phone service sucked, but they used it because bundled together the price wasn't too bad. Ringing endorsement!

Anyway, I don't have cable or cable internet. I went with AT&T. I think $50 for 12mbps, slower than Comcast for that price, but at least it's not Comcast.

Comment Re:Country? [Re:As a C programmer] (Score 1) 201

Where the devices are manufactured does not tell you anything about where the devices are designed and programmed. Sure, there may not be "growth" in C in the US, but growth comes and goes which means that the hordes of programmers in a fashionable language this year may be out of work in five years (after having to train their cheap replacements).

Comment Re:Country? [Re:As a C programmer] (Score 1) 201

Lots and lots of embedded work being done in the US. Anyone who makes devices. Internet of Things, smart phones, dumb phones, automotive ignition, microwaves, toys, medical devices, anything anywhere that uses Linux, the traffic light at the corner, the security checkpoint at the airport, etc. Oh wait, encryption too, it's usually a mix of hardware, assembler, and C in many products. And the implementation of most scripting languages and their runtime code... All of that is happening within the US. And it's happening in other countries too of course, C isn't bigoted.

Comment Re:As a C programmer (Score 1) 201

You can do both. Have the small straight forward language without lots of pitfalls, and at the same time make the code maintainable and reusable. However, avoid the "fast deployment", that means "rapid prototyping" which means speed matters more than quality and the customer ends up with mocked up prototype. Rapid prototyping is not part of the "science" of computer science.

And basically "computer science" has almost nothing to do with programming anyway, it's a broad interdisciplinary field that covers both mathematics and engineering.

Comment Re:As a C programmer (Score 1) 201

C++ has some different rules about types, which some people think are better than the C rules.

Personally, I'd take the subset of C++ that still includes basic inheritable classes/structs, name spaces, etc. But avoid exceptions (hard to make this efficient a lot of times), avoid templates that are larger than a line or two (avoid the gawdawful code bloat it can lead to), etc. The "better C than C" version of C++ before the goal of every C++ standards committee became how new features they could cram in.

Comment Re:As a C programmer (Score 1) 201

If they're pointers to bytes then you can compare them directly. Alignment is the same forwards or backwards. If the regions overlap then sometimes you need a forward copy but sometimes a backwards copy! The direction depends upon where they overlap!

If you copy 0-100 over to locations 50-150, then you have to copy backwards, copy the 100 over first, then 99, etc. But if you're copying 50-150 over to 0-100, then you have to copy forwards, starting with 50 first.

That's the point in the interview where I suggest they can draw this on the whiteboard instead of trying to do it in their heads.

Comment Re:And you shouldn't be.... (Score 1) 220

There's really not much risk here. They're trying to play the fear card too much. It wasn't long ago when we didn't have smart phones with encryption. It is so recent that even a millenial can remember those days. And was it a world where all criminals were captures, all crimes solved, people were always safe and secure? No! Rates of violent crime were higher. Criminals still figured out how to talk to each other securely without the FBI listening in. We had organized crime operating with impunity for long periods of time, they even figured out how to use encryption.

There's nothing law enforcement can do to put this genie back in the bottle. One simple app to do a pgp style communication and encryption is back no matter how many back doors the manufacturers put in (or get a warrant to get the phone maker to stick on keyloggers, but everyone's going to avoid those phones like the plague once word is out). Use some third party SOCs from outside America as your key dongle on the PC and you can detect tampering and destroy your keys.. There's just no way they can lock this down.

We have some phones locked tight that may or may not contain evidence about crimes. So what?? This is not a disaster. We've never had a time when we could gather all possible evidence, search everywhere we liked, and solve all crimes. Claiming that it's wrong that they can't open up the phones and get the data from them is like whining that the parrot at the crime scene isn't talking.

Comment Re:Does MS have any idea what they are doing? (Score 1) 268

I've used plenty of machines that do use swap space. Servers with VM images, with the whole point of such servers being to overallocate resources. So less frequently used stuff gets swapped out. You ask them to upgrade memory and they laugh and nothing happens. It's the real world.

Given that price points changed so that RAM is now relatively cheaper, it's still theoretically possible for it to go back the other way again in time, where getting beyond 128GB is just too expensive to justify when you've got terabytes of dirt cheap storage on your servers.

Slashdot Top Deals

Real Programmers don't write in FORTRAN. FORTRAN is for pipe stress freaks and crystallography weenies. FORTRAN is for wimp engineers who wear white socks.