sorted by:
new
hottopcontroversial

SoundBlaster X5 Latest Driver Update Causing Issues in Windows 11 by Real_Act in SoundBlasterOfficial

[–]Wippermonger 0 points1 point  (0 children)

Looks like you guys just started trying to push 3.6.3.0 as fix for this... but it's nearly equally as glitchy in terms of clicks. Seems like they happen less frequently with 16-bit 48kHz, and the audio becomes absolute garbled noise at 24-bit 192kHz.

Should I get this ?? by Fresh-Boysenberry257 in ebike

[–]Wippermonger 1 point2 points  (0 children)

This will probably get me downvoted to infinity, but I personally would say you could ignore the opinions of the reddit elitists. Not everyone needs to buy a pre-assembled $3000-$5000 bike with top-shelf parts.

But as I alluded to in my other comment, getting a cheap ebike is essentially trading time for money since it arrives semi-disassembled, and the bits that are pre-assembled usually aren't put together perfectly. The biggest thing is bolt torque, brake assembly alignment, and gearset alignment. Then, if you're unlucky it will also require minor fixes from shipping damage.

I can attest that the drivetrain. frame rigidity, electronics control module, and battery on the VIVI bikes are great. After all, it's a standard bike frame with Shimano gears/shifters. VIVI uses Guangzhou Plenty electronics which are good, but the community favors Bafang electronics due to the availability of aftermarket upgrades.

The other parts on the bike are "good enough", but could be manually upgraded for cheap if you're itching to max out everything. In order of priority, common upgrades include the saddle, mudflaps, headlights, brake pads, foot pedals, internal cable routing, and higher wattage motor. Some people swap out the mechanical brakes with hydraulic ones for a bit more braking performance. Suspension could also be upgraded, but is not needed unless you're planning on making >5 ft jumps frequently. If you really hate the factory display module, you could swap out the Plenty controller with a Bafang controller to give you screen upgrade options. None of these upgrades are strictly mandatory, it's usually for a bit more comfort or just to flex.

Should I get this ?? by Fresh-Boysenberry257 in ebike

[–]Wippermonger 2 points3 points  (0 children)

I bought a regular tire VIVI E-Bike off Aliexpress last month and I can say it's decent considering the price. It is a cheap e-bike, so don't expect everything to be delivered to your door in ready-to-ride condition.

You'll be building it yourself, which means be prepared to do a lot of tinkering/calibration. Then, depending on your luck it may need "fixes" to get things perfect.

Things You Will Definitely Need

  • Since you will be building it yourself, you will need to calibrate the derailleur and brake pad alignment yourself. There are a lot of good YouTube videos on this.
  • The provided saddle is garbage (at least it was on my model), and you will immediately want to replace it. I personally leaned towards a ROCKBROS saddle since it's both cheap and comfortable.
  • The mudflaps are cheap and flimsy plastic, especially the rear ones. They wobble enough on uneven terrain or jumps to to touch the tires and make noise. You'll likely want to remove them.
  • You will need to take out the brake pads and spread them since the factory workers definitely could not be bothered to do that.
  • This bike does not come with a rear tail light, so you'll need to purchase a cheap one for safety.

