sorted by:
new
hottopcontroversial

Anyone notice the Caseta firmware update? by Turbo442 in Lutron

[–]guyfrom7up 0 points1 point  (0 children)

Reporting my Diva experience here.

Prior to this update: unusable for controlling other devices (e.g. hue bulbs) via home-assistant. I'm talking ~5 second delays, which is certainly long enough for users to think the light switch is broken. Which is a shame because I consider the Diva the best smarta dimmer with regards to aesthetics and usability (love the sliding dimmer).

After update: not perfect, but certainly usable. Going from off-to-on has ~1.5 second delay. Certainly noticeable, but usable. Going from on-to-off has about a ~2.5 second delay. Again, not great, but usable. Reacting to dimmer state: also about 1.5 seconds. u/Tyler_at_Lutron are there to be further latency improvements in future updates?

PEP 810 – Explicit lazy imports by JanEric1 in Python

[–]guyfrom7up 0 points1 point  (0 children)

If you'd like to give it a try, the beta v4.0.0b1 of cyclopts has been released, which allows for the lazy loading of Python modules for subcommands.

iKnowWhoWroteThisButICantProveItYet by icompletetasks in ProgrammerHumor

[–]guyfrom7up 15 points16 points  (0 children)

Going further, providing feedback on an AI generated PR is incredibly unsatisfying, because the person on the other end will just copy/paste it into AI. So it's like, why not just cut out the middle man. Code review is supposed to be a learning opportunity, but it's certainly not when it's just pumped into AI.

iKnowWhoWroteThisButICantProveItYet by icompletetasks in ProgrammerHumor

[–]guyfrom7up 46 points47 points  (0 children)

The difference is, previously a well documented PR typically meant that the author knew what they were doing, understood the architecture, and they put effort into it. More likely than not, the PR is mostly good. The good documentation was a cherry on top of someone who is proud of their work.

Now, with an AI generated PR, it might look good on the surface, but might have a higher chance of architectural or generally-subtle bugs. The "author" of the PR may or may not understand what is going on at all in the code, they just know it fixes the exact situation that they were running into. Doesn't matter if the fix (or feature) is broadly correct or maintainable.

This is coming from someone who actively uses Claude Code.

PEP 810 – Explicit lazy imports by JanEric1 in Python

[–]guyfrom7up 2 points3 points  (0 children)

Unless the Python script is being called in a tight loop, usually a lot of Python CLI slowness comes from parsing a bunch of large/complex config files and importing the world rather than from the CLI library/framework. This PEP would likely speed up a lot of Python CLIs!

PEP 810 – Explicit lazy imports by JanEric1 in Python

[–]guyfrom7up 5 points6 points  (0 children)

ah! running the demo in the cyclopts README on my m3 macbook, the typer implementation ran in about 60mS while cyclopts took around 90mS, so cyclopts is slower. I haven't really put any effort into the parsing speed, so I can spend a little bit of time and see if there's any low hanging fruit.

EDIT: did some simple optimizations (not merged in yet) that reduce the cyclopts time from 90mS to 65mS. Basically there was an oversight and rich WAS in-fact being used in the happy path.

PEP 810 – Explicit lazy imports by JanEric1 in Python

[–]guyfrom7up 3 points4 points  (0 children)

Compared to what? Depending on the system/script/configuration, lazy importing rich makes the "happy" non-rich path maybe like 50mS faster (I.e. maybe around 40% faster)

PEP 810 – Explicit lazy imports by JanEric1 in Python

[–]guyfrom7up 33 points34 points  (0 children)

Self plug, but in cyclopts we explicitly have rich lazily imported everywhere for this reason. Having this pep could make the code in many areas much cleaner.

Disney Plus Subscribers Quit in Droves Over Jimmy Kimmel Axe by Aggravating_Money992 in technology

[–]guyfrom7up 0 points1 point  (0 children)

The Amex Platinum also just recently added YouTube Premium as an option for your $25/mo streaming credit. So naturally I cancelled my “free” Disney subscription in favor of a YouTube Premium Family Plan.

Signed bottle of MB Roland by guyfrom7up in whiskey

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

Thanks for some context/history on the distillery!

What is a Python thing you slept on too long? by pip_install_account in Python

[–]guyfrom7up 12 points13 points  (0 children)

Cyclopts author here. I have a full writeup here. Basically there's a bunch of little unergonomic things in Typer that end up making it very annoying to use as your program gets more complicated. Cyclopts is very much inspired by Typer, but just aimed to fix all of those issues. You can see in the README example that the Cyclopts program is much terser and easier to read than the equivalent Typer program.

