Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
skohan
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
47 ms
·
571.
▲
by
skohan
5y ago
What's the pain point here? Can't you go HLSL -> SPIR-V -> MSL with SPIR-V Cross?
572.
▲
by
skohan
5y ago
Not yet
573.
▲
by
skohan
5y ago
I think the challenge here is that you need buy-in from industry pros to make this really worth it. The platform can be best-in-class from a hardware/API perspective, but if no tools exist using in it, why am I going to give up my CUD
574.
▲
by
skohan
5y ago
WebGPU is a different animal from Vulkan/Metal. It's more like an updated OpenGL than a true low-level graphics API. It's also pretty far from being ready for prime-time if I understand correctly.
575.
▲
by
skohan
5y ago
I'm using proc macros to generate a parser implementation from a context-free grammar, I find it pretty neat.
576.
▲
by
skohan
5y ago
Disney creates works billions of people want to see, and they have governments around the world enforce the ownership rights. Nobody wants the piece of art associated with your NFT’s. And is there even any legally framework for the ownersh
577.
▲
by
skohan
5y ago
Oh my friend just started working at Ableton! Anything you wish you had from their products?
578.
▲
by
skohan
5y ago
Wouldn't the other poster's point be that these are not "real numbers" relative go Google's revenue? Fines actually have to affect the bottom line to act as an incentive to change.
579.
▲
by
skohan
5y ago
Well Firefox is largely the default on Linux, so it wouldn't represent a proactive choice. And linux users are probably more likely to fall into the category of sophisticated user than the general population. I don't see any evide
580.
▲
by
skohan
5y ago
It's perfectly reasonable to be skeptical of the measures being put in place which would make this possible, especially given MS's history. To give an analogy, there might have been a time in East Berlin where people could have sa
581.
▲
by
skohan
5y ago
Yeah I totally agree. I think there are some small companies which intentionally set themselves up to forward a particular cause, like sustainability for example. Also privately held companies don't have the same accountability struc
582.
▲
by
skohan
5y ago
How does that graph disprove my supposition? I would assume Firefox's share is almost completely Linux users and people on the more sophisticated end who choose Firefox explicitly. The pattern you see there would still hold in the sce
583.
▲
by
skohan
5y ago
It also doesn't mean that the work they're doing with VSCode is "virtuous". It's generally foolish to expect multinational corporations to act as if they are motivated by virtue - the incentive structure is just not
584.
▲
by
skohan
5y ago
That's exactly the cost-benefit equation which anti-trust regulation is supposed to correct. That's why it's a shame it's not currently working.
585.
▲
by
skohan
5y ago
The main difference is that Microsoft literally had a massive anti-trust action taken against them in 2001 on exactly this issue . I agree that Apple and Google are also guilty here, but MS is repeating actions which there is not only a di
586.
▲
by
skohan
5y ago
Which software would you need to work to make the switch? So much of what I use is web-based nowadays, it's only really dev tools and games which I care about running natively. The former is best-in-class on Linux, and the latter is
587.
▲
by
skohan
5y ago
> How much money do they lose because of the reputation damage and increased regulator attention because of it? Unfortunately I doubt they lose very much at all based on a move like this. To sophisticated users this is a huge red-flag,
588.
▲
by
skohan
5y ago
Well obviously they lose telemetry when you leave the ms ecosystem, so the user journey has effectively ended at that point /s > things like password autofill in a lot of the MS auth flows (which appear to be web-based, as far as I
589.
▲
by
skohan
5y ago
This in particular seems to blatantly fly in the face of the precedent which was established by the earlier anti-trust judgements against them. It almost seems as if they believe anti-trust has been effectively killed between then and now,
590.
▲
by
skohan
5y ago
What are the innovations allowing for these large leaps? It seems like forever that progress was extremely slow.
591.
▲
by
skohan
5y ago
The problem with ARC in swift is that it’s always atomic. This is fast enough on ARM, but on x86 it’s really slow
592.
▲
by
skohan
5y ago
Are you kidding? You don't think this kind of behavior disincentivizes innovation? And it's not exactly new. Common carrier regulations have been a thing forever.
593.
▲
by
skohan
5y ago
Yeah I have done some work trying to optimize code written in GC'd runtimes, and eventually you will hit a wall. GC is great for a lot of use-cases: for instance if I am writing a server-less application with mostly lambdas/clou
594.
▲
by
skohan
5y ago
Zig's approach is really nice here, but it's also a notably easier problem to solve than rust has, since it's not trying to solve for parallel/concurrent safety. Do you think Zig's approach would be feasible in Rust
595.
▲
by
skohan
5y ago
Yeah maybe not like go, but it's not impossible to imagine that you could create a language from the ground up with a rust-like ownership model and some async model - maybe not async await precisely.
596.
▲
by
skohan
5y ago
I don't disagree. After working with Rust's model, which forces you to confront a lot of the tradeoffs and complexity, I'm more inclined to think async is a feature which should really be considered from the ground up when a
597.
▲
by
skohan
5y ago
I think it's not entirely fair to paint problems with rust's async features as an aversion to low-level-ness. If anything, I think the issue with Rust's async is that it tries to be too high level . In my experience with asy
598.
▲
by
skohan
5y ago
Swift doesn't have tracing gc but ref counting is a form of gc
599.
▲
by
skohan
5y ago
Swift doesn't have tracing GC, but to be pedantic automatic reference counting is a form of GC. But that only goes for reference types. For value types you're correct that both languages use mostly static memory management. I gue
600.
▲
by
skohan
5y ago
Yeah I agree, I think one of the biggest mistakes in Swift was coupling reference types to classes. Choosing whether something is a reference type of value type should have been orthogonal to the class system, if they included classes at a
More ›