julenx
Every society (another name given to txokos) has its own rules which are agreed upon by their members. There might be a vanishingly small number of societies where women are still not allowed to cook, but this an extremely rare exception rather than a widespread fact.
> sang a traditional Basque song called Hegoak (The Wings)
Note the name of the poem and later popular song is "Txoria txori"[1] (the bird is bird), which was written by Joxan Artze. The most well-known sung version is by Mikel Laboa[2].
On top of that, when catching up it's great to have an indication of _when_ to start watching a race. For that I've been using the info provided on the HowFarOut[1] Twitter account.
> a) Try to find ones with a pulsating mode, blinding other road users by shining bright rapidly blinking lights into their eyes is not good, actually.
The motivation to use a memory safe language as the alpha approaches sounds more of a longer term bet [3].
[1] https://ladybird.org/newsletter/2024-11-30/#swift-language-a...
[2] https://ladybird.org/posts/adopting-rust/
[3] https://ladybird.org/posts/changing-how-we-develop-ladybird/
> The assistant sends the full prompt (including your query, any relevant Memories, and any additional relevant browsing context) to a Mozilla server.
>
> Upon receipt, Mozilla forwards the request to a third-party large language model (LLM) on your behalf. The LLM receives the request from Mozilla, not directly from you, and sees a Mozilla IP address rather than your own. The request includes only the information needed to generate a response or perform the requested action.
> When you submit a query in the Smart Bar, the assistant uses a local (on-device) intent classification model to determine whether the query is best addressed by a chat or a search.
> In Bun 1.4, I rewrote Bun in Rust. [...] I did it in 11 days, using Claude Code, and wrote about how, in our blog.
Everything else in the video is phrased as "we", and even the section in the blog post is "We rewrote Bun in Rust"[1].
There's no question Jarred did the work and deserves enormous credit for it. I just found the contrast interesting, because the video explicitly frames the rewrite as "I", whereas the rest of the release frames it as "we".
- https://github.com/torvalds/linux/blob/master/Documentation/...
> I'm writing to you as the founder and strategic director of Infomaniak because something important has just happened, and it concerns you directly.
All in all the final message is great but the way it was communicated not so much.
defaults write -g NSWindowShouldDragOnGesture -bool true
Given the output speed, it's practically impossible for developers to keep up, which directly impacts maintenance: the knowledge that would previously reside in-house, now is becoming dependent on having codebases pre-processed by LLMs.
I hope in the near future local LLMs will gain traction and provide an alternative, otherwise we are in the risky path where businesses are over-reliant on a few big companies.
Creating these wrong things is only cheaper with LLMs. Since developers now spend less time and effort to create that wrong thing, they don't feel the need validate or reflect on them so much.
The risk is not the tool itself, but the over-reliance on it and forgoing feedback loops that have made teams stronger, e.g. debugging, testing, and reasoning why something works a particular way.
They started to copy the infrastructure, and the data is currently in Switzerland, Germany, and Norway. They can technically shut down the systems in Switzerland on short time. He (Andy Yen, CEO) always hoped they'd never need to take such steps, but the environment in Switzerland is too insecure for them at the moment. So they had no other choice but to plan their way out.
> Also I don't like that React requires installing Node and compilation tools, this is a waste of time when making a quick prototype. Vue can be used without Node.
> I don’t see enough value in the added complexity and the increasingly complicated API surface.
In terms of the complicated API surface and the difficulty to grasp newer concepts introduced with the app router, it continuously reminds me a couple lines of the Zen of Python[0]:
> If the implementation is hard to explain, it's a bad idea.
> If the implementation is easy to explain, it may be a good idea.
Well you don't have to, you can switch to the map screen before starting the descent. If you are willing to change screens while descending, the blame on safety is not on technology, but rather on your own decision to do so.
[0] https://en.wikipedia.org/wiki/Saint_Pierre_and_Miquelon [1] https://en.wikipedia.org/wiki/Ikurri%C3%B1a
In my experience, devs rarely pay attention to this, so commit messages end up as a big list of:
* Ticket-1234 feature
* fix
* cleanups
* fix
* another fix
* now the real fix
(edit: formatting)