Catch up on stories from the past week (and beyond) at the Slashdot story archive


Forgot your password?

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).


Comment: Re:No one is forcing anyone to do anything (Score 2) 488

Presumably he paid for a home space which would accommodate the office. What he should or shouldn't do is pretty much his business and his alone.

Yes, it is his business alone, but that doesn't insulate him from reasonable criticism of his choices. Exploring the choice of renting office space is much,much cheaper than reselling a home, specially one recently purchased.

Comment: Re:No one is forcing anyone to do anything (Score 1) 488

Heck, he could, you know, rent an OFFICE to conduct his business from that has connectivity. There are tons and tons of incubator spaces that would be happy to have his business.

I've conducted business from home. It sucks. There are many good reasons to separate work and home.

You took the words right out of my mouth (or keyboard). This is one of my plan-B's when I work from home and internet connectivity at works sucks. It sucks to pay an extra few hundred dollars a month, but it sucks less than not working or having to relocate.

Comment: Re:Seriously... (Score 1) 757

by luis_a_espinal (#49275675) Attached to: Was Linus Torvalds Right About C++ Being So Wrong?

That's what "typedef" is for. Put "typdef" in front, replace signal with signal_handler, and it's only really ugly in one place.

Or cdecl...

Of course. IRL we would use typedef to manage that kind of ugliness. But one will always encounter definitions like that - signal will never be defined with a typedef in any form of POSIX documentation.

Thus working at certain levels, it is important to understand such declarations (if not fully, at least partially to ask the right questions.)

Comment: Seriously... (Score 1) 757

by luis_a_espinal (#49229483) Attached to: Was Linus Torvalds Right About C++ Being So Wrong?
Seriously, if we are going to complain about crazy parsing, pointer to array of ints is not a good example. This is a good (and thank goodness, relatively obscure) example:

void (*signal(int, void (*)(int)))(int)

with signal as a function that takes one int and one pointer to function that takes one int and returns void, and which in turn returns a pointer to function which takes an int and returns void. Thankfully, this shit is seldom seen in most applications of C, except in very specialized cases.

The rest of cases it's nothing mind-warping if you know the rules.

Comment: Re:Syntax and typo errors compile (Score 1) 757

by luis_a_espinal (#49229393) Attached to: Was Linus Torvalds Right About C++ Being So Wrong?

gahh. I just typoed my example!!! oops. int (*foo)[20]; int *foo[20];

But I bet that error would even compile!

Not mind boggling. A person that works in C *must* know the syntax and how that stuff gets parsed.

First a pointer to an array of 20 ints (the parenthesis binds the '*' to the variable, making it a pointer). Second, an array of 20 pointers to int (the [20] binds to the variable, making it an array of 20 something, that something being determined by int * (pointer to int).

Yes, the parsing is idiotic (go right till no more, then left till no more and non-sense like that), but the rules have existed forever. And to me, that is a prerequisite to work in C... and when in doubt, use cdecl.

Comment: Gawd! Damnit, not Mayans! (Score 3, Interesting) 61

by luis_a_espinal (#49181293) Attached to: Lost City Discovered In Honduran Rain Forest

Or someone very closely related to them? You know, the group in that area that formed a thriving civilization that supposedly fell apart during a drought...RIGHT AT THAT TIME?

Those unknown people?

Mayans were only one of the many people living in the area. There were/are Pech in the East (linguistically affiliated with Macro-Chibchan), the powerful Lenca in the north west (also Macro-Chibchan) living where the Mayan once were, Tolupan/Xicaque (language isolate), Pipil (Uto-Aztecan), Ulwa, Tawahka, Mayagna, and Matagalpa (Misumalpan), etc.

That is, Mayan are just the best known culture in Honduras. They weren't even the predominant culture anymore by the time of the Spanish conquest of Honduras. I've been hearing the rumors of the "White City" since the late 80's, and we keep finding archeological stuff in Honduras and Nicaragua which are really hard to categorize as cultures go.

The location of it, in the Mosquitia region, far to the east, is waaaay too far away from the Honduran Mayan homelands. The culture from this site are almost certainty neither Mayan nor Lenca. I doubt they are Tolupan because the proposed Tolupan homeland is to the north of Honduras.

By the geographic location of it, the culture was either Proto-Pech or Misumalpan (or even a culture long gone with no linguistic/ethnic survivors).

Comment: WTF? Ease of analysis =/= ease of maintenance??? (Score 1) 247

by luis_a_espinal (#49181169) Attached to: Study: Refactoring Doesn't Improve Code Quality

A team of researchers in Sri Lanka set out to test whether common refactoring techniques resulted in measurable improvements in software quality, both externally (e.g., Is the code more maintainable?) and internally (e.g., Number of lines of code). Here's the short version of their findings: Refactoring doesn't make code easier to analyze or change (PDF); it doesn't make code run faster; and it doesn't result in lower resource utilization. But it may make code more maintainable.

From the OP, how the fuck do we reconcile this:

Refactoring doesn't make code easier to analyze or change

with this:

But it may make code more maintainable.

Seriously, those two statements conflict with one another. And since when refactoring was done primarily to make things run faster or more efficient resource-wise? Optimization is typically an architectural issue, or a point of local optimization in changing algorithms and data structures. Refactoring for the most part has always been about structural changes to enable analysis, re-usability and replacement and to ensure correctness (or at least to avoid introducing new fuck-ups.)

On The Onion News at 11, refactoring does not make code more eco-friendly/gmo-free.

Comment: Re:Crime (Score -1, Troll) 538

Shes a democrat, she could kill children on the street and get away with it.

Unlike Republicans who have gotten our soldiers and drones in a position to kill civilians of all genders and ages, even children, in Iraq and Afghanistan, and whom are all in jail because of that... err, wait.

Seriously, stop injecting your stupid political pet peeves in every conversation. How old are you? 10?

Comment: Re:Is that really a lot? (Score 1) 280

by luis_a_espinal (#49149065) Attached to: Drones Cost $28,000 Per Arrest, On Average

The working class was making a living wage doing, for the most part, manual unskilled job (pull a lever on a converyor belt or making US flags.

I'd like to know where you got the idea that the working class was doing mostly manual unskilled jobs.

Because I was in the middle class doing manual unskilled work (soldering electronics) 26 years ago. Because that is what I saw predominantly everywhere I went. Yeah, you had a factory that manufactured and repaired electric motors. For each one of "you" there were a dozen of "others" truly doing unskilled jobs.

Jesus, look at all those people that used to work in the auto industry. Sure, there were truly skilled laborers, but the lot was just put thing A in mold B, yell "clear" and pull the lever. The garment industry? Unskilled by modern standards. Assembly of electronics? The bulk of it is unskilled by modern standards.

Look at the work done by FoxConn workers in China. Yeah, they are assembling your fucking awesome, newest iButtPlug electro-trinket, but those workers are unskilled. They simply pick part A and B from conveyor belt and put them together in a bucket in another conveyor belt.

Those are the type of manufacturing jobs that were predominant here, that were uber-sophisticated by the standards of the 50's and 60's when Europe and Japan were recovering from the ashes, China and India were completed fucked, Latin America was fucked and incompetent (hasn't changed much) and 2/3 of the planet was living in some weird state mixing stages from the Neolithic, Iron Age and Feudalism with a bit here and there from the Industrial Age circa 1800's.

Things changed, and those uber-sophisticated jobs no longer count as skilled. The rest of the planet did some catching up, and what counted as skilled now counts as menial.

Time to deal with it.

Comment: Re:#1 slashdot article submitters (Score 1) 257

by luis_a_espinal (#49138295) Attached to: 5 White Collar Jobs Robots Already Have Taken

Unemployment is created by government rules, laws, taxes, nothing else.

Unemployment is a function of capitalism in order to create fear and a willing pool of people prepared to do awful jobs for rubbish pay.

Unemployment, underployment and poverty have existed for as long as humans have developed stratified societies (7K years). I'm sure as fuck that this preceded capitalism, but don't let that stop you from posting ideological histrionics. Whatever rocks your boat, I'm not judging.

"What is wanted is not the will to believe, but the will to find out, which is the exact opposite." -- Bertrand Russell, _Sceptical_Essays_, 1928