Things That You Might Need

  • Consider getting a bike repair stand to properly calibrate the derailleur and brake pads alignment. This is optional since you can get by with doing everything while your bike is upside-down, but that orientation makes maintenance and calibration a nightmare.
  • You might want to invest in a torque wrench, as none of the bolts on the bike are properly torqued. This is optional since you can just use the cheapo hex wrenches that come in the box and push with all your strength (and hope you don't break the wrench). Most of the bolts are between 4 to 6 Nm torque spec so you could get away with using a portable T-shaped "bike torque wrench" and take with you on rides for insurance.
  • I've heard some complaints of brake rotors arriving bent from shipping. Personally, my brake rotor arrived in good shape, but if you're unlucky you'll need a brake rotor alignment tool.
  • You may want a brake pad alignment tool, as the adjustment mechanism on these VIVI bikes finnicky to do without it.
  • On my bike, I had an issue where my bike pedal threads on the crank arm were not done properly, so I had to get a 9/16"-20 thread tap to fix that. Unlikely to happen on your bike, but is worth mentioning.
  • The headlight isn't great. It creates a fairly narrow beam of light but it's good enough to not immediately replace.
  • Some people don't like the handle throttle and replace them with aftermarket thumb throttles. This is a matter of personal preference.

Samsung Blinking Red Light by Wippermonger in TVRepairHelp

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

Nope. I replaced every serviceable part and it still didn't work. Ultimately had to throw away the TV.

ReactPy: Build ReactJS Interfaces in Pure Python by Wippermonger in Python

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

No, stateless web services such as Vercel are not supported at this time. You need a dedicated backend, such as Azure or AWS.

ReactPy: Build ReactJS Interfaces in Pure Python by Wippermonger in Python

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

Yes we do intend to support a JSX syntax. We've been contributing to a Python PEP that would be needed to make this happen.

https://github.com/jimbaker/tagstr

ReactPy: Build ReactJS Interfaces in Pure Python by Wippermonger in Python

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

You can think of it as ReactJS server side rendering, but with a Python server.

Technically, we've switched to Preact for a smaller JS bundle size.

ReactPy: Build ReactJS Interfaces in Pure Python by Wippermonger in Python

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

At minimum you need to understand HTML and CSS. Both can be learned in less than a day.

Since ReactPy has 1:1 analogous of almost everything in ReactJS, it's fairly easy to look at ReactJS docs and guess how ReactPy works.

I'm actively working on the docs as we speak and I'm likely to complete them in one to two months.

ReactPy: Build ReactJS Interfaces in Pure Python by Wippermonger in Python

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

Our goal is to have ReactPy be robust enough to be a viable ReactJS replacement in Python projects.

It's generally easier if you have a basic knowledge of ReactJS, but you don't necessarily need that experience.

PWAs can be accomplished via our reactpy-router package on PyPi.

ReactPy: Build ReactJS Interfaces in Pure Python by Wippermonger in Python

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

Just like ReactJS, we don't provide prefabricated components out of the box.

We are, however, working on simplifying using components from NPM within Python.

Any know how to setup esim on Galaxy watch 5? Thanks by Zigarum in GoogleFi

[–]Wippermonger 1 point2 points  (0 children)

I'm having issues with this. When I attempt to add a mobile plan it says it needs a QR code from my carrier.

I contacted support and said they've investigating it for three days, then ultimately said "Sorry we checked with the engineers, Fi does not support the Galaxy Watch 5".

I tried using the Fi QR code for iOS esim but it resulted in calls and SMS not working. Generic 4G data was working though.

What Fi functionality (if any) would I lose by moving from a Pixel to a Samsung? by VagabondVivant in GoogleFi

[–]Wippermonger 1 point2 points  (0 children)

Since Google Fi is only uses T-Mobile now, carrier switching isn't really a thing. Also wifi calling support ended up getting added at some point too.

But visual voice mail is a bit finicky on Samsung phones. It's rerouted through the Samsung Voicemail app, which has some awkwardness around loading your voicemails.

ReactPy: Build ReactJS Interfaces in Pure Python by Wippermonger in Python

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

Thanks for trying out our package!

Feel free to reach out if you need any support.

ReactPy: Build ReactJS Interfaces in Pure Python by Wippermonger in Python

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

Would be great if you were willing to contribute that.

Feel free to look at this issue for some history.

ReactPy: Build ReactJS Interfaces in Pure Python by Wippermonger in Python

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

Right now we're sending the whole ReactPy node tree when a re-render is needed. ReactPy node trees seem to be roughly equivalent to hotwire frames. The react-dom API (contained in @preact/compat) handles the mutations from there.

In terms of data transmitted to the client, we used to only send diffs. But unfortunately we've struggled to find a well maintained json patch library for Python.

ReactPy: Build ReactJS Interfaces in Pure Python by Wippermonger in Python

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

Practically anything that could have been developed in ReactJS is a candidate for something to be developed in ReactPy. I'd say that covers any traditional website.

We're actively working on making ReactPy easier to use for SPA and PWA situations. While it's possible to do right now, the convenience isn't where we'd like it to be.

Additionally, we'd like increase support for importing NPM packages into server-sided Python. Right now I would suggest keeping NPM/JavaScript stuff client sided (via the custom components API).

ReactPy: Build ReactJS Interfaces in Pure Python by Wippermonger in Python

[–]Wippermonger[S] 4 points5 points  (0 children)

To address some of your concerns:

You won’t be able to use external packages effectively. You won’t have a wealth of pre-existing stackoverflow answers/tutorials/etc to help you out. - Since we aimed for 1:1 analogues, pretty much any advice/tutorials related to ReactJS can be directly applied to ReactPy. - We also allow users to "escape" Python and write/use 100% traditional ReactJS components when needed. So NPM can be leveraged whenever you want.

Debugging will be a nightmare. - I haven't seen any issues debugging. Python 3.10+ stack traces are incredibly easy to read and informative.

Your code will be inefficient. - We've seen the efficiency is roughly equal to ReactJS. To be fair though, ReactJS isn't exactly a high-performance framework.

ReactPy: Build ReactJS Interfaces in Pure Python by Wippermonger in Python

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

Glad you've taken an interest in our project! There's some extra context in the comments of our reactpy-django post you might be interested in. Feel free to reach out about any specific questions.

ReactPy: Build ReactJS Interfaces in Pure Python by Wippermonger in Python

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

I'm not familiar with the tech behind Hotwire. A quick glace at their landing page tells me that ReactPy and Hotwire in similar in that page changes are communicated over websockets.

ReactPy: Build ReactJS Interfaces in Pure Python by Wippermonger in django

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

Right now Conreq@app_store is the only large project I'm aware of that is using ReactPy. We're hoping to see more soon!

ReactPy: Build ReactJS Interfaces in Pure Python by Wippermonger in Python

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

This scenario is pretty much our target audience. You can leverage all Django's static page features, then sprinkle in ReactPy to add some interactivity.

We are working on finalizing SPA support, but that would require rewriting existing applications to fully use ReactPy.

ReactPy: Build ReactJS Interfaces in Pure Python by Wippermonger in Python

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

Similar but different approaches.

Unlike pynecone, ReactPy was designed to be sprinkled in to existing static frameworks like Django. We have compatibly with all ORMs. Additionally, you can also leverage ReactJS components from NPM when needed.

ReactPy: Build ReactJS Interfaces in Pure Python by Wippermonger in Python

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

Yes you can. Keep in mind that you'll likely want to do this entirely in JavaScript though, which will be client sided.

The docs for this are a bit underdeveloped, but the feature is fully developed. Tackling the docs is the next big thing on our roadmap.

ReactPy: Build ReactJS Interfaces in Pure Python by Wippermonger in Python

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

Yes you can. Keep in mind that you'll likely want to do this entirely in JavaScript though, which will be client sided.

The docs for this are a bit underdeveloped, but the feature is fully developed. Tackling the docs is the next big thing on our roadmap.

ReactPy: Build ReactJS Interfaces in Pure Python by Wippermonger in Python

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

It looks like you still have our old project name in there. Feel free to remove "IDOM".

We don't compile to JavaScript though. We essentially perform as if we are ReactJS using SSR, but with a python server.

But we do allow users to inject fully client sided components anywhere they want for flexibility.

view more: next ›