Recommended Posts

Some asshat put some spoilers for the movie on another forum I go on, at least I assume they are, I can't see the movie for a few weeks and its eating away at me.

Is

Harrison, Khan?

Read Wikipedia's article, under the plot section if you want to know all of the details. Looks like he is.

Saw this last night, extremely action packed with the HUGE amount of lens flare I expected from Abrams :p. Benedict Cumberbatch was a terrific villain (and VERY well acted). I'd easily give Into Darkness a 9/10!

I enjoyed it and definitely worth seeing in 3D (great use of atmospheric effects like dust motes and sparks etc). Its a good movie and one I would recommend, just not great Trek. The social commentary and physics were weak at best - but JJ admits that he isn't very smart. Thats ok though, this story is clearly more character driven and that is something he is good at. Cumberbatch and chemistry between the crew, if exaggerated, was good. (Including a certain baby mamma) The remainder after the reveal seemed more predictable and flat, but still entertaining. Pacing throughout was good.

I think I'm still the most disappointed in this new 'machine gun' phaser BS, especially on the ship to ship scale. It could have been more.

Didn't care much for the reversal either, as it highlights one of my annoyances - Quinto. He just doesn't deliver the understated machismo Nimoy infused into the character, let alone the reasoned, logical tones. Maybe I'm just biased against him being less Vulcan (yet somehow has all the usual tricks, though the neck pinch didn't seem very effective - maybe he moved that nerve cluster? ;) ).

Didn't care much for the reversal either, as it highlights one of my annoyances - Quinto. He just doesn't deliver the understated machismo Nimoy infused into the character, let alone the reasoned, logical tones. Maybe I'm just biased against him being less Vulcan (yet somehow has all the usual tricks, though the neck pinch didn't seem very effective - maybe he moved that nerve cluster? ;) ).

Quinto plays Spock as someone who's repressing his emotions, while Nimoy played him as someone in control of them (a stoic).

I was thoroughly impressed with the movie.

It was predictable (somewhat) if you're familiar with the cannon lore, but at the

same time that's exactly what made it exciting for me.

The ONLY thing that disappointed me about the movie- as a HUGE fan of the original

Star Trek TV show- was:

I wanted either an end-credits scene with the Tribbles,

or I wanted to see them use the Tribbles as a weapon against Cumberbatch's ship. :)

Quinto plays Spock as someone who's repressing his emotions, while Nimoy played him as someone in control of them.

This. The original film was set before the events of TOS, so it's perfectly reasonable to expect that Spock's control over his human side isn't as developed. Regardless, the alternate timeline means that the two characters cannot be compared, especially after the emotional pain caused by the destruction of Vulcan. Personally I think that Quinto is excellent as Spock. It's the new Sulu that I consider the biggest disappointment but not enough to annoy me.

The ONLY thing that disappointed me about the movie- as a HUGE fan of the original

Star Trek TV show- was:

I wanted either an end-credits scene with the Tribbles,

or I wanted to see them use the Tribbles as a weapon against Cumberbatch's ship. :)

It would have been nice but they couldn't very well do that without introducing the concept of Tribbles to a new audience. However, if the next film is going to focus on Klingons?as seems likely?then we could see them return in the next film. I think the cameo role they played was fine, as it's a nod to the original without simply copying everything.

JJ didn't want to make it complicated or too trekkie because he wanted it to be able to target everyone. The fact those who don't know anything about trek can go in and enjoy this means he's done what he set out to do. He's said as much publically.

Just saw it and

hotdamn.jpg

Cumberbatch is GREAT, one evil SOB, the action is almost non-stop, Spock has a Hulk moment, and there's a potential spoiler every 5 minutes. Lots of references to TOS, earlier Trek movies etc., but often with an alt-timeline twist. Our group of 6 really enjoyed it.

F/X: fantastic!

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • No news articles about the Arch Linux repo being majorly infected with malware?!?
    • Waymo recalls self-driving software after cars enter closed freeway work zones by Paul Hill Waymo, the self-driving car maker owned by Alphabet – the parent company of Google –, has recalled some of its fifth-generation Automated Driving Systems (ADS). It did so after some of its cars drove through closed construction zones. According to the National Highway Traffic Safety Administration (NHTSA), the affected vehicles were capable of driving through a closed freeway construction zone and continuing to drive at speed. The listing on the NHTSA website says that Waymo is currently developing a solution to fix this issue, but in the meantime, freeway driving is being restricted. Waymo will update its ADS software so that vehicles can detect when they can avoid entering construction zones. According to the Safety Recall Report, on April 20, 2026, Waymo’s Field Safety Committee began meetings reviewing an event from April 11, 2026, and five events from April 19, 2026, where Waymo’s autonomous vehicles didn’t recognize and drove past ramp closure signs into the pre-planned freeway construction zones. This took place in Phoenix, Arizona. Separately, on May 18, 2026, seven Waymo vehicles entered freeway lanes with active construction in the San Francisco Bay Area by driving between cones that were placed to show the lane was closed. On the back of both of these events, Waymo restricted freeway driving until it could address the issue. In June, Waymo’s Safety Board reviewed the issue and additional information related to ADS performances around construction zones; then, as a result, it decided to conduct a recall. This development is not good for Waymo as it adds to a growing list of technical hiccups its cars have experienced. Ultimately, it will lead to more scrutiny from lawmakers around the world who will be more cautious about letting autonomous vehicles on their roads without tighter regulation. For readers in areas where Waymo operates, does this news make you more wary about stepping into one of these vehicles?
    • I'm still on Windows 10 22H2 because I didn't want to deal with all the issues in Windows 11, so I waited almost a week before installing the latest Patch Tuesday update (KB5094127), I went ahead and did it, and it was a huge mistake—ever since then, my File Explorer has seen a performance drop of about 30% when transferring large files... Once again, Microsoft has outdone itself! This update cannot be uninstalled, either through the Control Panel (via Settings) or by accessing Advanced Startup Options. The only possible alternative would be to use system restore points, but I’d have to reinstall all app and driver updates (and there’s no guarantee it would work). Or there’s the “nuclear option” of a in-place repair without losing files or apps, but even then, all my customizations would be lost! Microsoft just can’t help but mess everything up! Way to go, Microsoft! But I still don’t want your c****y Windows 11!
    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
    • And with SO much better perf than the laggy mess that is Files.
  • Recent Achievements

    • One Year In
      Skeet Campbell earned a badge
      One Year In
    • One Month Later
      Sharbel earned a badge
      One Month Later
    • First Post
      BizSAR earned a badge
      First Post
    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
  • Popular Contributors

    1. 1
      +primortal
      598
    2. 2
      +Edouard
      190
    3. 3
      PsYcHoKiLLa
      79
    4. 4
      Michael Scrip
      76
    5. 5
      Steven P.
      70
  • Tell a friend

    Love Neowin? Tell a friend!