hucker

Have you tried aider, and if so, how is it lacking compared to Claude Code in your opinion?

You're in luck, this seems to _only_ support WASM in the browser for the time being.

> Graphite's code architecture is structured to deliver native performance for your graphically intensive workloads on desktop platforms and very low overhead on the web thanks to WebAssembly and WebGPU

Agreed, my company tried buck2 first when evaluating a cargo replacement, but bazel is just so much more mature at this point that it ended up being the natural choice. Thanks for your examples, they helped us get started :)

This is not.. really the right takeaway from his work. That not every true statement within a system is provable from its axioms, or that the consistency of a system is not provable within that system, does not mean that axioms are not useful. Indeed, what math is not grounded in the end by axioms?

> I have been thinking about turning it into a literate code document.

Please do! This looks like the perfect size and complexity to learn the basics, I'd love a structured walk-through of the code.

For some more leftfield genres Bandcamp is the only game in town

The last three are taken from the OPs Zig example, and is not valid Rust at all.

This is not some "glossing over some details for a lay audience" situation. It is not a lack of depth. It makes ridiculous claims, fundamentally misrepresenting what this research is, to make it sound cooler and more interesting. This is one of the worst pieces of science journalism I've ever seen.

Not to be that guy, but this is probably the biggest and most well known of all crypto trading firms, and the source of SBFs fortune initially.

You typically wouldn't use an array with a million objects in Java if you cared about performance though (for exactly that reason), you'd architect it some other way. Using SoA style when appropriate, for example.

Thanks for the love! Please let me know if there are any features that you feel are missing.

This is a really good idea! I assume support for more languages / package managers is coming?

This is a pretty misleading title. The article is a GSoC-report about adding BTRFS-support to ReactOS.

https://web.archive.org/web/20180814113709/www.ingegneri.inf... An old mirror on the waybackmachine

This was changed to a 15/15 week split this summer I believe (with the remainder still split as the couple sees fit).

There has been big debates about this in Norway for as long as I can remember. One of the arguments for the "father's quota" is that when fathers were not "forced" to take at least some parental leave, there was an implied policy many places that as a father you left all the parental leave for the mother, with all the inequality that follows. Personally I am very pro the father's quota, as no employer can now (implicitly) force me to not take it.

That is basically the case in Norway. Both the mother and the father gets 15 weeks mandatory each, and the rest (of a full year) is divided between them as they themselves see fit, iirc.

Good point, that's true. But yes you could, using row-level security. See https://www.postgresql.org/docs/current/static/ddl-rowsecuri... and https://postgrest.org/en/v4.4/auth.html#users-and-groups

There's nothing in PostgREST that stops you from limiting control so that even anonymous users can use it safely. I've used PostgREST for user-facing APIs with success, but it requires some knowledge about the postgres access control model.

EDIT: And "Just point Postgrest at your PostreSQL database" is rarely a good idea in my experience, I usually have (versioned) API-schemas containing views, so that I can change my underlying data schema at will without borking the API.

Take a look at racket (https://racket-lang.org/), works on windows and is the most beginner-friendly lisp I know.

Shameless self-promotion incoming, but if you're mostly using postgres (like me), you can take a look at https://github.com/martingms/vipsql as well.

Are there any bootable releases anywhere?

They presented this at FOSDEM today, and ran the entire presentation (and a demo afterwards) on the actual hardware. They used PCI via an FPGA to interface with a standard ATI gfx card iirc. I don't know if the video is out yet, but have a look!

We use a separate schema for the API (that way we can easily version our APIs as well). The API schemas only contain views/function that expose the tables/fields/etc that we want to expose.

Yes, with good results. Anything specific you're curious about?

I'm glad you like it! It's pretty rough around the edges yet, but it solves the same problem for me (iterating on complex queries). Let me know if there's anything you're missing!