Even in the age of physical copies, pre-order made little sense. If a product is successful, you make more of that product to sell. If your supply chain can't keep up with demand, you build more production capacity to capture that demand before a competitor does.

In the digital age, consumers have zero need to pre-order. There is no scarcity. If anything, publishers should thank their lucky stars that we still pay retail prices for a file that costs less than a penny to deliver, instead of blowing roughly half the sticker price on packaging, distribution, mark-up and overstock.

Pre-orders are basically rewarding big publishers for harassing us with obnoxious marketing campaigns.

This is my take-away as well. I've had 10GbE for 3+ years in my lab and at the datacenter, but the prices for add-in NICs and switches have not budged at all since launch. I can get a motherboard with two 10GbE ports built-in for roughly the same as just a dual-port PCIe NIC, so the numbers just don't make sense.

Adding 2.5G and 5G to the mix will only result in more market segregation, to keep the cheap consumer/enthusiast parts from bringing enterprise costs down.

Nevermind that a bunch of people have been running 10GBase-T over Cat5e for relatively short distances, myself included. There's a 50-foot run going from my workstation to the rack, running right by an electrical panel and a pile of assorted wireless transmitters. I have no problems saturating the pipe. For the 3-to-7 foot lengths within the rack, I'm using ultra-cheap Cat5e patches from China. Again, zero speed or latency issues.

I would not be at all surprised to see 10GbE run effortlessly over typical office runs of Cat5e, even if it dips to half its theoretical capacity it's still a bargain. This new standard seems quite redundant, and the vicious cynic in me suspects this was done to protect the nascent 10GbE switch market from competition. Now they can target 2.5G as the cheap option, charge a premium for 5G "enthusiasts", and keep 10G firmly pegged above $100 per port.

That's funny, I used Borland and other 3rd party compilers for almost my entire career, and never encountered any such breakage. Heck I have code from 20 years ago that somehow runs perfectly fine in W10. The only things I've had to fix from that era, were things I wasn't supposed to be doing in the first place, like self-modifying code and other low-level hacks that don't fly in a post-80486 world. MS jumps through hoops to retain backward compatibility because the entire value of their platform is in the massive wealth of software written for it.

What ?! I've sold "naked" systems since the 90's and somehow managed to turn a profit. MS doesn't make it unprofitable. All they did was give ridiculously cheap licenses to the big guys, while the rest of us indies have to pay the regular "OEM" pricing which is frankly not much cheaper than full retail.

There are plenty of reasons to dislike Microsoft. The ones you've mentioned have very little basis in reality. The only people who can break Steam are Valve with their potato-quality code. Microsoft and its partners do not want to piss off the hordes of PC gamers, because the day we abandon Windows will be the day Linux finally gets decent graphics drivers for Steam Boxes, and that day will mark the beginning of the end for Windows' market dominance.

I'm an independent white-box NAS guy, and with the exception of the truly awful 1.5TB Seagate drives from 2008-2009 or so, I have not had any significant problems with them. I've got a few thousand 3 to 8 TB drives deployed with my clients, most of them cheap consumer drives (not even the "NAS" editions), and the annual failure rate is roughly 2% across all brands. This has been consistent for many years and I factor these stats into my costs and warranty projections. I have

The thing that bothers me about Backblaze, and the reason why I have a very hard time taking their results seriously, is the way they design their pods. They take a custom fabbed chassis, then fill it with the most ghetto components known to man: SATA port multipliers, ultra-low-end HBAs, dual "gamer" power supplies, very substandard cooling, and until recently they used super sketchy desktop boards. It's only last year that they finally changed the board for a Supermicro, primarily to get 10GbE very cheaply. For that same money, you can buy a ready-made 60-bay Supermicro chassis with redundant power and SAS - and a warranty. Hell, I bet SM would deliver directly to Backblaze's doorstep *and* give them a friendly discount.

Anyway... epic digression aside, when people ask me which brand is better, I tell them to buy whichever has the best warranty. A hard drive *will* die, the question is when, so the only logical course of action is to plan around its inevitable demise by keeping backups and redundancies, and learning the ins and outs of the RMA process.

