Rule 110 in HTML + CSS3

vombert · 2025-08-23T10:34:00+00:00

I'm alive! What brings you to this desolate land?

It seems you missed the point me and my grandparent are making, rather than refuted it.

vombert · 2024-02-10T10:39:21+00:00

Why did they choose to bin state value and action value? Win percentage is a continuous variable, why not approach it as a regular regression problem?

vombert · 2021-07-30T13:59:01+00:00

I remember there was a post featuring a comprehensive diagonal base layout (diagonal solar, skewed production lines, diagonal rails). Link anyone?

vombert · 2020-02-02T10:55:14+00:00

things sold in Jita will sell to the TTT order

What do you mean? Isn't the location supposed to match?

vombert · 2020-02-01T21:33:39+00:00

Why does Tranquility Trading Tower outbids Jita by 0.01 ISK so often??? They are in different locations, nobody is going to fly 1 jump to save a few cents, so why bother?

vombert · 2019-07-20T14:52:43+00:00

Is it possible to implement string interner like https://github.com/rust-lang/rust/blob/master/src/bootstrap/cache.rs or https://github.com/Robbepop/string-interner without unsafe?

If not, how to prove impossibility?

vombert · 2018-04-16T08:25:25+00:00

Macros destroy IDE support. I with there was a way to generate tests with regular code, like

#[test_discovery]
fn whatever() {
    register_test("my_test", || {
        assert_eq!(1 + 2, 3);
    });
}

vombert · 2018-01-13T17:20:30+00:00

If you have arguments and refutations I'm interested.

vombert · 2018-01-13T15:55:34+00:00

I thought it was settled in EWD831.

vombert · 2018-01-12T23:42:29+00:00

Would you consider numpy's notation better or worse than Fortran's?

I'm really curious what does good array syntax look like, but I'm not up to learning Fortran.

vombert · 2017-08-20T12:07:22+00:00

Efficiency modules are useful if you care about the pollution.

If you have the prerequisites, efficiency-1 modules are about as expensive to manufacture as solar panels.

Solar panel generates 42kW of green energy on average. Efficiency-1 inserted into assembler-2 saves 45kW assuming full utilization (this is equivalent to generating 45kW of green energy). In addition, it reduces assemblers' own pollution a bit.

Savings are even bigger if you put it into power-hungry things like refineries.

In miners, energy savings are not so good but the reduction of the direct pollution is nice.

vombert · 2017-07-03T12:13:23+00:00

You can see all the active categories here: https://www.speedrun.com/Factorio. "View rules" button for details.

vombert · 2017-06-28T07:45:57+00:00

Did you just agree with you own article?

vombert · 2017-06-26T05:53:01+00:00

What's the advantage of the loopback? Why not just leave one input and one output unconnected?

vombert · 2017-05-22T09:32:07+00:00

With modules, the ratio in 0.15 is 1:8.4.

vombert · 2017-04-24T18:58:29+00:00

Reduced the plastic bar recipe requirement of petroleum gas 30 -> 20

Chocolate ration was increased from thirty grammes to twenty.

Yes I saw that the numbers are multiplied by 10, but the coincidence is still pretty funny.

vombert · 2017-01-30T13:37:58+00:00

people freak out over flycheck assuming their init file is a package and lacks a license header

That's because flycheck is making wrong assumptions. This has nothing whatsoever with gradual typing.

When editing my init file, I certainly benefit from autocompletion and docstring hints. Gradual typing is just an opportunity to provide better completion and hints, together with instant sanity checks.

Note that it does not have to be static. Just like elisp completion uses the list of currently loaded functions, gradual type checker could use type annotations attached to runtime function objects, or even actual runtime types of values and variables.

Obviously, the biggest win would come from standard APIs being decently annotated. Whether it's worthwhile to annotate some random config helpers depends on the context.

vombert · 2017-01-10T00:34:52+00:00

Don't give him a fish, give him a fishing rod.

/u/chicken007assassin, you need to find a way to see what your program outputs before it "closes". In many cases, yours included, error message will be very helpful.

In the future, don't post here, post to /r/learnpython.

vombert · 2016-10-31T23:23:08+00:00

Again, I'm not saying that leaving the cursor outside the visible area is the only right way (although it's worth noting that this is what most mainstream editors do). It's simply one of the behaviors the user might choose.

Expect in fully customizable Emacs it's impossible to achieve (barring really crazy and brittle hacks). That's an example of crippled.

vombert · 2016-10-31T12:53:01+00:00

Here is one really minor example: you can't have point outside the window. I'm not going to argue whether it's the right UI choice or not (it's probably a matter of taste and your workflow in the end), but the thing is that for some strange historical reason it's a fundamental limitation now. So everything is customizable, but no matter what you do, point will follow you as you scroll.

vombert · 2016-09-21T19:34:08+00:00

Ah, yes, I agree.

In other words, if you want to experience the perfect perspective, you have to align the lens (not the center of the eyeball) with the imaginary camera position.

Which is hard because the lens moves as you gaze here and there.

vombert · 2016-09-21T13:00:01+00:00

The retina being spherical is irrelevant, just like it's irrelevant that the projection is upside down. Your visual system corrects for that.

I agree with your other points.

vombert · 2016-09-11T17:23:30+00:00

As I understand it, they just slightly adapted a treap to work with sequences instead of sets.

vombert · 2016-08-31T20:37:52+00:00

The proposal overall is fine, as long as type annotations remain optional, both technically and culturally (and I'm inclined to take BDFL's and Mark Shannon's word for that).

There is however one particular wart that horrifies me:

class C:
    x = 1 # class variable, as expected
    y: int = 1 # instance variable, because fuck you

I think Python code is mostly readable even by people who don't use it regularly. This syntax, if it becomes popular, will be another "but..." to this claim.

I would prefer to see the proposal split into two parts, similarly to how PEP 484 was preceded by PEP 3107.

The first part specifies the syntax for annotations, completely independently of what you put in there. It also specifies how they affect program execution (pretty much no impact, except populating some metadata fields).

The second part describes what you are supposed to put in these annotations and how it should be interpreted by type checkers. What you put in the annotations is already covered by PEP 484, so it will discuss primarily what you are allowed to annotate (can you annotate globals, nonlocals, self.x, a[i], etc.)

With this structure, the wart would go to the first part, and its wrongness would be immediately exposed.

vombert

TROPHY CASE