saidinesh5

Mark of the ninja - definitely fun and half the gameplay was putting out lamps.

The mimimi games: Shadow Tactics, Desperados 3, Shadow Gambit are my favourite.. it's view cones but they also depend on the amount of light there is. they're isometric though.

The worst part of this is half of these are the same white labelled tuya devices that can simply bind to each other's apps or the original tuya app..

And half of them completely disable local network access... Like why?!

I encountered this while scrolling and thought this would be a good small low level programming video to share

Mosh instead of ssh. Works well enough for as long as it works.

Road warrior even supports it.

But i keep going back to regular ssh or shpool with roadwarrior.

I think things might have changed in the last 6-7 years? That's when I switched away from Nvidia.

Or does your laptop have no other igpu?

My last Nvidia laptop was a Hybrid optimus laptop. I almost always ran it on the built in Intel igpu because of the really bad issues with the Nvidia cards. Video tearing, bad power management etc... I remember even switching the GPU wasn't easy... And performance wasn't as good either ..

Nvidia on desktop has been mostly fine, if not rock solid, on the happy path they provide.

But their happy path hasn't included proper wayland support for a long time.

Nvidia on laptops? Insert the famous Linus Torvalds meme here

The vast majority of the TVs only come with HDMI .. not even good enough analog inputs anymore..

Putting all the cynicism side.. it's amazing how big the changes in how we deal with information in our life time changed..

When I was younger, to solve a problem, we had to memorize a large amount of information. Or know someone who does. Or visit libraries and pray they have a book on what you need.

Then came the internet. All of that memorizing was replaced by web searches. You just focus on solving the problem, figuring out what you don't know and searching for that.

Now, it feels like we're automating the searching, connecting the dots and most of the problem solving. We focus on the high level problem description, verification of the results.

I wonder what they'd be adding to this curriculum.

Now, it feels like we're even offloading

Honestly, LLMs have been quite good at helping me procrastinate less on my pet projects.

It took me a weekend to build a little esp8266 gadget that automatically turns off my parents' water heater after a fixed time. They saw a dip in our power bill thanks to that. I did not want the complexity of a full blown home assistant setup there. And the Philips Wiz socket did not support setting timers/simple automations.I wanted to test out micropython too for this instead of the usual C++/Arduino/etc..

I started on a saturday and went from 0 to 90 that single day. The product I had after that day was mostly complete but it was crashing at odd times. I spent another day to get to the root cause of the issue - caused by the LLM mixing up async and sync functions. One prompt to the LLM and the problem is gone. The product has been running flawlessly since then - for months.

Every weekend I spent with Antigravity - I was able to push out something totally usable. Water Heater monitor, configurations for the custom Tuya devices I installed in my home, a chrome extension I wanted to use at work.

I am honestly impressed at the pace at which this whole thing improved too. Just 2 years ago - it was a totally useless tool that couldn't even match the speed or accuracy of my text editor snippets.

The link isn't available here. Can you share the specs and price of that panel?

But without the planetary alignment, can't we just rely on brute force ? Better fuel and bigger engines?

The standard advice is always to buy a transmitter and get started with the simulator. Then buy / build your custom racing drone that suits your flying style and area. Anything from 20 gram whoops that fly indoors to 5" racing quads that need a lot of open space.

But with dji neo 2 / avata you get a fairly beginner friendly set up. Once you're used to it, you can upgrade to a good racing drone by building one yourself.

One more reason for randomizing hash table iteration was to prevent Denial of service attacks:

https://lukasmartinelli.ch/web/2014/11/17/php-dos-attack-rev...

With micropython or some of the js based frameworks for microcontrollers, it's really not that new/different.Especially with ESP32/Pi Pico W/their clones...

In fact it's a lot more straight forward to not have to deal with Network Manager config files or systemd unit files or read only rootfs headaches of Linux world.

Mostly for the network stack. Economics, also, sometimes.

These days, with ESP32, Pi Pico W etc... things have changed a lot.

But before they got popular, Why deal with MCU + wiring some weird peripheral for wifi / ethernet when you get a Pi Zero W / Clone with built in wifi for the same price?

It might be developer fantasy but half of the giants in the mobile market really did take off this way:

* xiaomi with their miui skin/custom ROM - "bringing iOS like polish to Android" back then

* oneplus with their initial devices with cyanogenmod - clean aosp interface without any bloat and lots of features.

In fact, when my brother was buying phones for my mom (neither of them were really that technically inclined), he bought a Motorola mostly because "it doesn't have all those ads like redmi at the same price"

I think the main difference due to weight boils down to you riding in one gear lower when not using assistance.

On flat roads, I usually ride on 3rd or 4th gear (out of 7), now i ride in 2nd or 3rd.

But where i ride, the road isn't even and has a lot of steep slopes. There I'm on 1st gear all the time anyway and the assistance i get totally saves my knees, and ensures I'm not all sweaty when i reach my destination. Even compared to the light weight regular bicycles i rode before, this is better.

