267 karma · joined April 7, 2020
https://michaeldnahas.com
The epsilon terms are used for breaking ties. If you are deciding if a point is to the right or left of a line, you can use the factors on epsilon terms to decide. If the limit of the point for epsilon close to but greater than 0 is right or left, you use that answer.
You can use multiple epsilon terms, one for each dimension and claim that the x-dimension approaches zero faster than the y or z-dimension, etc. It makes it all work as integer linear algebra with simple greater than or less than on scalar result.
We can learn to push through hard times, but not forever. You need connection, exercise, good food, and nature.
After burning out, I relaxed for a while. Then, I focused on things that were under my control and didn’t depend on others. Exercise, losing weight, etc.
The other team brought walkee-talkies! My team won. A devious member waited and then changed clothes into a bright floral full-length dress with a large floppy hat. Disguised as a random park user, she strolled in, grabbed the flag, and strolled out undetected!
Highly recommend.
The govt should only be stepping into the loan market if the market isn’t happening. (Not that the market is doing loans wonderfully, but there are some new innovators.)
The govt should be helping the poor and investing in strategic capabilities. But the whole loan market and helping school rob parents of as much as they can pay? No.
I don’t think open-source project leaders have the resources to fight this risk on their own. We should discuss if there is a role for government, just the way government pays for security (police) and protects critical infrastructure.
I do want to write an article on “technical debt” at some point. “Debt” is not a great metaphor for the concept. Maybe “high viscosity code” might be better? The code cannot be changed easily to accommodate new features, so it feels like it has a high derivative. Debt is something else completely.
Thus, if you want to write a simple website that needs permissions, storage, and server-side code, it's a great backend solution. The limitation is that it isn't high performance.
BUT, if you need a multi-page webapp, SvelteKit is complicated and not well documented.
When I moved to multiple pages, I had to use SvelteKit, which is complicated and not well documented.
It is simple, so its single program is (1) a webserver, (2) runs server-side code, and (3) hosts a DB. I'm running a $12-per-month server on Vultr and its only service is PocketBase.
You don't need to host the webpages on PocketBase. If you wanted all your webpages to be on Github Pages, you could do that.
As someone else mentioned, API rules can control access to rows.
It can send emails. Set timers. And send its own requests to other webservers. (I haven't used any of these features.) https://pocketbase.io/docs/js-sending-emails/
I had to write my own CSV importer. (I'm hoping to open-source it.)
As for internationalization, what specific features did you want? That seems more like a front-end feature.
JavaScript API: https://pocketbase.io/docs/js-database/ Go API: https://pocketbase.io/docs/go-database/
I'm exceptionally happy with it. I'm developing an webapp for a friend's company and wanted a very simple system to hand-off. The whole thing is running with one binary: Pocketbase. It runs a webserver, server-side Javascript (compiled TypeScript) code, and SQLite database. The single process is hosted on Vultr for $12 per month. My frontend is written in SvelteKit (static adapter) + Svelte + TypeScript.
Pocketbase is well done. The author has been exceptionally responsive to my questions. He is fast and clear.
I have had a few minor issues: The documentation has bare spots (but is very good for most things). I had to write my own CSV loader. (I hope to open-source it.) Writing lots of objects through the CRUD interface is slow. (It's possible to write faster using server-side code.) Unit testing for the server-side JavaScript had to be shoehorned in. And I wish Copilot/ChatGPT could answer questions better. But these issues have been minor, given all my work on the project.
It has some quirks. There's no way to set the 404 page on the webserver. And the binary's location in the filesystem matters. It was designed for the author's use and you have to live with these choices.
As I said, I've been happy using it. It fit my needs exactly: simple and I could code everything in one language, TypeScript. Pocketbase is not high-performance, but I didn't need that. I've had a few ideas for side projects and, when I'm done this work, I'll implement one on Pocketbase because it is that easy.
And, as part of my contract, my friend's company will donate to Pocketbase. :)
Incomes of the workers continued to increase, they were just outside the USA. Rich Americans were running a world economy, not just the American economy, so their incomes increased. American workers did well - their incomes remained high while competing with everyone in the globe.
Yes, that’s true. If you read “Enlightenment Now”, there are tons of wonderful graphs showing life improving. And for almost every country, as it gets richer, it gets happier. But the one exception is the USA. We’ve gotten richer lately, but not happier.
Our government’s decision making ability is messed up. We have an excellent economy, but debt is increasing. Our government has income, but we nearly defaulted on our debt. Healthcare has been a problem for 30+ years.
My state of Texas is run by Republican primary voters, which are an extreme 10% of the population.
We need to end gerrymandering with single-party primaries. (I like jungle primaries with ranked choice voting.) We need popular elections for President (not everything riding on swing states). We need to remove the filibuster. We need to weaken the Speaker’s power, which caused omnibus bills rather than real debate.
I’ve seen good activism and change at the city level. YIMBY’s are making progress. They’re now working at the state level. But it is still hard to see us making the necessary fixes at the federal level. I have horrible worries about what will happen if we don’t fix those very soon.
I started in tech, but went back and got an econ degree. A market for insurance works well for unpredictable things, like broken legs. But it doesn’t work well if some can predict their need, like life-long conditions. So, there is a role for non-market solutions. At that point, you need to address how to keep patients from consuming “too much” healthcare, because they’re not paying the full cost.
Many countries spend less and have longer lives. But it is hard to get the US to implement one of those systems when healthcare companies spend more than $1 million per member of Congress on lobbying and campaign donations.
I was so disgusted by the tutorials for Coq that I wrote my own. It has been reviewed positively on Hacker News before. If you want a look at some of the basics of formal proof and these tools, take a look:
That will allow you to verify the pure functions. It will not verify the input/output that will also be necessary.