"/* ugly hack to... */" is a modest expression of pride describing concise, functional, readable and elegant C code...
Speak for yourself.
I usually use the expression "ugly hack" to describe the stupid shit I need to do to get around compiler or library bugs.
Because it is by design able to access a hell of a lot more than other languages. How many languages have direct hardware access? Or inline ASM code?
Amen.
As a rule of thumb, any code (in any language) that deals directly with hardware and doesn't have at least a few commented hacks should be treated with suspicion. It likely either doesn't work, the hackery is too subtle for mortals to comprehend, or the person writing the code is so clueless that they don't recognize when they've transgressed into writing horrible hacks.
So, basically, it's going to be just like school is today, except the teachers will be working remotely?
I suspect that veteran teacher has been doing it so like that he can't get outside of the box and imagine education without classrooms, schools, or even structured classes.
I think the future is going to look a lot more like home schooling (possibly in groups to get around the whole school-as-babysitter issue that allows parent to hold jobs) than anything close to the institutions teachers currently work in.
Copyright needs to (I reckon) end with the death of the creator; simple.
Given that we've established that the entertainment industry is a collection of sociopathic asshats, are you quite sure you want to give them a genuine monetary incentive to, say, kill copyright holders in order to plunder their now-orphan works?
Then there's the whole question of figuring out if/when a creator died.
A reasonable fixed term from publication/creation makes the most sense. Emphasis on "reasonable".
34% of users can't tell their iPhones not to connect to a hotspot named attwifi. That sounds like the ability to force connection to a WiFi network to me.
I'm thinking that if a malicious hotspot cycled through the known pre-installed SSIDs like "attwifi", common open SSIDs like "linksys", "NETGEAR", "dlink", "default", etc, plus corporate branded/hotspot SSIDs such as whatever Starbucks or McDonald's use, they could easily increase the vulnerable population to well over 75%.
Don't worry, after a while you'll stop caring about having anything correct in the summary at all.
Then you'll be fully qualified as a Slashdot editor.
The only time I have ever been aware of hitting a mobile site is when you have that "gah, WTF is this crap?" moment where you can't find anything and the link you followed has been swallowed by the crap which has said
:"hey, you're on a mobile, how about we fail to show you what you were looking for?".
Their guidelines suggest suggest this is one of those things that will be punished. Which makes this smartphone user quite happy.
I'm kinda hoping that having a handwriting engine allows them to do something useful, like OneNote-style integration with Google Docs.
What's worse than the apps on an Apple watch?
A 2 hour podcast about the Apple watch.
Keep in mind that you're looking at people who spent hours upon hours writing blog posts speculating about the leather and alloys Apple would be using in their watch bands.
A 2 hour podcast about an actual shipping device seems comparatively reasonable.
Yeah the MS junk won't be installed into CM just yet - but wait until that "Deep integration" Kirt McMaster keeps talking up starts happening - you're going to see architectural changes happen in CM designed solely to be beneficial to Microsoft.
Well... I'm less certain of that.
CM/Cyngn has to walk a fine line between making investors/partners happy and not pissing off the CM community. They don't make money from the community, but the community is a huge QA base and they'll have a lot of trouble developing and supporting Cyanogen OS without it.
If they ram through MS-specific stuff (versus just expanding the capabilities of the OS for everyone), a huge chunk of the community is going to bail on them.
I don't think they're quite stupid enough to do this. But I did say "Yet", because
So far that seems to be the major target market. As long as the carriers are heavily involved in choosing and customizing phone for consumers as they are in the US and Canada, I doubt you'll see a CM-based phone get much traction over here.
It maybe sucks for those who buy a phone with CM pre-installed, but they've already announced that there's no plan to install any MS junk into CyanogenMod, and it's highly unlikely that the community would stand for it if they tried.
So, not something to worry about terribly much. Yet.
That's probably because somewhere in the google complex, there are some crusty old bureaucrats that just cant let go of the notion that "Proprietary == Profit!", and that "Control" takes many forms other than just "Stop all competition at all costs!"
I think it's just as, if not more, likely that within the Google complex the general mindset is that any Google service in Android (or more generally, on the web) is going to so much better than any competing service that nobody in their right mind would care about that competing service.
Which isn't an entirely unreasonable opinion/bias if you think of it from their perspective. There's obvious counter-examples like Google+, but in the case of the core services like search, maps, their app store, etc, it's... well, I don't think it's the slam-dunk Google might think it is, but there's at least a rational basis for having that bias.
To some degree, that's where this EU action leaves a sour taste... there might be a basis for some action (scraping competitors websites for data to use in a shopping service *does* sound pretty dodgy), but the overall tone of it seems like the EU attempting to punish Google for sincerely believing that their own products are best of breed in their respective spaces.
Someone needs to come out with a diagram of how, what, and who gets paid in the music business.
Risky. On one hand, you might just end up with a diagram telling you where the buck stops. On the other hand, you might end up summoning the Elder Gods.
... something like this:
int is_troll( const char* username ) {
if( !whitelisted(username) ) {
return 1;
}
}
Eureka! -- Archimedes
