TheCoreh

If your hobby project consumes libraries which are not already locally available on your machine, this same restriction would also apply when using gcc/make/vim. (e.g. say you want to use zlib, you'll need the zlib-devel package)

If the packages are already available locally, cargo works offline.

We tend to forget, being so used to them, but both C and C++ have playful names (C is a successor to B, and C++ is an incremented version of C)

UNIX also has a playful name (from Multics)

The package manager is an integral part of how the language is intended to be used in everyday practice, so it makes sense that it would be mentioned in the book, though.

It could be argued that it's not a good look for Ubuntu's support of copyleft, but MIT license _is_ free software, as per the FSF definition of free software.

Meta-question: Given how common :: is in programming languages, and how rare of a typo it is, is it really worth it for HN's title filtering logic to include a rule for automatically replacing it with a single :?

They probably meant readings, as the cognate for "lecture" in romance languages generally means both a lecture and a reading

It is extremely hard to make a phone detector that's able to detect only phones in a specific room, considering how far the cellular signals can travel, and how pervasive wifi is for everything

You don't have to search the students. Or even put the phones in a locker. You just make the rules about them known, and if students are found using a phone during class, they can just be punished with detention/suspension.

I don't understand why this is hard to enforce, or requires special laws. We had rules about not using (feature) phones back when I was in middle school (~2002), and you just kept your phone in your backpack/pocket until the class was over. It worked.

Culturally, the first person is not reserved only for human entities, for example the "don't pet me, I'm working" vests on service dogs, or the juvenile prank of writing "wash me" on a dirty car. Beyond these examples there's a very long history of mythological and fictional talking creatures, entities and objects all using the first person.

> I don't care if there's a buried flag that enables or disables this behaviour. I want a binary that doesn't have this capability in it at all.

That's a rather absurd way of approaching the threat model of data exfiltration on a terminal app.

By its very definition a terminal needs the ability to spawn unsandboxed processes and send/receive input from/to them, including processes that have network access. Even if the binary doesn't contain specific logic to do this it could invoke curl, or a variety of other binaries that do, either on purpose or accidentally. In addition, it links against AppKit, which includes NSURLRequest. Is that off-limits too?

If one's this allergic to OpenAI, that even an opt-in feature is a concern, they're better off using a firewall like Little Snitch, or blocking it at the DNS level.

Additionally, if you don't trust the developer with this, why would you trust a binary from them without this feature?

The pixel checkerboard pattern on the page's background paired with smooth scrolling on an LCD display can unfortunately result in some distracting flashing afterimages.

Perhaps the issue could be reduced by using `background-attachment: fixed` and changing the element that has the pattern to be the <body> tag, so that the background is fixed on the browser's viewport?

Not bundled in a distro-specific way, but ollama fairly straightforward to install and use:

https://github.com/ollama/ollama/blob/main/docs/linux.md

If I understand it correctly, this seems to be more than just quantizing, the models are apparently trained in this format as well. So it's possible that the many layers adjust themselves in a way that "cancels out" the inaccuracies of the lower bit count

I believe that they're just waiting for Firefox to ship it, at which point it will be upgraded to Stage 4 and included in ES2024.

The networks trained were really small, with only one hidden layer, and a width of 16.

You can now opt in to the proper interpolation with the `in srgb-linear` option:

linear-gradient(in srgb-linear, ...)

Works in Safari/Chrome but not yet on Firefox

C is a much simpler language, so it's far easier to reason about the semantics of "unsafe" code.

For example: Rust has destructors (Drop trait) that run automatically when a value goes out of scope or is overwritten. If memory for a struct with a Drop trait is manually allocated (and initialized with garbage) and it is assigned to, the `drop()` method will run for the previous value of it which will cause undefined behavior.

That's just one feature: Rust also has references, tagged unions, virtual method calls (&dyn Trait), move semantics, `Pin<T>`, closures, async/await, and many more, all of which make it harder to reason about safety without the guardrails provided by the language for regular, "safe" code—for which barring a compiler bug it is actually _impossible_ to shoot yourself in the foot like this.

This is actually why it's so incredibly hard to write C++ code that is provably correct: It has even more features that could cause problems than Rust, and is _always_ in "unsafe" mode, with no guardrails.

It's like a docker/package manager for the LLMs. You can easily install them, discover new ones, update them via a standardized, simple CLI. It also auto updates effortlessly.

When I saw the name "Toledo" I sorta knew I was in for a treat.

Familia Toledo is somewhat legendary, they are a multigenerational family of coders from Mexico who did an operating system and a browser in the 90s.

My gut feeling with how far they've come in so little time says it's definitely in the double digit percentage points.

I am also looking forward to that, but I think the Serenity philosophy is to not make any long term plans and commitments.

If the language becomes mature enough, and there are people interested enough in doing that porting, it will likely happen.

I think their C++ code is also constrained enough due to the use of their custom standard library that it would be possible to write a transpiler from C++ to Jakt.

When you open sites on other "new" browser engines you typically get a really butchered visual result, with layouts completely broken, elements missing, wrong colors, etc. For example, Servo didn't support floats until recently, and IIRC even simple sites like Hacker News look "wrong".

Ladybird's approach has been to start with a somewhat naive implementation of features, then choose popular websites and apps and just continuously iterate to make them gradually look better, by fixing the parts that stand out. This pragmatic approach means that their supported feature set, while nowhere near 100%, can decently render 90% of websites due to being aligned with the most commonly used features.

Isn't this just `&dyn Trait`?

Would it be a stack allocated, owning version of that, that can be moved? A pure `dyn Trait`?

Thanks for replying with added context, didn't really mean to add more to your plate with this!

At a quick glance, I found several that don't match that criteria you mention, here are a few:

Open Source Doesn't Require Providing Builds

https://codeengineered.com/blog/2024/open-source-not-builds/

Sam Altman Says AI Using Too Much Energy Will Require Breakthrough Energy Source

https://futurism.com/sam-altman-energy-breakthrough

Avoid Async Rust at All Cost

https://blog.hugpoint.tech/avoid_async_rust.html

(Perhaps that last one could be renamed to be less hyperbolic, but the content was still an interesting opinion piece)

I don't think this is being done by the mods, by the way. It's more likely some spam filter with false positives, report brigading, or an anti upvote ring mechanism.

With HiDPI/Retina displays, that 24px is actually 48px or 72px, so the need for pixel hinting is much less commonplace than it was 10 or 15 years ago.

Also, nothing's really stopping most developers from just scaling it naively to those tiny sizes, in fact it's what commonly happens.

I agree we should keep support for custom icons for each size, and it's probably a best practice, but shouldn't be a _requirement_ anymore.

This tool has been incredibly useful to me for getting a high level overview of compiled binaries and JS bundles: you can typically tell if something fishy is getting included by the unexpected changes in entropy/categories. Thanks!

iOS popup menus have actual separators, they are much thicker than those lines around each item. They just haven't shipped hr for select support in Safari for iOS yet (they will in 17.4, you can try it in the beta)

For an example of how they look like in iOS 17.3 or earlier, long press the address bar/tab title in Safari

I wonder why they only sent one? Why couldn't they send 3-5 identical helicopters so they still had a few more to spare?

(The hover weights ~1000kg, the helicopter ~1kg)

iCloud already supports this, and from what I gather it works decently well:

https://developer.apple.com/documentation/uikit/uidocumentst...

https://developer.apple.com/library/archive/technotes/tn2336...

Essentially there's an OS mechanism for getting the different versions of the file, your app can detect conflicts and choose how to resolve them, including by displaying arbitrary UI to the user. IIRC This UI can even be integrated with the file open dialog. As a last resort fallback if the app doesn't resolve it Finder/Files will let you keep either version or both (as separate files)