> So glad to see Lester's name back on El Reg!
It’s in everything the server sends. Check the HTTP headers…
69 posts • joined 27 Jun 2015
> You know this works in windows 10?
It didn’t in the early days – both active and inactive title bars were grey, and the shading on the active application’s taskbar button was barely perceptible, so it was impossible to tell at a glance which window was active. It’s just one example of the bigger point: Microsoft went out of their way to degrade the existing UI, which had worked brilliantly for years, solely in the pursuit of “Ooh, new! Shiny!” They may have relented now (in one or two places), but you know it was through gritted teeth.
> Microsoft give you options to customise the appearance of the OS, and get what you want
They give me a much more limited set of options than they used to, and I cannot get what I want…
IRIX had a great little additional feature, which I’ve not seen anywhere else: as you dragged the slider, it drew a divot in the trough at the slider’s original position, allowing you easily to return to where you started.
> What is the impulse to break established UI conventions?
Ooh, new! Shiny!
You’re not the only one, but Microsoft simply does not care.
As for using the File Manager source as the basis of something decent for Windows 10: it’s a nice idea — but if Windows 10 has got to the stage where the guy who wrote Classic Shell has given up, you might have your work cut out…
> Where's the Thinklight?
Gone because everything has to be razor-thin, because MacBook.
> Why on earth did they waste so much space on the palmrest?
Because the touchpad has to be vast, because MacBook.
OK: to be fair, the X1C is competing with the MacBook Air, so thinness is a feature. And a battery big enough to earn you a review like this one has to go somewhere.
Yes, the screen ratio is the other bête noire of old-skool ThinkPad fanbois (who admittedly constitute a minuscule proportion of Lenovo’s market). But it’s probably more complex than just penny-pinching: seemingly even the premium business segment is very price-sensitive; Apple and Microsoft have captured the entire supply of 16:10 and 3:2 LCDs; and trying to change the chicken-and-egg supply/demand status quo is a risk that even the big players are not willing to take.
The 90s happened; what’s less clear is whether Microsoft actively erases them from its employees’ memories or whether there’s simply nobody left who remembers them…
(There are notable exceptions such as Raymond Chen and probably a handful of others, but they are unlikely to have much influence over product strategy.)
It doesn’t matter how low the operating costs are; they always greater than zero, and the profit generated is negligible. Every fee-free ATM is unprofitable, and every business seeks to eliminate unprofitable activities…
(Furthermore, I doubt the restocking services comes cheap, given the risks involved; and you didn’t mention increased insurance premiums for having a high-risk theft target on the premises, or the cost of renting the space taken up by the machine that could otherwise be used for profitable business…)
… and unlike in the U.K., it’s ownership of any device capable of reception that makes you liable for the fee.
But if “all you have is an internet connection or a radio in your car” – and no Internet TV service accounts – you don’t have to pay the TV fee. (Yet. That will change in a couple of years’ time…)
The document linked in the article is (if I’ve understood correctly) just a motion to alter an existing motion before the city council. Schultz above linked to the full motion, which as mentioned refers to an external assessment of the city’s IT. Related documents are here:
Right up to the point some bright spark decides to send you their module’s version number in a double, then acts confused when you ask them how you’re supposed to tell the difference between 4.1 and 4.10…
By 4.99 the supplier had understood the issue, and skipped 4.100 – even if it really shouldn’t have taken them that many iterations to get the product working in the first place. At the same time our GUI had to go through a few versions of its own as we tried to keep up: "%.1f", "%.2f", "%.3f", …; "%g" might have appeared to be the clever answer, except another module had its final version at 3.120 and couldn’t be changed; we ended up having to set the number of digits to appear after the decimal point in a configuration file, which you might think would have led to "%.*f", except the person coding it didn’t know about that so we got if (numDigits == 1) printf("%.1f", version); else if (numDigits == 2) …
> “Read the man page for vi.”
Ah, if only I had been as enlightened for my own first encounter with the UNIX CLI.
Coming from an MS‑DOS and Windows background, my instructions were along the lines of: open telnet GUI in Windows; log in to SunOS server; “cd” is the same as MS‑DOS but it’s “ls” instead of “dir” and forward slashes instead of backslashes as directory separators; and “vi” is an editor. (No mention of “man”.)
OK, fine. Open telnet GUI in Windows; log in to SunOS server; poke around the filesystem a bit. So far, so good; maybe this UNIX thing isn’t so scary after all.
[Blank screen; no instructions.]
Press some keys. Nothing happens.
Press F1 for help. Nothing happens.
Press Ctrl+C to bail out. Nothing happens.
Use mouse to close Windows telnet GUI.
Biting the hand that feeds IT © 1998–2019