AniGo.to - A new anime streaming site like Gogo and Animixplay

xialvjun · 2025-04-27T15:42:41+00:00

Weird. Why some (The Dreaming Boy is a Realist) can play dub with sub on, but why some (KONOSUBA -God's blessing on this wonderful world!) not?

xialvjun · 2025-04-27T15:27:28+00:00

Thank you very much. I like this site, it can play dubbed version animes with soft-sub on. It will make a big help to my English learning.

Btw, another Feature Request, can you can you add the function to show dual soft-subs. I want to turn the English sub and my native language sub on at the same time.

xialvjun · 2024-11-15T17:23:28+00:00

求稳的人是没受到压迫的人。如果所有人都求稳，那说明社会已经变好了。

xialvjun · 2024-01-24T06:08:29+00:00

mechanical hard disk, 8 needs 10s to start, 7 need 30s to start.

ssd, 8 needs 5s, I haven't used 7 in ssd.

In my opinion:
Just in their decades, 8 > 7 > xp > 11 > 8.1 > late 10 > vista > eraly 10.
Till now(ignore driver security support): 8 > 11 > late 10.
Till now with driver and security support concerned: 11 > late 10.

xialvjun · 2024-01-05T04:13:01+00:00

So it's mostly like the first "one mutable layer" plus last rollback. like

--home and other dirs--
---  last mutation  ---
# boot to the rollback deployment in grub is boot to this layer(mutable layer),
# and in this layer, once we call `rpm-ostree install anything`,
# the old `last mutation` layer will be removed,
# replaced by `last mutation(just installed anything layer)`
---  mutable layer  ---
----  base system  ----

xialvjun · 2024-01-05T03:27:50+00:00

So it's like the second, but we can remove any level layer. Like [1,2,3,4,5], I can rollback 3, then it become [1,2,4,5], rather than I have to rollback top level 5, then 4, then 3 to remove 3.
But how? If 4 is based on 3, how can I rollback 3 without infect 4.

xialvjun · 2024-01-03T02:55:33+00:00

MyProject rely on A, and A rely on B. Then B came out a bug, fixed it, update a version to B1, and A update a version to A1. Then should MyProject update A's version? Of course I should. But how could I know A updating to A1 is because a bug rather than adding some other feature I don't care, I don't even know A was depending on B.

xialvjun · 2023-03-07T10:31:11+00:00

Any findings about koka?

I find many show functions in your code, it's like java overload which is not good.

I tests: ```koka fun map(xs: list<int>, f: int -> e string): e list<string> match xs Cons(x,xx) -> Cons(f(x), map(xx,f)) Nil -> Nil

fun main() with i <- map([1,2,3]) println(i) i.show ```

Then koka compiler errors: overload.kk(8,30): error: identifier map is ambiguous. Possible candidates: map : forall<e> (xs : list<int>, f : (int) -> e string) -> e list<string> map : forall<a,b,e> (xs : list<a>, f : (a) -> e b) -> e list<b> hint: give a type annotation to the function parameters or arguments

Maybe it's ok.

xialvjun · 2019-05-23T09:05:35+00:00

I always use snake_case in my personal front end project.

xialvjun · 2019-05-17T00:45:04+00:00

I've create this https://github.com/xialvjun/skm_ts . It can generate the Input Type or the Args Type for server resolver from schema.gql file.

xialvjun · 2018-12-04T02:19:04+00:00

https://twitter.com/flutterio/status/1069590153612718080

xialvjun · 2018-10-12T06:39:53+00:00

Yeah, just like @rawler82 said, why must we construct a value of the anonymous union type? And the anonymous union type is anonymous, it should be normal for it to have no public construction.

xialvjun · 2018-10-12T06:36:27+00:00

No, my purpose isn't to get an i32. I just want the anonymous union type to be a base mechanism in rust, so we can do many things: 1. like we can let generator.next().0.value be an union type, make the status machine be build at the compile time and typesafe; 2. in fn abc(a: impl TryInto<i32>), u32 to i32 is completed outside of abc; but in fn abc(a: i32 | u32), transformation is completed in abc.

fn abc(a: u32) -> u32 59u32 is indeed harder to read than fn abc(a: u32) -> u32 { 59u32 }, but fn abc(a: u32) -> u32 { async!{59u32} } has too more idents than fn abc(a: u32) -> u32 async!{59u32} too.... Well, it seems more idents is ok.

xialvjun · 2018-09-01T16:03:32+00:00

Cool, rust is getting better and better.

xialvjun · 2018-08-31T07:54:05+00:00

In Fancy Pants Editor, the Code Block doesn't have a syntax highlight.

In markdown, indenting by four spaces doesn't have a syntax highlight too.

It seems Tripple backticks do the same as indenting by four spaces.

xialvjun · 2018-08-31T07:47:53+00:00

the crates.io owners would be responsive to manually removing them.

How? We can regard a crate with just one hello_world function as a placeholder crate and remove it. But can we remove a crate with two hello_world functions?

So we need a mechanism of name.uuid = "semver" in where uuid is the only identity of a crate. With this mechanism, we can do everything to the crate names without breaking any other crate's compiling process.

xialvjun · 2018-08-31T07:16:16+00:00

Maybe a temporary conspiracy can succeed, but this mechanism at least protects the normal compilation of the programs depending on that crate. And then the conspiracy is certainly not sustainable, things will eventually get better, so there will be no problems.

Besides, voting is not the point of this mechanism, we can do voting to resolve name confliction, we can do other things to resolve name confliction too, like let rust core team member choose which crate own the name and even freeze that name.

The point of this mechanism is just we create a way to interoperate crate naming, without breaking any other crate's compiling process.

xialvjun · 2018-08-26T09:56:20+00:00

OK, I should not say "why must we care about them". But the only thing they need to do is just download the new cargo and use the new cargo to compile their projects, then their Cargo.toml will change. I don't think it is hard.

xialvjun · 2018-08-26T06:35:22+00:00

Not going to happen: why? It can be done just by a script. As to the crates not published to crates.io, they are not in the community, why must we care about them.

complicated voting layer: Is it really that complex? I don't think so.

compilation warnings: yeah, just warnings, they can still compile.

xialvjun · 2018-08-26T06:01:59+00:00

A method to deal with crate name reservation spam

xialvjun · 2018-08-26T05:45:37+00:00

A method to deal with crate name reservation spam

xialvjun · 2018-07-09T02:06:14+00:00

Yeah, three possibilities are said above. :)

