Is this the genesis of Cylon fighters* in our universe?! By your command.
(* the grown ones, not the original ones with humanoid bots in)
18 posts • joined 27 Sep 2019
I was on KS1, thus I have a Next. Yes, it is awesome. It really is. It's awesomer that I thought it would be. It's also way more than just a faster and better Spectrum, which is awesome in itself and is a major success (did I say it's awesome?!). As well as the improved Spectrumness (and backward compatibilty to 48k) it also runs other cores (FPGA, not emulation) like arcade boards and other retro cores like BBC Micro etc. I'm well chuffed with mine.
(Just a punter, not affillated to or friends with anyone on the ZXN team).
I ran a bunch of CommuniGate Pro servers for years. It was unfortunately commercial (and, latterly, expensive) software, not open-source, but they were like tanks. CGP just sat on top of a bare-bones Linux-with-networking stack and just ran... and ran... and ran... and ran.... so much so that one of them lasted a good decade longer in production than it should have done. The vendor added some wobbly microsoft-facing bells and toys to it over the years in order to try and compete beyond their competency, but we never used those. We just stuck to your standard SMTP/IMAP/POP3/LDAP schenanigans. It never broke. As near to a 'bulletproof' set-it-up-and-walk-away system as I've ever run for anything. (Just my experience).
Just because the development workstation is Windows-based it doesn't necessarily follow that the development *server* running on it is also Windows. Firstly, if you're fully developing locally then your 'server' may be running in a local VM (or container or similar) and be, say, Linux to more accurately reflect your production environment. Or, similarly, it could be in a VM (or container or similar) just to keep it separate from your local workstation environment. There are of course other options; for example, even if you code locally you might have an actual separate dev server parked nearby (or far-by). Your dev server doesn't necessarily have to be on your dev machine any more. None of those options *requires* Windows to be the dev server host OS - it only applies if you install a server stack directly on to your local workstation OS (if you're still that way inclined?!)
Been logged into Teams all day on my Mac as well. It's mostly spending its life hovering between 1-2% CPU usage. I'll check and compare on the Win10 PC tomorrow.
Do I love it? No.
Do I hate it? No.
Can it be improved? Yes.
Are there things about it that annoy me? Yes.
Is it useful to us right now? Yes.
Is it keeping my users in touch? Yes.
Is 'free' a good thing? Yes.
Does using it on an RDS server really fork me off? Yes. :-(
Are there any little things I like about it? Yes.
Are there any little things I hate about it? Yes.
Are we going to keep using it? For now at least, Yes.
I backed the 'accelerated' version, so I'm still waiting — patiently, and with an increasingly happy and lunatic smile — for its arrival. I'm really looking forward to getting mine 'in the flesh'. It's been great hearing about others receiving theirs in the mean time. There's been a great buzz in the community about it. I hear the 1980s calling me back :-)
In a similar vein, I've still got a pair of Apple Newtons from the first half of the 90s as well, although maybe the less said about the Newton the better.
Which reminds me of my all-time favourite joke: "How many Newton engineers does it take to change a lightbulb? Foo! Therefore to and eat fish."
(The youngsters here won't get it).
"Sinofsky said that Microsoft was "blinded" as to where Apple was heading, and was expecting a "pen computer based on Mac"."
What? From what I recall every idiot on the planet knew it was going to be an iPhone (iOS) with a big screen. What were Microsoft smoking to think otherwise? No wonder they lost that particular race, they were at the wrong sports event.
Regarding the 'Arctic Vault': if we're really concerned about very-long-term backups - be it of wobbly code on Github or actual flesh machines - should we not really be investing in something off-planet? Y'know, just in case this single-point-of-failure that we orbit upon has either a slow- or rapid-disassembly moment? Svalbard would be part of the same failed component/subsystem in those cases.
"As much as I dislike Apple, blaming them for Intel's failure is a bit much. What you can blame them for, though, is 'designed-to-fail-early' hardware."
Whilst I could rib Apple on many, many points, long-term personal experience tells me I'd have to disagree with you on this particular one.
I've been an Apple and a Windows (inc Server) - and Linux - user for more years than I care to remember or tell and, for longevity, Apple's hardware *generally* outstrips anything even Lenovo or HP have thrown at me, at least on the desktop, laptop front. Ditto for phones. Servers are another matter entirely (cut me and I have the letters HP DL through me like a stick of rock :-). Yes, there are exceptions both ways, with odd bits dying early or living extra long on both sides of the fence, but *overall* the Apple stuff has generally had a longer *useful* (or trickle-down) lifespan, in my personal experience (excluding swapping some PCs to 'lite' Linux installs maybe).
YMMV of course.
"The thing with holes is that they are consistent, half a hole or a hole twice as big are still both whole holes."
You mean a smaller hole, or a hole half the size, surely? By your own description you can't have half a hole; half a hole is a whole hole, just in a more portable size.
Biting the hand that feeds IT © 1998–2021