naasking

40 ms·

781.
by naasking 1y ago
I'm not sure what you're trying to argue. SSR sites and apps still have scripting and client-side interactivity, the only difference is where the rendering is happening. That's what SSR stands for. SSR switches from APIs exch
782.
by naasking 1y ago
That's not a use case, that's an implementation. What is the end user actually getting with this architecture that can't be obtained by the server-side one? Offline functionality is the only differentiating feature.
783.
by naasking 1y ago
The only thing that would be comparable might be something like RazorSlices.
784.
by naasking 1y ago
Some dangers with injection attacks if you don't santitize inputs correctly, but this is probably faster than most templating languages like razor.
785.
by naasking 1y ago
The only real use case for an SPA is something that has to continue to work offline. There are legitimate cases like this, but most apps developed as SPAs aren't it. > No SSR framework figured out how to do this because they thought
786.
by naasking 1y ago
Unless the problem is "quantum mechanics", then that reduces to non-Markovian processes with unistochastic laws, and ironically, this makes for a causally local QM: https://arxiv.org/abs/2402.16935v1
787.
by naasking 1y ago
> Once you start publishing regularly in ML conferences, you understand that there is no traditional form of peer review anymore in this domain. Which is fine, because peer review is not a good proxy for quality or validity.
788.
by naasking 1y ago
> From experience, in simple terms, a word: Have the work for and the funding from the US DOD, department of defense, military, for some work they really care about. Arguably, national defense research is and should be a core funding tar
789.
by naasking 1y ago
These analyses are highly questionable. NASA has a long reputation of being highly inefficient for good reasons. SpaceX did a much better job at optimizing cost in a way that NASA never could have, so it raises the obvious point: how much b
790.
by naasking 1y ago
> https://github.com/koka-lang/libhandle Dropped the r somehow: https://github.com/koka-lang/libhandler > Sure, if everything has to be able to "wait" for the result of a continuat
791.
by naasking 1y ago
> They are akin to making everything async, which proves my point: you have to make everything of one kind in order to solve the problem. You can use ordinary direct style compilation, but all references to stack values simply have to be
792.
by naasking 1y ago
Not fully replaced, but some percentage should be reserved for sortition. This can increase efficiency and break deadlocks, like two party rule.
793.
by naasking 1y ago
> In which case SQLite is probably the wrong tool for the job Why? If all it's missing is an async connection pool to make it a good tool for more jobs, what's the problem with just creating one?
794.
by naasking 1y ago
Infinities are typically indications of where a theory breaks down, not of something real.
795.
by naasking 1y ago
> Because async/await are not values They are computations that produce values. Computations can be reified as values. What do you think functions and threads are? As I described above, "delimited continuations" are values
796.
by naasking 1y ago
I'm not even sure what it would mean for two black holes to be too big to collide, or where that became some kind of constraint.
797.
by naasking 1y ago
Another poster up thread identified the exact problem: async/await contexts are not first-class values, they are second class citizens. If they were values then you could just stick the context in a struct/class and pass that arou
798.
by naasking 1y ago
If you've added guards and diagnostics, then you close it until someone else files a follow-up, then it can be re-opened. There's no sense keeping it open unless there are ongoing reports of the issue.
799.
by naasking 1y ago
I appreciate the desire for consistency and being able to lean on old textbooks and documentation. A couple of considerations since this is a new language where history and precedent should (I think) be less important if it leads to clarity
800.
by naasking 1y ago
// Computes the delivery date for each component. let r = query p select (c, d) from ReadyDate(c; d) facepalm . Select should always come last, not first, haven't we learned anything from the problems of SQL? L
801.
by naasking 1y ago
That's not the only prudent behaviour, as the OP said, the prudent behaviour is to add more diagnostics and guards against the conditions that lead up to the bug.
802.
by naasking 1y ago
While I haven't looked too deeply, I think HN might be an example that follows REST. At least I don't see anything in the functionality that wouldn't be easily fulfilled by following REST with no change in the outwards behavi
803.
by naasking 1y ago
Fielding's thesis barely mentions HTML (20 times), and usually in the context of discussing standards or why JS beat Java applets, but he discusses hypermedia quite a bit (over 70 times). If you extended JSON so that URLs (or URIs) wer
804.
by naasking 1y ago
> Yikes. Nobody wants to implement a browser to create a UI for ordering meals from a restaurant. You don't need a full web browser. Fielding published his thesis in 2000, browsers were almost trivial then, and the needs for program
805.
by naasking 1y ago
> but the client code (JavaScript/HTML/CSS) is not generic The HTML/hypermedia returned is never generic, that's why HATEOAS works at all and is so flexible. The "client" JS code is provided by the server,
806.
by naasking 1y ago
> There are many ideas in the REST paper that are super useful, but the goal of making a generic client working with any API is difficult if not impossible to achieve. It's definitely possible to achieve: anywhere that data is missi
807.
by naasking 1y ago
The problems do exist, and they're everywhere. People just invented all sorts of hacks and workarounds for these issues instead of thinking more carefully about them. See my posts in this thread for some examples: https://ne
808.
by naasking 1y ago
> For things like debugger, REPL, or some database inspection/manipulation tool, this approach is useful, but for most apps exposed to end users Yes, exactly, but the point is that something like Swagger becomes completely trivial,
809.
by naasking 1y ago
And that's fine, but then you're doing RPC instead of REST and we should all be clear and honest about that.
810.
by naasking 1y ago
> To make truly discoverable API you need to specify protocol for endpoints discovery, operations descriptions, help messages etc. Then you need clients that understand your specification, so it is not really a generic client. Generic cl

More ›