ederamen

I'd be interested in this too. I know it's possible, but haven't found a good guide on how to do it well and manage the multi-lang complexity.

Uv is so good. I'm a curmudgeon about adopting new tooling, and tried uv with a lot of skepticism, but it was just better in every way. And even if it wasn't so polished and reliable, the raw speed makes it hard to go back to any other tool.

Uv combined with type hints reaching critical mass in the Python ecosystem, and how solid PyLance is in VSCode, feels so good it has made me consider investing in Python as my primary language for everything. But then I remember that Python is dog slow compared to other languages with comparable ergonomics and first-class support for static typing, and...idk it's a tough sell.

I know the performance meta in Python is to...not use python (bind to C, Rust, JVM) - and you can get pretty far with that (see: uv), but I'd rather spend my limited time building expertise in a language that isn't constantly hemorrhaging resources unless your code secretly calls something written in another language :/

There are so many good language options available today that compete. Python has become dominant in certain domains though, so you might not have a choice - which makes me grateful for these big steps forward in improving the tooling and ecosystem.

LLMs are brain rot

My second Oura ring (3rd gen) is ~3 years old and is currently collecting dust in a drawer because the battery lasts < 24 hrs, and If you forget to sync your data by opening the app (which can take a minute or longer of having the app open in the foreground) before it dies, it dumps all data collected since the last sync. Super frustrating.

I might be able to get it replaced if support decides to be generous, but dealing w/support is a pain, and the alternative is buying a $400 replacement every 2-3 years when the battery starts to fail.

I don't have to pay the monthly subscription - they had a deal where you could buy a third gen ring (at full price) and would get lifetime access without paying a monthly subscription. Despite that it still doesn't feel worth it to me to have yet another device I have to babysit (remember to sync with the app every day, remember to wear, remember to charge) and pay hundreds of $ to replace every 2-3 years. With the subscription cost, there's no way this product's value proposition makes sense for me.

Use Data Classes

Obviously

Just started using Raylib, bummed to hear about the limitations!

As a novice C programmer, the simplicity and immediacy of results opened my eyes to how C can feel as productive as higher level languages with robust standard libs.

We should probably just do nuclear.

Oh cool - I started looking into Qt a while ago but was confused by their license. Would you recommend it?

Agreed, but it's because Apple has deliberately and relentlessly sabotaged PWAs as a competitive option.

If it were in their financial/competitive interest for PWAs to be amazing on iOS, they would be.

Unfortunately for us this would circumvent their 30% app tax, so they'll be dying on this hill.

I'm hoping the latest EU regulation enforcing alternate browser engines will make a dent in this.

...but when I see how petulantly defiant Apple's responses to other regulations which threaten their lock-in strategies have been, I'm not optimistic.

This. Apple has been slowly, relentlessly, sneakily squeezing out any open or cross platform dev options.

If you want to develop for Apple's devices, you have to sacrifice your future career options with any other tech stack/vendor by investing your limited time into skills that are only relevant in the Apple ecosystem.

Then you have to hope that it's still financially viable to do software dev in Apple's world for the next few decades - which given their demonstrated behavior of scraping back more and more of the pie for themselves and their shareholders, seems like a risky bet.

Apple has done an incredible job of gaslighting developers into believe they care about them and are making generous investment into APIs and tooling, while simultaneously doing everything in their power to lock those devs into the platform and and force them to spend their limited time/resources learning the Apple-exclusive tech stack.

The intolerable part for me is that after you've spent years investing in learning their (non-portable outside of Apple) languages and APIs, they can reject anything you build for mobile for any reason, and you ultimately have zero recourse.

In other areas of software you could take the skills you've learned to your next job/project - but as Apple is moving more towards declarative frameworks where you aren't supposed to think about what's going on under the hood (I.e. SwitfUI), the amount of actual deep, transferable software engineering skills you gain from working with these frameworks approaches zero.

The investment just doesn't feel worth it to me, when there are so many other things I could be learning to advance my career.

They don't develop those APIs out of the goodness of their heart - it's a lock in strategy.

They've made it practically impossible to write native cross platform code that runs on IOS, and they've everything they can (within political limits) to prevent web apps from being able to compete with native apps.

That's 40% of "ton-miles" - trains disproportionately move heavy, cheap goods (i.e. aggregate, coal), which makes that number potentially misleading. The percentage of freight moved by rail by "value" is closer to 15% (trucking is ~65%).

https://www.bts.gov/newsroom/2017-north-american-freight-num...

https://www.aar.org/facts-figures#:~:text=Freight%20rail%20a....

Yes.

^ This - thank you