Well, kind of. They probably don't hate "you", but they sure as shit hate their job, their managers, the company policies, the guy whose sole purpose is to wag his finger if you log in two seconds late. There is plenty to hate in a call centre, but for the most part the customers are cool enough.

I can confirm that most are totally oblivious to whatever product they're supporting. It's all knowledge bases, wikis and checklists, and man are they ever confusing and poorly curated. Often times agents would be so wound up trying to read all that garbage that they'd completely miss some crucial bit of information shared by the customer, going down some rabbit hole, troubleshooting the wrong issue and getting all tangled up in the process.

During my brief stint at $BIGPCCORP's call centre, out of about 200 agents on our floor, we had three hardware wizards, maybe five coders, and the rest were completely unskilled, except for a week's training on the company's previous gen products. They really hired any warm body willing to work shit hours for shit pay, and that reflected in the performance metrics. Us three hardware wonks jockeyed for the top three spots, followed by most of the coders, and then a huuuuuuge gap in call times for everyone else (I'm talking 30:1 between top and median agents).

So really, for clients calling in, they had a 1.5% chance of getting a rockstar techie, a 2.5% chance for a really decent techie, and a 96% chance of wasting the next two hours of their life over something as simple as a dead hard drive. The irony ? They took the best people off the phones to put us in different, non-customer-facing roles. I left shortly after that move.

Strange, I could have sworn that I replied to this with a very detailed and lengthy response... urg.

Anyway, upshot is this: Perl 6 hasn't yet had a chance to flop. It was released in beta in December of last year and continues to make steady progress. Users are checking it out slowly, but I don't expect a landslide migration. P6 will have to prove itself as a language.

I won't say, "I don't think it has," because it demonstrably has not.

The language has been released in open beta. It still has many properties that I think chase away those who approach it outside of language research communities. As a Perl 5 nostalgia fix, the learning curve is just too daunting, so as the beta progresses, I expect it to continue to build its own base of enthusiasts, the same way Perl did when it was first released.

So the language has not "flopped" yet because it hasn't had a chance to succeed yet.

It took Perl many years to go from a small toy that a trivial number of Usenet enthusiasts had heard of to a standard part of the Unix and Unix-like toolset. I don't think Perl 6 will gain traction any faster, especially given the learning curve. That's not flopping.

However, it has some substantial advantages over other languages. High on that list is the trivial nature of slinging highly functional grammars as first-class objects. That's something that you just can't do as easily in any other language that I know of. Perl 5 parsers and those of many other high level languages have some pretty severe performance penalties; yacc and its kin aren't dynamic enough; the various parser generators for Java are fast and mostly complete, but really painful to use.

Basically, you need a language that closely integrates grammars with the language itself in order gain the benefits of Perl 6. Here's and example parser I posted to reddit the other day:

https://www.reddit.com/r/perl6...

A few other notable things that I think will draw people in:

The generalization of operators over iterable sequences and the hyper-operator version of reduction are features that you're going to hear a lot more about, I suspect. Perhaps in Perl 6, perhaps in other languages that adopt these ideas. I'm especially stunned by the utility of hyper-method-invocation (foo>>.method) which dispatches a given method over any iterable sequence of objects (whether they are the same type or not).

Full macros have not yet landed, not least because we've never had a full understanding of what macros would be. We know that they need to operate on the ASTs that represent code, and all of the self-hosting properties necessary to support that are there, but the exact syntax and semantics that are most Perl-friendly haven't fully gelled, yet. Once they do, I think that every language to have true macros in the past (mostly Lisp variants) has demonstrated the power of this tool.

A few other languages auto-generate accessors for classes, but I find the way Perl 6 does it to be a substantial improvement on the field, and it really is a joy to use. I think others will feel the same.

Speaking of objects, role composition will take some time for people to get used to, but as in other languages that have had similar features, I think this will be critical to Perl 6's adoption.

There are dozens of smaller features that are just quality-of-life benefits ranging from lexical variable/named parameter passing to the way any block can be turned into an anonymous closure and even curried. Some of these will be important to some, but not to others. It will be interesting to see it play out.

