matharmin

6 ms·

31.
by matharmin 1y ago
That is completely wrong for this stage of a company. The ability to make profit in the future is important. Making profit while growing is not.
32.
by matharmin 1y ago
Let's say I have an open-source project licensed under Apache 2. The grant allows me to include the extension in my project. But it doesn't allow me to relicense it under Apache 2 or any other compatible license. So if I include i
33.
by matharmin 1y ago
It would help to have more info on what you need to run this. The page mentions "without the need for any new hardware", but doesn't say what existing types of hardware it is compatible with. The apps available for download g
34.
by matharmin 1y ago
> Overall, I haven’t seen many issues with the drives, and when I did, it was a Linux kernel issue. Reading the linked post, it's not a Linux kernel issue. Rather, the Linux kernel was forced to disable queued TRIM and maybe even NC
35.
by matharmin 1y ago
There may be good reasons to do that, but this isn't one. Any project using CocoaPods will still remain working for the foreseeable future - you'll just not get new updates to dependencies at some point. And at that point you can
36.
by matharmin 1y ago
You'll still be able to use those - the CocoaPods repo will not go away any time soon. If someone wants to provide updates for those, it has to be migrated to SwiftPM. And in the meantime you may have to use both SwiftPM and CocoaPods,
37.
CocoaPods trunk read-only plan(blog.cocoapods.org)
248 points by matharmin 1y ago|113 comments
38.
by matharmin 1y ago
wa-sqlite on top of OPFS is actually pretty great these days. Performance is about half of what I'd get in native SQLite, which is not too bad overall. It's around 10x faster than SQLite on top of IndexedDB for large databases in
39.
by matharmin 1y ago
Luckily there are still other options out there. ZeroSSL is one I quite like: Free ACME-based certificates just like LetsEncrypt, without the rate limits, and does have paid plans if you need support. It also has better legacy client compat
40.
by matharmin 1y ago
Certificates have a static expiry date by design - it's not "LetsEncrypt expiring the cert". There is no way to avoid expiring a cert if the DNS entry is still there - all you can do is make it easier to renew the cert. That
41.
by matharmin 1y ago
Destructors I other languages are typically used for when the object is garbage collected. That has a whole bunch of associated issues, which is why the pattern is often avoided these days. The dispose methods on the other hand are called w
42.
by matharmin 2y ago
In my opinion neither hooks nor CI should ever make changes to code automatically. When I commit changes, I want to see exactly what I commit, and not have some system change it at the last minute. Instead, have tooling to do that before co
43.
by matharmin 2y ago
This doesn't work if you have branch protection rules blocking pushes to main, which in my opinion should be standard on any repo
44.
by matharmin 2y ago
I view JQuery as similar to C in some ways: It's been around forever, it's mature, and it works. It gives a good experience to get something up and running quickly: it's lightweight and simple. But if you're working on b
45.
by matharmin 2y ago
I think I'm missing something here - what is specific about Docker in the exploit? Nowhere is it mentioned what the actual exploit was, and whether for example a non-containerized postgres would have avoided it. Should the recommendati
46.
by matharmin 2y ago
With your own native client: Yes, you can send arbitrary headers in the Upgrade request. In a browser however, you can't. It typically sets very little headers itself, and doesn't allow you to add custom headers.
47.
by matharmin 2y ago
It feels a little misleading to say you're using Google Sheets as the backend database, when you need an actual database in conjunction with it.
48.
Zero (sync engine) is in public alpha(zero.rocicorp.dev)
4 points by matharmin 2y ago|0 comments
49.
by matharmin 2y ago
In my experience, the "outbox" approach means a lot more manual work for developers. It requires developers to create a message for every type of change they want to sync to the client, and then also interpret that on the client.
50.
by matharmin 2y ago
They did not say it was dementia, and they did not offer care suggestions - they merely shared their own related experience.
51.
by matharmin 2y ago
Unlike other opinions here I do think it is technically feasible to stream a copy of the WAL - it just has to be implemented in the VFS. "Shared memory" could be a SharedArrayBuffer, or just a normal buffer if you only have one da
52.
by matharmin 2y ago
Just wondering, do you have a specific use case for read transactions implemented on the database level here? In SQLite in general read transactions are useful since you can access the same database from multiple processes at a time. Here,
53.
by matharmin 2y ago
I can't tell whether you're trolling or serious... It's not about moderators being harmed or not. It's a preference of the wider community to not have the harmful content, and the moderators volunteering to help keep it
54.
by matharmin 2y ago
By your argument, moderators on HN/Reddit shouldn't remove harmful content, since moderators would still have seen it either way.
55.
by matharmin 2y ago
There is a proposal for that: https://github.com/tc39/proposal-type-annotations
56.
by matharmin 2y ago
It sounds like a niche use case where SQLite does work quite well server-side without needing any replication, since the database is read-only. Other alternatives may use static files loaded in-memory, but I'm guessing the data is more
57.
by matharmin 2y ago
As a novice with Rust maintaining a cross-platform library written in Rust, I've found panics/unwinding is one of the most annoying things to figure out in the builds for various platforms. I'm using nostd and panic=abort to
58.
by matharmin 2y ago
If it's pulsing, get it checked out. Pulsatile tinnitus is often a symptom of a bigger underlying issue.
59.
by matharmin 2y ago
It's right at the start of the post - the git remote including credentials was exposed via the .git directory
60.
by matharmin 2y ago
Thanks, that gives a good overview

More ›