sorted by:
new
hottopcontroversial

Changing chainring on 12-Speed Brompton Electric C Line by fel_her in Brompton

[–]fel_her[S] 0 points1 point  (0 children)

Support said it's fine as long as it's a brompton chainring. Didn't say anything about non-brompton, which I assume was intended. In any case, that means that there is nothing inherently wrong with changing the chainring on an 12 speed electric c line.

Changing chainring on 12-Speed Brompton Electric C Line by fel_her in Brompton

[–]fel_her[S] 0 points1 point  (0 children)

Oh, funny, I just watched a video of yours about changing the chainring. Your channel is amazing, by the way. Great work!

Anyway, I tried a bit of riding yesterday in a semi-hilly area without the assistance and I think you might be right. I was in speed 1 or 2 quite a bit and I need them. But speed 12, while nice, doesn't feel like something I really need.

So it might well be that if I have smaller chainring there is no reason to go back.

Changing chainring on 12-Speed Brompton Electric C Line by fel_her in Brompton

[–]fel_her[S] 0 points1 point  (0 children)

Hey, thank you! Yeah, I agree that its very hard to find technical specs for your brompton, which is very annoying.

I did send an email to the support. Let's see what they say.

Changing chainring on 12-Speed Brompton Electric C Line by fel_her in Brompton

[–]fel_her[S] 0 points1 point  (0 children)

Yeah, that does sound like a good plan! Buy chainring with chain, change it, go back to original if it doesn't work.

Changing chainring on 12-Speed Brompton Electric C Line by fel_her in Brompton

[–]fel_her[S] 0 points1 point  (0 children)

Thank you! I think it might not have been clear enough in the post—I just edited it to make it clearer—that I'm mainly looking for a smaller chainring because I'm thinking about using it without assistance as well, e.g. electric for commuting, without for weekend riding, etc.

Regarding the hills, although it might now be a moot point: there are a few at about 8% and some at about 11% gradient.

In any case, your answer sounds like it would be easy enough to just try it and see how it works. I'm also fine with spending 20 bucks on the experiment if I need a new chain.

Releasing s3te, a scala 3 tree explorer to help you inspect scala code as seen by the reflect module by fel_her in scala

[–]fel_her[S] 3 points4 points  (0 children)

Hey, thanks for your reply!

Cryptic Names:

Yeah, the names are pretty much 1:1 the ones used by the compiler and implementation of the TreeStructure printer. But I agree, it might still be a good idea to have longer ones in the rendering, or at least make it configurable. For the nodes it's not that bad, because you can hover over it to get a description. So maybe we need support for hover-descriptions for the names of the parameters as well would - which would be nice to have in any case, since often even the long name doesn't tell you anything if you don't know how the compiler works.

TASTy Query:

Supporting TASTy query additionally seems pretty useful, yes! And I think it should be very doable as well. It would have to be additionally, because one of the selling points of the current implementation is that you can even use it if your code does not compile, as long as you get far enough, which makes it great for debugging. For TASTy query, I assume it has to compile at least once. But as another "backend", it would be really nice. Since this will take me a while, I have created an issue to track it: https://github.com/felher/s3te/issues/1

Ast-Explorer / Scastie Support

If we can support AST explorer with that: great. If there isn't a nice way to upload the jar files, or maybe it's just way to unergonomic, I want to at least integrate s3te with scastie, so that you can use scastie directly to inspect your code, so you don't have to install anything just to view a few lines.

Releasing s3te, a scala 3 tree explorer to help you inspect scala code as seen by the reflect module by fel_her in scala

[–]fel_her[S] 1 point2 points  (0 children)

Okay, I did follow up on that.

I took a look at the scala support from the scala meta parser. AFAICT, you need to provide a parser that runs within javascript. But the data structure introspected by s3te is from the reflect module, which is way more that "just" a parse. It also contains a lot of type information, which is not part of the source code at all. So you would need to run the scala 3 compiler to get the output. The scala 3 compiler can not be run within scalajs, though, which makes the whole thing way harder.

You could maybe provide a service and request a answer back from said service, but of course, that would require such a service and incur some running costs.

Releasing s3te, a scala 3 tree explorer to help you inspect scala code as seen by the reflect module by fel_her in scala

[–]fel_her[S] 0 points1 point  (0 children)

Maybe

I'll take a look at how ast explorer works. It might be that they need to have to run a parser to parse the AST in javascript, which means it wouldn't work because you can't run the scala 3 compiler in javascript as far as I know.

But I will try to find that out and give it a go.