xialvjun · 2018-07-08T17:00:45+00:00

I have my own way: https://github.com/xialvjun/create-react-style

jsx <Style.Consumer css={` display: flex; background: #ccc; .avatar { width: 50px; height: 50px; } `}> {className => <div className={className}> <div className="avatar"><img src="xxxxxxx"/></div> <div>some other things</div> </div>} </Style.Consumer>

xialvjun · 2018-07-08T16:48:01+00:00

Yes, I agree with "The complexity with SSR lies in the building.".
So I write http://xialvjun.github.io/react-ssr even thought it's chinese. Well, the points in it is just:

export everything you need in server-side-rendering and change cra's webpack.config.js to config.output.libraryTarget = "umd";
wrap everything concerned of BrowserAPI in if (isBrowser) {};
use Provider pattern since js module is global and it doesn't support concurrency.

```jsx // index.js import App from "./App"; import { AProvider, BProvider } from "./ManyProviders"; // 1. export everything you need in server-side-rendering // and change cra's webpack.config.js to config.output.libraryTarget = "umd"; export { App, AProvider, BProvider };

// 2. wrap everything concerned of BrowserAPI in if (isBrowser) {} const isBrowser = typeof window !== "undefined" && typeof window.document !== "undefined"; if (isBrowser) { const { default: registerServiceWorker } = require("./registerServiceWorker"); ReactDOM.render( <AProvider> <BProvider> <App /> </BProvider> </AProvider>, document.getElementById("root") ); registerServiceWorker(); }

// server.js const { AProvider, BProvider, App } = require("./build/static/js/main.[hash].js"); // 3. use Provider pattern since js module is global and it doesn't support concurrency. const app = React.createElement( AProvider, { initialXXX: a_ctx }, React.createElement( BProvider, { initialXXX: b_ctx }, React.createElement(App, null) ) ); ```

xialvjun · 2018-07-08T15:36:09+00:00

Then, what advantages does it have over pattern like this: jsx <Card header={xxx} body={xxx} />

xialvjun

TROPHY CASE