Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
the_duke
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
70 ms
·
961.
▲
by
the_duke
6y ago
If you want transparent failover you need to use your own domain for the repo URL. In case of a failure you (or some automatic job) would have to change the DNS record. Gitlab has a repo mirroring feature [1]. But of course you'd also
962.
▲
by
the_duke
6y ago
Just hearing Salesforce should make you run as fast as you can , if you value your sanity as a developer. Salesforce is unbeatable in marketing and sales strategy, but the products are horrible.
963.
▲
by
the_duke
6y ago
Can you share a few? YouTube always seems to stick me in a bubble and never recommends any worthwhile new channels.
964.
▲
by
the_duke
6y ago
Many companies invested a lot of time. But from what I have seen, most of that time was spent on the legal and policy site, not on actually implementing the technical changes required to properly handle, store and delete data. I can absolut
965.
▲
by
the_duke
6y ago
> And Zap (scheduler for Zig) is already faster than Tokio. I'm not necessarily doubtful, tokio isn't the fastest implementation of a runtime. But can you point to a non-trivial benchmark that shows this? Performance claims sho
966.
▲
by
the_duke
6y ago
I encourage you to have a look at the operating income that AWS rakes in. Sure, the amount of expertise, redundancy and breadth of service offerings they provide is worth a markup, but they are also significantly more expensive than they ne
967.
▲
by
the_duke
6y ago
I agree that Rust async is currently in a somewhat awkward state. Don't get me wrong, it's usable and many projects use it to great effect. But there are a few important features like async trait methods (blocked by HKT), async c
968.
▲
by
the_duke
6y ago
That's an interesting observation. It definitely has merit. I've run into this exact same thing in type-system heavy languages like Haskell/Scala/Rust, where I spend more time juggling abstractions than implementing feat
969.
▲
by
the_duke
6y ago
The new compiler is very innovative and a distinguishing feature, but I would recommend giving a higher priority to package management. A package manager is more or less expected by developers now, and I bet you will see a lot more adoption
970.
▲
by
the_duke
6y ago
There are so many situations where an error payload is either mandatory for properly handling the error, or required to get somewhat decent error output... Side channels are not really a feasible implementation option. So you have to resort
971.
▲
by
the_duke
6y ago
As mentioned in my other (wall of text) comment, that's not strictly beneficial. It forces you to implement a lot of logic in "userspace" that other languages do for you automatically. Complexity for certain abstractions move
972.
▲
by
the_duke
6y ago
Correct me if I'm wrong, but I don't think D has the ability to just import C headers and seamlessly use them without having generated or manually written `extern` declarations?
973.
▲
by
the_duke
6y ago
What do you find radical about Zig? I like Zig, but can't see anything particularly revolutionary about it's design. The features mostly an evolution of concepts found in languages like D or Nim. Between the two, Rust is much more
974.
▲
by
the_duke
6y ago
Can you mention some concrete criticism? Rust has evolved a lot, even since 1.0, but all changes were well designed and for the better, in my view.
975.
▲
by
the_duke
6y ago
After writing a lot of Rust, I recently did a small project with Zig to learn the language. I'm especially impressed with the C interop. You can just import C headers, and Zig will use clang to analyze the header and make all symbols a
976.
▲
by
the_duke
6y ago
I used to assume that Linux had a huge test suite with hundreds of thousands of tests, given the crazy feature matrix that the kernel has to support. And that they would have started requiring tests for new features and bug fixes. Alas, tha
977.
▲
by
the_duke
6y ago
Humour is rarely appreciated here, but I found this funny and on point. Battery technology announcements are always extremely over hyped. Mostly by media and PR departments rather than actual scientific or domain specific outlets. Advanceme
978.
▲
by
the_duke
6y ago
The list of changes is tiny compared to the 2018 edition. The module system was a big change, and the macro changes caused quite a bit of breakage. Both were important. The changes here are nice to have, especially the partial struct borrow
979.
▲
by
the_duke
6y ago
Well, I can see how someone fixated on a "store" Vs "cache" terminology might arrive at that name. Browsers store, proxies cache , so it should be no-cache, obviously! Sure, it's stupid, but naming is hard and these
980.
▲
by
the_duke
6y ago
Wouldn't many bugs only surface in multi-instruction and status register interactions? But those are also probably way harder to verify.
981.
▲
by
the_duke
6y ago
No, please, no. I understand that it's often easier to express something with a quick voice message, rather than writing it up. But is it searchable? Is it coherent information that I can refer to, copy and paste? Is it efficiently con
982.
▲
by
the_duke
6y ago
Repaired by whom? Many companies make it hard/impossible and expensive to repair things on purpose, because they really, really want you to buy something new every few years. Mitigating this "build to fail" mentality is the v
983.
▲
by
the_duke
6y ago
It has been said again and again, but this is a very common misconception. The memory is a soldered on extra chip. It's not on the SoC.
984.
▲
by
the_duke
6y ago
It wouldn't be that far off if we had the money and motivation. We could probably have a mostly self sustaining colony in caves on Mars within ten years , if we really wanted to. It would just take an absurd amount of money and singula
985.
▲
by
the_duke
6y ago
On one of the unofficial cams (Labpadre) it looked like they deployed but didn't lock in place. But it looks like the engine gave out early. The rocket was way too fast, so the legs probably wouldn't have made much difference.
986.
▲
by
the_duke
6y ago
As usual for Google products, this works fine in Chrome on a decently powerful desktop. Not up to the speed of well-written Javascript, but definitely viable. In contrast, this is completely unusable on other browsers or on lower powered de
987.
▲
by
the_duke
6y ago
You are arguing from the perspective of a single company, while the parent is arguing from an ecosystem perspective. Sure, for a single customer it's good to have a widely used product with a big ops and security response team. But if
988.
▲
by
the_duke
6y ago
The gallery already downloads a wasm file for me. Not sure if it's used. ps: for me the Gallery is extremely laggy in Firefox, but works decently well on Chrome. Maybe wasm is enabled on Chrome only.
989.
▲
by
the_duke
6y ago
Never heard of it, but it does sound like a good read!
990.
▲
by
the_duke
6y ago
Can you share any example of Flutter Web that isn't a extremely basic Todo app, doesn't completely break regular browser UX and works without being slow as molasses? I haven't seen one. I like Flutter, but I don't think
More ›