Well, better late than never; I'll be looking forward to picking up one of these. Chording on the UHK 60 v2 was a minor but constant irritation since I had to move between regular keyboards and the UHK frequently.
Not a fan of the integrated palmrests that look like they can't be removed. Also not a fan of the OLED since the lifespan is going to be far shorter than the LEDs on the previous model.
Rather obscure but there there's also Hostile Waters: Antaeus Rising which comes in second only to Battlezone 98 as my favorite in the first person RTS genre. Tom Baker voices the narration, which is a nice little bonus.
Which can make business sense if you take into account both the probability of the project failing to deliver a competitive product (always high no matter how slick the pitch deck is) and the probability that it gets no traction in the marketplace even if it is as good as the competition. Buying an existing successful product and its customer base can be much lower risk even if it is the more expensive route.
The display, RAM, and other peripherals are consuming power too. Short of running continuous high CPU loads, which most people don't do on laptops, changes in CPU efficiency have less apparent effect on battery life because it's only a fraction of overall power draw.
And Neal Stephenson acknowledged it was obsolete in 2004:
"I embraced OS X as soon as it was available and have never looked back. So a lot of 'In the beginning was the command line' is now obsolete. I keep meaning to update it, but if I'm honest with myself, I have to say this is unlikely."
But people still dredge this quarter century old apocrypha up and use it to pat themselves on the back for being Linux users. "I use a Hole Hawg! I drive a tank! I'm not like those other fellows because I'm a real hacker!"
Sure, I'd be fine with that but that's going to have knock-on effects on developers because they're the ones writing the code and therefore the vulnerabilities / bugs. Software engineering would turn into something like civil or aerospace engineering or medicine where where practitioners are required to be certified in various ways, either they or their employers carry liability insurance for bugs they write, and endure onerous processes / audits that their employers and insurers demand of them to reduce the risk of bugs. That I'm fine with too since there's so much crap code being churned out but most software developers probably wouldn't.
Sure but what does "rewarding security", as the author suggests, in a way that is genuinely meaningful look like? The direct metric would a low number of security holes or bugs in the product but then you run straight into the problem that many holes/bugs are not found until much, much later, if ever. Perhaps code review failed to notice it, perhaps QA didn't cover that case, perhaps security scanning tools missed it, perhaps no black or white hat hacker ever bothered to try to break it, etc. Without a meaningful metric, what will likely happen is that people get rewarded for some kind of security theater.
Ouch, now that really stings to wake up to. Eva aside, Nadia, Gunbuster, FLCL all stand out among the great anime of the '90s-'00s. Even lesser known series, like KareKano, which Anno had a hand in, really have a vivaciousness to them to them that just isn't that common. RIP Gainax.
Rapid reading and comprehension¹ and exposure to a breadth of vocabulary and ideas is the professional equivalent of having superpowers. So many developers have crappy writing skills and weak reading comprehension and have to struggle harder to develop their careers because of it.
¹ The barren wasteland that is online discourse doesn't count for obvious reasons.
Solid article. The one quibble I have is IMO that there should be mention that, when the choice is made to use an untried technology, it needs to be acknowledged and communicated that this carries some level of risk and an increased chance of not meeting the project goals.
Don't commercially available software controlled USB hubs exist already? The Yepkit YKUSH 3 came to mind immediately (https://www.yepkit.com/product/300110/YKUSH3) and is the only device I've seen that explicitly says that it disconnects both the data lines and power lines when switching. A casual search also finds https://www.usbgear.com/managed-hubs.html
Oh, I don't think it's quite that grim. When development teams can no longer easily spend their way out of their inefficient code, being able to write high performance code becomes a competitive advantage. I'd even go so far as to say that individual developers looking to get ahead in their careers should pay less attention to flashy tech fads and more at foundational stuff like how to diagnose performance problems and write efficient code.
I'd say digital logic and computer architecture teaches pretty immediate lessons about tackling concurrency? Every gate and transistor is operating in parallel and it's up to the engineer to arrange things so that race conditions don't occur and valid results are available when the next clock edge arrives.
Probably my favorite book on software testing would be "Lessons Learned In Software Testing", which is more a discussion about the people and process aspects of software testing instead of specific techniques. If you're interested in testing as a profession rather than merely as a job, it's worth a read.
Much like reverse engineering, it's easier to come up with an explanation when you have someone else's working solution to examine than it is to come up with a working solution from scratch on your own. So that doesn't really help.
> "...this is information that you're going to need if you actually want to go into the field..."
That has never, ever stopped anyone motivated to cheat. Even here on highly-educated HN, you get posters with open disdain for what they learned in college.
> "... at the end of the day is the purpose of the course to measure the student or to teach the student?"
Both. Otherwise, the college diploma really does become the meaningless scrap of sheepskin that its detractors claim it is.
Straight up assembly language, preferably Motorola MC680x0 or some other contemporary that was meant to be coded by hand; it's the only way, man! Plus students will gain some appreciation for how microprocessors actually work.
In the same vein, just have them write code out on paper during exams and coding competitions like the way we did it back in my day. It's not as if they're not going to need that skill anyway when they get whiteboarded during interview loops when even the most lenient employers get exasperated at "CoPilot-only" graduates.
Linux beer: Displaced the various flavors of UNIX beer by being free (as in beer) and is extremely popular where that's important, i.e. everywhere. Tasted a bit manky in its earliest brewings but eventually got tasty enough to displace all the other UNIX beers, although Solaris beer brewers fiercely insist to this day that it's not nearly as good. Currently the most widely drunk beer in the world, although its detractors point out that for most of that it's only an ingredient and not being drank straight up. Its drinkers have a one-sided rivalry with Windows beer drinkers for some reason even though the latter has long since ceased to care.
Kind of depressing to contrast that with today where there are just three deeply entrenched operating systems (phone and embedded OSes don't count since the end-user has no meaningful access to them). We, or at least I, naively thought we'd see continued rapid evolution of a plethora of OSes to accompany the rapid evolution of computer hardware.
Depends on what you mean by "good OS". Architecturally, it was a descendant of VMS and its kernel was considered well engineered for its time. It had a ton of bugs and security issues but so did all the pre-2.0 Linux kernels/distributions that were its contemporary.
From the userland and UI perspective, well, it's just Windows, both in the positive and negative sense; NT is the granddady of Windows XP and Windows 7 both of which were well regarded but NT also suffered from all the warts and ugliness caused by being converted into a consumer OS.
K&R ("The C Programming Language") still stands out, at least to me, for its clarity and conciseness. I have yet to see a programming language manual that equals it.
Along those lines, a biography video for Admiral Lee by a naval history enthusiast really manages to capture what an impressive and capable person he was: https://www.youtube.com/watch?v=58lfaMFUQc0
Contrary to some sibling posts, datapath width isn't really the limiting factor for comprehension IMO; everything is "wider" but not more difficult to understand. For example, undergraduate computer engineering students could and did design pipelined in-order 32 bit processors as part of their studies.
At least IMO superscalar + out of order execution was when things really became too complex to hold comprehension of the entire processor in one's head.
I say this jokingly but if you really, really wanted to go all out, you could use an artificial head with mouth simulator, e.g. https://www.head-acoustics.com/products/artificial-head-bina... Being a very specialized test instrument, though, it costs vastly more to get such a device and the auxiliary equipment to operate it than the experience would ever be worth. Even basic mouth simulators, sans head, like https://www.bksv.com/en/transducers/simulators/ear-mouth-sim... are astonishingly expensive.