Not sure where your information that n8 was supposed to run Meego comes from, but I remember working with the Nokia s60 team already early 2009 and they were using n8 protos at the time. It’s definitely possible that there were two parallel projects though.
On the other hand, Maemo, the predecessor to Meego, required a pen-like pointer to comfortable use at the time as the UI elements were designed to be small. Only after they completely overhauled the UI (and renamed the Linux based OS Meego) it could have worked on the N8.
That would have been around the time when they should have launched a successor to the N800, which launched in 2007. As I recall, the n8 was originally designed to be that.
Meego/maemo had several UI redesigns. The issue was that Nokia just kept ripping it apart instead of just fixing it. The reason for the pen was resistive screens. Bigger buttons would have been an OK solution. The later n900 had the same issue. Ultimately, they bought QT to fix Symbian and then made the Meego team switch to that. They wasted years on the UI. Jolla emerged out of the ashes of that and is still around. Samsung's Bada is another descendant.
I’m not a ship engineer but I do know that ships are not built to be suspended from the ends. I guess in the worst case the hull breaks which would mean the canal to be blocked for quite a while.
That's usually only a real problem when the ship is suspended in the air, between wavetops. This one is still in the water, though maybe it has a little less support in the center than normal
Ships actually are designed to be suspended from the ends. Ocean going vessels are going to experience wave crests which can be any length apart, including the full length of the ship.
Wow, looks like triplebyte profile settings page is full of dark patterns. Like, setting yourself as not interested in offers will forcefully revert back after a time period, and that even though there’s a checkbox for opting in to being shown to companies you can’t save the profile without giving consent.
I don't think he's agreeing or disagreeing with the article, just providing a possible explanation for this behaviour. The two people arguing are ignoring the context, which is common in many debates. Especially with politicians - shift the context a bit and you're right even if what you're saying is unrelated to the original point.
The article chose pretty good examples, they are all of the form, "generally true statement" with a "specific, or even completely unrealistic, edge case disagreement". They all require no context to understand the exchange.
Debates, especially political debates, are purely about winning the debate. Context in a debate is particularly irrelevant.
I'm not sure I agree with "edge case disagreement". TLS, for example, has shown it's limits (e.g. CA hijacking) and was improved (e.g. CT). However, someone had to find those edge cases and discover the limitations of stated assertions: "2010 TLS was safe under the assumption that the CAs are not hijacked."
Ok. So, are you saying that we should stop using HTTPS and instead use HTTP? If you are not, what is your point? Is it not under the 100% correct but missing the point label this article is talking about?
Well, you could use HTTP over an IPSec tunnel with a pre-shared key (obviously distributed face-to-face), and that would have been resistant to a CA being hijacked.
However, nowadays, I believe with CT HTTPS is really safe. But again, someone had to nitpick on the security limitations of HTTPS for CT to be invented.
Could you enlighten me as to why my comment isn't relevant to this post or how I've missed the point?
I've read the post again in the best faith that I can give and I think I understand the point, I just thought it would be intersting to discuss the idea of "context" in conversation.
Instead of seeing the replies as pedantic seekers to logical truth they may just be misunderstood individuals who is talking with a different context. If we assume my comment as the first comment in his examples, I am equally at fault for not communicating my context clearly.
Unlike the author I don't find such interactions as frustrating, and hopefully I've effectively explain why in this comment.
> The main class of failures that I am worrying about regarding the MTTR is the very same observable problem that you solved last week occurring again due to a lack of quality gates. To the customer this looks like last weeks problem was not solved at all despite promises to the contrary.
I think the quality gates mentioned in the article are the ones where you have a human approving a deployment. If you have an issue in production and you solve it you should definitely add an automated test to make sure the same issue doesn’t reappear. That automated test should then work as a gate preventing deployment if the test fails.
I can't say I spelled every letter in the article but it says so many strange and wrong things I would not give it any benefit of the doubt of the sort of 'but it cannot really actually say that, right?'
Wow, this article made me realize I was a part of the very early generation game devs in Finland getting my first job in the industry in 2001. I was so young and naive then that I didn't understand how early it was.
Is it possible that the problem there is the amount of women starting studies in stem fields? I don’t have any numbers but anecdotal evidence of two Helsinki based schools in CS related programs had very lopsided gender ratios in bachelors and masters levels.
The correlation of women in STEM graduates and Global Gender Gap index is negative: the higher gender equality, the lower the proportion of women graduating from STEM subjects.
If someone told the young Linux freak me back in the early 2000s that one day Internet Explorer’s rendering engine is based on the KDE rendering engine I would’ve probably died laughing and frozen in horror at the same time.
Yeah, I realize there’s probably nothing left if the old KHTML but it still does give me a chuckle.
An open source project released by Apple, that Google added a bunch of features to - including DRM, and Microsoft adopted to help unify the web for internal enterprise apps.
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6)
AppleWebKit/537.36 (KHTML, like Gecko)
Chrome/79.0.3945.117 Safari/537.36 Edg/79.0.309.65
"Edg"* , like Chrome, like Safari/AppleWebKit, like KHTML, like Gecko, like Mozilla 5.0.
My lord, this ridiculous header is f'ed (and I don't mean this string, just this entire ridiculous slow-motion trainwreck that requires every browser to pretend to be every browser that ever came before).
\* presuming that spelling means 'please don't lock me out like Edge' -- modern Chromium Opera identifies as OPR, similarly
On the other hand, Maemo, the predecessor to Meego, required a pen-like pointer to comfortable use at the time as the UI elements were designed to be small. Only after they completely overhauled the UI (and renamed the Linux based OS Meego) it could have worked on the N8.