Hacker Newsnew | past | comments | ask | show | jobs | submit | sebsebmc's commentslogin

The location they have that's "well into construction" is SPARC, which is not intended to be a net power production facility. It will host their net gain demonstrator that they intend to have first plasma in next year and target a net gain demonstration in 2027.

ARC which they announced siting for and is intended to be their first grid-attached net power provider only just had the location selected so I don't believe its got much construction going on yet. The goal for that plant to be producing power is "early 2030s".


Ah, maybe not well into construction. But a friend of mine works with exotic materials and they are purchasing lots of things for ARC. Though I imagine these materials have a long lead time.


According to the IEA "Heat accounted for almost half of total final energy consumption and 38% of energy-related CO2 emissions in 2022" so finding ways to create process heat that can reach hot enough temperatures efficiently from electricity is a big deal for industry.


Im still hoping that Typescript support comes soon!


Thanks for the feedback. We implemented the transform to strip TypeScript annotations (using esbuild)…

https://github.com/observablehq/framework/pull/129

but this approach stalled because it doesn’t implement validation of TypeScript: the TypeScript annotations are simply ignored. I felt this defeats the point of using TypeScript. We probably need to use tsc instead of esbuild to get type checking. Hints welcome!


> All regular expressions for this function, as well as REGEXEXTRACT and REGEXREPLACE use the PCRE2 'flavor' of regex.


Okay, thanks! Now next question which comes into my mind: is there info about the regex engine they are using? I would expect there is some (proprietary?) C++ library also used in other MS products or are they even using a FOSS licensed one?


Seems likely that if they explicitly say they're supporting the PCRE2 syntax it is because they are using the BSD licensed libpcre.

Reinventing a regular expression system is very far down on the list of things I'd ever want to do. Those things are filled with dragons and require years of refinement to get the bugs out.


Another semantic distance guessing game is https://semantle.com/


SpaceX themselves[1] seem to corroborate what you're saying. "The second flight test of a fully integrated Starship could launch as early as Friday, November 17, pending final regulatory approval." and the FAA page[2] for the approval still doesn't have any updates.

[1]: https://www.spacex.com/launches/mission/?missionId=starship-...

[2]: https://www.faa.gov/space/stakeholder_engagement/spacex_star...


Did they ever satisfy the regulators asking them about the probability of hitting a shark with the rocket?


For a skeptic's response I recommend https://www.youtube.com/watch?v=3vUPhsFoniw


The Path of Exile wiki made a similar move a few years ago. Fandom was such a limitation for the community and the ads and page speed were awful. Now the Minecraft wiki will have to spend effort beating the Fandom site on SEO so that people get directed to the actually updated wiki. For Path of Exile there was a browser extension that would hide the Fandom from search results and redirect you to the new community wiki.


Are you thinking of the "Indie Wiki Buddy" extension? They have already added support for the new minecraft wiki: https://getindie.wiki/listings/

It's pretty incredible that Fandom/Fextralife have driven people to developing browser extensions just to avoid everything they touch...


No, there's a Path of Exile wiki specific extension also.

It's slightly counterproductive from an SEO perspective as it redirects Fandom clicks to the new wiki, which gives Fandom all the SEO benefits of receiving those clicks.


Indeed, which is I suspect why fandom still ranked so highly above poewiki for many searches for far too long, and initially even appending poewiki would often return no results or just the fandom result.

Thankfully there's been a notable shift in the past 3-6 months.

What has finally helped I think is the sheer amount of stale or missing data on fandom, so as a really basic current example, it doesn't have mention of tattoos, a fairly critical aspect of the current league.


The biggest reason was simply that we were being penalised for having duplicate content, which Google are able to detect.

We definitely over index on content added post-fork, which makes sense given that we're not competing with Fandom for those searches.

According to Google Search console, in the last 3 months we've had 32.9M impressions and 4.39M clicks, which is nothing to sniff at.


Are there any headers added by the extension so you can detect natural vs redirected traffic?


I don't believe so, we never implemented client or server side tracking on the wiki though so it's not like we'd look at it anyway.


Critically, the developers of PoE also provide hosting for the wiki pro-bono. The service is so beneficial for players I imagine they figured the game would benefit from an ad-free (and therefore more usable) community wiki. Personally I have recently started seeing the correct wiki at the top of searches so I think the SEO battle is winnable with community effort. It helps that Fandom wikis are uniquely unusable without an ad blocker running.


For those of you that use VS Code, there is a plugin[1] that follow a lot of the Kakoune grammar but doesn't try to emulate fully, opting instead for better integration with vscode. I have been using it for a few years after using Kakoune for a few and then trying and failing to make my own Kakoune emulation mode for vscode.

[1]: https://github.com/71/dance


Using Dance as well for VSCode development. It's decent, albeit that the README could be more helpful.


It actually was expected to do a flip and perform stage separation. It was a problem when it kept trying to flip and Starship didn't separate.

The explosion at the end was the Flight Termination System. In case of uncontrolled flight you detonate the rocket to keep it from flying somewhere dangerous.


From a PR perspective, I'm surprised that they don't have a procedure where they announce that they're considering to terminate, then announce that they'll blow it up, before actually doing it, if time allows.

I think there is a significant difference in public perception between "it blew up during the test" and "the test wasn't going to go anywhere good so they blew it up".


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: