And thank you for that. I found beta unusable (and unreadable unless I turned CSS off). I'da hated to give up on.... good gods, 17 years I've been here??! the site is older than some of its users!
One thing that comes to mind on this 'new' look is make sure you check how it behaves at very large font sizes (which a lot of low-vision folks do use) and not necessarily an ultra-wide screen. Right now the Search box winds up overlaying part of the top menu.
The problem with black-box programming is that it's a trap. Far more often than anyone cares to admit, the black box implements functionality in an unreliable or inefficient manner. When you're dealing with code that you wrote yourself, you can correct that behaviour of the "grey" box. But with a third-party black box, all you can do is file a bug report and hope that someone can not only replicate the problem, but that they'll give it high enough priority to fix it before you retire or your project is cancelled.
The worst culprit for black box problems are frameworks of all kinds. Some say you're not a "real programmer" until you've written your own framework. I firmly believe that's true, because what is a reusable code base on a large project except a custom framework?
The difference between a custom framework and an off-the-shelf one is that your custom framework is designed and coded with your project in mind, to service the bulk of your project's needs while maintaining enough flexibility to deal with the exceptional cases of your project. A third party black box framework is pretty much never designed that way. It was designed to serve the needs of someone else's conceptual or real project, then tweaked and adapted to serve needs it wasn't originally designed for, and finally unleashed on an unsuspecting world as "the next big thing."
A pox upon frameworks, I say. Design a solid object model, code to it, use it, and get over the fact that you're going to have to write some code.
At least if you wrote the code, you can fix it. Without worrying about whether some upstream integrator will deign to consider your "fix" worthy of integration to the mainstream code. Without having to wait for someone else to replicate, analyze, prioritize, schedule, implement, and test a fix for your problem.
Realistically, any half decent custom framework isn't going to be more than 10% of your total code base anyhow. "Framework" is just a fancy term for what was called for decades "application library."
I knew a lot of people who had the controllers for those types of games over the years, which they'd either bought along with their consoles in bundles, or been given by relatives. But not once in my life did I ever see anyone actually play games like "Guitar Hero." Not once.
Yet I knew over a dozen people who had the controllers.
I wonder what percentage of those overpriced components sat gathering dust, never to be used after the novelty wore off in the first couple of weeks?
Verizon's arguments about controlling content are absolute red herrings. A content creator like a newspaper gets to determine the content and articles they publish or promote. The manufacturer of the paper it's printed on has no say.
The first thing I uninstall is McAfee. That piece of crap wedges in a VB script interpreter that breaks many of the software installers I have to put on my machines to make them useful. THE worst anti-virus product ever.
It also claims that SAP/Sybase ASE is infected, and deletes critical files from the install.
I find it gratifying to see that Mr. Nimoy is being remembered on every website and feed that I've visited today. And not merely remembered, but remembered by more people than I've ever seen pay tribute at the same time. Even the passing of Robin Williams wasn't marked with as many posts and comments.
RIP, Leonard.
The automobile industry coasted on that for decades. Identical car, different fenders.
No doubt so, but how about the cost of operations in rough country with poor access, where going in on foot is feasible (witness the illegals crossing it) but patrolling in ground vehicles is not?
Hence I think the real comparison should be: How does the cost of using a drone compare to the cost of using a helicopter in those same areas? I'd guess the drone is significantly cheaper.
Second, how long does it take a drone to patrol, compared to a manned ground vehicle in the same area? What's the total patrol cost per hour for drone vs 4x4?? (Don't forget to factor in the cost of the 4x4 as well as for the drone.) In rough country, a drone (or helicopter) can get an overview in a few minutes, but a ground vehicle might be forced to wind back and forth for an hour to reach the same point (and might still not get a view of the ravines). If patrolling a given area takes the drone ten minutes and the 4x4 an hour, which one is more cost effective?
How does it affect man-hours? The patrol is generally two men, while the drone only needs its operator.
How does all this affect insurance rates on their various equipment? Do reduced hours in use also reduce rates on 4x4s and such? (Certainly it will reduce maintenance costs.)
Lots of factors to consider, not just 'dollars per arrest'. We need to see spreadsheets and balance columns, not assumptions.
It's absolutely sickening how many trolls have responded to this topic with comments about people "just wanting attention" or the world being better off without them, and other such tripe.
The absolute cruelty and judgementalism of people who've never dealt with chronic depression or mental illness is just shameful.
This is the "intelligent" commentary of slashdot nowadays?
Man has this place ever gone down hill. How I long for the days of harmless "trolls" posting comments about Natalie Portman and hot grits, which did nothing more than annoy instead of being outright mean, spiteful, and hurtful.
Not lying, but your average tyro is not going to achieve that. Like the guys on that beekeeper forum said, a single super might produce anywhere from 3 to 20 pounds. But the location and climate need to be optimized. City flora are hardly ideal, and your bees need to be where the nectar is. Where I worked (this was a pro operation, these guys did bees for a living) the supers were on the heavy end, but those bees were taken out to the orchards and buckwheat, or even out of state as conditions might dictate. They didn't make do with whatever the hell was growing around 'em.
(Buckwheat honey, gag. Most of that got exported.)
My experience has been that management comes to the developers for estimates. They provide those estimates to the end users. The end users bitch, whine, and complain that they need it to be done in half that time.
Management then comes back to the dev team and tells them they've agreed to get the project done in half the time that was estimated.
Then both management and the user community bitch when their "estimates/targets" aren't met, and who is blamed for the issue?
The developers.
The developers always are to blame for computer problems, never the bad specs, the conflicting specs, the unknown variables, the use of "new technology" that some vendor flim-flammed onto the department/team, or anything or anyone else.
Screw 'em. Now that I'm retired, I'll never have to give anything more than the most vague ballpark estimate of how long it will take me to do something ever again. Instead, on my pet project, I just bullet point some of the things I intend to work on next -- and even that is subject to change. The lack of stress and the freedom to live my life according to my own whims and needs has proven an invaluable source of improvement in my "quality of life."
What a shame I've never encountered a job that would let you do that.
The creators of the printed ravioli were very enthusiastic about their product. "It's almost as good as Chef Boyardee!", they exclaimed.
*Blech*
Remember this?
It wouldn't be gallons; it would be a few quarts. A lot of the interior of the hive is space for the bees to move around. Figure maybe a third or at most half the volume of the super (the part with honey-laden comb in it) is honey.
http://www.beesource.com/forum...
I used to work in for a beekeeper, mostly building hives and extracting honey.
Journalism has already been crowdsourced. All you have to do is look at the number of blog postings and discussions at any website that references "news" articles (including Slashdot) to realize that.
Newspapers are already being forced into a co-operative model to apply the resources needed to do true investigative reporting, like the most recent HSBC scandal. None of them have enough staff left on the payroll to do it by themselves.
Software and IT have much the same problem, though the "crowd" is a bunch of cheap overseas labourers instead of the general public. But the end result is the same -- highly paid skilled professionals replaced by cheap mob mentality grunts working on the "million monkeys" theory of producing quality.
The legal profession has been impacted big time just by the ability to do keyword searches of article databases instead of paying junior staff to do the legwork of researching relevant cases for the lawyers in a firm. Most new lawyers are finding it hard as hell to get into any real firms to gain experience as a result, much less ever be offered a partnership.
Note that not one of these changes required anything as earth-shattering as "AI" -- just automation and distribution of common tasks.
Suggest you just sit there and wait till life gets easier.