Look, I don't like COBOL as a language, never have. I dislike it almost as much as I do Python (for diametrically opposite reasons). Thing is, it has worked for a very long time, and governments around the globe are still using it to this day. I know up here in "where you're moving when Trump wins" Canada, we have a lot of gov't projects to migrate off of old COBOL systems. It's not because the old system is broken: it ain't. It's because the people who can maintain such systems are dying of old age.

It's not a simple matter of watching a Youtube video made by a 12 year old. The language itself is quite simple, it's the fifty years of legacy code that make it a nightmare to find new blood, and the few who can pull it off get to charge whatever they want. On paper, this becomes a steep liability, which is why departments are making the largely financial decision to migrate.

Problem is, governments are legendary at hiring the most incompetent, 7000% over budget, milk-the-cash-cow-dry kind of contractors. Whether it's due to corruption or ineptitude, it's true up here in Apologyland. It's true down there in Gunfreakland. It's probably true across the pond in Thataintfoodland.

Don't blame COBOL, that old dog has done us well for most of our lifetimes. Blame these idiots who can't manage their contractors, and the contractors who can't manage their idiots.

You are absolutely correct on all counts, hairyfeet. I don't vape, but I have learned more than I ever cared about vaping, after challenging my wife on all the technical aspects and the pseudo-sciencey specs she was parroting from the manufacturers.

While I find it rather absurd that anyone would buy a device that is little more than a shiny chassis around a shorted battery (the "mech mod"), well these things do exist and they often attract a very special kind of idiot who will absolutely cause it to blow up in their face. To me, that is Darwinism at work, and perhaps a few disfigured imbeciles will scare some sense into the rest.

It reminds me of this kid I drove when I was a cab driver, 18-19 years old. He had flipped his nitro-boosted Honda while illegally racing on a main street, but somehow dodged jail time. The crushed door frame sliced his arm lengthwise, dude looked like something out of a horror movie, skin grafts and inch-wide scars all over. So what does he do ? He builds another nitro ricer and crashes it, hardly a year after his first accident. Luckily (for society), that killed him outright.

TL;DR, idiots do idiot things, because they're idiots. They always have, and always will. Vaping is no exception.

Okay, so why can't they release those customizations as packages that install on top of the standard Android OS ? Why can't Google put out an official "blessed" kernel and base system, and then the OEMs load their themes, custom launchers or whatever else they think defines their brand ? That blasted Samsung browser is an app like any other.

It's Linux and Java: two things that are extremely modular by design. Two things that already excel at combining executable code from dozens if not hundreds of different people, and adapting to wildly divergent environments. I develop friggin' appliances for a living so I'm not about to buy into the idea that a company a million times larger than mine can't figure out how to create a DEB or RPM or JAR or whatever the heck. Nevermind that it frees up the resources they're currently spending on rebuilding and revalidating the core OS with each update.

Reader who knows nothing about a thing proposes a contrived and oversimplified way to "improve" said thing, which didn't need improving in the first place.

Reader then questions why he's not the president of the universe with all his great ideas.

Dude... I feel you. I too was once 13 years old. It gets better.

It's been a little while since I wrote mobile apps, but I seem to recall camera functions being freakin' easy to use. What are they "building" exactly ? These camera apps are the kind of thing a mobile noob can pump out in a day or two (speaking from experience). I mean, both iOS and Android APIs will happily encode to an MP4 file of your chosen quality, which you then read and upload wherever. Live streaming is less obvious, but well researched and documented... a simple copy-paste-tweak-run affair.

Or maybe the engineers are waiting for the Kardashian seal of approval :P

Bah. I like it for many of the same reasons you guys hate it. It absolutely is weird indie no-budget art-house hoopla, and that's what I find refreshing about it. It's like someone deconstructed the video feed from my own waking nightmares. I mean, I kind of related with the character. Obsessing over patterns, crazies pestering me with numerology nonsense, migraine-triggered freakouts and irrational behaviour... pretty much how my twenties played out.

Beyond that, the technical merits of the production are pretty killer. I really liked the deliberate (ab)use of framing, lighting and music/noise to highlight the lead character's mental states Migraines for me are often a hallucinatory affair, and I thought they did a great job of recreating that distressing synesthesia.

But hey, to each their own. Lots of people paid money to see Transformers, and I think those were giant nonsensical turds...