It's not about what gets redrawn but also how much of the UI state is still retained (by the GPU). Imagine having to reupload all the textures, meshes to the GPU every frame.

Something like a lot of text ? Probably easier to redraw everything in immediate mode.

Something like a lot of images just moving, scaling, around? Easier to retain that state in GPU and just update a few values here and there...

> The more dynamic/animated an UI is, the less there's a difference between a retained- and immediate-mode API, since the UI needs to be redrawn each frame anyway. Immediate mode UIs might even be more efficient for highly dynamic UIs because they skip a lot of internal state update code - like creating/destroying/showing/hiding/moving widget objects).

That depends on the kind of animations - typically for user interfaces, it's just moving, scaling, playing with opacity etc.. that's just updating the matrices once.

So you describe the scene graph once (this rectangle here, upload that texture there, this border there) using DOM, QML etc..., and then just update the item properties on it.

As far as the end user/application developer is concerned , this is retained mode. As far as the GPU is considered it can be redrawing the whole UI every frame..

That really depends on the kind of user interface no?

If you just have a lot of text and a few rectangles and no animation, immediate mode would work well...

But if you have a lot of images, animation etc ... You'd anyway have to track all the textures uploaded to the GPU to not reupload them. Might as well retain as much of the state as possible? (Eg. QtQuick)

And more draconian.

"Our systems aren't foolproof because anyone can just boot Linux from USB. Hence we should enforce secure boot with proprietary keys and disable functionality for non attested PCs"

This is not far fetched. All Android vendors went down this path and now you can't even enable developer mode if you want your bank app to work to approve your bank loan.

> Also, don’t expose it to hot water (this could weaken the waterproof seals), or high pressure water. It’s not invincible.

Aahhh. Finally the mystery of how my old pebble died is solved. Hopefully . One fine morning, the display came off. It was supposed to be waterproof and there was no puffed up battery either.

I don't think there is a single "they" here such as consumer electronics manufacturers. All the bloated web apps, all the native apps etc... Are responsible for this too. "Memory is cheap" has been the mantra for ages now.

It's just that the first people who would feel the heat because of all this is consumer electronics manufacturers.

See if there is an OTA package available for your speaker that you can extract and figure out what goes where.

Then figure out what SoC your smart speaker is running.

A lot of soc vendors just provide SDKs for IoT applications. Maybe you'll find something like that you can flash.

Also if there's a separate SPI flash chip, you can simply dump it and study the firmware.

It really depends on the websites no?

If you're building a "webapp" where you think in terms of components, no point keeping the style sheet separate..

If you're building a "website" which is basically a list of hyperlinked documents with the same styling, having just one style sheet would make sense...

Of course, there's a lot of gray area in between the two...

At the end of the day, the most that most of us can really do is be annoyed at the quirks of these leaky abstractions in the large codebases that's thrust upon us.

While I don't have the performance bottleneck numbers of React, I don't think it's about Javascript vs. WASM here.

I've seen/built some large Qt/QML applications with so much javascript and they all performed much better than your average React webapp. In fact the V8 / other browser Javascript engines also have JIT while the QML engine didn't.

Comparing QtQuick/QML + JS to HTML + JS - both GPU accelerated scenegraphs, you should get similar performance in both. But in reality it is rarely the case. I suspect it might be the whole document oriented text layout and css rules, along with React using a virtual DOM and a lot of other dependencies to give us an abstraction layer.

I'd love to know more about this from someone who did an in depth profiling of the same/similar apps on something like QtQuick vs. React.

Let's say you need to use a function like:

    int add(int a, int b){
        // Long logic and then this
        return a+b;
    }

Let's say this is your main.c.

    #include "add.h"

    int main(void) {
      return add(5,6);
    }

The preprocessor just copies the contents of add.h into your main.c whenever you're trying to compile main.c. (let's ignore the concept of precompiled headers for now).

What you can instead do is just put the add function declaration in add.h that just tells the compiler that add function takes two integers and returns an integer.

   int add(int a, int b);

You can then put the add function definition in add.c , compile that to an add.o and link it to your main.o at link time to get your final binary - without having to recompile add.o every time you change your main.c.

Precompiled headers: https://maskray.me/blog/2023-07-16-precompiled-headers

It's not.

It's a tradeoff people make between ease of integration - just download the .h file into your project folder and #include it in your source file instead of worrying about source build system vs target build system, cross compiling headaches etc...

And compilation times: any time you change any of your source files, your compiler also has to recompile your dependencies. (Assuming you haven't used precompiled headers).

Old one but good...

Flying wing from pizza box: https://m.youtube.com/watch?v=hTYuj7hzKeI

Or just help you avoid clicking next next while searching for something you want.

Although there is a special place in hell for those who put a website options for customer care at the bottom of an infinite scrolling page...