Applied rationality for a coding agent. Defensive epistemology: minimize false beliefs, catch errors early, avoid compounding mistakes.
This is correct for code, where:
this is for Tizen 8 Samsung TV. You have other options available if you have an older TV
Install Tizen Studio
Install the following from the Package Manager dialog:
From Main SDK:
8.0 Tizen
This guide is based on using an Ubuntu VM. The whole process will take several hours when doing for the first time. I faced issues with Windows 11, but you are free to try it. There are helpful comments below for Windows users.
Please read all the steps first before proceeding.
| #!/bin/bash | |
| sudo apt install software-properties-common && sudo add-apt-repository ppa:ondrej/php -y | |
| sudo apt update | |
| sudo apt upgrade -y | |
| sudo apt install php8.1 -y | |
| sudo apt install php8.1-bcmath -y | |
| sudo apt install php8.1-bz2 -y | |
| sudo apt install php8.1-cli -y | |
| sudo apt install php8.1-common -y | |
| sudo apt install php8.1-curl -y |
| <template> | |
| <div> | |
| <form> | |
| <input | |
| @input="setSearch($event.target.value)" | |
| :value="search" | |
| type="text" | |
| placeholder="Search" | |
| class="border p-1" | |
| /> |
I haven't found a way to set your main profile photo on meetup.com such that it overrides any old photos you have set in individual groups. This script will do just that — set your group specific profile photo to your main photo for every group you're in.
Here's what to do:
enter:(async function() {
| #!/bin/bash | |
| # To install: just copy this script to your machine and name it whatever you want. | |
| # Let's say you named it toggle-desktop-icons.sh, then all you need to do is make | |
| # the script executable, like this: | |
| # | |
| # chmod +x toggle-desktop-icons.sh | |
| # | |
| # Now you can execute the script directly in the terminal any time you want to | |
| # show/hide the desktop icons, like this: |
I heard some points of criticism to how React deals with reactivity and it's focus on "purity". It's interesting because there are really two approaches evolving. There's a mutable + change tracking approach and there's an immutability + referential equality testing approach. It's difficult to mix and match them when you build new features on top. So that's why React has been pushing a bit harder on immutability lately to be able to build on top of it. Both have various tradeoffs but others are doing good research in other areas, so we've decided to focus on this direction and see where it leads us.
I did want to address a few points that I didn't see get enough consideration around the tradeoffs. So here's a small brain dump.
"Compiled output results in smaller apps" - E.g. Svelte apps start smaller but the compiler output is 3-4x larger per component than the equivalent VDOM approach. This is mostly due to the code that is usually shared in the VDOM "VM" needs to be inlined into each component. The tr