jayd16

32 ms·

841.
by jayd16 1y ago
But again, that's conflating web connected or even web required with mainframe compute and it's just not the same. PC was never 'no web'. No one actually 'counted every screw in their garage' as the PC killer
842.
by jayd16 1y ago
I don't know, I think you're conflating content streaming with central compute. Also, is percentage of screentime the relevant metric? We moved TV consumption to the PC, does that take away from PCs? Many apps moved to the web bu
843.
by jayd16 1y ago
Don't be evil but also morality is relative.
844.
by jayd16 1y ago
Yeah but to be fair, that can have adverse effects if you, say, busy wait. The sync code might be running in an async context. Your async context might only have one thread. The task you're waiting for can never start because the thr
845.
by jayd16 1y ago
The moving faster is how it would work in a good economy with investment dollars. We're in a cycle where we need excuses to lay people off so that's AIs main use case.
846.
by jayd16 1y ago
More like "I need to fire everyone, how can I spin this?" Don't forget the implicit admission that "my product can be made in claude code."
847.
by jayd16 1y ago
That's fine but the alternatives are insufficient.
848.
by jayd16 1y ago
Knowing when execution will yield is useful when you want to hold onto a thread. If you run your GUI related async tasks on the GUI thread you don't have to worry about locks or multi threaded data structures. Only a single GUI opera
849.
by jayd16 1y ago
I think this analogy is too extreme. That said, modern languages should probably consider the main function/threading context default to async. Calling sync code from async is fine in and of itself, but once you're in a problem s
850.
by jayd16 1y ago
You mean like with web workers or something?
851.
by jayd16 1y ago
Const is similar, now that you mention it.
852.
by jayd16 1y ago
I don't really know Zig. How does it handle the common GUI thread pattern where you get lock free concurrency by funneling the async GUI code through the GUI thread? When you know what functions and blocks are synchronous, you know th
853.
by jayd16 1y ago
I really wish people would get over the coloring meme. Knowing if a function will yield the thread is actually extremely relevant knowledge you want available.
854.
by jayd16 1y ago
You've never experienced someone who isn't a good listener? It's fairly common and not always intentional. For example, Kids are great at rambling off information for attention. Active listening is a skill and isn't th
855.
by jayd16 1y ago
Seeing as their approach to it is "good vs bad" and not "fact vs fiction" I think we can draw some conclusions.
856.
by jayd16 1y ago
> collected and curated by LLMs. Wah? LLMs don't collect things. I mean, if any of these AI companies want to open up all their training data as a searchable archive, I'd be all for it.
857.
by jayd16 1y ago
It's not controlled by a trusted actor so it doesn't matter how it happens to act at the moment. They could pull the rug at any future time and its almost better to gain trust now and cash in that trust later.
858.
by jayd16 1y ago
I mean... do they? TSMC is the best but in a world where they had to use Samsung or Intel is it really a death sentence?
859.
by jayd16 1y ago
I wonder if dumping the fuel ASAP is a good idea or bad idea.
860.
by jayd16 1y ago
As Carmack points out, naming the intermediate values aides in debugging. It also helps you write code as you can give a name to every mutation. But also keep in mind that correct and incorrect is not binary. You might want to pass a fooA
861.
by jayd16 1y ago
Intel has the Optane drives but I think anyone in need just pays for the ram.
862.
by jayd16 1y ago
A common naming is value. You can call them immutable values and mutable variables. Another way to look at it is a variables are separate from compile time constants whether you mutate them or not.
863.
by jayd16 1y ago
If you need new values you just make new things. If you want to do an operation on fooA, you don't mutate fooA. You call fooB = MyFunc(fooA) and use fooB. The nice thing here is you can pass around pointers to fooA and never worry tha
864.
by jayd16 1y ago
Yeah, love it or hate it, I do think they thread the needle between genuine excitement and overhyping. The titles and thumbnails are getting clickbaity though.
865.
by jayd16 1y ago
This seems to be the relevant Two Minute Papers with a very quick explainer. https://m.youtube.com/watch?v=VOORiyip4_c
866.
by jayd16 1y ago
I think you're misunderstanding my conjecture. My point is that there is no technical reason these features can't live on the web. I'm not talking about the incidental or intentional decision by some company to force user b
867.
by jayd16 1y ago
Maybe its the insane wealth gap that's the problem...
868.
by jayd16 1y ago
You're saying we can make good toothpaste but we can't make good mouthwash?
869.
by jayd16 1y ago
Even with flouride mouthwash? You're saying the paste/gel is physically more capable of depositing flouride or something?
870.
by jayd16 1y ago
All functionality found on the web.

More ›