# Makefile
compile-deps:
uv pip compile pyproject.toml -o requirements.txt
compile-deps-dev:
uv pip compile --extra=dev pyproject.toml -o requirements.dev.txt8,442 karma · joined February 1, 2017
# Makefile
compile-deps:
uv pip compile pyproject.toml -o requirements.txt
compile-deps-dev:
uv pip compile --extra=dev pyproject.toml -o requirements.dev.txtAbsolutely brilliant. It's so stupid (in that it's kind of silly how easy it is to game our mammal brain) but I can absolutely see this giving an extra kick of motivation.
Have you heard of the INCUP model for ADHD? Interest, Novelty, Challenge, Urgency, and Passion. The more factors an activity has, the more drive the ADHD mind has. Rarity system adds novelty and a bit of passion.
Also if you have looked into operant conditioning at all, you know that variable interval reward schedules are the strongest behavior-forming systems (hence, slot machines and every game that act like them).
I have been planning on making a system based on those long scrolls of paper for doodle boards, so at least there is a history, but of course I procrastinated on building the mount for it.
I would love to use your application, I know there's a million to-do apps out there but I get the overwhelm/daunting very easily, so I really appreciate the scope-hiding aspect.
UUIDs/ULIDs/etc are fully distributed, you can have two clients assign an ID without coordinating with ~0% of collision.
1. do the first step in the process
2. then do the next thing
3. followed by a third action
I struggle to think of any context outside of programming, retrosynthesis in chemistry, and some aspects of reverse-Polish notation calculators, where you conceive of the operations/arguments last-to-first. All of which are things typically encountered pretty late in one's educational journey.
In this case, the safety concerns outweigh the environmental concerns.
Just wanted to elaborate a bit on this. Oil is a fantastic example for "why international trade good?" Oil is weird in that it is a fungible commodity (one barrel here is the same as one barrel there), but at the same time, functionality it's not. Each oil formation has different geology and chemistry. There are light sweet crudes, sour crudes, heavy crudes, and so on [1], and refineries (which are massive capital investments with specialized work forces) are typically tooled out to only process one type or family of types of crude oil products.
One paradox of the USA crude industry is that nearly 70% of U.S. refining capacity runs most efficiently with heavier crude, but our shale crude is lighter. Thus, 90% of crude oil imports into the United States are heavier than U.S.-produced shale crude [2]. So even if we had perfect supply/demand of crude within the USA, we would not be able to run our refineries efficiently without a massive overhaul. They have been built under decades of the assumption of a high degree of free international trade.
And these companies will be loathe to invest in retooling if they believe that the tariffs will just be rolled back in four years.
[1] https://en.wikipedia.org/wiki/List_of_crude_oil_products
[2] https://www.afpm.org/newsroom/blog/whats-difference-between-...
And the employer wants to pay the employee as little as possible for as much productivity as possible.
In a perfect world with perfect information and rational actors on a level playing field, this is great: we expect supply and demand to converge, this is econ 101.
But it's not a perfect playing field, one side is coercive, holds most/all the cards, calls all the shots, treats people with lives and experiences as "resources", and seeks profit over all other objective functions. This is class dynamics 101.
Fixed that for you.
> WebAssembly is a true write-once-run-anywhere experience.
Except not. The wasm ISA is really quite limited in the types of operations. A full-blown RISC/CISC ISA will have way more opportunities for optimization. To say nothing of multithreading and pipelining. JITing also has overhead.
> You can compile several languages into WebAssembly already.
But if you can compile them, why not just compile to container, and get free performance?
Wasm will have a hard time with anything low level: networking, I/O, GPU, multimedia codecs.
People are seeing a trajectory even worse than anticipated and sounding the alarm. The Trump administration is blasting off executive orders that many feel are unconstitutional, and the populace wants to pump the brakes.
func mayfail() error {
if snafu {
return errors.New("oops")
} else { return nil}
}
err := mayfail()
if err != nil { handle }
Same as `mayfail() ? handle : happypath` would behave with lazy evaluation.Is this how linux manages to avoid needing to "install drivers" in the vast majority of cases? And if there are standard device APIs, why does windows have to go through that whole install driver routine every time I plug something in?
https://en.m.wikipedia.org/wiki/Assignment_(computer_science...
Garret Galvin @fishingarrett has made a name for himself yoinking all sorts of critters in the wild but in particular seems to be targeting invasive pythons in the Everglades. He's very entertaining if you like nature stuff, he's like Steve Irwin's spiritual successor.
The only exception is if the vape juice contains something it "shouldn't", like the vitamin E acetate debacle, but if you put the same wrong things in tobacco, you get the same issue. This problem is avoided entirely with a verified source of ingredients.
Partial combustion products will always contain, at minimum, polycyclic aromatic hydrocarbons, a verified carcinogen. The hotter the conditions, the more complex the precursors, and the more incomplete the reaction is, the more nasty junk you will create. Vaping might or might not be bad, but the chemistries of smoking includes the full set of chemistries of vaping, and then way way more, due to the incomplete combustion of the much larger molecules in plant matter.
Bottom line: probably don't put the volatile reaction products of substances heated above 100°C into your lungs: tobacco smoke, vape, campfire smoke, car exhaust, brake dust, etc. But some reactants are far worse than others.
Also you need perceptual hashing (since one bitflip of the generated media alters the whole hash) which is squishy and not perfectly reliable to begin with.
It's not really feasible to turn ammonium nitrate back to natural gas, moreso GP was insinuating it's a way to export (a proxy for) natural gas, eg to bypass sanctions.
What is the performance hit like? I could see these getting pretty expensive (but correctness is invaluable). Seems like it would be great for something like aws lambda in python where you have already decided performance isn't an utmost priority and scrutability is difficult, so any correctness you can bolt on is a boon.