Build something better, undercut his price, then we can talk.
482 karma · joined October 2, 2012
Working on boomla.com, a no-code-first web application platform.
Build something better, undercut his price, then we can talk.
- Allow everyone to have close range kill switches, which use a universal open standard protocol that works on every robot (alas pepper spray for robots).
Write speed wasn't my primary motivation though. I wanted a data storage solution that is hard to fuck up. Hard to beat append only in this regard. Plus everything is stored in merkle trees like in Git, so there is the added benefit of data integrity checks. Yes, bit rot is real, and I love to have a mechanism in place to detect and fix those.
I mean, what's the trick NVMe can do to be meaningfully faster?
I mean, using a merkle tree or something like that to make sense of the underlying data.
Also, as a result, need more scrolling.
Consider some parametrization, like swapping dehyped title (better than orig!), and showing/collapsing summary and comments by default. Ideally via url params for bookmark persistence.
> We need more imagination and more bold deviations from the norm
This is what I reacted on, a bit too compactly - apologies. Let me unzip.
My problem is that this statement 1) feels so far removed from reality, 2) I'm so much interested in this space that this hurts.
Why would you recommend others to throw out the good ideas of decades of research just to be hip? Evolution doesn't work that way. Humans didn't evolve by throwing away state-of-the-art apes. Evolution happens by changing one or few bits at a time and iterating while selecting for the good. This means there will be many programming languages that look just like those before them - at least to the untrained eyes.
Mutable value semantics is one of the most fascinating ideas in programming. It's like the good parts of functional programming without the bad parts. I'm pretty certain it will revolutionize programming. To dismiss it as being close to existing languages blows my mind.
I get that it's hard for any language to take hold without being 10x better. At the same time, it feels naive to build a 10x better language without keeping the good parts of existing languages. Not removing good ideas is as important as adding good ideas.
Also, humans are 'stateful', switching costs are real. 10x better not only includes the upsides but also the downsides. Hence, it feels like a sane strategy to not only maximize the upsides of new ideas, but at the same time minimize the downsides of not only removed good ideas but also changes in general, to minimize switching costs.
I expected npm packages to somehow carry the social engineering, like carry a message somehow, but that’s not the case.
I understand this is the second approach.
That said, I was wondering about a similar thing: what if I modify a 1GB string? Is it copy-on-write?
I feel like it can be optimized away 99% of the time only to leave you with 1% of cases that result in very-hard-to-find performance degradations.
I’m so tired of this advice. Maybe metrics are bad, but the only thing worse than metrics is no metrics.
Discouraging an action just because it doesn’t work 100% of the time doesn’t seem efficient either.
The argument really should be that certain metrics are bad. Sure, propose a better one, but saying that leaders don’t think hard enough just because a metric turns out to have ill effects seems useless advice. How can you be certain in advance when you have thought hard enough?
A better approach is probably to recognize that metrics are hard. Keep an eye on them, iterate, and be willing to make mistakes as that’s the only way to improve.
I'm currently in a position where the core tech is way ahead of every other aspect of the business.
Com could be free as well. The only real difference is choice.
Or to put it differently, you say it doesnt need registration. Well, it does. They require it. So what.
I think healthy eating habits would be the last thing that came to my friends minds when describing me.
I totally agree I'm only a sample of one that I know of, but the fact that this doctor relative of ours told my parents the cause-and-effect relationship beforehand, and it worked out, makes me believe the theory. Either way, I keep recommending it to my friends getting babies, so I'll be able to collect more data in the next 50 years. ;)
The thing is, that's the kind of gamble that costs nothing and might have immense upside, so it would be kinda silly not to apply it. My 2c.
I don’t know if that’s a scientifically proven thing, but indeed i simply can not gain weight, whatever i eat. As if i had zero fat cells.
The only downside is that I’m often cold, which is of course far easier to manage. I’m not a water person though, as its nontrivial to “dress up” for swimming.
It’s a miracle, please spread it. The next generation could avoid the fatness problem alltogether.
Probably accurate. So that’s what you need to figure out then. It’s great you are aware of it, now make it the nr.1 most important thing in your life.
Put it under a URL only you know, then start DoS-ing it.
Of course that requires you to be able to serve a prepared gzipped resonse, depends on your stack.
We were never accused of cheating, it was a tiny group though (20).
Edit: By identical, I do mean _literally_ the same mistakes, same points. Not 99% similar. 100%.
I desperately needed a _language_ instead of a framework back when Tailwind was still a framework. As I could not get any response from them, I ended up rolling my own called Turbo CSS - this was like 2 years before their compiled version came out. Take a look if you want to consider alternatives.
https://developer.boomla.com/turbo-css
I'd compare the two as Tailwind being primarily a framework, a language second, while Turbo is a language first. For example, in Turbo you write libraries and reference class names in libraries via `my.btn` instead of polluting the global namespace. It also has first class support for classes, like you can do `hover:my.btn`, which Tailwind doesn't support (to my best of knowledge, it definitely didn't back then). Also, Turbo has zero global side-effects, which makes it great if you don't control the entire codebase (think CSS reset).
Authorative A records:
# help.leavemealone.app
help.leavemealone.app. 60 IN CNAME help.leavemealone.com.
# help.leavemealone.com
help.leavemealone.com. 30 IN CNAME leavemealone.helpkit.so.
# leavemealone.helpkit.so
leavemealone.helpkit.so. 1799 IN CNAME helpkit-ssr.onrender.com.
# helpkit-ssr.onrender.com
helpkit-ssr.onrender.com. 300 IN CNAME helpkit-ssr.onrender.com.cdn.cloudflare.net.
# Authorative A records for helpkit-ssr.onrender.com.cdn.cloudflare.net:
helpkit-ssr.onrender.com.cdn.cloudflare.net. 300 IN A 216.24.57.3 helpkit-ssr.onrender.com.cdn.cloudflare.net. 300 IN A 216.24.57.253
--
Indeed opening the page loads 216.24.57.3 where I get a HTTPS response with statusCode 302 that redirects to -> https://dinkydani.gitbook.io/leave-me-alone-help/
Seems to be what should happen?
ps - I'm stunned though to see 4 CNAMEs, especially with 60 and 30s TTLs