Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
pcwalton
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
51 ms
·
751.
▲
by
pcwalton
5y ago
Zig is no way closer to Rust than C or C++ in this regard. Zig is in fact not appreciably safer than C or C++. All of the same classes of memory safety problems that are present in C or C++ are present in Zig. I am extremely doubtful of t
752.
▲
by
pcwalton
5y ago
Have you tried cxx? C++ interoperability in Rust has come a long way.
753.
▲
by
pcwalton
5y ago
Do you have examples of this actually causing security problems in Rust code at anywhere near the levels of memory safety problems in C/C++? It strikes me as extremely dubious to tout Zig, which doesn't have memory safety at all,
754.
▲
by
pcwalton
5y ago
Zombo.com stopped Firefox development for a day back in, oh, 2011 or so. Somebody noticed that new tests were failing and the tree ended up being closed for new commits while the problem was investigated. Turns out that a month or so prior
755.
▲
by
pcwalton
5y ago
Why not compile at -O0? That gives you everything that you want today, including no register allocation.
756.
▲
by
pcwalton
5y ago
Bugs based on optimizations that compilers make based on assumptions enabled by undefined behavior (like the null check issue from 2009 in the Linux kernel) actually don't cost very much. They get a disproportionate amount of scrutin
757.
▲
by
pcwalton
5y ago
Then you should logically be OK with deleting the null pointer check, as that check is unreachable.
758.
▲
by
pcwalton
5y ago
I wouldn't say anything with separate register files for addresses and data is "beautiful", but it's certainly miles better than other microprocessors at the same time like the 65816.
759.
▲
by
pcwalton
5y ago
Not at all. We had this article a while back which will hopefully nip this topic in the bud. https://astralcodexten.substack.com/p/ivermectin-much-more-t...
760.
▲
by
pcwalton
5y ago
> Ah, but you might say, if a shared library is compromised, it's easy to push a fix! But how to you think it got so widely compromised in the first place? Perhaps because it was a widely shared library? Sharing is a double-edged sw
761.
▲
by
pcwalton
5y ago
We've had sandboxing for a decade on mainstream operating systems with mainstream browsers. I doubt that just adopting Plan 9 would offer any meaningful security improvements over the status quo. It would just be switching a big pile o
762.
▲
by
pcwalton
5y ago
Zork ZIL was pretty Lispy (example at [1]). Whether it qualifies as "a Lisp" depends on your definition. [1]: https://github.com/MITDDC/zork/tree/master/zork
763.
▲
by
pcwalton
5y ago
Office 97 is probably missing support for modern Unicode (i.e. astral planes). Apparently Office 97 was the first version to support Unicode at all, but I bet it's BMP only. I also highly suspect Office 97 has no support for modern Ope
764.
▲
by
pcwalton
5y ago
> If any, I prefer plan9/9front's drawterm/cpu which runs circles over Unix/Linux VNC and RDP. By a huge mile. How can this [1] code possibly be faster than modern hardware accelerated blitting? I don't see a lin
765.
▲
by
pcwalton
5y ago
Who's going to construct the linked list, and where does it live? That's what the parent comment is pointing out. In the general case I see no alternative to either the compiler generating one alloca() per defer or heap allocating
766.
▲
by
pcwalton
5y ago
The semantics of block-scope defer are much simpler, easier to understand, and faster. The compiler always statically knows which defers execute at any given point, which aids optimization. With function-scope defer, the semantics are ext
767.
▲
by
pcwalton
5y ago
In reality, sqlx [1], probably the most popular SQL library for Rust, has a query! format string that ensures that all parameters are properly escaped. As far as I can tell, you can't use the new format string support to create SQL que
768.
▲
by
pcwalton
5y ago
CEF is a third-party project that isn't officially supported by Google, unlike XULRunner. Which gets back to my point about market share: when you're popular enough, then people will step in to provide embeddability (in this cas
769.
▲
by
pcwalton
5y ago
And Chromium's embeddability is just as bad. Notice you're talking about WebKit, not Chromium. Chromium doesn't even have a XULRunner.
770.
▲
by
pcwalton
5y ago
Correct. And Chromium, as shipped and supported by Google (not third-party projects like CEF), is no better than Firefox at embedding (and certainly wasn't when Chromium was taking off in market share). There is a reason why Chromium-b
771.
▲
by
pcwalton
5y ago
It's never been easier to build a custom branded Chrome than to build a custom branded Firefox. Building a custom branded Firefox is very easy, which is why tons of people have done it. Google achieved market share by taking the embedd
772.
▲
by
pcwalton
5y ago
As an engine, Chromium has overwhelming market share, so it decreases risk to build on top of it. Choosing an alternative browser engine increases risk. Embeddability has little to do with it; Chromium (as opposed to WebKit) isn't actu
773.
▲
by
pcwalton
5y ago
That's essentially 5-bit Baudot code: https://en.wikipedia.org/wiki/Baudot_code
774.
▲
SoK: On the Analysis of Web Browser Security
(arxiv.org)
4 points
by
pcwalton
5y ago
|
0 comments
775.
▲
by
pcwalton
5y ago
Or just straight-up stolen art. For every one artist selling NFTs of their own art, there are easily five NFTs sold by fraudsters misrepresenting themselves to have to right to do so.
776.
▲
by
pcwalton
5y ago
Ironically given the benefits that the cryptocurrency ecosystem supposedly brings to artists, this promotional material contains stolen IP from at least one independent artist [1]. Cryptoland's response was to block the victim [2]. [1]
777.
▲
by
pcwalton
5y ago
Well, lack of skeletal animation is a showstopper. Every 3D game needs that no matter what.
778.
▲
by
pcwalton
5y ago
I'd like to see irregular Z buffers deployed in a modern graphics engine, as they actually provide pixel-perfect shadows without the need for raytracing hardware. They're pretty experimental, though. Maybe I'll take a stab at
779.
▲
by
pcwalton
5y ago
This is antivax misinformation.
780.
▲
by
pcwalton
5y ago
Because the unvaccinated death rate from COVID is 13x higher than the vaccinated death rate in the US. It's simple. Get vaccinated.
More ›