Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
Note: You can take 10% off all Slashdot Deals with coupon code "slashdot10off." ×

Comment Re:Shouldn't this work the other way? (Score 1) 194

You go to war with the army you have

What we have is Unicode and a good set of font fallbacks. What we don't have is an unspecified, unplanned, unwritten way to somehow insert a "pictogram" inside my stream of "glyphs".

What we need is a way to draw shapes on a screen or piece of paper where a designer gets to pick roughly what they look like. Unicode does that, and therefore seems like an adequate tool for this job.

Comment Re:Shouldn't this work the other way? (Score 1) 194

Yes, except that they didn't. They took a list of eight items (section 4.2.1.4 of the underlying CODEX STAN 1-1985), and presented a proposal for seven of them. What happened to the last? I don't know: perhaps they didn't figure out how to make a character for "Sulphite in concentrations of 10 mg/kg or more".

They also missed section 5.2.1, irradiated foods, with a separate symbol.

Comment Re:The difference... (Score 1) 97

I've recently been pawing through my old Basic manuals (I'm implementing a Basic environment for run). And what stands out is how incomplete and limited most of the old environments were (although I did love them at the time).

The Basics were grossly limited. Examples includes the Sinclair AND and OR statements, the very limited FN statements and severe limitations on FOR loops. Given the high expense of disks in those days, it's no surprise that disk handling was uneven at best.

Networking capabilities were trivial to non-existent, and mostly non-existent.

The connection to their environment was deeply weird. From a modern perspective, the first thing we normally do when we see a bit of hardware is to wrap it in a little bit of code to make it simpler to control. The common pattern in the old days was to revel in the POKE and PEEK statements, directly setting hardware registers.

The difference between then and now is that then my plan was to write an program to play lunar lander. My plan today is to write a program that will listen to my mailboxes and change the color of my lights accordingly ("Make it pink!", "Make it blue!")

Comment Re:SubjectsInCommentsAreStupid (Score 1) 529

So, of that persons comments, the one about branded actually makes sense. Different companies actually do work on different frequencies (and there's a bunch of other differences; frequency is just part of it). Once we posit that some microwaves cause problems, it's very reasonable that different frequencies would cause more or fewer problems.

Comment Re:Two things... (Score 1) 583

I'm going to rephrase what you said, and change it. Don't whine at your boss. Don't complain at your boss.

But do ask for advice ("this other team is delivering really slowly, how should I handle it?", or, "I think I have a better solution for the problem of the day, but I'm having trouble advocating for it, can you help me?")

And let them know when you're behind. My company takes the output of many, many teams and sells the result; there's nothing they hate more than surprises.

Comment Re:Last week I tried to write a Win8.1 universal a (Score 1) 133

I've got several apps in the store. Most of the UI code is fully shared, and moderately adoptive to screen size. In a few places, I needed something special for one or the other.

My trick is that the 8.1 universal apps have two mainpage.xaml files (one for desktop, one for phone). I just make a shared UserControl. Each MainPage just has one object, which is the shared control

(BTW: I work at Microsoft, but not in the group that does XAML; my way works but that doesn't mean there isn't a better way)

Comment Re:Lift the gag order first... (Score 1) 550

It's called, "the general operations budget" I work for a big company; from on high we get general guidelines ("computers are expected to last xyz years" and "you have abc to spend on travel this year"). itt's up to the more lower-level people to decide how to portion it out.

In the FCC's case, congress has already given them money to inforce their regulations (and gave them the authority to make the regulations, but also gave them requirements like hainvg a certain number of public hearings). The FCC can then spend it on those things.

Comment Re:This thread will be a sewer of misogyny (Score 1) 779

How's this for a counter-example? Orchestras used to have a ton of reasons why women were grossly under-represented -- they just weren't interested, they didn't have the skills, they didn't have the long-term ability -- whatever. But when orchestras started to have players audition behind curtains, suddenly a lot of talented women started getting hired.

Right now there are plenty of teachers who literally don't want women in their high-tech classes. This bill helps solve that problem, and doesn't let the teacher weasel their way out with cop-out answers.

Comment Re:5th Admendment? (Score 1) 446

Quote: "within their jurisdiction". That means that the court has ordered (in compliance with your rights) that certain data be discovered or turned over. Seriously, folks: the police do get to investigate crimes. If they need to look at your car (or, in 18th century terms, your horse), they get to.

Submission + - NASA Spacecraft Images Crash Site of Retired LADEE Probe->

An anonymous reader writes: In April, NASA ended the mission of its Lunar Atmosphere and Dust Environment Explorer (LADEE) mission by de-orbiting (read: crashing) it on the far side of the moon. The Lunar Reconnaissance Orbiter has now directly imaged the crash site, showing a small crater and the spray of rocks and dust caused by the crash. "LADEE's grave lies about 0.5 miles (0.8 kilometers) from the eastern rim of the larger Sundman V crater, just 0.2 miles (0.3 km) north of the spot where mission team members predicted the spacecraft would go down based on tracking data, NASA officials said. ... The new crater is less than 10 feet (3 meters) wide. It's so small because LADEE was just the size of a washing machine, and the probe was traveling relatively slowly (3,800 mph, or 6,116 km/h) when it impacted the surface. The LROC team was able to spot LADEE's impact crater after developing a new tool that compared before-and-after images of the same lunar sites, researchers said."
Link to Original Source

Variables don't; constants aren't.

Working...