Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
mrich
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
13 ms
·
91.
▲
by
mrich
5y ago
I think the original point still stands. When the application tries to handle memory pressure itself by writing data structures to disk, it will hit the case where the kernel has already paged that memory out, has to reload it, only to writ
92.
▲
by
mrich
5y ago
It's not malloc() but mmap() if I understand correctly. It's a beautifully powerful function :) https://man7.org/linux/man-pages/man2/mmap.2.html
93.
▲
by
mrich
5y ago
Hetzner is missing!
94.
▲
by
mrich
5y ago
Also use https://pagespeed.web.dev/
95.
▲
by
mrich
5y ago
I think you are exactly right and it's sad that you are getting downvoted for this. The "bright" side for coders unwilling to learn new things is that there is lots of legacy C code to maintain to last a lifetime. It's s
96.
▲
by
mrich
5y ago
> comparing c interchangeably with c++ For the sake of the arguments made with regards to using Rust instead, they are exactly the same and comparable - both do not have memory safety, suffer from races and lots of undefined behavior. Th
97.
▲
by
mrich
5y ago
You know, seeing one of the few existing Rust CVEs, which is a freak case, hard to exploit - makes me directly want to go back to the language family with the majority of the CVEs assigned. The existence of CVE itself arguably is a result o
98.
▲
by
mrich
5y ago
If we are starting to get snarky: There are two kinds of people who choose Rust over C++. Beginners who think C++ is too hard, and seasoned developers with years of experience working in large teams who _know_ C++ is too hard to get right.
99.
▲
by
mrich
5y ago
It's not hard to build a library in Rust that can be consumed the same way a C library can. Orders of magnitudes easier than getting your C/C++ program safe. https://docs.rust-embedded.org/book/interoperabilit
100.
▲
by
mrich
5y ago
C is a subset of C++. The key point is that both languages suffer from the same problems, e.g. memory safety issues, undefined behavior, data races. The software industry has been dealing with the fallout of these issues for the past three
101.
▲
by
mrich
5y ago
I will probably get downvoted for this, but I feel writing any new libraries in C/C++ is a bit of a waste when Rust is now available. Especially for file format parsing which is prone to overflows and the like. Yes there are safe codin
102.
▲
by
mrich
5y ago
I wish ZFS had a defrag option. On a server I run that would allow me to move all the used blocks to the beginning of storage and use the rest for hypervisor level snapshots. But I'll still take ZFS over any other file system :)
103.
▲
by
mrich
5y ago
For most file systems performance suffers at latest at the 90% full mark, if not before.
104.
▲
Tesla Model 3: Paris' largest taxi firm suspends cars after fatal crash
(bbc.com)
2 points
by
mrich
5y ago
|
0 comments
105.
▲
by
mrich
5y ago
Are they using split dwarf? This avoids linking the debug info.
106.
▲
by
mrich
5y ago
Great, thank you!
107.
▲
by
mrich
5y ago
Are there any good browser extensions for dealing with these banners? (auto clicking or blocking?) On a side note, recently I built a website and did not need cookies at all (even though you can buy stuff, but there's not shopping cart
108.
▲
by
mrich
5y ago
Well done, for finding the problem with analysis tools and especially lots of experience and even fixing it without source code. It's puzzling why the studio couldn't do this. The problem itself is easy to spot by a performance en
109.
▲
by
mrich
5y ago
Dumb question, for a given model, how many cars are destroyed in such tests? Are they bought on the market or just gifted by the manufacturer?
110.
▲
by
mrich
5y ago
Modern C++ is nice to use, but there's no way I would use it for a greenfield project. Rust simply gets so many things right and saves you the CPU years you have to spend on ASan/MSan/TSan/UBSan/valgrind and fuzzing
111.
▲
by
mrich
5y ago
This really tarnishes any trust you might have had in Amazon as a professionally run business. (of course outages can happen and are to be expected especially at Amazon's scale, it's just the bad communication and the amateurish n
112.
▲
by
mrich
5y ago
It's a pity WASM and all the tech around it wasn't available 20 years ago when Javascript was added to the browser, we'd all be using python now and node.js wouldn't exist at all ;)
113.
▲
by
mrich
5y ago
Rust and Python, in that order.
114.
▲
by
mrich
5y ago
Thanks. I had a use case in mind where LTO is enabled. Unfortunately the LTO step is quite expensive so relinking does not seem like a viable option. If I find some time I'll give it a try though.
115.
▲
by
mrich
5y ago
I'm guessing this does not yield that high compression for release builds, where code can be optimized across translation units? Likewise when a commit changes a header that is included in many cpps?
116.
▲
by
mrich
5y ago
On the server it was the predecessor to Node.js, back when the alternative was a C program :)
117.
▲
by
mrich
5y ago
Worse still, they would have to read Perl code :)
118.
▲
by
mrich
5y ago
Can they even make use of such a large number? Is this a Tesla options play on their part?
119.
▲
Tesla is now worth $1T
(finance.yahoo.com)
14 points
by
mrich
5y ago
|
0 comments
120.
▲
by
mrich
5y ago
Facebook to WhatsApp team in the acquisition negotiations: "If you don't sell to us, we'll build our own and offer it for free" And they would have been out of business sooner or later. There are enough people wanting to
More ›