@boomzilla said:
Provided you're equipped to listen to your customers, complaint driven development isn't that difficult.
Now we have a case study involving a guy who wasn't equipped.
Super Straight
@boomzilla said:
Provided you're equipped to listen to your customers, complaint driven development isn't that difficult.
Now we have a case study involving a guy who wasn't equipped.
@nullptr It could be worse! I'm not sure how, exactly, but I trust you'll come back next week to tell us how.
The effects are still being benchmarked, however we're looking at a ballpark figure of five to 30 per cent slow down, depending on the task and the processor model. More recent Intel chips have features – such as PCID – to reduce the performance hit.
...
It is understood the bug is present in modern Intel processors produced in the past decade. It allows normal user programs – from database applications to JavaScript in web browsers – to discern to some extent the contents of protected kernel memory.
Yikes. This sounds like a pretty big deal.
The fix is to separate the kernel's memory completely from user processes using what's called Kernel Page Table Isolation, or KPTI. At one point, Forcefully Unmap Complete Kernel With Interrupt Trampolines, aka FUCKWIT, was mulled by the Linux kernel team, giving you an idea of how annoying this has been for the developers.
LOL.
Yay! A new 12c misfeature!
Let me set the stage by pointing out that there are two types of clients...the "thin" client and the OCI client. "Thin" is what developers would generally use for stuff and the OCI is what you put on servers. Or at least, we do. It's my understanding that the OCI version handles clusters or whatever shit that you want on a server but don't really care for doing your development. Who the fuck knowscares?
Anywho...if you're using the thin client and your DB password is within 7 days of expiring, you get an error message:
ORA-28002: the password will expire within 7 days
OK, that's easy enough to deal with. But...if you're running the OCI client, you get something like this:
oracle.jdbc.driver.OraclePreparedStatement.<init>(OraclePreparedStatement.java:1387) java.lang.ArithmeticException: / by zero
Which is kind of scary to have happen when you haven't changed anything.
Fuck you Oracle. Fuck you.
We have it now, sort of, but because UIs don't directly make money it's been shuffled to the side where it's used to set timers and makes humans yell "OPERATOR" at their phones to try to get to talk to an actual person. :(
Because in the meantime people who work with computers a lot got used to keyboard and mouse, and found them to be fast and accurate, so the voice control isn't being an advantage. While the less tech savvy people, who find keyboards and touch-screens hard, appreciate it, even if they only need simple things like setting an alarm and choosing a person to dial. Plus the simple cases were easier to get working sufficiently reliably.
The voice stuff is super handy when you're doing other things with your hands (cooking, driving, etc) even for those of us who like using CLIs (and don't have scottish accents).
Scottish Elevator - Voice Recognition - ELEVEN ! – 03:36
— Noel Noone