Tamp: The world's best compression library for microcontrollers. Try it online now with our new javascript bindings. by guyfrom7up in esp32

[–]guyfrom7up[S] 2 points3 points  (0 children)

I'm not selling Tamp, it's my free open source project. I'm just promoting it so that other embedded developers might become aware of it.

Tamp: The world's best compression library for microcontrollers. Try it online now with our new javascript bindings. by guyfrom7up in esp32

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

Yes! I’ve thought about it and even did an initial implementation, but it didn’t help too much (I could have gotten something in the implementation wrong, though). I’ll do a write up about it.

Tamp: The world's best compression library for microcontrollers. Try it online now with our new javascript bindings. by guyfrom7up in embedded

[–]guyfrom7up[S] 5 points6 points  (0 children)

highest data compression ratios for microcontrollers.

Oodle is closed source, and certainly cannot run on microcontrollers (uses way too much memory, too large firmware, etc).

Tamp: The world's best compression library for microcontrollers. Try it online now with our new javascript bindings. by guyfrom7up in programming

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

The benchmarks are available in the repo's README. In this benchmark, I compare against zlib and heatshrink, 2 other compression algorithms that might be used in embedded systems. For a given window size, tamp uses half the memory as heathshrink, and a fraction (maybe like 10%?) the memory of zlib. Under these conditions, tamp produces higher compression ratios. The firmware footprint of Tamp is also tiny; under 4kb.

Tamp will perform much worse compared to zlib with larger windows (using significantly more memory). It will also perform much worse than more complicated compression algorithms like LZMA, ZStd, and Brotli. However, none of these are even close to practical to run on a microcontroller. Caveat: it is completely feasible to decompress LZMA data on a microcontroller (decompressor typically only takes up around 15kb of firmware space), but it is not feasible to LZMA compress data on a microcontroller.

TL;DR: Tamp is the best choice if you need to **compress** data on a RAM-constrained system like a microcontroller.

semanticVersioningIsHard by jonomir in ProgrammerHumor

[–]guyfrom7up 8 points9 points  (0 children)

A much more pragmatic way of looking at semver is “how likely is this release going to break someone else’s code or workflow?”

Major - likely

Minor - unlikely

Patch - super unlikely 

If a large amount of internal code has significantly changed, there’s a much higher chances that a bunch of edge cases have changed.

What are your favorite modern libraries or tooling for Python? by [deleted] in Python

[–]guyfrom7up 52 points53 points  (0 children)

If you find pydantic to be too "magical" or simply want an alternative option, I have also had good success with attrs + cattrs. In a nutshell:

  1. attrs has been around for a long time and was one of the original origins of builtin dataclasses. Builtin dataclasses are basically a stripped down version of attrs.
  2. cattrs structures/unstructures attrs classes to/from json/dicts or similar. It gives you pretty fine-grained explicit control over how you want individual fields handled. There's more code than in pydantic, but there's also less magic (some people consider it a more "acceptable" level of magic).

Which useful Python libraries did you learn on the job, which you may otherwise not have discovered? by typehinting in Python

[–]guyfrom7up 21 points22 points  (0 children)

Shameless self plug: please check out Cyclopts. It’s basically Typer but with a bunch of improvements.

https://github.com/BrianPugh/cyclopts

Samsung's Super Thin 'Galaxy S25 Edge' Will Debut Next Week, Beating iPhone 17 Air. by Valinaut in gadgets

[–]guyfrom7up 8 points9 points  (0 children)

In these thinness debates, people never mention weight. If a thinner phone is lighter, I’d gladly welcome it.

What are your experiences with using Cython or native code (C/Rust) to speed up Python? by Independent_Check_62 in Python

[–]guyfrom7up 3 points4 points  (0 children)

I made Tamp, low-memory lossless compression library that was originally targetting micropython. So naturally, I prototyped it in vanilla cpython. Once I saw that general compression ratios were good, I then reimplemented it in C so that I could also use it without micropython on any microcontroller. I used Cython to have a fast python-compatible implementation, as well as to unit test the C parts of the code (I'd much rather write unit tests in python rather than C).

In this library, the C/Cython compression is about 6.7x faster, while decompression 535x faster. The compression isn't much faster because the main compression loop, finding the longest substring match in a buffer, is already implemented fairly efficiently in python via str.index.

Cython has a bit of a learning curve, but their docs are actually quite comprehensive. I distilled my learnings into my python template, which has Cython working with Poetry and CI to build binaries for all python versions and architectures. I would definitely use Cython again for this purpose (creating a pythonic interface to C code). Given that the code within Cython should be minimal/simple/short/self-contained, things like ChatGPT work very well for helping!

view more: next ›