@coffeegeek
Medium format is pretty affordable if you shoot film
Posts
-
#NCP -
Is BlueSky similar to the Fediverse? No.@thisismissem @FediTips
And it's only "anyone" that has the technical knowledge and the free time to install, configure and maintain a cloud service.That is, almost nobody.
-
There has been a minor resurgence in "personal cassette tape players" (known more widely by Sony brand name 'walkmen') The most disturbing thing is how bare-bones these new products are... falling *far* short of the walkmen of yore.@Nfoonf @trurl @futurebird
This is why Pentax decided to create a new film camera recently. They realized they were on the verge of losing the institutional knowledge on how to make mechanical film cameras, so by making a new product they transfer the knowledge to new generations of engineers. -
A motivated group of Rust developers could build a production ready mostly Linux-compatible kernel from scratch within 5 years without doing any politics on LKML@drewdevault Good point. But those use cases also need a positive reason to pick it.
I work in HPC - a datacenter field - and just the thought of having to deal with kernel level compatibility problems for user code is enough to dismiss it out of hand.
For mobile, perhaps a more permissive license might do it. But then you end up with the drawbacks of permissive licenses too...
-
A motivated group of Rust developers could build a production ready mostly Linux-compatible kernel from scratch within 5 years without doing any politics on LKML@drewdevault
Who would use it? What would the selling point be for users? It being in rust is, by itself not one; nobody cares what language is being used. And while the number of bugs would drop, the kernel is already fairly stable for its users.They'd need to have some other, positive reason to go through the pain and uncertainty of switching.
-
Well, I vote for Han unification of #Unicode, and I rather think that more Chinese characters should have been unified (e.g., 高 & 髙, 產 & 産, 內 & 内).@hongminhee You can see it the other way: the reason Japan encoded these differences is because people felt strongly about them.
-
Well, I vote for Han unification of #Unicode, and I rather think that more Chinese characters should have been unified (e.g., 高 & 髙, 產 & 産, 內 & 内).@hongminhee I think that's really the point: to at least some users, those differences aren't small.
Here in Japan there's another, related issue where some family and place names were/are traditionally written with variant characters. That worked fine when everything was written by hand, but those variants got left out when defining print types and fonts, leaving a lot of people frustrated about it.
And yes, it is what it is. We're human; nothing ever ends up 100% clean and logical
-
Well, I vote for Han unification of #Unicode, and I rather think that more Chinese characters should have been unified (e.g., 高 & 髙, 產 & 産, 內 & 内).@hongminhee
We could have a debate about descriptivism versus prescriptivism and so on - can a language area be "wrong" about its own use of language - but setting that aside, that matter of fact is that people in practice disagree about the characters being interchangeable. And that makes them not unified.If I'm wrong, then I'm sure China will be perfectly fine with standardizing on the Japanese way of writing them for all international use. They're the same after all.
-
Well, I vote for Han unification of #Unicode, and I rather think that more Chinese characters should have been unified (e.g., 高 & 髙, 產 & 産, 內 & 内).@hongminhee
And yet, people have (sometimes strong) language-specific preferences for how the character should be written.And so you end up having to create and distribute separate fonts for the different CJK languages anyhow.
Not sure how that is an improvement over being able to define a single CJK font that encompasses the usage preferences of all its users.
-
Well, I vote for Han unification of #Unicode, and I rather think that more Chinese characters should have been unified (e.g., 高 & 髙, 產 & 産, 內 & 内).@hongminhee
I know. It's kind of partly their fault we're in this mess already. -
Well, I vote for Han unification of #Unicode, and I rather think that more Chinese characters should have been unified (e.g., 高 & 髙, 產 & 産, 內 & 内).@hongminhee
They don't need to be split up. You could have "高" and "髙" as adjacent codepoints in a single unified CJK plane.To take my example just now, ä and æ, ö and ø and so on are all in the same collection despite being the "same" characters, rendered differently in different languages.
-
Well, I vote for Han unification of #Unicode, and I rather think that more Chinese characters should have been unified (e.g., 高 & 髙, 產 & 産, 內 & 内).@hongminhee @riley
They're not interchangeable. They don't look the same and that is what's important to people.If you use "髙" in a Japanese text, people will think you're a Chinese speaker that doesn't know Japanese very well. It would lose you points in a school exam.
It'd be like telling Danes they now need to use the Swedish "ö" instead of the Danish "ø".
The point of Unicode was that you no longer had to switch fonts to render the same code point differently. Unification breaks that.
-
Do you ever use LLM tools like Claude or ChatGPT to help code up exploratory prototypes?@simon
I was trying to get help on Chapel, but that failed pretty badly.And if I try with Gdscript the models will tend to give me Python code instead. It looks quite similar, and with orders of magnitude more training examples that's perhaps not unexpected.
Oh, and I did try getting help on writing lock-free parallel code in Julia but that failure may honestly be a Julia problem more than the models'.
-
Do you ever use LLM tools like Claude or ChatGPT to help code up exploratory prototypes?@simon
In my brief exploration of it (and based on others experience) it seems to be a direct replacement of Stack Overflow.That is, if you use reasonably mainstream technology, and you want help in solving a common problem or implementing a standard solution, perhaps with a small twist, then it's helpful and generally correct.
But as you veer off the mainstream path, the suggestions rapidly become misleading and wrong, and it's faster figuring it out for yourself.
-
Wow, English-only people (or Western languages, for that matter) are so naïve. In case you didn't know, the lang attribute is very important in East Asian languages.@hongminhee @threkk
And as a non-native I sigh each time I see a japanese site with only first and family name, and nowhere to put my middle name... -
“chromebooks are the new thinkpad”? them’s fighting words@ariadne
Chromebook with a ThinkPad-quality keyboard? I'd get one. -
A Grinder PSA.I know James Hoffmann, in a few videos now, heavily suggests doing the RDT (ross droplet technique) on coffee in single dose grinders; indeed, in one video, he heavily suggests doing this 3x as much to get, as he says 'better anti static ...@coffeegeek @coffee @espresso
You'd think you know you have an antistatic device since your grounds aren't clingy in the first place.Doing RDT in winter with my grinder makes such a major difference it's not even funny (summer is really humid, and RDT isn't necessary).