It seems that the 140x lower storage cost comes from:
1. S3 (OO) vs EBS (ES): about 5x
2. No indexing: About 10x ?
3. No data duplication (due to using S3 I assume) in HA deployment: 3x
Is my math right? Or do you use something different for compression?
2 Orders of magnitude of storage saving is pretty impressive.
One problem with Tauri is that it doesn't bundle Node runtime, meaning that you can't take advantage of the npm packages that works outside of a browser environment. It does allow you to use Rust packages, but that's another story than Javascript.
> After work I prep for dinner, keep working on my projects, and then drive 5 min west to the beach right before sunset and sit in the back of my car writing in my notebook. This is my favorite time of the whole day, a solid 30 min break where I don't look at my phone or any screen
Sounds like a wonderful time for unwinding. What would you be writing in those time?
Very interesting idea! I think I've heard something like this before on giving reward randomly yielding to addictive behaviours, like gambling. Do you have any recommended reference on this idea?
Karabiner is incredible for making keyboard shortcut to do some pretty complicated task.
Obsidian, what a note-taking app! Makes Evernote looks like a dinasour.
Vim (and NeoVim), you learn it once and use it for everything.
No need for the sarcasm, it's open source, you don't have to use it. But to answer your question, you can't do `./my-script foo`, because you can't call a function directly as argument.
If you also want auto-completion, you bascially re-implemented Bud.
Your statements are correct, but they are workarounds, and doesn't cover all the use cases. And they usually requires a StackOverflow search. For the above 2 reasons, I consider them to be limitations.
1. Problem is You have to explicit define a number of arguments and they have to be named. Consider the situation where you want to call an arbitary number of arguments, can't do that. (ref: https://stackoverflow.com/questions/2214575/passing-argument...)
.PHONY: a b
a:
echo A
b:
echo B
a # can't do this
echo B
3. .PHONY should be the default when you don't use file target, which is often the case for most non-C project.
With Bud, bash script become your Makefile and bash functions become your Make target. You can have arbitary numbers of arguments, you can reference other targets since they are just functions, and you don't need to explicitly add your target to .PHONY.
There are other reasons you want to move away from Make. For example:
cdf () {
target=`osascript -e 'tell application "Finder" to if (count of Finder windows) > 0 then get POSIX path of (target of front Finder window as text)'`
if [ "$target" != "" ]
then
cd "$target"
pwd
else
echo 'No Finder window found' >&2
fi
}
I would say that in terms of efficiency, Vim is >= Sublime. I have yet to see anyone using a GUI text editor beat the text editing speed of Vim.
Plus, you are at full productivity when working with terminal. Think about how easy it is to ssh to a server and edit files with Vim.
Hope it helps someone!