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

 



Forgot your password?
typodupeerror
×

Comment Re:Technically C++ (Score 1) 230

My Slashdot username predates my current employment arrangement by about 5 years, I think. But, yeah. Back then I ran FreeBSD (which is where the name is from) on my servers, and Gentoo on my desktop. Things change :) (well, some of them; some of my home servers are still FreeBSD - ain't broken and all that...)

By now, though, it's not really all that surprising, given the amount of work specifically targeting other platforms (Linux among them) happening throughout the company. My team, for example, is actually specifically looking for people with a Linux background right now, because we're building a service running on it, using Docker containers for isolation.

Comment Re:Technically C++ (Score 1) 230

In this particular case I just happen to know exactly what they were thinking when they were implementing this feature, because they are my colleagues (even if I don't work on the team that works on C++) :) The list of features that they did was based on some specific libraries that they had most complaints about on Windows, and then filtered down further based on ease of implementation. If I remember correctly, one major beneficiary of those changes is supposed to be ffmpeg.

This all might make more sense if you remember that Office in some incarnation or the other now ships across three non-Windows platforms (OS X, iOS and Android), then there is the OneDrive client etc. Basically there's a whole bunch of stuff that has suddenly gone cross-plat in the past couple of years, and that's a lot of C++ code that now has to play ball with the libraries that are the de facto standard outside of the MS ecosystem. In many cases, once you start doing that, it makes sense to use the same library on Windows as well, but then you start running into those conformance issues with C99.

The other aspect is that we want people to write cross-platform C and C++ code, because it's the kind that, right now, is most easily portable between all mobile platforms - and seeing where Windows phones and tables are in terms of popularity relative to iOS and Android, MS has to encourage portability as a way to get more apps ported to Windows. You see things like Apache Cordova tools and Clang/LLDB support in VS 2015 for the same reason - they make it easier to write Android apps, for example, but more importantly, the way they encourage writing those apps just happens to be the one that emphasizes portable code. Now that is more geared towards C++, but the question of popular libraries written in C also comes up there.

Comment Re:Technically C++ (Score 1) 230

VS2013 seems to understand a bit more or C99, but that isn't because Microsoft would suddenly have started caring about their C compiler. Their C++ compiler got a bit of an upgrade wrt. more recent changes to the C++ standard, and the C compiler understanding a few C99 idioms is largely a side-effect/waste-product of that process.

Not quite. VS 2013 actually saw a bunch of C-specific C99 features such as designated initializers for structs. The main reason why this was done is because there are now quite a few popular open source libraries that use those features, and VC is the only compiler that cannot handle them, which made it a pain to port them to Windows.

Comment Re:That's C code (Score 1) 230

stdio.h and cstdio are both valid in C++. However, there is a slight difference - cstdio is only guaranteed to define the identifiers that it provides in namespace std, while stdio.h makes the same guarantee only for the global namespace. In practice, they are usually both backed by the same header that does both, so you'll get both - but relying on that is non-portable. Since he doesn't use std:: to refer to those identifiers, "stdio.h" is the correct header for him to include.

Comment Re:That's C code (Score 1) 230

"stdio.h" searches the directory containing the current source file first, then the include directories.

The standard itself doesn't have any notion of "directory containing the current source file" or "include directories", actually. It just says that "..." does some form of implementation-defined search, which, if it fails, falls back to <...>.

Comment Re: That's C code (Score 1) 230

It's still not the same thing. In C, you can declare a function without specifying the argument types, but then define it with specific types in a different translation unit. In C++, the definition and the declaration must match - if you declare it as int foo(...), then you must also define it in the same way (which renders it effectively useless, since without any named arguments you won't have anything to pass to va_*).

Comment Won't hire 'monolingual' developers (Score 1) 267

I explicitly will not hire any programmer who knows only one programming language (C and C++ count as 1 for that score.) Learning a different programming language introduces you to alternative ways to think about problems and solutions. Lisp or Scheme, Ada or Eiffel, COBOL or MUMPS, all provide a different perspective on software design, coding, test and integration.

Too many hiring managers play "buzzword bingos" in search of "flying purple unicorns," candidates whose buzzwords match their current search list. Sure, you can make a living chasing buzzwords that way, with a combination of (primarily) resume engineering and (secondarily) training. And some people who do this are actually pretty good developers. But many more don't know how to apply the technology, they're just able to produce toy programs learned from " for Idiots" who produce the stuff documented on http://thedailywtf.com/ But the people I want are those who can think creatively about a problem, using more tools than just one hammer, and who can learn new stuff on the job. What's the half-life of a technology these days, 3 years?

Comment Re:Hmmm Tasty Whale Tongue (Score 1) 47

Were you trying to say:

"LOL, nei, (th)að var ekki augljóst að "here" ((væri?)) Ísland og að (th)ú værir íslensk. En ((??????)) Google Translate get ég látið eins og hálfviti á tveimur tungumálum. Ef gert er ráð fyrir auðvitað að Slashdot ((sé ekki að flækja Unicodeið?))"

That is:

"LOL, no, it wasn't clear that here is Iceland and that you were were Icelandic. But (????) Google Translate I can come across like an idiot in two languages. If one assumes of course that Slashdot isn't screwing up the Unicode"?

Comment Re:Hmmm Tasty Whale Tongue (Score 1) 47

I'll reiterate: People here think it's a ridiculous product. The page is stupid marketing to foreigners. Yes, there are separate accent and apostrophe keys (in case you're curious, here's what an Icelandic keyboard layout looks like). Hákarl (the fermented shark you refer to) isn't eaten commonly, it's actually fairly rarely eaten (though some people do like it). Most of the foods you'd consider weird are rarely consumed, like sheep heads, skate, etc, often associated with a particular festival or whatnot. Probably the only things you'd find weird that are eaten fairly commonly are horse and fish jerky (harðfiskur). Lamb is commonly eaten here but you probably wouldn't find that weird. We also have a lot of dairy products you don't have but I don't think you'd find most of them that weird. Anyway, probably the most commonly-eaten food here is pizza ;) Hamburgers and hotdogs are common too (though our hotdogs are made of lamb).

