"Should we begin divesting from Canada's corporations"
You should've been anyways, the Canadian economy is tanking like mad> Correction, if you weren't an idiot, you'd be buying heavy in Canada right now, since the exchange rate and relative weakness in the Canadian economy makes for some sweet low hanging fruit.
Slashdot videos: Now with more Slashdot!
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).
"Should we begin divesting from Canada's corporations"
You mean Half-life 2 deathmatch (which nobody played and Valve practically abandoned day 1)? No, we're talking about Half-life the single player experience. If Valve refuses to do a single player release then they should license the IP to a trusted dev do do it for them.
As for supported valve games, you have:
- DOTA 2 ~ 1.1m people playing it right now
- Counter-strike:Global Offensive ~ 300k people playing it right now
- TF2 ~68k
- Garry's Mod ~42k
- Counter-strike:Source ~11k
So yeah, they have a lot of games that people still play regularly.
"Starship Troopers the movie was lots of fun, but had very little to do with the book."
Reading the book recently, I can tell you that besides dropping the other aliens and turning the "highly trained soldiers of discression with pocket nukes when things go south" into jarheads, the book is story-wise pretty close to the book.
The huge distinction of the two was that the book takes itself seriously, and does a very good job at reinforcing the case for why their society took the course of events that they did. The movie took the opposite tact by ridiculing the entire system of governance and parodying the much more militarian nature of the society. Depending on your political stripes, you could lean with either take on the story material, but personally I enjoyed both (though the movie was a little heavy on the zany side).
Oh side note, Is Warhammer based loosely on troopers? Throughout the read, I kept remembering similarities to the architypes that game played (only video games, never played the tabletop).
His writing was certainly libertarian in nature varing from basically none to extreme. That said, his stories were always written well enough that you often don't realize/care about his politics bleeding int the pages.
His tendencies are more about frontier self-sufficience and the use of one's own (naturally brilliant though often fluke) ability to survive extrodinary situations. The formula generally works because his stories are written to play well against this formula while still being quite enjoyable (for the most part).
I'm really looking forward to the film, since mistress is one of my favorites from him.
An OS? God, you're such a young lazy punk. Get the hell off my lawn!
I know this post is supposed to be considered a critisism, but I'm not seeing it. Its exactly what should be done. Minimize the amount of work necessary to complete your work. I am the laziest programmer on earth, and if I can save an hour by dropping in a well tested cleanly interfaced library that meets my requirements, I'm going to do it.
"Nobody ever writes anything from bare metal, no complex algorithms, nothing"
No, people don't re-invent the wheel that already exists because we are too busy doing work that maximizes productivity. If I want to circle jerk about challenging and personally satisfying code, I do that at home because at work I'm paid to build. I don't get paid to pat myself on the back.
Meh, having the same number of code lines (highly dubious) then realizing that you implemented something wrong is just a waste of time for everyone. Why so quickly dismiss the expertese of the people writing (and maintaining) these libraries who in all likelyhood have much higher expertese in that one area of development? Instead, you write an in-house job that takes significantly longer (even if the LOC -may- comparible) then you realize it doesn't work. Your opinions are to bite the bullet and replace using off the shelf, or fight through the crap wasting more time and money.
All the above paragraph of course depends on what you're writing. If you can write the code in a day or two, I'd say its acceptible to eschew known libs'frameworks. If you're writing a very very tiny chunk of an existing library, you may be better served not dealing with the cognitive load and learning curve to introduce the new library. But, you also have to ask yourself if your currently fragile and developing system will ever have its requirements change and if so, will your implementation meet those future demands (Yes slippery slope and all that). Most of the time, built-frameworks were written by many hands for many different projects and they learned to support areas of expansion which are probably most likely to occur in the average project.
On the flip side, there are times where libraries and frameworks should be looked at skeptically, and it usually revolves around active engagement. If there isn't much or any active development on a product, its either reached its peak goal (something like log4j perhapse is a good example) vs. some dude's web templating engine that may have been brilliant when it was written 5 years ago, but has long been abandoned. It may end up being the perfect fit for your project and team, but it means having to learn and support that potentially unknown blob of functionality. That's when a library/framework can become a boat anchor, especially when it becomes a core function of your system.
From personal experience, I started a junior dev job on a several million line project where we were so highly coupled to a vendor's library that when vendor decided to stop supporting it, we were left dealing with the countless defects that came from it every time we needed to use it differently (sadly more often than anyone wanted). Lots of drama, blah blah, but by the time I left the company, little was done to fix it, which isn't surprising since they allowed the library in to begin with.
To be fair for OP, I've seen this behaviour as well form my Windows 7 machine. I know difinitively that I've seen it from in explorer file search results, but pretty sure I've seen it from basic tree navigation as well.
Yup, PDF's are bad on e-readers, but at least you can transcode them to native using something like calibre. Its not perfect obviously, but a whole lot better than suffering throught the squinting problem.
Too many people period are idiots about not negotiating equitable space that I just bowl them down. I'm taller and large bigger than most, so if I think they're being oblivious or careless, down they go! Being a dick about sharing a laneway is a dick move and the only ONLY way to punish it is to not yield.
If you wanted to be an uber dick, you'd pick up their phone and throw it away, but that's too much for me =) Oh, that goes double for movie theatre texters! Die in a pit of hell assholes!
Its still dumb now. Just have good public access to computers for educational purposes (for all) and maybe a few set aside for people with specifically high enough permissions for programming and such. 95% or higher computer work in school is research, and everyone should absolutely have access to use it. Do kids need them at home? Nope, but it'd help. If a family is willing to get a cheap computer / tablet / etc. for their kid, that's their imperitive. But for those unable/unwilling to pay for a computer, they should still have access to materials. But assuming unlimited portability is more of a pipe dream unless you're footing the bill. My libraries have had computers for going on 2 decades now, and they've worked great for what they do, supply people with access to information.
IPv6 needs 100% buy-in from all participants or else you need to run/pay for bridging services who converts between the two. HTTP/2 is backward compatible meaning any participants will transparently fall back on HTTP 1/1.1 if it's not supported. Plus, there are far fewer vendors of HTTP servers / clients than there are for IPv4 based software and hardware products.
Ok, I never watched the ill conceived TV program which by all accounts was simply a ploy by the production company to retain their rights to the show. Whatever, that's all legal BS that has absolutely nothing to do with the books or potential TV airing itself.
The only reason its being piped up now is because she was publically unsatisfied with the end product. Well guess what? How many people even heard of this poor excuse for a program if it wasn't mentioned in this article? In all accounts, a hell of a lot fewer people than those reading the new backlash. So now we know there was a show, it was horrible, and both the brand and the future for a visual adaptation (if and when they ever get off their asses to actually produce one) are worse off for it... Wooo
Screw all that crap. Just use Lombok and all of a sudden, your code gets considerably more concise while (the intellegent developer) still knows precicely what's happening behind the scenes.
Who cares about architecture when the OS platform and the development tooling around them are becoming more relevant? Android uses Java for almost everything, and IOS has its own toolchains that aren't portable, so the real problem is that the mobile development experience is largely siloed.
The only Android X86 product I've used is Nexus Player, which works fine for at least the cases that I use it on, and the few programs I've used from the side-loaded Android world work fine (it also has some form of ARM compat, so maybe a lousy example). The problem is that the VAST majority of X86 based devices are running windows, and on mobile, basically nobobdy cares anymore about microsoft. Its all Android / IOS regardless of how amazing a single piece of hardware is.
At least RIM woke up and started supporting Android apps, but even now, it may be too little too late (by like 4 years) for them. Microsoft's business is to make money from its OS, and doesn't seem to settle for app-space innovations, so they'll continue to be an also-run in mobile till they finally give up or somehow peak the next market hotness, but that seems more of a coin toss.