Here in Belgium there's a village that's famous for doing this. Currently there's about 100 people there who are living with another family. https://nl.wikipedia.org/wiki/Gezinsverpleging_(Geel) If you translate you can read about it.
The content is nice and insightful! But God I wish people stopped using LLMs to 'improve' their prose... Ironically, some day we might employ LLMs to re-humanize texts that had been already massacred.
Thanks :), that was indeed my intention. I think the previous 3.14 mistake was actually a good one on hindsight, because if I didn't publicize our work early, I wouldn't have caught the attention of Nelson. Nelson also probably wouldn't have spent one month digging into the Clang 19 bug. This also meant the bug wouldn't have been caught in the betas, and might've been out with the actual release, which would have been way worse. So this was all a happy accident on hindsight that I'm grateful for as it means overall CPython still benefited!
Also this time, I'm pretty confident because there are two perf improvements here: the dispatch logic, and the inlining. MSVC can actually convert switch-case interpreters to threaded code automatically if some conditions are met [1]. However, it does not seem to do that for the current CPython interpreter. In this case, I suspect the CPython interpreter loop is just too complicated to meet those conditions. The key point also that we would be relying on MSVC again to do its magic, but this tail calling approach gives more control to the writers of the C code. The inlining is pretty much impossible to convince MSVC to do except with `__forceinline` or changing things to use macros [2]. However, we don't just mark every function as forceinline in CPython as it might negatively affect other compilers.
If you follow HN over the course of 24 hours, you’ll see at least 3 major waves. I tend to have an odd sleep schedule, so I’m always amused when I’m online to see which group is currently active.
There is an Asian/Australian wave, followed by Europe, and the North America. Some of the best times are when the waves start to mix (ex: early morning NYC time, you’ll get the Europe and NA groups interacting).
You’ll see different types of stories posted. Similar enough to where it all makes sense to be on HN, but it seems like a different flavor. But the comments are where I start to see more differences. You can get new takes on the same article if you see the comments from different times of the day.
This doesn’t take into account the total numbers of people active from each region, which I suspect is skewed towards more users the US coasts. But, it does, I think, speak to how US centric HN is. I think it serves the needs each of the waves in a distinct way.
In many ways, this is just an extension of the weekend HN effect. You can clearly observe differences on the site over the weekends. So, to me, it is unsurprising that you’d find differences across time zones. I’d love to actually see this analyzed more. This is just the take from someone who has been awake at enough hours to observe some anecdotal trends.
Each controller and subcomponent on the motherboard needs a driver that correctly puts it into low power and sleep states to get battery savings.
Most of those components are proprietary and don't use the standard drivers available in Linux kernel.
So someone needs to go and reverse engineer them, upstream the drivers and pray that Apple doesn't change them in next revision (which they did) or the whole process needs to start again.
In other words: get an actually Linux supported laptop for Linux.
They're now a defense contractor, the copy on their website sounds like military cosplaying.... Probably chasing the stupid profits of Anduril and Palantir, and doing the old open source rugpull in the process.
Zulip (for Slack) and Wekan (for Trello) are good replacements, save yourself the ethical and technical worries.
The original LinkedIn post is pretty wild. I wonder if he did a fat line of coke before writing that, or if it actually were any concrete plans that have been worked out.
All talks will be live streamed, and right after the talk is done you have a rough cut available instantly under "re-live" you can watch until the final recording is available; https://streaming.media.ccc.de/39c3/relive
I should note that some talks will not be recorded, and only available at the congress. These are clearly marked on the congress hub website, but not easily available on the fahrplan view.
From multiple personal experiences, including both of my parents, dementia is a slow, horrible death where you are robbed of your dignity and end up dragging all of your relatives through a very long, very torturous hell. You will be drooling, pissing, and shitting yourself, all while slowly reverting back to a low IQ childhood mentality where you're very likely to have outbursts and verbally or physically attack the people around you. Your loved ones will be tormented, and if you don't have loved ones then if you're lucky you'll be tossed into a room and forgotten about by underpaid, overworked staff at some run-down nursing home. If you're not lucky you'll be laying in a gutter on the street until you die.
> The problem was that go get needed to fetch each dependency’s source code just to read its go.mod file and resolve transitive dependencies.
This article is mixing two separate issues. One is using git as the master database storing the index of packages and their versions. The other is fetching the code of each package through git. They are orthogonal; you can have a package index using git but the packages being zip/tar/etc archives, you can have a package index not using git but each package is cloned from a git repository, you can have both the index and the packages being git repositories, you can have neither using git, you can even not have a package index at all (AFAIK that's the case for Go).
The internet was originally promised as a way to disintermediate these kinds of supply chains, yet we often ignore these "boring" businesses for hype trains. The fact that he added a phone number and it sometimes out-sells the website is the cherry on top.
Non-neurotypicals can receive bad treatment from neurotypicals. But, it's also a trap to start thinking that neurotypicals are 100% intolerant.
The corollary of not knowing when they're offending people, is that they also don't know when they're receiving tolerance - which is actually a lot; although it's understandable that this is not obvious.
I plan to upload the entire book as a single PDF when I finish the next chapter (on the cycloid). That will probably be early next week.
I used the original book by Arthur Engel for many years. He was an inspirational teacher.
The MAA tried very hard to publish the book, but I kept adding new material, and a text consisting of math 'selections' rather than a single theme is a hard sell in today's publishing environment.
It's an interesting debate. The flip side of this coin is getting hires who are more interested in the language or approach than the problem space and tend to either burn out, actively dislike the work at hand, or create problems that don't exist in order to use the language to solve them.
With that said, Rust was a good language for this in my experience. Like any "interesting" thing, there was a moderate bit of language-nerd side quest thrown in, but overall, a good selection metric. I do think it's one of the best Rewrite it in X languages available today due to the availability of good developers with Rewrite in Rust project experience.
The Haskell commentary is curious to me. I've used Haskell professionally but never tried to hire for it. With that said, the other FP-heavy languages that were popular ~2010-2015 were absolutely horrible for this in my experience. I generally subscribe to a vague notion that "skill in a more esoteric programming language will usually indicate a combination of ability to learn/plasticity and interest in the trade," however, using this concept, I had really bad experiences hiring both Scala and Clojure engineers; there was _way_ too much academic interest in language concepts and way too little practical interest in doing work. YMMV :)
FYI, this was sent as an experiment by a non-profit that assigns fairly open ended tasks to computer-using AI models every day:
https://theaidigest.org/village
The goal for this day was "Do random acts of kindness". Claude seems to have chosen Rob Pike and sent this email by itself. It's a little unclear to me how much the humans were in the loop.
Sharing (but absolutely not endorsing) this because there seems to be a lot of misunderstanding of what this is.
>Such should be done only with great care, as a false low reading can harm and even kill the patient (who eats a high-sugar-content item while glucose in the blood is, in fact, not low).
I've been a type I diabetics for over 25 years and I don't quite understand this one. Low blood sugar is an immediate life or death situation, but high blood sugar killing people? Just how high was it and for how long?
As someone that has a CGM I still calibrate it by using a blood test every couple of days because the CGM sensors can wander on accuracy.
> The way Faulkner treats his characters, I treat domain name projects. I buy them with an intention to develop. And I let them take the lead. They’re the inspiration for the business itself. They guide me towards what they need to become. I’m just the dude behind the keyboard (sorta).
I feel the same way about personal projects and blogs. A good idea tends to be self-reinforcing. It just needs someone to uncover it. Selling onions on the internet seems unusual but to the right person that idea is gold.
Quite to the contrary, I'd say this update is evidence of the inner loop being hyperoptimized!
MSVC's support for musttail is hot off the press:
> The [[msvc::musttail]] attribute, introduced in MSVC Build Tools version 14.50, is an experimental x64-only Microsoft-specific attribute that enforces tail-call optimization. [1]
MSVC Build Tools version 14.50 was released last month, and it only took a few weeks for the CPython crew to turn that around into a performance improvement.
For the usual doomsdaysayers saying "ruby can't X so I left it for Y", when X is typing, RBS is becoming the accepted standard (now that sorbet supports it),and RBS inline notation next to signature/code too (for peeps complaining about separate files); when X is LSP, ruby-lsp is the standard and already supports "go to definition" (its major hole for a long time), and its plugin architecture allows other other features to reuse the same code AST/index (So that each linter/formatter/type checker doesn't have to parse their own); when X is parallelism, ractors are have actually become performant in a lot of common cases, and it's only missing some GC improvements to be truly non-experimental.
There are new shiny things like ZJIT or Box, but even the core team recommends against using them in production for now. But they'll get better, as its been happening with the things listed above.
No wildly new syntax changes is also a good thing. Should help alternative implementations catch up.
Why not? People can't fake their way through a deeply technical, probing, 2-hour conversation.
You'd be amazed just how much you can learn about someone's actual skills and experience (or lack thereof) through long-form discussion. I think we don't truly talk enough in our currently broken interview process.
> The strain comes from context switching. From 9:00 AM to 5:00 PM, I had to care deeply about our quarterly goals and production stability. Then, from 6:00 PM to midnight, I had to care about inverting binary trees and system architecture design.
We really need to stop the tech interview nonsense.
Here is an experienced, practicing software engineer, who can't get a job without drilling for and performing frat hazing rituals.