Whale is eaten here but rarely. Nearly half of the catch consumed in Iceland is eaten by tourists (a large percentage of which, I should add, come from America). Also I'm continually surprised by the percentage of Americans who criticize Iceland for whaling but don't know that America whales too, and no small amount (producing thousands of tonnes of whale meat per year). Yes, they're "natives" whaling, but 1) it's no less traditional for Icelanders to whale than it is for Alaskan natives, 2) Alaskan natives use modern equipment for whaling too, including chasing them down in speedboats, killing them with modern equipment, and dragging them on shore with backhoes; and 3) Alaskan whales end up no less dead than Icelandic ones. None of the Icelandic whale populations are threatened.

Anyone who wants to discourage whaling over here, a few tips.

One, don't come out with the self-righteous stuff, because it doesn't fly. Not only does the US whale too, but receiving lectures on morality from a country where a majority of the population supports torture and who engages in all sorts of obscene human rights abuses and whose domestic livestock are mostly raised in factory farms in horrible conditions doesn't exactly come across well.

Secondly, know that any overt pressure is just going to cause backlash, and the more overt, the more the backlash. Many of you may see for example Paul Watson as a hero. Here he's seen as a ecoterrorist; he literally sent people in to sink ships right in the public harbour. If you want to be taken seriously, you need to distance yourself from these sort of people. You don't make friends by talking up people who come in and wreck up the place.

Third, understand the local perspective. It's not only that they've been eaten traditionally since Iceland was settled (indeed, the word for "beached whale" also means "jackpot" or "godsend", because in the old days it could mean the difference between life or death for a whole town). It's that they live free out in the open ocean, growing up their whole lives unhindered by man (except when, say, a NATO ship uses a super-powerful anti-sub sonar in the area or whatnot :P), living a pretty much idyllic life - and a single whale provides a vast amount of meat. Meanwhile, pigs for example - also highly intelligent animals - grow up in horrible squalid conditions in many of the countries that criticize Iceland .

Fourth, there are actual arguments you can make that have effect, and have on their own been discouraging whale consumption - but which foreigners who oppose whaling rarely make. Probably the foremost of these is the health issue. Whales, being top predators, tend to have dangerously high levels of heavy metal and organic pollutant contamination. If you want to make someone feel uncomfortable about eating whale meat, point out how much mercury and lead they're eating in that serving. There are also lesser arguments you can make that may or may not have effects on the person, depending on the individual - intelligence (but you better be well versed in the scientific literature, unbacked claims won't fly), for example, or how long it takes a whale to die versus other types of animals slaughtered for meat - but depending on the person, that may or may not be seen as a good argument. But the toxin contamination issue will have an effect on pretty much everyone.

(also, realize that not everyone here eats whale at all, and most people who do eat it only rarely)

Lastly, focus on the tourists. They come in for just a couple days and yet a large chunk of them order whale while they're here. Many of them oppose whaling back home, but it's as if when they come here their strict "morality" goes out the door, in the interest of "trying new things". I don't think they realize that they eat such a large percentage of the Icelandic catch, or that they somehow disconnect from where the meat comes from. There's a campaign here called "Meet Us, Don't Eat Us", encouraging whale watching instead of eating whale meat, and I think that's a very good strategy. The whale watching industry is economic counterpressure to the whaling industry.

(As a side note - I say all of this as a vegetarian).

Slashdot Top Deals

With your bare hands?!?

Working...