For me it's the opposite. I played Q4 first, easily played it 5 times since then. I played Q1 later and have have had multiple replays.
Q2 is the only one where I don't get the hype. Sure, it's an interesting window into what games can become when the narrative guides the player rather than "find the exist button and kill everything in your path". But by Q2 too many important faces of id have left and I feel it way too much. No Sandy, no Romero... it just feels stale and generic.
I remember pirating Quake, got it in August before the Nov launch (gotta love early 0-day releases) and playing the hell out of it. Played so many mods and the early machinima mods. By the time Quake 2 came out I had money to buy the game and did so, great game. I setup my first Ethernet network between two machines and the first thing I did was call a few friends over for 1v1 Quake 2 matches. I can still remember my friend Jose killing me in that lava room trap and the laughs had. I wasnt a big twitch gamer but my brother and I did a little bit of Q3A DM but it wasn't my thing; I prefer a story and casual game play.
I remember buying Quake 4 but I don't remember playing it. Tells you a lot right there.
Yeah agreed - I played Quake 4 in... I don't even remember 2007 or 2008 maybe. It was fine but don't feel the need to revisit it. I've played Quake 2 a couple of times though and would happily go again.
I like Q1 the most. I played Q1 the first time around 2010 or so, after playing Q4. So it is not rose tinted glasses. Just Q1 is a lot of fun! Quake 4 is good, but I think I never finished it. While Q1 is something I now install on all my PCs just for a little fun when I want.
The enemy and level design is simply good. And there is tons of content online.
> As far as anyone is aware, disaster has been averted: The hack was discovered by cybersecurity researchers who reported it to the PHP Foundation, and a patch was released before any bad actors got their hands on the exploit.
Aren't there still vulnerable services right now being hacked?
I’m really keen for the future of modded firmwares on cameras. One feature I’d love to have is starting an SMB or ftp server on the camera so I can just copy files over the network rather than having to move sd cards or plug anything in.
I combine the a7cII with various small primes (Sony 24mm f2.8, Sony 40mm f2.5, Sigma 90mm f2.8, Voigtlander 35mm f1.4) and I have a very capable camera that fits in a tiny bag. It's great for street and travel.
Then when I need to I can attach the same body to a big lens (Tamron 28-200, Sigma 100-400) and slap on a Smallrig grip to counteract the lens weight. It's great for protests and birding.
IMO the benefit is that one can purchase a single body and do big camera and small camera things with it.
The a7cII has a built-in EVF and IBIS, though, and it’s priced similarly to the FP2. Autofocus on the a7cII is probably better, too. I can definitely see the appeal of the a7cII even though in the end I decided to go with a camera system with smaller, less expensive lenses.
Whereas the FP2 seems to compromise more on useful features in the name of compactness.
A project with the complexity of an email client cannot be considered stable in a month. There are bugs that will only show up after a year. It has a calendar after all.
> The UI looks pretty good too. It's really not hard to beat thunderbird.
I don't understand this mentality. It's an email client. There's not a lot needed UI-wise to make a functioning interface. Display a list of emails, show the full message when you open it, etc. I don't see anything functionally different between this email app and basically every other one I've ever used.
You've either got insane standards or are using email way different than I.
Can’t speak for others but for me Thunderbird’s UI feels distracting and almost grating in some ways. It’s technically functional but doesn’t feel right.
I know things like that don’t bother some folks and that’s fine, but others like myself can’t turn the visual parts of their brains off and so some software feels like nails on a chalkboard to use.
> It’s technically functional but doesn’t feel right.
That might be the most accurate description of Thunderbird that I've come across. It's hard to pinpoint exactly what's wrong with Thunderbird, despite me using it every day. Somehow it feels like the emails aren't the important bit of the UI, but I also couldn't tell you what I'm looking at instead.
It’s a gut feel sort of thing that’s usually grounded in some set of UI design principles that haven’t been adhered to. Defining it just pins down what the issues are rather than making the feeling go away.
Glancing at screenshots of TheBat! and Pegasus Mail, i don’t find them objectionable in the way I do Thunderbird. They’re just old school desktop clients like I used in the late 90s/early 2000s, which I generally find workable. They’re not quite my preferred style these days (which falls into the “it’s not what I’m used to” bucket you mentioned) but I could probably get used to them again if I had to.
Thunderbird on the other hand feels wrong somehow, and the recent UI “modernization” didn’t do much to change that.
But from a normal user's standpoint? I don't care. If my email client needs more than a single thread, something's fucked.
I randomly bounce between Thunderbird and KMail and honestly I can't tell the difference except cosmetically. Both are snappy. Neither crash. Both send and receive emails just fine.
I know parent is probably talking about a different type of threading, but Thunderbird's lack of process threading means the UI just gets stuck when it's syncing a large numbers of emails, which can happen if your subscribed to a lot of mailing lists, etc.
> There's not a lot needed UI-wise to make a functioning interface
I remember waiting for ~15 years until Thunderbird finally implemented rich content support in the e-mail list (needed for a proper 3-column layout, as otherwise the e-mail list, being a simple table, wouldn't fit on the widest screens available).
So, yeah... Not a lot, but Thunderbird has been missing the bar for over a decade.
There is a case to be made to always start at 1.0, especially libraries with public API’s. The reason is that if you use semantic versioning then below 1.0 you can’t properly declare a new release to be a feature or bugfix release (for example, 0.4 to 0.5. Is this bugfix or feature?). Above 1.0.0 this is easy (for example 1.1.0 vs 1.0.1).
In libraries, 0.x is for when you’re still figuring the API out. Basically you’re saying that no API is stable at this point, and you’re not doing semver yet, and anything can change.
Naturally, the users should treat those libraries as beta versions and only use them in production at their own risk.
> you can’t properly declare a new release to be a feature or bugfix
In practice, 0.5 can be assumed to be breaking but then how do you specify non breaking new features? 0.4.1? Moving to 1.0.0 makes things a lot clearer. For breaking, just go to 2.0.0 etc
> but then how do you specify non breaking new features?
You don’t. As soon as you feel the API is stable enough, move to 1.0.0. 0.x is for the “yeah the API doesn’t feel right just yet but it might be useful for early adopters” stage.
I know there’s the tendency for mature projects to live in 0.x for a long while, yeah – definitely try to avoid that. But 0.x is a useful first step for libraries, especially if the API is non-trivial.
the one-time payment will decrease the value of property they own, and increase their monthly expenses, but maybe they've been brainwashed into thinking otherwise and will take the bait
In this case keys are per-sensor and revokable. So surely if someone spends a lot of money and extracts a sensor key it can only get minimal use before revocation?
I've replayed Quake 1 and Quake 2 dozens of times but I'll never play Quake 4 again.
reply