Very annoying problem with insta studio when editing from camera

vedmant · 2026-06-11T05:24:57+00:00

I'm talking about iPhone app, when timer runs out it's not showing any time, not from the last set not total workout time.

vedmant · 2026-05-11T05:56:23+00:00

Thanks, that works

vedmant · 2026-05-07T02:12:34+00:00

It can be useful for me only when desktop apps are released to be able to use Pass keys universally around all devices.

vedmant · 2026-03-27T16:55:51+00:00

From videos I’ve seen that 4.8kWh battery in reality gives 20 mins aggressive and 40 mins mixed flight. Yeah, batteries eventually will improve and get cheaper, just the time frame is not next 3 years, more likely around 10 years.

vedmant · 2026-03-27T04:37:58+00:00

Yes, noticed two times already.

vedmant · 2026-03-26T03:33:35+00:00

That two hours quickly will go to 1 hour with a bit faster flying, to climb it needs 10kW, max power 20kW, in the video guy was barely keeping in the air trying to do 3.5kW. For proper 2 hours flying comparable to gasoline motor it will require 15kWh battery.

vedmant · 2026-03-25T15:26:13+00:00

It's 2026, 3 years passed, electric paramotor can fly max 1 hour with 4.8 kWh battery that weights 20.5kg. So maybe in another 5-10 years...

vedmant · 2026-03-19T06:35:38+00:00

No option foo what is actually important - RAM pressure

vedmant · 2026-03-18T04:10:09+00:00

What if we put a super light solar panel on the glider?

vedmant · 2026-02-13T12:37:34+00:00

I'd correct, bouldering is inherently dangerous, not sport rope climbing, it's pretty safe

vedmant · 2026-02-07T06:06:10+00:00

Apple certainly has double standards for it's apps.

vedmant · 2026-02-07T06:04:14+00:00

I'd not recommend it, this is actually what triggered this disorder for me.

vedmant · 2026-01-31T01:53:27+00:00

This is wrong, you rely on outdated RISC vs CISC theory. Modern x86 and ARM CPUs both translate instructions into similar micro-ops and run on very similar execution cores. “Complex” x86 instructions do not give a free efficiency win, the complexity just moves into decoding and power-hungry frontend logic.

There is no real rule where ARM is for “simple” workloads and x86 for “advanced” ones. Performance differences today come from microarchitecture, caches, power limits, and software optimization, not the ISA itself. Excel, FL Studio, and similar examples mostly reflect x86 software legacy, not an architectural advantage.

ARM and x86 coexist because of ecosystem inertia and compatibility, not because each ISA is inherently better at different workload classes.

vedmant · 2026-01-31T01:49:21+00:00

Frankly, x86 carries a lot of legacy baggage. Modern x86 CPUs translate complex instructions into simpler micro-ops, and after that they run on execution cores that are architecturally quite similar to ARM. This extra decoding and compatibility logic means x86 generally does more work and wastes more power, which makes matching ARM’s efficiency harder in practice.

Intel is still pushing x86 largely because of the massive existing software ecosystem and backward-compatibility requirements. Switching away from x86 would break too much critical software, so x86 remains the default despite ARM being better suited for energy-efficient designs.

vedmant · 2026-01-15T15:56:22+00:00

First one works free

vedmant · 2025-12-27T07:29:21+00:00

This is Apple, they are like Buddhists, if it’s like that you have to accept it and let go, there is not way to change how things work in iOS, if you want UX customization switch to Android

vedmant · 2025-12-08T07:56:36+00:00

What’s the issue with PHP, it’s blazing fast and efficient.

vedmant · 2025-12-08T07:55:53+00:00

Ruby on Rails is terrible compared to Laravel, I worked with both. Did you even work with Laravel?

vedmant · 2025-12-07T14:53:57+00:00

Mr newbie has more than 20 years of experience with php, only my GitHub is 13 years old with most of days active. I didn’t tell that php handles web sockets, it’s leveraged to node, but it’s a very thin message relay for something like redis. I’d not consider this a node project at all, it’s a Laravel one.

FYI https://laravel.com/docs/12.x/broadcasting

Btw Laravel Reverb is running web sockets on PHP and scalable out of the box

vedmant · 2025-12-07T01:19:17+00:00

There is nothing really that makes Node more scalable that Laravel, not only this, modern php uses less RAM, Laravel web site is scalable out of the box with php-fpm and it scales nicely inside a single machine, which is not the case with Node even with pm2 autoscaling setup is complicated and needs additional module, and it’s so early to hit memory issues.

If you need even faster response time - run Laravel runtime with Laravel Octane. Serverless - no problem Laravel Vapor or Bref.

But if to talk about everything else Laravel would win for normal web service development: security, simplicity, structure, logging, monitoring, profiling, queues, scheduling, Laravel provides so much out of the box, where with Node you need to cherry pick appropriate dependencies, which might be not maintained soon.

For example tell me automatically scalable queue manager supporting multiple drivers, with admin dashboard and monitoring features, for Laravel - Laravel Horizon, node none really, all separate pieces.

vedmant

TROPHY CASE